<rekado>re the locale incompatibility: would it at all be feasible to wrap applications in LOCPATH automatically?
<rekado>or doesn't this work because people might have different locales installed and LOCPATH must thus be pointed at some profile's directory?
<rekado>"It is a fundamental system misconfiguration issue not to have upgraded the binary locale data from one release [of glibc] to another." -- so, can we hard-code the path to locale data in our libc or wrap applications such that they will use the matching locale data?
<mark_weaver>civodul: any idea what's happening with build 689440 on hydra? it's been running for almost 24 hours, and the build log is completely empty. I've seen this many times, and in each case just killed the relevant process on hydra to free up the build slot, but this time I left it so you could take a look.
<mark_weaver>'patches' depends on 'python-notmuch' which depends on 'notmuch'
<mark_weaver>for some reason, which I don't know, the author of "guix refresh -l" thought it would be a good idea to only show you the set of packages that, if rebuilt, would rebuild all the other packages that depend on package P.
<mark_weaver>I guess maybe the idea was that those are the packages you need to rebuild to make sure that everything works, or something.
<toothbrush0>i remember last time i tried to do a similar thing a few months ago it bit me
<toothbrush0>although the details escape me in the mists of time.
<mark_weaver>I think it's generally agreed that we'd like an improved "guix refresh -l" command, but it's not entirely obvious what approach to take. I'd like a fully precise version that didn't miss anything, but it might be *very* slow.
<mark_weaver>and, I think it's good for the list at the top of the file to reflect the actual set of authors, and not just some subset, both to give the new author recognition, but also, in the case that bad code is added, to not have the existing authors' reputation harmed by the appearance that they wrote the bad code.
<mark_weaver>and finally, to me is seems to plainly be a matter of correctness to include the full set of copyright owners at the top of the file.
<civodul>it's about copyright holders, not authors, although in practice it's usually the same
<mark_weaver>and if you add a legally significant amount of code to a file, you *are* a copyright owner of the new file by default
<Mathnerd314>why did /nix/store get renamed to /gnu/store? it seems like a deliberate incompatibility
<mark_weaver>Mathnerd314: being incompatible was certainly not the intent of that change, but there's not much compatibility to be gained anyway. the actual packages in Guix are completely different from Nix, right down to the bootstrap packages.
<mark_weaver>if you want to run Nix and Guix on the same system, you can have /gnu and /nix on the same system