<rekado_>civodul: I can see no difference between the images on the online manual and the image files generated today on my laptop using gendocs.
<ng0>ACTION wonders wether they are creating the longest thread of this year with the pagure dependencies
<ng0>91 messages including the bug which counts into my message view on it
<ng0>anyone doing the curl update? otherwise I can do curl after I'm finished with gnurl
***Piece_Maker is now known as Acou_Bass
<civodul>rekado_: there was commit aaee461b9d5fb85fc1a548877dc7eea3dd4fbf50
<ng0>hm... grey area license question: I add a guix.scm to gnurl, as far as I understand it I must give it the same license as curl/gnurl and call it an "appendum to gnurl", right? I'm asking here as I guess more people with knowledge in licenses are around than in #gnunet :)
<civodul>davexunit, mark_weaver: is there a way we can forcefully disable user name spaces?
<ng0>anyway, I add an disclaimer that I'm not a fountain of wisdom when it comes to licenses and people shall contact me if it's wrong, i think i'm all good with that
<civodul>davexunit, mark_weaver: hydra-slave0 has /proc/self/ns/user but (clone (logior CLONE_NEWUSER CLONE_NEWNS SIGCHLD)) fails with EPERM, which was not the case before i think
<civodul>we can/should do a 'staging' branch during the coming weeks
<ng0>I.. I don#t know. I copy the quote for gnunet.org, but as you are not supposed to use gnurl on its own, I *think* it's safe to version bump, I do some more changes in the package definition for guix
<ng0>lfam: I've sent the patch to include gnurl update, it's up to guix wether this version should be included or left out. I think security bugs are always present, and their fix comes in a few days, so with not much information at hand I don't think it'll be high risk
<lfam>It's true, there are always more bugs to find. It's unusual for the curl maintainers to ask people to not update, however. I think the new bug must be very severe
<ng0>additionally I update the package definition, maybe it applies without the update