<shcv>I just installed (reinstalled) guix 0.16 on gentoo, made a directory for hacking in, and invoked 'guix environment guix', but it produces an error when building sed: inplace-selinux.sh: set-up failure: CONFIG_HEADER not defined
<bgardner>Good morning Guix; I'm trying to package up BOINC and have run into an issue I don't understand. The client package build correctlym but the server package fails in different ways each time I try. Sometimes it is 'file libboinc_la-<different each time>.lo does not exist' and sometimes it is 'file libboinc_la-<different each time>.lo is not a valid libtool object'. Any advice?
<civodul>bgardner: perhaps you need #:parallel-build? #f
<civodul>efraim: can you see if they have a localed fork?
<civodul>GDM does work without localed, but you lose some functionality
<efraim>civodul: looks like we need to compare %default-extra-linux-options in gnu/packages/linux and default-initrd-modules in gnu/system/linux-initrd
<efraim>I saw they have a gnome-first-start-wizard package
<apteryx>bgardner: looks like a parallel build issue, yes
<efraim>I found a locale based commit for firstname.lastname@example.org, so gnome2 days
<efraim>i'll see if they have any patches or something
<apteryx>civodul: will look into splitting my commits wrt pypi importer better, but it might take until the weekend. Thanks for the look!
<bgardner>civodul, apteryx: Thanks for the tip, I'll pursue that, thanks!
<apteryx>With a guix archive --export /gnu/store/xxx-some/profile and the Guix manifest that was used to generate that profile, I can recreate that exact profile on another Guix-enabled machine, right?
<apteryx>I would do: guix archive --import my-archive.nar, then guix package -m my-manifest.scm -p some/profile/path, correct?
<apteryx>is it possible to forego the override the key verification? In private context, it seems it adds some hassle for not much gain.
<roptat>apteryx, you would need the same guix pull commit too
<Blackbeard[m]>After installing fonts you may have to refresh the font cache to use them in applications. The same applies when applications installed via Guix do not seem to find fonts. To force rebuilding of the font cache run fc-cache -f. The fc-cache command is provided by thefontconfig package.
<bandali>on my new trisquel install i don't have anything in ~/.fonts as of yet, but i'd expect icecat to pick up system fonts, which it doesn't seem to do
<bandali>Blackbeard[m]: it *is* strange.. it's an old mate version (1.12.2 i think)
<apteryx>rekado: would you know if we still have cases of Python byte compiled files non-reproducibility? I think I've just found one in a new package I've prepared. Just checking if there's any known issue.
<bandali>anyone know how i can have guix subcommands always use berlin.guixsd.org instead of ci.guix.info, without having to build guix itself?
<bavier>bandali: you can start the guix-daemon with the --substitute-urls option
<roptat>bandali, if you're on a foreign distro, have a look in /etc/systemd/system/guix-daemon.service (if your distro uses systemd)
<ngz>Hello. I have a question about sdl-union. In the Makefile of a package draft of mine, there is, e.g. "$(shell sdl-config --libs)", and the same with "--cflags". The package requires "sdl-image" and "sdl-mixer". So, I add "(sdl-union (list sdl sdl-image sdl-mixer))" as an input. However, it doesn't work as expected: the directory in "-I/path/...-sdl/include/SDL" is not the union, but the sdl alone. So the build phase error out wi
<ngz>e.g., "cannot find SDL-image.h". I thought it was a problem due to the wrong "sdl-config" being picked up, so I substituted the full path of the sdl-union in the Makefile, but it still uses "-I/...single-sdl/include/SDL".
<apteryx>rekado: we have deterministic pycs yes, but it's still fragile, as the mtime is recorded as a timestamp it the .pyc file. With PEP-0552, we can have the pyc record a hash of the file content instead of a timestamp. When is this going to be useful? Supposed that source files get generated/manipulated at build time, this would introduce non-determinism. Not with PEP-0552.
<rekado>where do you see the timestamp? I think we are in fact recording the hash, no?
<apteryx>rekado: I understand now: it must use hashes, and what I'm seeing is something else... Because the documentation of py_compile.compile (which distutils ends up calling) says: Changed in version 3.7: The invalidation_mode parameter was added as specified in PEP 552. If the SOURCE_DATE_EPOCH environment variable is set, invalidation_mode will be forced to PycInvalidationMode.CHECKED_HASH, and we *do* set