<roptat>so the system on my cubietruck is broken and unusable... last time I had an fs corruption I was able to recover from a less recent guix that wasn't corrupted in the store, but this time it seems that I only have one version of guix in the store and it's corrupted
<apteryx>civodul: perhaps you've reached the level where bugs are fixed with a simple 'why can't you' ;-)
<roptat>this is the end of my record: 3 years without breaking a system, thanks to guix :)
<pinoaffe>what should I change / what module do I need to include to define sway?
<mikadoZero>I am using Guix System. I am trying to switch my shell from zsh to bash. I have removed zsh from my system configuration, remove the shell section form my users in the system configuration, run system reconfigure and restarted the computer. When I open a new terminal it is still zsh. How can I complete my switch back to bash?
<bavier>mikadoZero: do you have a shell set in /etc/passwd?
<mikadoZero>bavier: In /etc/passwd at the end of the : seperated lists for my users there is: /gnu/store/ia34lsanp33vaf32yhw2nnpnm2pc2g1y-zsh-5.6.2/bin/zsh
<lsl88>and the weird thing is that even with my user, I am still asked to run guix gull (even that is the version I showed you I have installed)
<nckx>‘guix pull’ gives you a new Guix command that ‘knows about’ all the new packages. You still need to install them, either with ‘guix package’ or ’guix system reconfigure’. The latter will update your daemon (which must then be restarted).
<nckx>lsl88: Hm. I don't use guix pull so am conditioned to ignore that message, no idea what it means, sorry.
<nckx>lsl88: Why don't you reconfigure now if you haven't done so after ‘guix pull’? Then you'll be running the newest Guix System, at least. And your daemon will use ci.guix.info automatically.
<mikadoZero>nckx: Yes `grep zsh /etc/passwd` returns the lines for both user with the last item in there colon seperated lists being zsh's path.
<lsl88>but it asks me to run guix pull and package -u and starts with derivations
<charlag>Hey everyone! I have a stupid question again. I'm trying to package a crate but something's wrong with my setup. I cannot import any gnu or guix modules. I cannot find any info where to get them or how to check that they're installed. Thanks in advance.
<bavier>charlag: usually something like "$prefix/share/guile/site/2.*"
<bavier>charlag: that, or start guile up with guix's pre-inst-env script (if you installed from source)
<mikadoZero>nckx bavier: Thanks for the help. I am still working on it.
<nckx>lsl88: For example, you'll see that you need to ‘build’ …-qemu….drv, but that …-qemu (no .drv) will be downloaded. The latter is the actual package that would take ages to build locally. The .drv is just a text file.
<lsl88>I have always thought it was for updating your system: ie adding a service
<apteryx>Blackbeard[m]: maybe a 'not enough ram' issue?
<pkill9>it would be good for `guix publish` to be able to report build failures, so if you try to build a package and the substitute server has already tried but failed to build it, then guix will just error out saying that the subsittute server reports that the build fails
<kmicu>rvgn: you can add --dry-run to see whether a package will be downloaded or built.
<rockandska>not sure if it could be done easily, but, is there any way to install a specific old "native" guix package version ? a kind of search on previous guix commits without adding additional definitions ?
<pinoaffe>kmicu: my process: boot guixsd iso, run dhclient -v, mount /dev/sdb5 /mnt/guix mount /dev/sdb4 /mnt/guix/boot, herd start cow-store /mnt, guix pull, gnu system init /mnt/etc/config.scm /mnt
<pinoaffe>so I ran guix pull as the root user of the livecd
<rockandska>'guix package -s firstname.lastname@example.org' works only for the actual repository commit, doesn't it ?
<kmicu>pinoaffe: could you execute ‘guix package -A sway’? What is returned?
<kmicu>pinoaffe: thank you for additional info. I assumed you already installed the stock config. Now I understand you are during installation process and have root shell.
<pinoaffe>kmicu: guix package -A sway prints nothing
<pinoaffe>i'm running guix from /root/.config/guix/current/bin/guix
<kmicu>So it pulls 1c4d419 but guix is still on 0.16.0-1.c845323. It looks like LiveCD has different behavior than real system.
<kmicu>(This is why I always try to install stock config and then adjust system to my liking.)
<kmicu>(Cuz even when we fix that unbound sway error then Wayland can be broken anyway.)
<kmicu>nckx: any ideas why ‘my process: boot guixsd iso, run dhclient -v, mount /dev/sdb5 /mnt/guix mount /dev/sdb4 /mnt/guix/boot, herd start cow-store /mnt, guix pull, gnu system init /mnt/etc/config.scm /mnt’ doesn’t update guix and make ‘sway’ visible?
<civodul>commit c845323 is from Dec. 2018, whereas Sway was added a week ago
<rockandska>does the git repository with the definitions is fully cloned in the store and could be used at a search "database" for the commit corresponding to a targeted version by doing "git grep" on it ?
<nckx>rockandska: I think it would build bash from bash commit xxx if bash were fetched from git.
<jonsger>nckx: yeah, that was just reading out real, big repos out of the list. Minus stuff like CPAN, which haves of course 100%...
<nckx>And my preconceptions about the AUR are somewhat tempered.
<rockandska>nckx: ok got it, it needs to be a reference for the bash git itself and doesn't work if the origin don't use git-fetch
<vagrantc>so, i've got the c201 working with The Guix System reasonably well ... but xf86-video-intel fails to compile (which i don't really need) and I'm not yet savvy enough to figure out how to install a minimalist desktop system
<rockandska>so there is not an easy way to install a package from a commit coming from the guix repository itself
<nckx>jonsger: I also don't push an update if it breaks even a single dependent package (and I hope that goes for everyone, minus the unavoidable mistake). Non-functional distributions provide less reassurance there so we might even have a slight handicap there (which is, of course, good for users).
<vagrantc>how do you build just the xf86-video* that are needed for a particular machine?
<nckx>rockandska: Not in that mix-&-match manner, I don't think. You'll have to guix pull that commit, then install bash, then be sure to guix pull back to the future.
<rockandska>nckx: that's the part i'm missing in guix since all the data with the package history are somewhere :/
<rekado>then again, most of the CRAN/Bioconductor packages in Nix are not usable.
<nckx>rockandska: The main goal of Guix (if I may speak for it) is to provide a single well-working (and ideally tested) graph of packages at any point in time. Not a generic mechanism to build email@example.com. Not saying you're wrong for wanting to (it's cool and we can probably pull it of) but it's not the main goal.
<jonsger>Ignoring all this list, I think we are overall quite especially if we look on our resource (compared to e.g. what SUSE has...) and the hard things we do (bootstrapping)
<rockandska>nckx: indeed, but will be really useful to repro build env easily. Here, i was looking to an easy way to test some script on difference bash version, and use guxi as an "Bash version manager" since no one exist.
<rockandska>Having the version of bash i want to test my script against easy as 'guix package --with-commit=bash=xxxxxx' could have help a lot
<nckx>jonsger: Yeah. The more I click around on that confounded site the better I feel about our freshness.