<lfam>The point is to get the 'pre-inst-env' scripts, and then use it to run your guix commands
<apteryx>raghavgururajan: still having issues with btrfs? Had you changed the faulty disk that caused the problems you've had in the past?
<atkka>has anyone successfully installed guix system using the installer? I have tried multiple computers, version 1.2.0 and snapshots. I haven't been able to get a bootable system or even finish the install in one go...
<atkka>lfam: the installer has hung while downloading from ci.guix.gnu.org at somepoint during the installation on every attempt (I'm at attemp 7 or 8 today alone). I have tried both encrypted and unencrypted partition layouts, if the installer actually makes it to the end to reboot, I boot into grub recovery without a viable filesystem
<atkka>also the installer will only accept my keyboard layout on external keyboard, laptop keymap stays qwerty, this happens on multiple computers
<atkka>I normally chroot install my distros so I'm not too woried about using the terminal method, since I'm new to guix I wanted to try the automated installer to get a config to start from though
<atkka>on the two computers I've tried there's issues with the keymap on both, install fails on both, using just the defaults and the installers proposed partitioning
<atkka>also, every single install hangs at some point during the download portion, it will start downloading the files from the ci, then a random file with stop downloading in the middle and sit forever, I have to restart the installer and resume from the last step
<sundbry>I had some hacks in there to run on old kernels < 3.10 without CONFIG_USER_NS but with User namespaces it should work better
<atkka>sundbry: thanks, I bookmarked it, I'll go through it sometime, need to take a break for an hour or so
<sundbry>Theory of operation for the script: Downloads the Guix binary distribution (not system dist) and installs it on a /mnt chroot to bootstrap itself. Once that is installed it will `guix system init /` on itself to install Guix System Distribution from your inline config.scm
***janneke_ is now known as janneke
<sundbry>@lfam so I have a repl running with the pre-inst-env, it recompiled all of the dependent modules when I did (load "gnu/packages/clojure.scm") [the file I am hacking], which although that was somewhat slow was not a problem. Now I want to test building it with `guix build clojure` naturally, so I loaded (use-modules (guix ui)) inteinding to call (guix-main ...)
<sundbry>which loaded some more modules and broke on gnu/packages/commencement.scm, which looks from the comments in that file like it should not be loaded at all
<sundbry>How do you do your repl flow with testing package builds?
<sundbry>hm it seems if I just ignore the pre-inst-env and use guile in the default environment it wont bother recompiling the world which works out fine
<firstlove>what's herd equivalent of systemctl start sshd? I cannot find any services like sshd/openssh and etc with "sudo herd status".
<sundbry>@firstlove `sudo herd status` for all services
<davidl>My store is totally corrup after a failed btrfs-convert, is it possible to "reinstall" the store by booting to the guix installer, mounting and removing /gnu/store and then doing the normal herd start cow-store /mnt, guix system init procedure? Or are there for example files outside of /gnu/store that keeps tracks of links and things that would cause issues when rebooting to disk?
<davidl>Im currently running guix gc --verify=repair,contents but Im not sure thats gonna fix it.
<davidl>an example error: root@librem13v3guixsd ~# guix gc
<rekado_>davidl: have you tried “guix gc --verify=repair,contents”?
<efraim>I know I can use #:system to build for a system, is there something like #:target to target a specific system? and still work as cross-compiling?
<jlicht>Is there an example configuration on how get started with Guix' openvpn-server-service?
<efraim>oh, it looks like it works, but (cc-for-target) doesn't give me what I was hoping for
<davidl>rekade_: hi, yes and it finally just finished without error. Now I have issues with dead links in the /gnu/store/.links dir - which I am currently removing (will run guix gc --optimize again after). Maybe things will work after this.
<zimoun>On Guix System, is it possible to install Debian package? Does something like “guix environment --ad-hoc dpkg -- sudo dpkg -i ./foo.deb” work? Some scientific packages I need are in Debian and not yet in Guix.
<zimoun>well, you said «install a dpkg package need install all its dependencies too, which mean bring the whole debian system» so same story with any container. ;-) My question is if there is a technical reason that prevents to install Debian package on Guix System?
<efraim>zimoun: I suppose, if you want to, you could use dpkg and override admindir and use a different root and use --force to get it started. dpkg --help lists some options if you really want to go that route :)
<zimoun>efraim, thanks! I will give a try… first in a Guix VM. :-)
<nefix>Hello! How can I add `libGL.so.1` for both 32 and 64 bits? I've tried to add meson in inputs and propagated inputs with no luck. Thanks!
<nefix>raghavgururajan: yeah, I have mesa, not meson. I think the issue is that I'm using python-build-system
<raghavgururajan>netfix: So while building you see something like .../lib64/foo not found?
<cybersyn>is anyone here using the meson build system on guix? i just installed it, and while the guix install went fine, there is an error when i'm trying to run it. i'm not familiar with meson, as its the build system for Akira UX, free UX design software that I want to package, so any help is appreciated
<cybersyn>does anyone perhaps know a recent working commit?
<roptat>if you never ran guix pull, I think you'll get slightly older stuff than what the installer installed for you, but I'm not sure
<mdevos>quelle: is this a new install? The installation images on guix.gnu.org use a guix that's a little old. So when you run guix pull, and then install new/updated packages (e.g. via guix system reconfigure), then the new versions will be downloaded (or built if there aren't any substitutes yet)
<roptat>civodul, when we build the installer from the release commit, the installer system uses a guix daemon that's older than that commit, right? Then, when it installs the system, it installs a guix-daemon that's even older; when you reconfigure that system without pulling, you end up building something that's again older
<roptat>actually, if you never pull, don't you get an older and older guix every time?
<quelle>was not suppose to be a new install.. but im not sure what i did. i just run guix system reconfigure /path/to/new configfile
<roptat>quelle, have you ever run "guix pull" before?
<quelle>roptat,actually i would really love. but i belive i need a mentor or something similar because for me the manuals really looks complicate and i always get stocked.maybe you can suggest me some links to have an easy start
<roptat>(if you click on "crypt" in the example, it gets you to that page in the guile manual)
<quelle>roptat,Thankyou very much.the lenguage is not a problem...i will study it!!! even if seems difficoult to me on a first look :)
<atkka>so, I'm running into the same issue I was having yesterday with the installer. I ran guix system init, downloaded several packages, now it has hung getting cdparanoia-10.2. been stuck at 71.4% for 15 minutes
<rekado_>it is closely tied to the glibc, all the way down to the bootstrap
<joshuaBPMan>atkka: I felt that way when I first installed guix. I had to install ubuntu first to correctly install grub. Then in the grub screen I had to say boot from this usb. That was interestingly learning how to do that.
<lfam>It's a shame the installation process is still so difficult for newcomers
***rekado_ is now known as rekado
<joshuaBPMan>rekado_ I've been reading about Zig and sway and they both talk about how musl is pretty gravy. I get that we want to be tied to GNU....idk...thoughts?
<rekado>joshuaBPMan: it’s a technical decision to use the glibc
<rekado>this has wide-ranging implications for all of Guix
<joshuaBPMan>rekado may I ask what that decision is? I'm certain I'd agree with it...
<rekado>we won’t switch to musl, nor will musl be a selectable option
<rekado>joshuaBPMan: this is a common pattern. I don’t mean to sound dismissive. I think it’s good that there are more C library implementations. But the initial impulse to start from scratch, implement things “cleanly”, without “bloat” … well, it often turns out that “bloat” is another term for “features” or
<rekado>that’s how we ended up with autotools, and why any attempt to replace it has been frustrated by the same problems that made autotools look like gorilla spit.
<atkka>apteryx: yes, it has happened every single time on two different computers, then if I can resume and actually finish (gui method only so far), it reboots into grub but with a botched filesystem (this is using the installers recommended partition scheme, both with or without luks)
<atkka>I have successfully ran guix as a package manager on void without issues