<quiliro>i have decided to write manuals from now on in Esperanto like scientists used to do in ancient times in latin so everyone could understand...that way...more people could learn a second language with more ease
<quiliro>on the other hand, ssh-daemon is already up....the manual says to lift the daemon with herd start
<mbakke>quiliro: is it because the loadkeys command is not available?
<quiliro>mbakke: no...loadkeys is available locally on the target machine
<quiliro>but it has no effect when running it remotely
<quiliro>another thing is that on the previous usb install the hard disk was recognized as sda and the usdb as sdb so that eased installation because guix system init will use sdb for installation and that i think will conflict at boot because the hard disk will become sda
<mbakke>but, once you have booted, you may have to update your configuration file before `guix system reconfigure`
<mbakke>maybe we should use UUIDs for the bootloader configuration instead
<mbakke>and definitely for the swap and FAT partitions
<quiliro>on another issue...i have been installing with 0.12 for 3 days with installation giving errors....i checked and /tmp has the downloaded and compiled files...so now i want to continue. i assume i would have no problem. but i have decided to use another disk. how do i copy the files to the other disk? with cp?
<quiliro>i assume i would have no problem using the same disk with 0.13
<quiliro>but how can i mirror the files with permissions and owners right
<quiliro>"Interesting. I wonder how much of a stretch it'd be to use a fork of NixOS, GuixSD (since it uses a Hurd microkernel as well), instead of NixOS. But thanks for the write up! I will certainly be following this soon"
<bms_>Well, on a Mac, I think it is just an Apple-modified EFI, yes.
<quiliro>i was told i could install guixsd with 0.13
<bms_>Yeah, I'm assuming fresh installs work, just wondering about updates for past installations.
<bms_>I can currently boot into GuixSD, with a little GRUB2 scripting every time I boot. I know I could get around this if I really tried, but I'd rather make sure that I have to.
<marusich>bms_, for additional information about it, you might want to check the version of the manual that is in the master branch. I think some commits which update the manual to document the new support were accidentally omitted from the release.
<bms_>On Git, in doc/guix.texi. I browser-searched for UEFI. You need to import (gnu bootloaders) in your system .scm file. And add (grub grub-efi) to your Grub expression.
<fusion809>Howdy folks has anyone had any success installing GuixSD on a VirtualBox VM? I saw the VM guide but it's for QEMU and I tried using VBoxManage to convert the USB image to a VDI. Booted it but there were failures that prevented it from booting properly.
<j-r>fusion809: I did such many months ago. IIRC I just loaded the usb image onta a sata controller and booted from it.
<j-r>I was unable to install the guest additions and then lost interest.
<fusion809>Oh so you added it sort of like a disk image?
<fusion809>Hey I'm presently trying to installing GuixSD to a VM the old fashion way by following the installation guide. It's going fairly well except one error I'm getting whenever I install a package and when I set the mirror, "guile: warning: failed to install locale
<fusion809>warning: failed to install locale: invalid argument"
<reepca>utf8 should work in most cases, what's the value of GUIX_LOCPATH environment variable?
<fusion809>It's unset. Btw I've been wondering is GuixSD meant to be installed on a host OS or can be it installed as standalone OS? The install guide doesn't mention installing it to a blank root partition it seems to just be about installing to an existing Linux distro.
<reepca>Ah, are you reading section 2 ("installation")?
<fusion809>Nope, I had some trouble with that so I thought I'd following the binary installation guide inside a VM for Arch Linux (I choose Arch Linux as it has systemd so following the service commands should be simple)
<quiliro>guixsd (distro) should have herd....guix (package manager) shouldn't
<reepca>alright, then you could try installing from guix (package manager) on top of arch linux. The "guix system init" stuff is part of the package manager, you can run it from anything with guix (package manager) on it, the installation image is just nice because it's a predictable environment.
<fusion809>Would it be good to ditch the Arch Linux environment and try with the installation image? I haven't tried using it as a SATA image like you suggested yet, so I might try that if you think it's a good idea.
<quiliro>brendyn: they should....what problems do you have?
<brendyn>They don't find icons and have trouble mounting drives
<brendyn>I've only got 3 patches in this last release. next time I want... 50!
***andreh1 is now known as andreh
<reepca>I don't know much about images and VMs and stuff - I know that I had success in putting GuixSD on a flash drive several months ago by just creating a file system on it, mounting it, and running "guix system init /mount/place/here myconfig.scm"
<reepca>Just look at the first example, the "barebones" one, then add the stuff from the second example that you want
<fusion809>I think I've followed it as I removed the mapped devices sec of the file-systems part of the config. Now guix init is giving: "guix system: error: build failed: getting info about the Nix store mount point: No such file or directory"
<fusion809>I was gonna suggest pastebining the config.scm in case you's can see an issue with it, but unfortunately there's no wgetpaste or pastebinit in this USB image and as guix isn't working for me it seems like that's not a possibility.
<fusion809>Seems you missed when I mentioned my errors when installing packages with guix package -i <PACKAGE>. It gives me "guix package: error: build failed: getting info about the Nix store mount point: No such file or directory"
<reepca>Alright, so the file it's complaining doesn't exist is specified by processEnvironment() and directly by guix-register. processEnvironment() is only called by guix-register. It seems reasonable that the culprit is somewhere in guix-register.
<quiliro>i wonder why you get that error and i don't
<OCmylife>I'm trying to install it on bare metal (nvme)
<reepca>the problem is that guix-register, despite being a separate program, is actually still just a node in a deep tree of abstraction. The fastest way to figure out which file it's complaining about would be to add a print statement and recompile or to break out a debugger... but for some reason I get the feeling if curl isn't installed, then neither is gdb.
<quiliro>rekado_: (23:13:10) fusion809: Thanks. I must admit GuixSD is an interesting OS, 'tis unusual like NixOS. Kinda sad to hear that Ututo XS is practically dead as it's now Ubuntu-based and nothing like it used to be.
<sneek>civodul, rekado says: Should we start writing NEWS for the next release as we make commits (to avoid the painful process of writing it weeks later)? I just pushed the new Java bootstrap and think that could be mentioned there.
<civodul>perhaps at the time of release we'll find that we have to trim it a bit, to keep the most important items, but that's fine
<civodul>really happy about the new Java bootstrap!
<civodul>do you think you could write about it? :-)
<quiliro>i have a meeting tomorrow with the chancellor of a small public university....i would like to ask him to have his students volunteer to guix.....they do not know much about installing gnu....but they could learn....what do you recommend about this?
<jlicht>I am trying to add some custom udev rules to my GuixSD system, and thought I could do it by adding a simple `(simple-service 'some-rule udev-service-type (list <myrule-pkg>))` to my operating system declaration
<jlicht>but it seems that my rules are not included at all :O
<jlicht>is there any way in which I can debug this?
<fusion809>Hey folks I've noticed a flaw in the virtual machine documentation. For me running: qemu-img create -f qcow2 guixsd-usb-install-0.13.0.x86_64-linux.img 5G creates the qcow2 file and names it guixsd-usb-install-0.13.0.x86_64-linux.img thereby overwriting the USB image file.
<fusion809>Plus on top of that the new guixsd-usb-install-0.13.0.x86_64-linux.img file is then only 196K in size, much smaller than the 1.1GB USB img file, making me wonder if it truly contains the required data to boot GuixSD
<rekado_>fusion809: my copy of the manual lists this command: qemu-img create -f qcow2 guixsd.img 5G
<rekado_>in step 3 you then add both this guixsd.img and the file you downloaded as drives when invoking qemu-system-x86_64
<fusion809>Ya but where do you get guixsd.img? Isn't the file you get from the xz-compressed USB image? If so I'm guessing the name of the file shouldn't make any diff
<fusion809>But pressing Enter still seems to get me a console.
<fusion809>Now internet is giving me some dramas. ipconfig -a reveals eth0 and lo as available connections. I ran `ifconfig eth0 up && dhclient -v eth0` to set the net up and then ran `ping -c 3 gnu.org` and it said 'ping: Unknown host`.
<civodul>i think we've reached the point where it's less work to fix it than to keep restarting manually ;-)
<m-o>for sure but I'm not sure how to notify cuirass that you want a new evaluation
<civodul>it's supposed to poll and start a new evaluation when a new commit comes in
<m-o>yes it does so (module bugs), the problem rekado and I were talking is when cuirass has seen new commit XXX, started and failed an evaluation and you want to reevaluate this commit XXX without removing database and restarting cuirass. Because, once cuirass has added XXX as the last evaluated commit in database, you have no way to tell it to restart evaluation on XXX.
<solene>I can't get the usb image to boot on a Toshiba portégé laptop. The usb flash DEL shows that it tries do read, the screen lights up and display a "_" char and then goes black, and loop infinitely. I rewrited the usb disk with no better result. Did someone encountered this issue before ?
<jlicht>rekado_: thanks a bunch, I will also pilfer some other parts of your config while I am at it
<rekado_>civodul, m-o There are a couple of problems with Cuirass. What keeps me from relying on it here at the institute is that it stops doing things all the time.
<rekado_>if anything fails it stops until the service is restarted
<jlicht>rekado_: unless I am mistaken, looking at your config (and my observations), it seems that e.g. `(simple-service 'mtp udev-service-type (list libmtp))' in %desktop-services does not do anything currently.
<rekado_>jlicht: oh, that could be a remnant of some work that never made it to master
<j-r>Hello Guix. I've setup an offload build daemon. guix offload test works. However when I run guix package -i blah or guix package -u everything is built locally. How does the offload daemon get called during package builds?
<civodul>j-r: the daemon looks for /etc/guix/machines.scm and calls the offload "hook" when it finds a matching machine
<civodul>also, if you do not want to build anything on the local machine, you must run "guix-daemon --max-jobs=0"
<davidl>Im trying to LUKS-encrypt my partition with the latest 0.13 image but I get an error: "CPU feature 'AVX registers' is not supported" and then when I check the partition with cryptsetup isLuks /dev/sda1 it returns false.
<davidl>this wasn't the case with the 0.12 usb image.
<j-r>civodul: I have /etc/guix/machines.scm configured properly (I think) guix offload test finds it and sends a test thing to it.... Anyway I add --max-jobs=0 to guix-daemon. Now I have a message that says either increase --max-jobs or enable distributed builds. I can find nothing in the manual about how to enable distributed builds.
<rekado_>brendyn: no, I don’t. But it wasn’t much more work than creating a variant of linux-libre (by inheriting), taking the patches, and adding them to the list of patches that ought to be applied to the sources.
<ng___>did anyone have a succesful uefi install using the guixsd usb install medium yet? It can't just be 4 people with problems..
<ng___>then you can either use emacs debbugs or subscribe to the bug-guix@ list
<ng___>it is relatively silent compared to guix-patches@
<fusion809>Is it just me or does Guix take forever to perform an update (with `guix pull && guix package -u`)? From the latest USB img I decided to do an update before installing Vim as running `guix package -i vim` suggested and it's still running after almost two hours. Is this usual or has it got something to do with the fact I'm running it on a USB img session?
<quiliro>ng___: that is what i am asking: how to subscribe to the bug-guix@ list
<fusion809>Ah thanks. Makes me feel better to know it wasn't my own screw up, granted what I had screwed up to cause it would escape me as all I've done is set up the net before running these guix commands.
<rekado_>I wonder where to put all those bioconductor packages.
<rekado_>the bioinformatics module is already ~ 10k lines long.
<rekado_>with the packages I just imported it’s four times as large.
<rekado_>maybe a new module called “gnu packages bioconductor”?
<Apteryx>Can I use thunks in search-path-specification? Like... I'd like something to be formed dynamically there (EMACSLOADPATH="share/emacs/site-lisp:share/emacs/site-lisp/guix.d/ELPA-NAME-VERSION) --> The capitalized part depend on the package being looked at.
<sirgazil>`guix pull` messages are looking tidy :)
<Apteryx>If you ask me why: because the current discovery mechanism is limited to profiles only (guix-emacs.el looks for those folders in the current profile). This doesn't work to find other emacs dependencies at build time and would require me to fiddle with EMACSLoADPATH manually, which seems wrong.
<lantw44>I am a maintainer of unofficial guix package on Arch User Repository and Fedora Copr. I found the systemd service files provided by guix 0.13.0 use /var/guix/profiles/per-user/root/guix-profile/bin/guix* in ExecStart=, but this path doesn't exist when guix package is installed by pacman or rpm. Should I patch it back to /usr/bin/guix*, or ask users to manually start guix-daemon and install guix with guix before
<lantw44>they can use these systemd service files?
<quiliro>i had some problem wit starting mariadb because of /var permissions too
<roelj>lantw44: Is the /gnu/store included in those packages? In that case, the path to guix in the store would be the right way to substitute the faulty path with.
<quiliro>i just created the directories as the guix user
<Apteryx>civodul: Do you think search-path-specification can be include some kind of lazy evaluated code for dynamically resolving a path?
<Apteryx>I'd like to replace the guix-emacs.el mechanism by search-path-specifications, so that the elisp discovery mechanism works even at build time. Normally EMACSLOADPATH=share/emacs/site-lisp would have been enough (I think), but we are using these share/emacs/site-lisp/guix.d/ELPA-NAME-VERSION subdirs which complicate the task.
<ng___>could a workaround for 27032 be to try with bios instead of uefi? not that I think that this test fails because of uefi, but you never know..
<civodul>Apteryx: no idea, that's a good question for guix-devel though :-)
<civodul>it seems like i'm postponing all the discussions today, terrible :-)
<Apteryx>civodul: no problem :) You must have a lot on your plate ;)
<SovereignBleak>Congratulations on the release everyone. BTRFS support is perfectly timed since I just switched to a BTRFS partitionless outlay with NixOS and Manjaro on their own subvolumes acting in place of partitions. Does GuixSD allow me to mount one of these subvolumes and install to it? Or will it balk at my zero partitions?
<quiliro>trying 'guix system init /mnt/etc/bare-bones.scm /mnt --fallback'
<SovereignBleak>By “these subvolumes” I mean creating a guixsd subvolume, mounting it then writing to it.
<davidl>SovereignBleak: I tried this before and despite setting the btrfs-subvol as default mount-volume on my brtfs-partition that I ran the guix system init command on, Grub would mount the GuixSD root at /btrfs_sub/
<davidl>however, I think you can pass extra mount options in the system declaration, where you could possibly do something similar to mount -o subvolid=<my-subvol>
<reggggieee>but you have to install glibc-locales / glibc-utf8-locales as the user that's running guix commands
<catonano>it's taking so long to compile the kernel :-/
<fusion809>Hey I've been running guix system init in a VM for the past several hours and I'm wondering if I close this VM and open it up later and run this same command will all the progress this command's made towards installing GuixSD to my virtual drive be lost?
<buenouanq>I imagine so. Guix commands either complete successfully, or fail and do nothing. This is part of it"s functional nature. Being stateless or whatever, there is no `progress' as you are thinking about it.
<buenouanq>I could totally be wrong though, I'm not really sure how any of this works.
<davexunit>some sort of progress meter could be possible, but it is a bit tricky
<davexunit>would be nice to know how far along you are, for sure.
<fusion809>By progress I'm interested in knowing will all these hours be in vein? Like will the guix system init command take just as long to install the system as it would if I hadn't have spent these several hours running it?
<reggggieee>i just upgraded guix (on foreign distro) and now when I do guix commands, i get a huge number of "";;; ERROR: In procedure load-thunk-from-memory: Invalid or incomplete multibyte or wide character