IRC channel logs
2026-02-02.log
back to list of logs
<renbus>Hello, this is my first time installing Guix SD. I wanted to create LVM partitions, but the Guix iso (1.4.0) doesn't have them. So I did "guix shell lvm2", and now I'm seeing lines with "substitute: updating substitutes from 'https://ci.guix.gnu.org'... 0.0%", alternating with the same line, but with "bordeaux.guix.gnu.org". That has been going on <renbus>for a while... is it stuck? (My internet connexion was working before getting there.) <renbus>(I meant, the Guix ISO doesn't have the required programs to create LVM partitions.) <ieure>renbus, 1.5.0 released recently, please start by using that. <ieure>renbus, Do you have network at all? ex. does `ping 1.1.1.1' work? <renbus>Oh, that's it, it went down, now it works. <ieure>Still recommend you start from the 1.5.0 installer. <renbus>It seems like I lose the wifi connection easily, during installation. I find it strange that when I do the "wpa_supplicant -c wifi.conf -i wlp3s0" command, it writes a few lines, it says the "Connection to :MAC: completed", but it doesn't exit the program, I do "Ctrl+z" to suspend. I don't think it is normal. <ieure>renbus, The graphical installer option will handle all that for you. <ieure>I always use a tethered Android phone to install, works good. I don't have any WiFi hardware the installer supports. <mange>renbus: I think hitting ctrl+z stops the background program. You can then run the "bg" command in bash to resume the program, but in the background. <mange>I think it's also possible to go through the graphical installer until after the network set up step, then exit out to a shell (or use one of the other ttys). <renbus>I've read that I could also use the "-B" option with wpa_supplicant, which puts it in the background while keeping it alive <hugohugo>By the way, it is groundhog day, so it is obligatory to watch Groundhog Day on repeat on the Guix Days <rustyguix>Hi, looking for help to figure out how to build the latest rust version, 1.93.0. We're currently using pre-built binaries via guix-rustup, but would like to build from source instead. <futurile>rustyguix: the most recent versions of rust will be on the rust-team branch in the archive <futurile>rustyguix: you could grab that branch and build the versions that they have, adding a later version that you need <futurile>rustyguix: you could also see if another channel is doing it and use that or copy-n-paste their definition <futurile>untrusem-: can you use guix weather to check if they have a substitute built? or maybe they have a web interface that you can check their builder (I've never used that substitute server) <futurile>untrusem-: oh sorry - more coffee - I reread what you're saying - how odd <untrusem->guix archive: warning: replacing symbolic link /etc/guix/acl with a regular file <apteryx>untrusem-: the file would only exist if you declaratively added authorized keys, I think <apteryx>it's not a big deal, if you didn't care what it already contained <untrusem->I authorized a key using command line that when it gave me a warning <untrusem->echo 'key contents' | doas guix archive --authorize <untrusem->but I guess it didn't work as I am still not getting substitutes from there <untrusem->doas guix archive --import < key.pub, this did the trick <untrusem->btw when I add it to guix-service-type in my system config later, will the /etc/guix/acl change then right? <janneke>Guix Days started with introductions; already over 45 people present! <janneke>aaand we're already over 50 (fifty!) <futurile>janneke: oh very cool! everyone got their name cards and lanyards? :-)) <janneke>futurile: the name cards are a very nice touch, thanks! <janneke>efraim: you're right, we have a team bootstrap <janneke>efraim: i'm pushing my latest wip-riscv-bootstrap as bootstrap-team <janneke>"my" so please force-push another version if i messed-up with your fixup commits :) <ekaitz>janneke: did you manage to build hello-world in riscv? <efraim>we're going to work on it during Guix Days <yarl>Is there live or recording on guix days? <futurile>yarl: unfortunately not, we don't really have the money/team to do it - the venue doesn't have good bandwidth either - I did look into it a bit but couldn't figure it out <janneke>ekaitz: i didn't try risc-v, i built "hello" for x86_64-linux <janneke>ekaitz: but i did push the branch as bootstrap-team, which should already help us going <efraim>on bootstrap-team I started building out to hello on x86_64 and i686 on berlin and to binutils-boot0 on riscv64 on my machine <newguixbie>oh no some still work but i confused links to guix.moe with guix.gnu.org in chat history oops :) <newguixbie>oh no still not finding working ones still, all url confusion <rustyguix>futurile untrusem- using guix time-machine and pointing to the rust-team branch works to use 1.90.0 <rustyguix>But what's the "recommended" way to get a working version for 1.91 and above? Should I try to simply add to the latest rust-team branch? <rustyguix>I imagine rust-team maintainers must have a fairly good idea on that. <futurile>rustyguix: It depends what you want to do and how long you're willing to wait. If you need to use it "now" you either need to use rust-team from time-machine, OR you need a local copy. <rustyguix>I need it now, like this week, and need 1.93.0. <futurile>rustyguix: OR, you can now contribute a PR to the rust-team branch and someone in rust-team (there's only 3 people really) will have a look at it <rustyguix>I am willing to put it whatever effort needed. <futurile>rustyguix: ok, do you need to share the package with anyone else, or is it just for yourself? <rustyguix>I need to build some open source rust-based packages which depend on 1.93.0 <futurile>rustyguix: ok, so I'm asking because it sounds like you don't need a "channel" - in which case you can just create a local file and use the GUIX_PACKAGE_PATH or the -L switch <futurile>rustyguix: you basically create your own local directory/file and keep packages in there - just cut-n-paste - and you add the path to your build command <rustyguix>so is the recommended approach still to build atop the latest rust-team branch? I am happy to submit PRs <futurile>rustyguix: I would do that myself, because I want to upstream my PRs. I find it easier than copy-paste package definitions. I have a couple of local things that I know I won't upstream, I keep those in a separate file/module <rustyguix>yes, I also wish to benefit from others reviewing the code and trying it, which can be of great help to spot problems <untrusem->I tried to update rust to rust-1.91 in my channel <untrusem->the reason I can't use inferior because then I will need to define inferior in the rust.scm local fine and actually I tried to this yesterday but was not succesfull <untrusem->>I am trying to package rust-1.91, for that I need rust-1.90 , so I am trying to use inferiors here as I don't want to build rust-1.90 myself -> here is the bit for that https://bpa.st/XTXEI <untrusem->for rust-1.91, I saw that it was compiling so l stopped it, I will do ci rest of that and tell me if it errors out <mwette>I'm curious how one deals with julia and adding packages. Is there a way to translate Pkg.add("Foo") into a guilx package? <futurile>mwette: I don't know if we have an importer <mwette>I saw the julia and julia-xyz. I also saw some references on the interwebs that in cases binary patching needs to be done. Maybe native julia for now. <futurile>mwette: you'd have to look at the nonguix repo for binary patching, there's also a guix-science repo <yelninei>'phase `build' failed after 9515.4 seconds': :( <futurile>mwette: no worries, there's probably lots of people on guix-help / guix-devel who will have more info than me :-) <futurile>yelninei: you still working on your branch? <yelninei>futurile: Not currently. It's waiting on a gash release and feedback on some workarounds for coreutils-mesboot, texinfo and curl. texinfo is for some perl things I dont know much about and curl has issues with default certs and pkgconfig Requires <ieure>rustyguix, It's frequently down. <ieure>PotentialUser-90, I think you'd need to make a variant of the nss-certs package containing your cert, and use that instead of the default one. <ieure>Someone else might have a better answer than this. <ieure>PotentialUser-90, It's definitely not ideal. <ieure>PotentialUser-90, You might ask the help-guix mailing list. <yelninei>The childhurds really struggle with the huge llvm checkouts. Adding the patches to the source alone takes like 15min and most of the time is spent copying the source to and from the store <renbus>Hello. I'm trying to install Guix SD, I have a LVM partition, with 2 logical volumes, no LUKS encryption. While booting, it says that it finds the two logical volumes, but then it does a "pre-mount" error, and give me a Guile prompt. I'm trying to find examples of "config.scm" files with LVM, so I can find if I edited something wrong, but I don't <renbus>find any. Anybody has a working example I could look at? I'm wondering if I should load any "initrd-modules" for LVM... <identity>renbus: unhelpful remark: Guix System Distribution is the old name, now it is just Guix System <futurile>renbus: so you have an existing device (like /home) and a partition you want to install Guix on? <rustyguix>futurile: your rust 1.91 work builds successfully on my machine. Will you submit a PR to rust-team branch? <rustyguix>untrusem- your rust 1.91 builds on my machine. Hopefully you can submit a PR to rust-team! Thanks! <untrusem->rustyguix: added rust-1.92 too i haven't build it though <untrusem->as you already have substitute for rust-1.91, you can try building this too <sunless>my progress with accessing foreign binaries from the official rust installer script in a fhs container has been truly miserable, thankfully i've reached a functional state where i can work in <sunless>i have been thinking of a solution involving emacs' tramp connection to the fhs container (/guix-fhs:local...) like how docker and podman does it, it's easy to access packages in containers with tramp instead of hacky bash scripts <sunless>so what do you guys who use emacs think? <ieure>sunless, It sounds like accidental complexity downstream of running binaries instead of building from source. I would build Guix packages from source instead. <untrusem->rustyguix, added rust-1.93, I am not building there myself, hoping to find out if they build successfully when the ci picks in up <kestrelwx>I accidentally pushed wrong stuff into a pr. <ieure>Sounds like a screwed up rebase. Fix it and force-push. <ieure>But yeah, it'll look for people to review based on team ownership of files changed... So if you push stuff that touches code N teams own, N teams will be pinged. <csantosb>It is a bit scary for a second, but it happens 😉 <ieure>untrusem-, No problem! I really appreciate you picking up some of these updates, even if I'm doing most of them, I'm glad the bus factor for the package is doubled. <untrusem->lol yeah, hopefully when emacs has a proper web browser, I will step down 😛 <ieure>I've seen them in #emacs and maybe EmacsConf? <ieure>untrusem-, That's cool, Emacs' graphics stuff is indeed very hacky and slow. <ieure>Long ways from a whole web browser, though. EXWM + my exwm-firefox package do a pretty good job, though. <ieure>I used to use eww for reading documentation a lot, but now most of those sites have LLM scraper mitigations which require JS. <pomel0>hi everyone, does the 1.5.0 .iso download for i686 include the option to choose the kernel (linux-libre or hurd) when installing? <ekaitz>guys, the guix website says "reproducability" <yelninei>ACTION restarts llvm build with an updated patch again <lilyp>that's it, I'll be using ED for error reporting in the future <pomel0>yelninei: well I was going to check, but it seems libreboot does not want to boot the usb installer <acidbong>reading on Guix Home rn, am i understanding correctly that it creates its own gcroot at .guix-home, that's separate from the imperative .guix-profile? <ieure>Well, I don't think that *is* the GC root, but it is a separate GC root. <ieure>GC roots are always kept in /var/guix/gcroots, those are links to the profile store item for the profile -- the same place $HOME/.guix-home points ot. <ieure>Presence in /var/guix/gcroots is how `guix gc' knows is a root is active or not. <acidbong>well, a profile is a gcroot of sorts, just with versioning 😅