bug#66610: potrace, po4a; guix bug, complete console output
Hi Olav, [...] Thanks for the initial bug report about a po4a non reproducible segfault (did I get this right?). Please refrain from posting unrelated things to this report, as that's lowering the signal to noise ratio and making it less likely that someone is interested in reading your future replies. -- Thanks, Maxim
bug#30948: [PATCH core-updates] guix: Reap finished child processes in build containers.
Hey Maxim, Maxim Cournoyer skribis: > I haven't yet looked at the code, but looking at the bigger picture, > wouldn't it be a useful behavior to have for Guile itself? Perhaps not, > as there already exists a Guile init manager (GNU Shepherd), but if it's > something relatively simple/compact to implement, perhaps it could find > its place in Guile itself, just like Bash implements correctly signal > handling when used as a PID 1 (if I'm not mistaken). Bash is a shell whereas Guile is a programming language, and to me that makes a big difference: we want to be able to implement init systems in Guile just like we implement them in C, and that means we need full control over what to do when running as PID 1. That’s why I wouldn’t do anything special in Guile itself (nor in libc). The patch I submitted fixes our immediate problem with build processes, so I’d like to have it in ‘core-updates’. Hopeful as I am, I see us merging ‘core-updates’ in the first half of January. Ambition! :-) Ludo’.
bug#58719: core-updates: Build failure for file on i686-linux
Hi Maxim, On Sunday, December 17th, 2023 at 2:15 PM, Maxim Cournoyer wrote: > > Hello, > > Kaelyn kaelyn.al...@protonmail.com writes: > > > As a bit of followup, this bug still exists with the latest > > core-updates commit. This not only affects i686 systems, but also some > > x86_64 packages like wine/wine64 which require a 32-bit build in > > addition to a 64-bit one. > > > Is this problem known upstream? If not, we should forward it to them. Thank you for the follow-up. I'm fairly certain this bug is outdated and can be closed now (it was from a previous iteration of core-updates). I don't remember what fixed it (possibly the update of file from 5.42 to 5.44), but the issue did get resolved by the time core-updates was merged and I haven't run into issues building wine since then. Cheers, Kaelyn > > -- > Thanks, > Maxim
