*raghavgururajan is on #firstname.lastname@example.org
***Kimapr4 is now known as Kimapr
<clacke>I've been on XMPP before but the bridges I was relying on went down, so I was on Matrix again for a year. When the bridge didn't come up immediately in the liberapolypse, I found a new bridge, uninstalled Element and went right back to XMPP =)
<clacke>Native Matrix rooms work great on XMPP too
<clacke>the virtual MUC for any Matrix room is at #email@example.com on XMPP
<dstolfa>thanks! i'll be around on and off, have to get some groceries, nice day and all, but will be around :)
***pjotpr is now known as pjotrp
<muradm>hi, can someone point to an example of rust package with Cargo.toml as virtual manifest?
<muradm>i.e how to properly build rust cargo project with subprojects
<muradm>this what I get for now: error: manifest path `/tmp/guix-build-greetd-0.7.0.drv-0/source/Cargo.toml` is a virtual manifest, but this command requires running against an actual package in this workspace
<muradm>should I build every subproject and then use them as inputs to main one? O_o
<muradm>daviwil: id you will want to change which services should be started or not, look at installation-os it self, it uses it like (services %installation-services), so you can use (services (modify-services %installation-services ....))
<muradm>using it from installation-os some how evaluates everything and you get that error with already defined
<daviwil>muradm: Unfortunately %installation-services can't be used directly, it isn't exported from `gnu system install`. I'm just trying to add a new service to the same list. Got it working now!
<civodul>i'm guessing it's not much of a consolation though :-)
<minikN>Hello. Could someone explain to me if/how it is possible to set env vars inside my /etc/config.scm? I'd like to change $ZDOTDIR, either setting it directly in my scm file or defining it inside /etc/zshenv. For both approaches I find little to no information online.
<iung>Hello! Asking for help with guix installation on btrfs raid0. Failing to mount root subvolume at startup. Example error message from guile-rescue: "kernel: BTRFS error (device sda): devid 2 uuid 65c21020-6607-425b-a36b-5455d80ab0d1 is missing". I can mount it from live usb. I'm confident config is standard and correct. Internet suggests that
<iung>mounting is made too early, that 64-btrfs.udev if placed in iniitsomething should delay it properly. Looking for your help,
<viivien>I’m glad I set up a local clone on my system :)
<mitzman>hm, I might be a bit challenged - i've created a directory X/packages/package.scm. In package.scm, i've defined the module (X packages package), and the package inside is defined publicly. any reason why guix install -L ... package fails? it does read the package file, gives hints about naming
***ChanServ sets mode: +o nckx
***nckx changes topic to 'GNU Guix | ⚠️ guix pull broken: https://hostux.social/@fsfstatus | 1.3.0 is out! https://guix.gnu.org/en/blog/2021/gnu-guix-1.3.0-released | videos: https://guix.gnu.org/blog/tags/talks/ | bugs & patches: https://issues.guix.gnu.org | paste: https://paste.debian.net/ | Guix in high-performance computing: https://hpc.guix.info | This channel's logged: https://logs.guix.gnu.org'
<nckx>bandali: IIUC, that's handled relatively well: well-configured relays will retry until mails are accepted again, and issues.guix will still show all the bugs (and none can be added so it's not even stale :) — correct?
<nckx>It won't really differ from the occasional mysterious 6h debbugs delays that happen occasionally.
<bandali>nckx, yeah i'd hope so. email is generally quite resilient
<apteryx>civodul: ./pre-inst-env guix build ppsspp --with-latest=ppsspp -> guix build: warning: could not determine latest upstream release of 'ppsspp' -> proceeds to build the current version; shouldn't that be a hard-stop warning? Otherwise i might think it built the latest version (the warning is soon burried in a ton of output).
<katco>bricewge: thanks for that snippet! that automates getting the installer to output onto the serial console. i'm a little confused though because even though the installer displays now, it looks like it still switches to tty1 after booting? i'm unclear on how i'm meant to continue with installation over a serial console =/
<katco>i.e. i get this: "NOTICE: vt: using tty /dev/tty1 (open_tty() in src/uterm_vt.c:285)"
<bricewge>I didn't remeber if I actually managed to use the graphical install through the console. But I curious to know since I have a a pcengines too, but not running Guix since it's lacking advanced networking configuration
<bricewge>Using the default Guix image to install through a serial console would be great
<katco>yeah it, it would really be great if i could have just popped in the usb drive and had it work like normal. i'm going to try setting the `virtual-terminal` field to `ttys0` and see what happens. barring that, i'll just enable openssh to start by default
<civodul>apteryx: re --with-latest warning, yes, maybe this could be an error instead
<civodul>apteryx: could you email bug-guix for the segfault?
<civodul>i get the "NULL string pointer" exception too
<bandali>fyi savannah seems to be back again (for?) now
<bauermann>civodul, I noticed that the texlive package is 2 years old. instead of trying to pin down exactly what is wrong with it, do you think it's too crazy to update it to the current version and see if it solves the heisenbug?
<civodul>bauermann: gasp, i had forgotten about that bug, ouch!
<zap>yep was just about to write about relocatable packs
<bauermann>civodul, I've been wondering if it's feasible/desirable to rebase guix on current nix/libstore. I'm not sure, but I think it's likely that they have fixed this bug (checking that is on my to do list)
<raghavgururajan>zap and civodul: But that is a symlink patch right? extracted file sshould be at /gnu/store ... profile ..??
<ixmpp>guys, i have a shepherd service that depends on a python package
<katco>bricewge: it was a long shot, but specifying ttyS0 does not work. it errors with the following: "WARNING: vt: cannot find the currently active VT (25): Inappropriate ioctl for device (real_open() in src/uterm_vt.c:328)". but i created an ISO with openssh enabled and can continue the installation from there. i just need to figure out how to manually invoke the installer. but my daughter just got home, so a task for later :)
<mbakke>bauermann: unfortunately TeX Live 2020 does not solve the indeterministic build failures
<katco>bricewge: i was able to start the graphical installer manually from an ssh session. this was pretty easy, but it is unfortunate that i had to build my own ISO to enable openssh to get this far.