<katco>hi, i think the common-lisp build system might be broken for "package-inferred-system" style common-lisp packages. the build system appears to find the dependencies, but then replace "invalid" (within the context of the store) characters with `-`. i think this breaks asdf as it then cannot find the package. "package-inferred-system" packages almost always contain a `/`  which is flagged as an invalid character. does anyone have
<sturm>On GuixSD, is it a problem that the "user-homes" and "term-auto" services don't start? I can't seem to find any info about these in the manual. The only output I can see is "Service term-auto could not be started." in /var/log/messages. Same for user-homes
<lfam>sturm: In practice it should not be a problem
<lfam>I see the same things on my system and it still works for me
<lfam>It would be good to figure out what's up and fix the services
<dannym>If you have a system with a head, term-auto will not start and that's by design. gnu/services/base.scm default-serial-port tries to determine the kernel console (by parsing /proc/cmdline at boot). However, guix services are declarative - so the decision whether to include an agetty (and thus call default-serial-port) has to be made earlier (on reconfigure). But it doesn't have information there, and the only thing to do is to always
<dannym>start the service and then fail if there's no serial console after all.
<dannym>If you have a headless system it will probably boot with a "console=ttyS0" argument and then the agetty will also start up and enable you to login.
<dannym>But the decision of whether to boot with serial console is done by u-boot and/or the user, so it's not really known in advance.
<q6AA4FD>this is only sort of guile unrelated, but there's a build check that sed appears to be failing of it's own accord, would it be bad practice to make a package to replace sed that skips that test?
<g_bor>civodul: I am finally making some progress... It seems that I could overcome the jmod files in the openjdk, there are still differences, but it looks much better.
<g_bor>The video documentation project is going fine, the framework is almost complete, we would like to onboard roptat if possible to have a look at the video translation workflow, mainly to check if we should mark the strings in the svg files not meant for translation as such.
<roptat>I do, but I need to check when 12:00 UTC is
<roptat>ah, I might not be available at 12:00, but I'll try to participate as soon as possible (12:15 maybe)
<Swedneck>i have added ~/.guix-profile/share to $XDG_DATA_DIRS to get menu entries from guix-installed packages, is there any way to make guix automatically modify .desktop files to append "(guix)" to the entry name?
<janneke>civodul, g_bor: no i don't really have a build log; the errors are usually symptoms not causes and very silly; an awk script that is invalid because sed or grep or gash made an error while producing it
<janneke>my strategy now is to first find the tool that is problematic, resurrect the build and then try to find the real cause
<janneke>i'm really tempted right now to first repackage gcc-4.7.4 into a gcc-4.7.4-core (upstream stopped doing that after 4.6)
<janneke>hmm, would gcc-4.6.4 be good enough to build gcc-4.9.4? i could try that!
<civodul>janneke: heh, so many possible paths! :-)
<roptat>arg, I've got a step while building sbt that requires network access
<roptat>the tool uses a tool that uses protoc (protobuf from google), but instead of the system-wide tool, it tries to download the latest version from maven
<roptat>I have no idea how to disable that behaviour...
<janneke>civodul: yes -- i'm using gcc-core-4.6.4 now (at least to bisect), that's a lot faster/friendlier
<ng0>doesn't guix have this in the manual these days?
<rekado>fellow humans! I’d like to push the GNOME 3.30 stuff to core-updates (because the glib update is required), but I can’t test it as core-updates seems to be in disarray. Python 2 doesn’t build, for example.
<rekado>is anyone feeling responsible for core-updates at this point?
<rekado>who would like to be the core-updates “meister” for this round?
<Swedneck>heads up: the ssl cert for the irc logs is expired since dec 30
<rekado>bavier: You added EXTRATESTOPTS=-j~d with parallel-job-count to Python 2 (on core-updates), but the check phase fails because it says that “-l” and “-j” cannot be used together.
<rekado>Swedneck: thanks. It probably isn’t actually expired; the server just hasn’t been reloaded.
<janneke>when my wip-bootstrap branch builds somewhere this weekend i intend to mail gash/bootstrap status to guix-devel; i think we may need to fully support guile 2.0 and want to plan for a real 0.1 release (update doc, compile warning cleanup, dead code removal, ...)
<samplet>Do you think we could pull out the utilities to a separate project before then?
<samplet>We could start with the wip-merge branch, so all the Autotools stuff is in place.
<ibanja_>Hi... I just discovered guix while searching for a way to distribute my admin scripts to some of my computers which run on two different distros--void and devuan. Would this be a good solution for what I am trying to do?
<samplet>Then, break of gash/commands.scm from the shell.
<samplet>janneke: Yeah. I would like to work towards a more Scheme-focused approach for the text commands, and I think that defining them in terms of SRFI 158 (generators) would be a nice way to do it.
*janneke has to look at generators; in python those are something like "broken coroutines" ;-)
<samplet>Right. They are not the greatest, but they work really well with ports.
<bgardner>Hey all; I finished a clean install EFI install and after rebooting got into a situation where "guix reconfigure" was hanging. I decided to wipe the root partition and reinstall, but now I can't get the installer to write the boot information. It does "copying to /mnt" for about 15 minutes and then gives: "Could not prepare Boot variable: No such file or directory", then "[...]/grub-install: error: efibootmgr failed to register the
<samplet>bgardner: Maybe your EFI partition is not mounted or is not mounted where your configuration file expects it.
<bgardner>samplet: I did check that, it is mounted at /boot/efi and is the correct type. I also rewrote the partition and reset the esp flag on it to be completely sure it was right.
<bgardner>I also added a stanza to the (file-systems ) block per the documentation to refer to the EFI by UUID. Didn't change the error.
<samplet>bgardner: I think the important part is the “target” field of your “bootloader-configuration”. It probably already points to “/boot/efi”, though.
<bgardner>It does, yes - and like I said this install worked once. I'm sure I've done this to myself in some fashion with leftovers from the prior install but I feel pretty confident I blanked both partitions. I'm puzzled.
<bgardner>samplet: I'm going to blank everything and try again, thanks for the response
<ArneBab>(I want libaom to get ffmpeg with AV1 support)
<ArneBab>(because I now have a fast Guix machine at home, so I want to experiment with AV1 encoding)
<ArneBab>(sidenote: did you know that most students nowadays don’t know plausible bitrates anymore? Only very few realized that 0.1kbit/s is much too low for music, though 15 years ago I’d have been very intrigued if someone told me that we could stream HD video at 200kbit/s)