<vagrantc>mbakke: apparently libgit2 is 1.0.x in experimental...
<nckx>fnstudio: guix.tobias.gr has diffoscope if the diffing's urgent (...probably not), unfortunately no icedove yet.
<fnstudio>nckx: amazing, thanks! (and i'm very happy i understood the underlying logic)
<technomancy>when I boot a guix USB drive on my old thinkpads, I just get a black screen with the word "GRUB" in the top-right corner. pressing keys makes it just beep. it's very difficult to search for this problem; can anyone recommend search terms that would be illuminating? "grub stuck boot" gives no relevant results.
<nckx>fnstudio: It's also building IceDove at the moment so it *might* beat berlin.
<vagrantc>to test the issue with "guix pull" not finding origin/keyring, maybe i need to rebuild guile-git with libgit2-dev 1.0.x and then rebuild guix with that to see if that fixes the issue...
***catonano_ is now known as catonano
***amiloradovsky1 is now known as amiloradovsky
***amiloradovsky1 is now known as amiloradovsky
<vagrantc>mbakke: you were spot on with your guess about libgit2! upgrading libgit2-dev and using libgit2-1.0 fixes it without even rebuilding guile-git or guix
<vagrantc>so with that in mind, guix pull works correctly
<nefix>hello! I'm getting the following error when I run docker build: `cgroups: cannot find cgroup mount destination: unknown`. Does anybody know what does this mean?
<sss2>hi all, how to properly setup offload facility on foreign host os with guix installed ?
<jid>Hi. With stable graphical installer the guided partition step fails and goes back to the locale selection screen. At this point in /var/log/messages it says: 'nvme nvme0: ctrl returned bogus length: 16 for NVME_NIDT_EUI64'. Is there a workaround for this?
<zceejkr>Hello everyone. I am trying to install the Guix System on my laptop using the graphical installer, and when I get to the partitioning part, the installer restarts back to the beginning. Is this a known issue? What can I do to fix it? Cheers.
<zceejkr>I found this same issue via googling on the guix mailing list, and the person said they resolved it like so (quoting): "I noticed that the installer detected my EFI partition as FAT16. After changing it to FAT32, the installer continued.". But I do not know how to check this, or change it.
<mbakke>zceejkr: there will be a beta release of guix 1.2 in a few hours, if you're not in a hurry it would be great if you could try that :-)
<zceejkr>mbakke: great to hear. Will wait, thanks for the heads up.
<zceejkr>Still making my way trough the manual anyways :)
<apteryx>civodul: When fixing broken things I think we should put them on the version-1.2.0; we can merge version-1.2.0 periodically back into master. This will make things easier to track and prevent forgetting cherry-picking fixes to version-1.2.0. WDYT?
<civodul>apteryx: sure; i have a local tag for RC so just don't push right now please
<civodul>but yeah, that sounds like a good strategy
<civodul>as long as it's mostly about leaf packages though
<civodul>otherwise we could end up having to wait for CI to catch up again
<apteryx>civodul: hmm I just pushed 4e01bc440a which fixed the build for python-pysam on version-1.2.0, before I could see your message about a local tag. Well, the RC won't include that one. No big deal.
<jsoo>sneek: later tell rekado_: I want to fix the package db (ghc can't find packages when used after installing libraries anymore). Do you know where I should start? How did cabal register change in haskell-build-system?
<db48x>whatever simple way that you want to build the file is likely fine
<zceejkr>mbakke: tried installing the 1.2rc. I still get an error on the same spot, but this time I see an error message instead of the installer restarting. So when I tried to partition the disk, I get an error that says: "Unhandeled ext2 fs-type". Can anyone recommend some next steps I could take to get around this? Cheers
<zceejkr>The error message is actually quite long, and I can try to take a picture if needed, but I guess what I wrote above is the gist of it.
<nckx>vagrantc: Fair'nough; my suggestion might've been based on a somewhat stereotypical view of stateful package managers ☺
<vagrantc>but maybe just running it if not present will be good enough
<vagrantc>oh, i have to handle a sysadmin removing the file and not re-add it ... bah.
<apteryx>question: should the ctypes.find_library of Python in Guix be patched to look into LIBRARY_PATH? Currently it only looks in LD_LIBRARY_PATH
<vagrantc>i think i'll just create the file during package build, and then it can be managed by conffile handling.
<sneek>__red__, jsoo says: I want to fix the package db (ghc can't find packages when used after installing libraries anymore). Do you know where I should start? How did cabal register change in haskell-build-system?
<__red__>I am entirely the wrong person to ask sneek / jsoo
<nckx>rndd: How did you install GCC? If I echo that C into test2.c and run ‘guix environment --pure --ad-hoc gcc-toolchain -- gcc test2.c && ./a.out’, it just works. That is equivalent to running ‘guix install gcc-toolchain’.
<rndd>nckx: i installed gcc with ‘guix install gcc-toolchain’.
<nckx>Is this on a Guix System? Does the above pure environment work for you?
<nckx>It works outside of that environment with a previously guix-installed gcc-toolchain, but I'm on Guix System. If you're not, perhaps Guix's gcc is trying to link against non-Guix libraries and that may well cause fiery death.
<pkill9>i wonder if the parts of gtk+ and hwatever that are used to generate guix profiles could be split out into their own package
<pkill9>so it wouldn't take much time to build/download
<nckx>rndd: \o/ Now I'm certain that your previous ‘guix install gcc-toolchain’ was in the same terminal, and that it printed the 2 GUIX_PROFILE lines above 😉
<nckx>That's not to berate you (I ‘forget’ to read warnings all the time) but to point out that this one can be important.
<nckx>Well, ‘same terminal’ isn't quite right. If you'd opened a new terminal and run ‘gcc’ it would have worked.
<rndd>nckx: well, i definately should read warnings next time
<nckx>What happens is ‘guix install gcc-toolchain’ updates your bash profile to set some important variables for GCC, but Guix can't change the environment of processes that have already been started. It can only ask you to copy & paste a command.