<bjc>although, thinking about it: one of the things the grub.cfg does is specify which generation you're on (from the gnu.store cmdline option to the kernel). so you should /already/ be rolled back at boot time
<bjc>iirc all the currently supported ones that can be checked are being checked
<bjc>looks like the only one that isn't is nfs, for the obvious reason. maybe some of the check-*-file-system procedures are stubs, though
<nckx>Not unconditionally, and not—well, I rewrote most of the fsck calling code, it's… complicated. Messy. Yech. I'd always recommend booting with fsck.mode=force after fs weirdness, but it's just me.
<ss2>somehow the most current generation is quite broken: https://paste.rs/5dD guix system list-generations throughs an error there.
<horizoninnovatio>Good morning! I'm trying to set up evolution with gmail accounts. I've install evolution-data-server and glib-networking & rebooted. The error I'm getting is "TLS support not available". How do I fix this? or is there a better email client that works well with gmail?
<ulfvonbelow>I had to 'kill -9' my X server, but now when I try running 'sudo herd start xorg-server' it outputs to /var/log/Xorg.0.log '(EE) Cannot establish any listening sockets - Make sure an X server isn't already running(EE)'
<ss2>Gonna do it tomorrow instead. Getting much later than expected. :)
<bjc>at the very least, your trials today have convinced me that zfs-on-root is still a good goal to work towards. being able to simply roll the whole filesystem back to a previous snapshot would have solved all of your problems almost instantly
<ss2>maybe. I'm also suspecting that this mainboard is going a bit crazy unfortunately. It has shown some odd freezes, and now this.
<bjc>it does seem like something bad happened when writing to the disk. might want to check your smart stats
<Aurora_v_kosmose>> I was at the 5th RISC-V Workshop in 2016, and heard Eric Grosse, then Google's VP of Security and Privacy, say that a future without risc-v was too scary to consider. | Considering the counterproductive attitude of the RISC Foundation, this seems oddly optimistic to me.
<bjc>i get that license fees are a problem, but honestly i don't see what the big deal is with the riscv isa. it doesn't seem particularly revolutionary
<kitty1>still not nearly enough, hope whoever is responsible keeps up the heat!
<Aurora_v_kosmose>littlebobeep: According to folks over in #lispcafe, LispMs have nothing that dooms them to be slower, newer CPU generations just weren't made as fast as the rest of the industry and didn't catch up.
<kitty1>what advantages did/do lisp machines have when working with lisp, apart from presumably being more elegant for systems designed around lisp?
<kitty1>err or rather would anyone know a good source to read more about that?
<Aurora_v_kosmose>Processor-wise, a lot of the type checks & GC operations were directly assisted in hardware.
<littlebobeep>Aurora_v_kosmose: Well obviously the vast majority of GPUs ever made my Intel are locked into the processors because they are different blocks of logic on the same package: iGPUs (very few had horrid PowerVR GPUs but let's forget those), and last I checked the "dedicated" Xe intel GPUs are mobile only so again you cannot use them without being locked on a motherboard with Intel chipsets and CPUs. But
<littlebobeep>given what little I have read about it, once a dedicated Intel GPU PCI-e card is made, it will probably require nonlibre firmware to run so it won't work in GNU Guix
<apteryx>the_tubular: OK, I've validate that Guix itself is healthy (make as-derivation)
<apteryx>I'm now trying to build the same derivation that failed on the CI with 'guix build /gnu/store/kmngv93i710fdpdqhl5rydzh68pxviv3-profile.drv'
<apteryx>sorry, no dice and it's late. I was trynig to figure out how to run the 'package-cache-file' procedure on the current checkout guix as a way to automatically bisect, but I'll need more time/energy. Hopefully someone else can fix it before me :-)
<apteryx>the_tubular: it's the profile hook used when building guix itself (not clear on *when* it's invoked by the CI exactly still)
<apteryx>but the purpose is to produce a cache file of all the current guix packages
<emacsomancer[m]>where are the gdm configuration/cache files located? was trying out sddm and I can't get gdm to work afterward (even reverting to an older derivation) - I assume some configuration file for gdm got altered when running sddm
<bjc>do a quick check on /var/lib/gdm and make sure it has the right ownership
<bjc>civodul: i just saw your response, thanks! i'll try to debug it further once i get some time later today
<zeta_>Hello. I can't install GNU Guix System because I can't connect to Guix's servers. Are Guix's developers blocked it for russian users? And can I install this distribution without internet connection? Thank you
<bjc>zeta_: the substitutes servers (where the binaries are downloaded from) have been having intermittent issues the last few days, so it may not be that you're from russia
<PotentialUser-42>davidl I specify a commit and version - no submodules though - but I use an access token in the git-reference https url
<bjc>an yes, you can install it without internet, but it's more complex than what you're likely doing now
<PotentialUser-42>davidl If I just replace the actual with the expected hash it works, but that does not sound right. guix hash -rx . should give me the right hash. I do something wrong
<bjc>sorry - i misspeak - you can install it without access to the substitutes servers, but you'll still need internet to get the source files for packages
<davidl>PotentialUser-42: just note that guix hash -rx works on current files not whatever files are in the commit. If you have a .gitignore file for example that might create a difference.
<zeta_>bjc: ok, thank you for help. I'll try install this on holidays
<Tirifto>Hello! I notice that the ‘glibc-utf8-locales’ is now gone, and the manual advises defining a custom locales package instead, even telling me what the definition should look like. I think that’s awesome, but how exactly should I make use of that definition? The first example of packaging in the cookbook suggests putting the definition in an arbitrary file and asking Guix to read that (guix package --install-from-file=my-hello.scm
<Tirifto>); would that be a good idea for a custom locales package?
<allana>Hi #guix! Anyone here use libvirt-service-type? I am using it for the first time and wondering how people interact with it. For example, I installed the virt-manager GUI application and it seems to want to talk to the wrong socket "/var/run/libvirt/virtlogd-sock" instead of the existing "/var/run/libvirt/libvert-sock"
<zamfofex>civodul: Thank you for getting back, I really appreciate it! I know people are oftentimes busy and I don’t want to sound demanding, is all. Other than that, I’ve just been a bit eager to try to get networking functional for the Hurd again! (Which depends on that patch.)
<apteryx>this probably does it for regular file systems that simply appear under '/dev/sdxN', but Btrfs is special in that it uses its own means to detect the file system arrangement ('btrfs device scan')
<apteryx>I suspect that if 'btrfs device scan' runs before the devices are ready it will cause the array to be degraded (missing drives)
<apteryx>the Btrfs udev rules meant to be used in the initrd are define in: /gnu/store/8c136063irrx9hig6dmf1xqli6rgibkk-btrfs-progs-5.15.1/lib/udev/rules.d/64-btrfs-dm.rules
<PotentialUser-42>Hi. I created my own python package. I can install it via guix package -i and afterwards start a python3 interpreter and import it. If I create a docker image with that package I can see it in the store but I can not import it. How can I tell python to look at the right place?
<apteryx>you need to include python in your image; this will cause the GUIX_PYTHONPATH environment variable to be defined and your package should be importable
<apteryx>rekado_: I saw a new public IP being registered in berlin; I guess what remains to be done is to assign it to some (non-berlin) machine to provide access to iDRAC when berlin is down?
<PotentialUser-42>apteryx This is my build command: guix pack -f docker -S /bin=bin python-ammosreader bash coreutils python grep ffmpeg findutils which
<apteryx>ah and yes, you'll have to source teh profile
<apteryx>so expose /etc to, and connect via 'bash -l' or something or manually 'source /etc/profile'
<apteryx>or is that just a warning that doesn't fail the build?
<apteryx>rekado_: so, how I was expecting to be able to try a PXE boot was: 1. connect to serial of node 129; 2. go to the iDRAC page of node 129 and request a reboot; 3. at the serial, see the boot options and choose to PXE boot from some IP address
<apteryx>rekado_: the wip-pyyaml branch can be deleted, correct?
<maximed>Would anyone like the WIP antioxidant code to be available in a channel?
<maximed>So people can do "guix install antioxidated-hexyl" and such.
<maximed>And maybe built by ci.guix.gnu.org for substitutes and a red/green / FTB/builds dashboard.
<apteryx>maximed: perhaps as a wip-* branch? I don't see how using it as a channel would be more convenient; what is this antioxidated-hexyl package?
<maximed>It's currently developed outside Guix itself
<maximed>It's also not just a build system, it also needs to rewrite package definitions a bit
<apteryx>ah, I had forgotten the goal is to have it as a standalone tool
<apteryx>oh. How does it rewrite package definitions, and for what purpose?
<maximed>basically, (define-public antioxidated-hexyl (vitaminate/auto hexyl)), where 'hexyl' is a rust app and 'vitaminate/auto' is the package definition rewriting procedure
<maximed>Purposes: (1) break package cycles (often caused by test dependencies, sometimes by optional features)
<maximed>(2) Set the required ‘features’ for each package (basically Cargo's equivalent of ./configure --enable-foobars)
<maximed>(3) resolve version conflicts -- usually by picking the newest version.
<apteryx>it seems like 2 could be handled at run time in the build system perhaps; I'm curious about the other 2
<ulfvonbelow>is there a way to tell 'guix pull' to only authenticate some channels? For example, if I have a channels.scm with a channel from a remote host and a local customized guix I'm working on personally, I'd like to be able to pull without having to commit and sign everything I'm currently working on.
<ulfvonbelow>alternatively, is there a way to use multiple channels from pre-inst-env?
<maximed>(4) fix build failures caused by using different versions from what Cargo does (see, e.g., "rust-x509-parser"'s #:phases in guix.scm)
<maximed>(4) can probably avoided but the packages will need to be updated anyway
<maximed>apteryx: By making it a channel instead of a branch (for now), you can still use 'master'.
<maximed>It's also a bit easier to develop it as a channel, no need for ./pre-inst-env, make, make clean, ./configure or "guix shell -D guix"
<apteryx>it seems like we'd probably want to move to use this antioxidant-build-system for most packages, so it'd be nice if the extra rewritting procedure boilerplate could be avoid to keep things simple
<apteryx>raghavgururajan: the wip-gnome3.34 and wip-gnome3.36 branches can be deleted, correct?
<apteryx>rekado_: Rocky-8-x86_64-LIVE or Rocky-8-x86_64-LIVE-GuixFarm ?
<apteryx>I get the same result with Rocky-8-x86_64-LIVE-GuixFarm
<mekeor[m]>lechner: are you on guix system? if so, did you add nss-certs to your system package list?
<apteryx>rekado_: oh, the 'Rocky-8-x86_64-LIVE' one boots!
<apteryx>what's the setup difference? perhaps it can be applied to our Guix image menu
<mekeor[m]>is cubes os any more poweful than a guix system where you launch programs in guix-shells? also, is it possible to e.g. start chromium inside a guix-shell while giving it read+write access to a browser profile?
<mekeor[m]><yarl> "make cscope does not work?" <- whats the context?
<ulfvonbelow>mekeor[m]: trouble is I want to reconfigure my system using code from my guix checkout as well as remote channels
<ulfvonbelow>oh, also, anyone know why whenever I reconfigure, the permissions on /var/run/dovecot and /var/run/knot get messed up? /var/run/dovecot ends up owned by knot:knot and /var/run/knot ends up owned by root:root
<pashencija[m]><mekeor[m]> "> <@pashencija:matrix.org> There..." <- Of course it does!