<ixxie>
still needs some cleanup but I can now drop the original one
<makefu>
funny enough the i3 tutorial change got reverted
<makefu>
:D
<makefu>
90b2dcdd2ae30f34e8354d78eda4090bc6a6b188
<makefu>
'i3 doesn't want cairo at all.'
<nixoswikibot>
[[Special:Log/delete]] delete * Ixxie * deleted "[[Pull request]]": This article was merged into the 'Get Involved' article.
<ixxie>
lol
<ixxie>
makefu: another option is to maybe ask samueldr to make templates for headers for Tutorials, Manuals and Cookbooks so that its super clear when you land on a page WHAT it is
<nixoswikibot>
[[Special:Log/move]] move * Makefu * moved [[Contributing to nixpkgs]] to [[Updating software in nixpkgs]]: clear description
<ixxie>
makefu: can we make it 'Upgrading Packages in Nixpkgs'?
<ixxie>
or maybe updating
<ixxie>
but packages for sure
<ixxie>
because its the package being update (the nix expression)
<ixxie>
also Nixpkgs (capitalization should be consistent in the Wiki)
<ixxie>
makefu: what is actually the difference between an update and upgrade
<makefu>
i wanted to add In order to complete this tutorial be sure to run <syntaxhighlight lang="bash" inline>git reset --hard 111c8db50038</syntaxhighlight> in the folder. as a notice but it seems that <syntaxHighlight is not supported in a note field
<makefu>
maybe you can add this somewhere
<ixxie>
makefu: realistically someone following this tutorial would be updating an actual package needing an update
<ixxie>
makefu: hmm yes.... but I guess I think this one *should* be turned into a manual? xD I don't know
<ixxie>
its also a bit borderline
<makefu>
i think we are fine now
<makefu>
:)
<makefu>
just a notice at the top "if you want to run this article as an tutorial, be sure to reset"
<ixxie>
makefu: I put it in introduction as "If you want reproduce the environment used in this tutorial exactly, you can git reset --hard 111c8db50038 in your local copy of Nixpkgs."
<makefu>
but yes an infographic may clear a lot things up
<makefu>
relations between things
<makefu>
the infographic of sander is only for deployment
<ixxie>
makefu: hmmmm maybe it should show a cluster of machines - some NixOS, some Linux, some Darwin - using Nix, connecting to Nixpkgs / Hydra / etc - and using NixOps for deployment
zarel has quit [(Quit: Leaving)]
<ixxie>
that would be hard to fit all together
<makefu>
unfortunately i haven't used disnix or nixops. but a generic overview for all things nix would be fantastic
<ixxie>
I haven't either
<ixxie>
nor have I really touched Hydra xD
<ixxie>
maybe two diagrams...
<makefu>
i don't know many people who actually managed to set up hydra ...
<ixxie>
makefu: I wanna do it this winter at some point
<makefu>
for krebs we have buildbot with templated python code
<makefu>
because hydra was too much of a hassle
<ixxie>
so its not very polished yet eh?
<ixxie>
well that means more of us should use it then no xD
<makefu>
fadenb: sure, go ahead. just make sure there are working backups :D
<samueldr>
it might be too late
<makefu>
di di diiii
<fadenb>
just executed systemctl start mysql-backup.service as well as systemctl restart borgbackup-nixos.wiki.service ;)
<samueldr>
:)
<samueldr>
is the new login thing up?
<fadenb>
was up and is gone :P should have read more carefully as it only supports auth delegation to another wiki
<fadenb>
The issue with the current github auth is that we do not get an email address for the user
<fadenb>
Without an email a user can not (re)set the password and therefore not use the normal login which would allow a user to set the "keep me logged in" flag
<samueldr>
right, that's the one I linked to from mediawiki's extensions wiki
<fadenb>
samueldr: ah that is interesting, I always assumed email was no longer available due to an github api change (which broke the whole extension)
<samueldr>
looks lieke a configuration scope might be needed
<samueldr>
never worked with mediawiki nor this extensions, but worked with oauth and integrations
<fadenb>
should look into that sometime. That might be a github bug
<samueldr>
isn't filled in my profile, but it might be because the profile already existed
<fadenb>
And seems like I found a fix for the redirect to the mainpaige. Can you verify that it is now redirecting to the page one came from after logging in via github?
<fadenb>
samueldr: do you by any chance know the correct value for "api_endpoint" when using Github oauth? I am using https://api.github.com/user which never returns email as it only show public info