<noobly>guix system error: some substittues... ...; try --fallback to build derivation from source
<noobly>like this "guix --fallback system init /mnt/etc/config.scm /mnt ?
<noobly>i only ask this dumb question because last time I had guix running I made some mistake involving fallback
<noobly>and what does it imply that there is now an `efi.img` in '/'?
***jonsger1 is now known as jonsger
<guix-vits>noobly: did you use btrfs with zstd compression on any of your file systems?
<noobly>so upon running 'guix system --fallback init /mnt/etc/config.scm /mnt' I get a weird error: no space left, while 'df -h' returns /dev/sda3 (root) with merely 2% used, and some weird 'none' filesystems of ~992M size, one of which that is 100% used. Does this sound familiar to anyone?
<noobly>i probably should've just started from a clean slate this morning rather than trying to save my botched install
<guix-vits>noobly: hint: you can access the "Installation Instructions" at tty2.
<noobly>guix-vits: yeah, that's what I've been using
<nckx>You're not in a great situation: Guix has (not unreasonably) started to download and build your system in /gnu, however in the installer, /gnu is entirely in your RAM. The only way to free it would be to run ‘guix gc’ now, but it's probably better to start from scratch. You'd be re-downloading everything in both cases. Just save your connfiguration and restart the installer IMO.
<nckx>Fiddling and copying things is just more error-prone risk at this point.
<noobly>ok, i've 'cp /mnt/etc/config.scm /', that should be saved onto the bootable media persistently right? and when I start my new fresh install, I shouldn't have to repartition, right?
<noobly>ok, awesome. then proceed as normal with herd start?
<guix-vits>noobly: i'm dare to recommend to you to use Arch Linux for a month, or so. They have all maded in easy way, with greatest Wiki ever. And their configs are not require you to know Lisp (and it is allowed to directly edit them). Also they have a "Post installation advices" (Firewall, Power-save, Service (systemd) management, etc...). You will return there then, if want. Just in Guix you even have a 'performance' set as a default
<guix-vits>nckx: Arch is about the just a few things to do yourself, from a list of things that maintainers did already (this or that good) elsewhere. But it helps (a lot) one to notice the existence of those things.
<nckx>Guix (and Nix) is probably the most transactional package manager on earth.
<nckx>There are edge cases like ‘power failure halfway writing your literal boot loader’ but y'know what I mean.
<sturm>nckx: I've installed mupdf and tried `emacs -q` again but no luck. On the right track by the looks of things - the messages buffer shows "No PNG support is available, or some conversion utility for pdf files is missing."
<ArneBab>guix-vits: the hack was `for i in $(pgrep .); do sudo prlimit --pid $i --nofile=1000000:1000000; done`
<ArneBab>Because our sourcetree at work is large enough that the normal open files limit does not allow building with maven.
<Gooberpatrol66>when I try to mount an NFS share, it says "bad option; for several filesystems (e.g. nfs, cifs) you might need a /sbin/mount.<type> helper program." But I already have nfs-utils installed. What gives?
<ArneBab>guix-vits: I guess I should blog the hacks I use …
<guix-vits>Gooberpatrol66: try to logoff then login in graphical session (or even reboot). I'd similar issues with GCC recently. str1ngs said that there is some variables that need to be re-set, or such. Which program do you use to mount the share?
<kahiru>nckx: still about zfs. I have no modules directory in /run/booted-system/profile/lib
<efraim>civodul: can I get your help (later) on reviewing the cargo recursive import patches? The limited testing I've done shows it works as expected on crates. I assume we want guile-semver to be an optional dependency for a bit.
<guix-vits>kahiru: cd /gnu/store/*linux-libre-`uname -r|cut -f1 -d'-'` modules should be there, i THINK (not know).
<kahiru>guix-vits: no luck. the module is provided by the zfs package, so I guess it will live somewhere else
<allana>Hi, I reconfigure my guixsd system every few days. That has worked well for me until today. An hour or so ago I reconfigured my system and upon the next boot, the boot process did not get past dns-resolving 0.guix.pool.ntp.org and I was not presented with my normal GDM-login prompt. Reverting back to a previous generation worked as expected. I'm here now to report this issue and maybe provide details if there is anyone who can direct
<nckx>jetomit: I wish all bugs were this easy to fix; they'd all be fixed that quickly 😉
<allana>so, to continue, I have reconfigured my system today. No changes to my system configuration, and shortly after a successful guix system reconfigure my new system never finishes booting up and presenting GDM. The boot process seems to try to resolve 0.guix.pool.ntp.org and fail repeatedly. Booting a previous generation will "boot normally", meaning that it is able to reach a GDM login prompt.
<guix-vits>nckx: i'm remember an cartoon: character are constructs an airplane, and says upon completion (gesturing a to big pile of gears): "I'm wonder, why do they sold to me so many unneccesary parts?". It was wonderful :)
<nckx>guix-vits: That's an option, if they think GDM is to blame. They don't seem to think so, and NTP is probably also a red herring. Still too many unknowns to help IMO.
<kahiru>efraim: I know that, but there is several of those, only with different hashes. some of them give "unknown symbol" errors when I try to load them. I'm looking for a reliable way of getting the one I can load
<kahiru>or ideally having it loaded at boot time and not having to worry about it
*guix-vits just had forget that they should be in sync.
<allana>nckx: A little above the previous message, "Screen 0 deleted because of no matching config section." And then further up, "No Layout section. Using the first Screen section." followed by "No screen section available. Using defaults." and "No monitor specified for screen 'Default Screen Section'"
<guix-vits>nckx: if some version will be listed for some pull in `guix search linux-libre`, it isn't an inferior? like 5.4.12 or such...
<nckx>guix-vits: I'm not sure what you mean. ‘Inferior’ is a declared older version of Guix from which you pull one or more packages into your (newer) Guix. It's not a value judgment, or something that packages are or aren't 🙂 See (guix)Inferiors, which needs love but should be readable.
<allana>nckx and guix-vits: Any idea what (kernel …) should look like? The manual doesn't offer any examples other than (kernel linux-libre) and I am not much of a schemer (yet).
<allana>something like (kernel linux-libre@57bd483f6730ce0daa9479d9b7be3b8b4a152097) ?
<guix-vits>allana: try like in (packages it is done: linux-libre-5.4.18
<nckx>guix-vits: Indeed. 4.19 (and 4.14) are long-term supported kernels that are still shipped in Guix today. However, you can't specify e.g. linux-libre-4.15. With inferiors, as long as there was ever a Guix commit with linux-libre 4.15, you can.
<nckx>We're missing an interface to ask ‘which commit was that, Guix?’ but thanks to our disciplined commit messages using ‘git log | less’ and ‘/’ is quite nice.
<nckx>guix-vits: allana needed 5.4.18, which is ‘gone’ from guix, so they need to ‘ressurect’ it from commit 57bd483f6730ce0daa9479d9b7be3b8b4a152097. That's what that code snippet does.
<nckx>‘Pretend it's 2 weeks ago, now give me linux-libre.’
<efraim>nckx: not a terrible assumption, but I just packaged zfs for the challenge
<nckx>kahiru: Not ‘no way’, just ‘hacky’. Unless you're using a custom (kernel …), insmodding the result of ‘guix build zfs’'s -module output in some right order (because, indeed, insmod doesn't do dependencies) will work just fine.
<apteryx>nckx: yeah, this fails because I need to reference the correct GRUB config somehow: /gnu/store/3433z5hdwsxks216d4xmv1nm44ycy1jc-grub-efi-2.04/sbin/grub-install: error: attempt to install to encrypted disk without cryptodisk enabled. Set `GRUB_ENABLE_CRYPTODISK=y' in file `/gnu/store/3433z5hdwsxks216d4xmv1nm44ycy1jc-grub-efi-2.04/etc/default/grub'.
<civodul>"Could not delete variable: Invalid argument"
<civodul>"efibootmgr failed to register the boot entry: Block device required"
<nckx>apteryx: You haven't changed your configuration at all?
<nckx>Are your boot-directory and efi-directory mounted?
<apteryx>nckx: only thing I've changed is going back from GDM to slim, but that shouldn't be relevant
<nckx>EFI grub-install doesn't take an explicit block device at all.
<apteryx>civodul: yes, this was from 'guix system reconfigure'
<apteryx>nckx: a reboot, and reconfigure now worked! A 2nd reboot, later, I'm back at home with Slim.
<apteryx>I wonder what other distros do to work around this pesky firmware bug, if they do anything. I wouldn't expect Ubuntu to suffer from this kind of problem.
<nckx>efraim, civodul: Kernel modules from outputs other than :out are not unioned into -system/profile/lib/modules. They're just missing. Merging zfs:module into zfs:out made the module magically appear.
<apteryx>thanks for pointing to the firmware, I would have pulled me some hair before thinking about that.
<guix-vits>i'd seen in the Fedora Linux: "BLS", entries in /boot/loader/entries. GRUB used to not be reconfigured at all, just updates placed and deleted the files in /boot/loader/entries/. And GRUB used some module to lookup these configs at boot time.
<nckx>I'm not going to spend time fixing this right now but it's worth noting we currently ship a near-useless ZFS kernel module.
<nckx>Oh god, the ol' systemd BootLoaderSpec. Is that still a thang.
<nckx>Probably is since they've subsumed booting too.
*sirgazil abandoned Alt+F2 because it is so slow (in the Guix System?) that it is faster to go and click on the app icon.
<sirgazil>The copy-build-system seems like something I'd like to use in the future for my own data packages.
<wingo>i wonder if removing xdg-user-dirs is also a problem...
<joshuaBPMan>Hey guix! I seriously love ya'll. You've made it sooo easy to set up a locally running nginx server. I am thinking about building a small guile web app, and your nginx syntax is sooo slick!
<wingo>regarding xdg-user-dirs, original motivation in c20cd0d24d9b5e8a47b864db9799e0992ffd44b9
<nckx>wingo: Proof that it should have been a comment ( :o) )
<nckx>I thought there was a meta-bug open about the GNOME situation but can't find any.
<civodul>AIUI, it's like a CLI to manifest-like dependency files
<NieDzejkob>Sometimes I need to restart dhclient to regain internet connectivity. When I do that, ping and curl work, but IceCat needs a restart to see the Internet connection again. Any idea what on earth might be happening here?
<nckx>raghav-gururajan: Whoa there, that's drastic, let's put that on hold. The first two only add packages (did they break anything? what?), the third has no effect on packages if your commit message is accurate. The fourth is the only one that removes packages, and even that might be better tweaked (this time: with comments noting what each non-core package brings to the GNOME table) than flat-out reverted. What do you think?
<nckx>I have to leave now but shall return, wet and mildly confused as ever.
<raghav-gururajan>nckx That reverse shouldn't break anything. In fact, it take GNOME back to the time where my screw ups has not started. :P
<nckx>I've sent the same message to bug-guix for Danny, but no reason to reply again of course It's not (just) about not breaking things, it's unnecessary. Talk more later 🙂
<raghav-gururajan>nckx Since we got lot of feedbacks regarding GNOME, I am gonna re-contemplate what can be done to gnome meta-package.
<nojr>https://guix.gnu.org/videos/ , my bad, also I'm referring to Part One, I'm confused because we need to start the shell with ./bootstrap, but is this a one time thing? also, the video says that `make` makes the ./pre-inst-env commands available
<HappyEnt>Hello, I recently updated my system and now gdm only starts when i add the intel gpu kernel modules to my initrd. Anybody else experiencing this problem?
<dftxbs3e>hey jonsger, still trying to remove that reference of bash inside gawk, somewhat skipped onto other things such as actually putting everything I had into the code, which is done now
<dftxbs3e>I just have to upload new bootstrap binaries and re-test now to see where we're at
<dftxbs3e>The static bash path embedded inside gawk is really weird
<dftxbs3e>everything patched in glibc, same story for gawk..
<janneke>civodul: i added a patch that makes wip-bootstrap build again for me; pushed to savannah. it removes bzip2 from `file' in commencement altogether; this was introduced in file-5.38 and fails because of libbz2.so built with earlier bootstrap gcc's
<janneke>civodul: i'll do a rebase on latest core-updates and also test that
<bandali>KE0VVT, ci is ci.guix.gnu.org, the official substitute server
<dftxbs3e>civodul, about the gawk bash-static store reference problem. Here's what I could figure out: gawk has a 'set-shell-filename phase that replaces /bin/sh with bash pkg then inputs replacement in make-bootstrap changes bash pkg to bash-static pkg -- so initially I tried to replace using (substitute* ..) inside make-bootstrap but because of the set-shell-filename step, it actually didnt happen because it was already replaced with bash pkg. So I ended
<dftxbs3e>up removing the set-shell-filename and then using substitute. I found a few places where /bin/sh (or any pkg it gets replaced by) could be spawned directly so I patched that as well with "sh" for PATH lookup. But I'm still getting bash-static in the final gawk static binary, so that makes me puzzled.
<necrophcodr[m]>I've been trying to make a package for some software that uses go, but I keep hitting an error: failed to initialize build cache at /homeless-shelter/.cache/go-build: mkdir /homeless-shelter: permission denied
<dftxbs3e>civodul, I just hope to finish this. I' tired right now, will run this test and send a concise email tomorrow.. I'll try
<dftxbs3e>I just tend to think it's not very useful since I'm kind of alone deep in this mess
<necrophcodr[m]>nckx: so the correct way to build packages that depend on go is to run `HOME=/tmp guix build ...` ?
<civodul>dftxbs3e: i know that feeling, but you're not alone!
<nckx>necrophcodr[m]: No, call setenv in a phase when writing the package.
<jackhill>HappyEnt: I'm not experiencing that, but I'm not quite sure what to suggest. Maybe you can post some more information about your system (guix describe output and more information about your intel gpu)
<nckx>Builds are self-contained, external environment variables have no effect anyway.
<civodul>dftxbs3e: often just sharing the current status and letting it rest for a day or two can help IME
<necrophcodr[m]>Alright, I'll look into making my own phases for the gnu build system. I'm not entirely certain how all of the pieces fit together, but there's always diving through the source code for hours lol
<dftxbs3e>civodul, noted, I've been having some difficulty contributing to GNU Guix as much as I love it, because it doesnt work on my machine, and my lack of knowledge of Scheme is damaging. I need to read a book about it. - I'll post useful news tomorrow on the list I promise.
<nckx>necrophcodr[m]: You need to add the phase to your package, not the build system: (arguments `(#:phases (modify-phases %standard-phases (add-before 'build 'set-HOME (lambda _ (setenv "HOME" "/tmp") #t)))))
<civodul>dftxbs3e: noted; take your time, no worries
<dftxbs3e>civodul, I feel like I've tried *lots* of things without progressing very much. Probably compiled things 100 times by now heh
<necrophcodr[m]><nckx "necrophcodr: You need to add the"> Ahh thanks. I'm not entirely sure how what you wrote works, so I'll look at it closer and how phases work, so I won't have to come back here asking these questions again.
<nckx>‘build’ is a guess by the way, it depends which phase is failing (this will be printed in the ‘guix build’ log output).
<HappyEnt>jackhill: i am currently building an older kernel, there seem to be quite a few people over on arch experiencing similar problems with the newer kernels. I will report back wether that works, otherwise I will try the mailing list and add more information about my system.
<dftxbs3e>At least I'll have deep understanding of the bootstrap process then :P
<civodul>dftxbs3e: yup, i understand & sympathize; tell janneke about building things 100 times :-)
<necrophcodr[m]><nckx "‘build’ is a guess by the way, i"> It is indeed the build phase, and this brings me a LOT closer now. Thanks for the help, I think I can figure out the rest of the problems that are cropping up now :D
<dftxbs3e>civodul, Thanks for cheering me up on that contribution, I hope to get it finished **very** soon! Grr!
<jackhill>necrophcodr[m]: you may also want to use the go-build-system, or if that's not appropriate, at least borrow some ideas from it.
<janneke>dftxbs3e: do feel free to talk about it here, that helps me a lot when i get frustrated :)
<jackhill>necrophcodr[m]: what software are you packaging by the way?
<necrophcodr[m]><jackhill "necrophcodr: you may also want t"> Absolutely considering it too.
<necrophcodr[m]><jackhill "necrophcodr: what software are y"> A couple of things. Consul by Hashicorp, and Gobetween, a TCP/HTTP proxy. Both are written in Go. And even if they end up being packaged before I'm done that's okay too, this is mostly a learning experience :D
<nckx>Wait, you're not using the Go build system for a Go package? That's definitely… recommended.
<necrophcodr[m]>The different importers in Guix are crazy. I'm used to writing packages like ebuilds, but Guix and especially the importers take it a couple of levels up for sure!
<necrophcodr[m]><nckx "Wait, you're not using the Go bu"> I've considered trying to get it working with that as well, but the gnu build system has gotten me the furthest with the least trouble so far. Some "Go packages" aren't strictly... Go packages either. Some require the use of the gnu make (and other) tools to even build, and cannot be built using `go get`.
<necrophcodr[m]>If all software was packaged neatly and organized in a single predictable manner, we might not even need `make` at all. Although that's quite a reach. Make is fantastic in it's own right.
<civodul>hmm the installer no longer works at all on master: blank screen