IRC channel logs


back to list of logs

<cybersyn>roptat: it worked! thanks for the advice, I'll clean it up and push it upstream in the morning. have to say the guix packaging system is a lot to take in at first, but already feel that getting through this first non-trivial package taught me how simple it actually is and I'll be able to contribute frequently soon enough.
<cybersyn>I've been using guix as m
<cybersyn>my daily driver since winter and have hit some obstacles in my packaging attempts since (because everything i've wanted that isn't already available has been a bit complex), so put it off until a rainy day, and now that we're under lockdowns for the first time since last year I've found the time, but already have some thoughts about better ways to communicate the process to newcomers, will do a post about it it in the near future :)
<hendursaga>How's ZFS support with Guix? I see there's been some activity but how has dogfooding gone so far, if it's at that stage yet?
<dstolfa>hendursaga: i haven't tried it but i guess it just works? partitioning your drive and specifying a mount type "zfs" with whatever options you want should just work (TM)
<marusich>civodul, not sure if you saw this email, but do you (or anyone with experience using gdb in Guix on a foreign distro) know of any obvious reason why this error might occur when using guix-built gdb in a pure environment on a foreign distro...?
<sneek>Welcome back marusich, you have 1 message!
<sneek>marusich, leoprikler says: pure environments still have access to your filesystem and depending how was linked that might make a difference
<marusich>leoprikler, oh ho. Well. Yes, that's true. Maybe somehow even the Guix built tools found those pesky libraries in /lib? :(
<marusich>I guess an option is to try using --container. I should also try with a simple C project to see if this happens when I try to use gdb on a toy program there.
<civodul>marusich: hi! you're debugging a glibc-2.33 (core-updates) binary with master's gdb, right?
<civodul>oh wait, you seem to actually be debugging /bin/sh, which uses the foreign distro's libc
<dstolfa>hendursaga: i haven't tried it but i guess it just works? partitioning your drive and specifying a mount type "zfs" with whatever options you want should just work (TM)
<civodul>and that leads to confusion because libfaketime's script must be setting LD_PRELOAD to its .so, and that one is linked against our own libc 2.33
<dstolfa>that was not intended.
<dstolfa>i meant to up-arrow another terminal :)
<marusich>civodul, Hmm... I tis certainly not my intent to be debugging /bin/sh
<marusich>Did I specify the program incorrectly?
<hendursaga>dstolfa: is there a filesystem you'd recommend for GuixSD?
<marusich>The program should be the timetest program.
<marusich>To answer your question, I am debugging a program named timetest, which should be linked against glibc-2.33 from Guix, and compiled using GCC from Guix.
<dstolfa>hendursaga: any you like, i use btrfs
<marusich>I am using the gdb that comes from Guix. glibc, gcc, and gdb all are the ones provided by Guix on a specific recent commit from core-updates.
<dstolfa>guix is free software and freedom 0 is that you can use the software however you wish, so whatever file system you prefer you can put on your machine :)
<marusich>I know this because I manually built everything in an environment provided by: re-inst-env guix environment --pure libfaketime --ad-hoc gcc-toolchain@10.3.0 gcc-toolchain@10.3.0:debug gdb
<marusich>Maybe I messed up somehow, but that is my intent.
<hendursaga>dstolfa: one reason I liked ZFS is it was (at least on FreeBSD) really easy to create different pools of data encrypted with different keys, transparently
<dstolfa>hendursaga: if you like ZFS, use ZFS. there's a guix package with the kernel module (that will be compiled on your machine because of the binary clauses of GPL and CDDL that are a bit of a grey area), and you should be able to just use it
<marusich>civodul, I have to run for now, but I will try some other things, like also running strace to see what gdb is trying to do...
<marusich>Oh, I forgot to say: thank you and everyone for taking a look. I appreciate it!
<pie_>is there an irc channel for make?
<daviid>pie_: i would ask on #autotools or (better imo) ##workingset (with 2 #)
<hendursaga>dstolfa: I think I'll use whatever is default for my system partition and ZFS for external data
<pie_>daviid: tnks
***califax- is now known as califax
<MysteriousSilver>when using git-fetch, will the .git file be in the build directory?
<the_tubular>I'm still stuck on this problem : anyone has an idea ?
<the_tubular>I'm pretty sure it's because I booted using BIOS, but I can't boot using EFI ...
<the_tubular>It doesn't see a EFI partition when I try to boot using EFI
<drakonis>what's your config and storage partitioning
<drakonis>does your target storage have a bios or gpt partitioning scheme?
<the_tubular>Should I paste my whole config ?
<danrobi70>the_tubular: you probly should upload to something like
<the_tubular>This is my config
<the_tubular>The disk partitioning was done using the guix installer ISO, and the only thing I messed with was changing the ext4 partition to btrfs
<the_tubular>Rest is default using encryption
<the_tubular>I'm kinda out of idea, right now. Unless restarting from scratch, but I have no idea what I would do differently
<the_tubular>Anything that could have gone wrong during the installation ?
<the_tubular>sdb 8:16 0 83.9G 0 disk
<the_tubular>├─sdb1 8:17 0 1023.5M 0 part /boot/efi
<the_tubular>├─sdb2 8:18 0 3M 0 part
<the_tubular>└─sdb3 8:19 0 82.9G 0 part
<the_tubular> └─cryptroot 253:0 0 82.9G 0 crypt /
*the_tubular broke guix :(
<marusich>the_tubular, it's tricky because the disk configuration is outside the management of Guix... I suggest examining the system tests for the gpt case and comparing it to what you are trying to do in your own situation.
<marusich>Line 441 shows one way that the tests configure the disks:
<marusich>Your error message suggests that perhaps you didn't set the bios_grub option (that's what parted calls it)
<the_tubular>Ok, how would I check that ?
<marusich>I believe the bios_grub option corresponds to the "BIOS Boot Partition" thing in your error message
<marusich>Try running parted to see what it says about your partitions. Something like sudo parted -l
<marusich>You should probably see something like "bios_grub" on the partition you would like to use for grub.
<marusich>Maybe what you want to do is different... I'm not sure if you're trying to use EFI or just a GPT-based partitioning scheme without EFI.
<the_tubular>Boot flags look like it's enabled. As I said, apart from changing ext4 to btrfs I didn't mess with disk partitioning
<marusich>is your computer booting in uefi mode, or legacy bios?
<the_tubular>Legacy bios, I couldn't get it to boot in uefi
<the_tubular>Boot uefi is my goal
<the_tubular>When I go into my bios and select uefi, it just skips it and goes to my default boot option
*the_tubular officially hates disks partitioning
<the_tubular>Any other ideas ?
<marusich>So it worked when the only difference was the file system type (no other changes to the os config or partitioning scheme)?
<marusich>If that's the case, then I suppose it's perhaps a btrfs-specific issue. Have you seen this discussion?
<marusich>I haven't tried using btrfs, so nothing obvious comes to mind.
<the_tubular>I'm sorry could you repeat your first line ?
<the_tubular>It never worked, I never been able to boot in efi
<marusich>Were you able to boot, using BIOS (not EFI mode)?
<the_tubular>Yes, I'm booted in BIOS right now
<marusich>OK. And is that using btrfs or ext4?
<marusich>OK, so the issue is that it's working now, but if you try to switch to using efi, it doesn't?
<marusich>OK. if that's the case, I suppose it's because you didn't specify efi mode in the os config. Let me find an example...
<the_tubular>Sure, if it is that simple, I'll be really happy
<the_tubular>But why isn't this done by default by the installer ?
<marusich>Do you recall if you were booted in efi mode at the time you ran the installer?
<the_tubular>I don't think so
<marusich>I think (but am not sure) that the installer might choose grub-efi-bootloader if you are booted in efi mode, but not otherwise.
<the_tubular>I'm not 100% sure though but I remember also having trouble booting in efi even with the ISO
<marusich>One necessary thing you probably have to do is to change bootloader-configuration to use grub-efi-bootloader instead of grub-bootloader. There is a section in the manual describing how to configure that:
<the_tubular>I pasted my config above, if you want to check if I've got everything needed for EFI
<marusich>You'll also need to update the target to be your /boot/efi, I think
<the_tubular>(mount-point "/boot/efi") this is already in my config.scm
<marusich>After making those changes, I suppose your bios_grub partition will no longer be necessary
<the_tubular>But the bootloader line says : (bootloader grub-bootloader)
<the_tubular>Please refer to my full paste above as I am still very new with guile
<marusich>Indeed, that is the mount point for your EFI file system. However, what I mean is, you will probably need to add (target "/boot/efi") to your bootloader-configuration stuff.
<marusich>Sure, I'll see if I can give you an example of what I mean, so it's more obvious
<the_tubular>From what you said the only change would be changing line 21 from : (bootloader grub-bootloader) to (bootloader grub-efi-bootloader)
<the_tubular>Thanks a lot for your help! It's very appreciated
<the_tubular>Next fun part will be mounting zfs ...
*the_tubular is scared
<marusich>something like this:
<marusich>yes, that is what i mean, but you also need to add a "target" field in the bootloader-configuration
<marusich>this will tell grub where to install the bootloader. It should be installing it into /boot/efi; my understanding is that the bios_grub partition you made will not be used at all in an EFI configuration.
<the_tubular>That seems plausible
<marusich>perhaps you already know, but when grub installs a bootloader to a gpt partitioned disk in bios mode, it can install the bootloader to a bios_grub partition. So that's the purpose of that partition.
<the_tubular>Line 21 still says : (bootloader grub-bootloader) in the pastebin you sent
<the_tubular>Is that wanted ?
<marusich>However, in EFI mode, grub will install the bootloader to the FAT32 file system used by the UEFI, which is mounted on your system currently at /boot/efi.
<marusich>No, that is not correct, perhaps I wrote it wrong
<the_tubular>Got it!
<marusich>I accidentally pasted your original one
<marusich>hopefully that will do the trick
<marusich>of course, i imagine you will have to make sure to boot your machine in efi mode also, in order to make use of the newly installed bootloader in /boot/efi
<the_tubular>Wait, don't you said I also need to change something in /boot/efi/grub.cfg to ?
<the_tubular>Or did I misunderstood you ?
<the_tubular>There are too many "/", but I meant /boot/boot/grub.cfg
<marusich>i don't think you need to; guix / grub should create the right config for you unless you are doing something requiring manual intervention like dual booting
<the_tubular>Ok, that's wht I though
<the_tubular>I'm rebooting, see if that works. This is a huge server so it might take a while for it to reboot, give me a sec
<marusich>good luck!
<the_tubular>Umm, wait
<the_tubular>I guix reconfigured and got another error : /gnu/store/mb7sg4q398ikdlx56whp2p8msa8pyakw-grub-efi-2.04/sbin/grub-install: error: /gnu/store/mb7sg4q398ikdlx56whp2p8msa8pyakw-grub-efi-2.04/lib/grub/i386-pc/ doesn't exist. Please specify --target or --directory.
<the_tubular>A shell script seems to be missing, is there a package I should download ?
<the_tubular>The only change I made was changed the line 21
<marusich>what's your current config?
<marusich>if you can paste it all again, that would be helpful.
<the_tubular>Exact same thing you did paste last time
<marusich>does it include a (target "/boot/efi") line?
<marusich>not a (mount-point "/boot/efi") line
<the_tubular>Ohh no
<the_tubular>I'll just paste the whole config you pasted in my new config
<marusich>OK, try adding (target "/boot/efi") after (bootloader grub-efi-bootloader)
<the_tubular>Sorry, I though you were talking about /boot/grub.cfg i got confused
<marusich>no problem
<the_tubular>I"m reconfiguring
<the_tubular>Off-topic, should I ignore this error : guix system: warning: cannot determine provenance for current system ?
<the_tubular>well this warning *
<the_tubular>Same error, let me paste you my config one more time
<MysteriousSilver>any emacs users here?
<MysteriousSilver>running `emacs -nw` gives:
<MysteriousSilver>Debugger entered--Lisp error: (void-variable \213)
<MysteriousSilver>it only happens on guix
<marusich>not sure about the provenance warning; i'd probably ignore it for now since it is likely unrelated to boot issues
<the_tubular>Does that seem correct ?
<marusich>seems correct to me
<the_tubular>Same error as before : error: /gnu/store/mb7sg4q398ikdlx56whp2p8msa8pyakw-grub-efi-2.04/lib/grub/i386-pc/ doesn't exist. Please specify --target or --directory.
<marusich>any other context in the error message, like the grub command being invoked?
<the_tubular>Yes, here it is : guix system: error: '/gnu/store/mb7sg4q398ikdlx56whp2p8msa8pyakw-grub-efi-2.04/sbin/grub-install --boot-directory //boot --bootloader-id=Guix --efi-directory //boot/efi' exited with status 1; output follows:
<the_tubular>Is there a package that I'm missing ?
<marusich>is your machine 32-bit?
<marusich>like, is your os 32-bit? what's uname -a say?
<marusich>I see that the grub-efi package, on my system, contains a file at lib/grub/x86_64-efi/ but not at lib/grub/i386-pc/
<the_tubular>No, machine is 64 bit
<the_tubular>Let me confirm
<marusich>Do you any output when you run: find $(guix build grub-efi) -name
<the_tubular>Linux node1 5.11.15-gnu #1 SMP 1 x86_64 GNU/Linux
<the_tubular>find $(guix build grub-efi) -name
<the_tubular> /gnu/store/mb7sg4q398ikdlx56whp2p8msa8pyakw-grub-efi-2.04/lib/grub/x86_64-efi/
<the_tubular>So it exists ...?
*the_tubular hurts itself in his confusion
<marusich>I think grub is confused about the system, see:
<marusich>I think something is causing grub to fail to detect automatically that it should be using efi
<marusich>Perhaps the presence of your bios_grub partition, or the presence or absence of various boot-related options on your partitions, is confusing grub?
<the_tubular>Should I manually call grub-install ?
<marusich>Honestly, I'm not sure. If I were doing this, I'd make sure I had a backup, and then try modifying the partition scheme, but I'm hesitant to recommend that since it could cause your system to become unbootable
<marusich>Is a directory named /sys/firmware/efi visible to your right now in your booted system?
<marusich>e.g. if you run ls /sys/firmware/efi, what do you see?
<the_tubular>Nope :/
<marusich>I think that means that you aren't booted in UEFI mode, which makes sense since you're booted in BIOS mode.
<marusich>Perhaps GRUB, for similar reasons, thinks it's not supposed to be using UEFI mode...
<marusich>Do you still have a Guix installation image handy?\
<the_tubular>Yes, but I can't boot that in UEFI mode either
<marusich>Oh, I see. That's what I was going to suggest
<the_tubular>Yeah, I though about that :/
<the_tubular>My question is why does it check in /grub/i386-pc
<marusich>The answer is, most likely it's because grub thinks the system is not UEFI compatible.
<marusich>Most likely it thinks it needs to use BIOS, not UEFI.
<the_tubular>But this is a completely different architecture no ?
<marusich>I think that's just the name grub uses to refer to "BIOS".
<marusich>I'm not sure, but I wouldn't be surprised.
<marusich>If you could somehow temporarily boot with efi, I feel like this failure wouldn't happen
<marusich>what prevented you from booting from the installation usb in efi mode?
<the_tubular>No clue, it just refused to boot
<marusich>were you able to access the boot menu and request that it boot from the usb?
<marusich>what happened after that? no error messages?
<the_tubular>But if I select UEFI : USB, it just booted my Gentoo install
<marusich>hm, i see
<the_tubular>My gentoo install was booting in UEFI though ...
<the_tubular>So I know my system supports it ...
<marusich>it is strange that you couldn't boot from the usb stick in uefi mode, but i'm not sure what the problem might have been.
<marusich>I guess Gentoo isn't still installed?
<the_tubular>I backed it up on nother usb key
<the_tubular>So I could boot back into it
<marusich>If it were, maybe you could boot into it in UEFI mode, and then install Guix, and then run "guix system init" from within it.
<marusich>i.e. instead of following the usual way of installing Guix System, you can start from a working foreign distro and make it a Guix System distro by running "guix system init".
***xgqtd is now known as xgqt
<the_tubular>Umm, that's a good idea
<marusich>It's one sort of hacky possibility; it might leave the gentoo stuff lying around (unused) in the root partition unless you take some kind of steps to avoid that
<marusich>I mean, this is all assuming that grub-install will do the right thing if the system is booted in efi mode
<the_tubular>But what is the cause of the problem ?
<the_tubular>My disk partition ?
<marusich>I still think it's probably that grub-install thinks it needs to do a BIOS installation, not a UEFI installation.
<the_tubular>Or the fact that I'm booted in BIOS
<marusich>I don't know why that would happen though; I think it's probably more likely due to the fact that you're booted into BIOS
<marusich>but...i am not sure
<the_tubular>Isn't that usually set up in grub.cfg ?
<the_tubular>What if I edit it manually and ran grub-install ?
<marusich>I don't know how grub-install detects whether it should be doing a BIOS install or a UEFI install. I imagine you could probaly invoke grub-install manually somehow, but you'd have to know the arguments to pass to it, and if you used stuff from /gnu/store, they might get GC'd if you run "guix gc" later on (Guix sets up gc roots ensures that won't happen when you run "guix system reconfigure")
<the_tubular>I'll be right back, try to download a fresh guix image and burn it into a USB stick
<the_tubular>If you think of something, ping me
<the_tubular>Check if I can boot in UEFI
<marusich>But yeah, if I were investigating, I would make sure I have backups, then try removing stuff related to BIOS (e.g., the bios_grub partition), and if it still doesn't work, I'd try booting Gentoo in UEFI mode and running "guix system init" from within there, to see if grub-install does the right thing there.
<marusich>I'm gonna have to go to sleep, but hopefully somebody else who knows about using Guix System with UEFI can help more.
<the_tubular>Alright, thanks a lot for your help!
<marusich>Sure thing. I have no hard evidence, but I feel like it's pretty likely that grub will behave correctly (i.e., try to install for UEFI) if you are booted in UEFI mode.
<marusich>If not, I apologize :(
<marusich>Just make sure that if you try "guix init" from within Gentoo, that you use the grub-efi-bootloader in your os config.
<marusich>"guix system init" I mean.
<the_tubular>Goodnight to you!
<marusich>FYI the_tubular, grub source indicates that if /sys/firmware/efi is a non-empty directory, it determines the system is EFI; otherwise it is not.
<marusich>get the source (guix build -S grub-efi), unpack it somewhere, then look in grub-core/osdep/linux/platform.c for grub_install_get_default_x86_platform and is_efi_system to see the logic.
<marusich>It clearly attempts to use i386-pc as the "platform" on x86-64 linux systems under Linux when the /sys/firmware/efi is missing. That happens if you boot in BIOS mode.
<marusich>So that's why it's trying to find i386-pc; if you can boot into EFI mode, it will likely work.
***Iacob_ is now known as Iacob
<the_tubular>So I might have an update on UEFI booting, if someone still reads that
<the_tubular>Basically I downloaded multiple linux ISO and tried rufus on Windows for mounting the ISO
<the_tubular>Every ISO I tried, except Guix gives me the option to use BIOS or UEFI
<the_tubular>But the only option I have with Guix is BIOS or UEFI-CSM
<the_tubular>Anyone has this problem ?
<the_tubular>Is this the way the Guix System ISO is made ?
<the_tubular>Also if I let's say boot it off a Debian ISO, could I install guix on it and also have access to the guix graphical installer ?
<drakonis>no graphical installer and i'm not sure how you'd install guix on the install iso, they're very slim
<the_tubular>ISO just won't give me an option to install it using UEFI
<the_tubular>I tried Rufus and Etcher, which are the 2 most used tools on Windows
<drakonis>might i suggest you something like ventoy?
<drakonis>if you install it on iso mode with rufus, it doesnt work quite right
<the_tubular>Never heard about it, but i'll surely give it a shot
<the_tubular>Seems to work, I'll have to disconnect from IRC, I'll brb
<tissevert>hello guix
<KittyOwO[m]>hii uwu, how's you?
<tissevert>not bad : 3 you ?
<KittyOwO[m]>eh just kinda existing lol
<tissevert>which is pretty rad already
<the_tubular>I don't remember who suggested ventoy but it works like a char!!
<tissevert>think of all the things not achieving existence, their pretty numerous if you ask me
<tissevert>I prefer «work like a char»
<the_tubular>Thank you!
<tissevert>I think I'll keep it
<tissevert>I sense some great potential for technical puns
<tissevert>what's ventoy anyway ?
<the_tubular>The thing to burn guix ISO to a USB stick
<KittyOwO[m]>Ah, there are many great things that have yet to achieve existance
<tissevert>ooohh that's great
<the_tubular>Other programs just bork it
<the_tubular>And I've been trying to figure it out for days lol
<tissevert>how come ?
<KittyOwO[m]>Anyone want to make bets on if James Webb space telescope or Hurd will come out first? :P
<tissevert>wait I thought Hurd was out already
<the_tubular>I don't know, the guix ISO just refused to boot in UEFI mode
<tissevert>ohhh that's sad : (
<the_tubular>You can scroll up if you have chat history, been trying to solve that issues for hours
<KittyOwO[m]>I haven't messed with hurd yet, but I mean, out as in something that anyone can use just as easily as linux-libre as a daily driver.
<KittyOwO[m]>I also think its on 0.9 last I heard. Several people here probably know more about hurd than I do lol
<KittyOwO[m]>I just know it exists and the broad concepts of it lol
<tissevert>I see, pretty bad it seems
<tissevert>(the UEFI issue, not Hurd obviously)
<KittyOwO[m]>:P, I need to mess with childhurds some time
<the_tubular>I'm back on the freshest guix install now
<the_tubular>It also solved my booting problem, from like 30 minutes down to 2 minutes ...
<the_tubular>Now time to mount ZFS pool, any tips on that ?
<tissevert>ooooh no, I've never tried that
<jeko>Yooo Guixters !
<tissevert>hey jeko
<civodul>Hello Guix!
<MysteriousSilver>(display "bonjour, civodul!")
<MysteriousSilver>civodul: is there a logo/mascot for dmd?
<civodul>for the Shepherd? no, not yet
<jeko>tissevert: hey ! I'm still waiting for another accoustic music record hahaha
<KittyOwO[m]>yknow, I'll give it a couple minutes and then ask lol
<jeko>Damn, I just realized I lost my notes about initializing Guix System on a DigitalOcean Droplet haha
<KittyOwO[m]>DigitalOcean Droplet?
<MysteriousSilver>➜ guix build st --with-patch=./change-key-bindings.patch
<MysteriousSilver>guix build: error: ./change-key-bindings.patch: invalid package patch specification
<MysteriousSilver>how should i specify patches?
<the_tubular>Ok, any idea on how to mount a zfs pool in a config.scm ?
<KittyOwO[m]>If you find out how, I am curious. I need to mess around with those kinds of things some time lol
<the_tubular>Sure KittyOwO[m] I'll try to find out cause I have no idea
<civodul>MysteriousSilver: the syntax is: guix build st --with-patch=st=./change-key-bindings.patch
<civodul>it'd be nice to have a clearer error message, though
<jeko>I'm back ?
<jeko>KittyOwO[m]: Yes a droplet ! It's like a virtual private server from a hosting company named DigitalOcean haha
<jeko>Annoying error:
<jeko>guix pull: error: Erreur Git : Failed to retrieve list of SSH authentication methods: Failed getting response
<jeko>I found a way to manually fix it
<jeko>but still annoying
<vivien>Hello all, remember to stay hydrated and run guix gc
<iyzsong>hello :~)
<jeko>vivien: hi
<jeko>iyzsong: yoo
<tissevert>jeko: you are ? that's so nice
<vivien>I’m confused: I thought that there was a json-ld module for guile, and in my memory jeko wrote it, but I can’t find it anymore
<tissevert>actually I've recorded a cover of Nuage
<tissevert>don't remember if I've uploaded it though
<vivien>(or not, I don’t remember)
<civodul>jeko: hey! are you pulling from an ssh:// URL or similar?
<tissevert>what is a «lowerable object» ? Oo
<tissevert>«lowering a plain-file yields a store item»: aren't there plain files in the store already ? all the .drv ?
<efraim>civodul: do you remember if we want to link julia to openblas and lapack or just openblas if we can?
<civodul>efraim: ah ha! i'm not sure what the conclusion was
<efraim>I'm hoping to merge julia-1.6.1 before the weekend
<civodul>my reading of is that openblas should be enough
<civodul>tissevert: a "lowerable object" or "file-like object" is a Scheme object that can be turned into a file in the store
<civodul>'plain-file', 'computed-file', package, etc.
<civodul>efraim: it'd be great to get Julia 1.6 merged
<jbv1[m]>efraim: yes ! I did not have time to send a new patch update, but julia 1.6.2 is out and there is probably very little changes necessary to the current patch
<tissevert>oooh I think I see, so not an actual file, simply an in-memory representation of something that we very much want turned into one at some point ?
<efraim>oh, powerpc64le failed with rust on core-updates with the same error aarch64 gets on master
<efraim>Unknown target name ''
<efraim>jbv1[m]: It's been long enough, I think we'll make sure it's good as-is and clean up as necessary and then later upgrade
<civodul>tissevert: yes, exactly
<tissevert>thanks for your clear explanation ! For some reason I couldn't pass through the «file» part ^^
<jeko>tissevert: I am jeko from Mastodon haha, if it helps haha
<jeko>civodul: I think I do, from ""
***dragesti- is now known as dragestil`
***smartin1 is now known as smartin
***dragestil` is now known as dragestil
***sneek_ is now known as sneek
<civodul`>jeko_: i guess pulling over SSH should work, but it might require you to be running an ssh agent
<jeko_>civodul`: I think it is already running but the SSH_AUTH_SOCK needs to be set manually
<civodul`>normally the agent sets it
<jeko_>when I run `ssh-agent` I can see it is
<jeko_>SSH_AUTH_SOCK=/tmp/ssh-0rNyNmIh8HIM/agent.45005; export SSH_AUTH_SOCK;
<jeko_>SSH_AGENT_PID=45006; export SSH_AGENT_PID;
<jeko_>echo Agent pid 45006;
<jeko_>I found a solution in the mailing list
<jeko_>anyway it may not be Guix related
<jeko_>(running on foreign distro)
<jeko_>boundaries are not clear to me haha
<raghavgururajan>Hello Guix!
<dstolfa>hello raghavgururajan!
<jeko_>raghavgururajan: yooo
<jab`>morning guix!
<jeko_>jab```: hey
<jab>hey guix, I think that I am following the manual about modifying sysctl service...but guix is saying that sysctl is defined more than once.
<jab>nevermind I think I found the problem.
<jab>and I'm pretty excited to try out the childhurd service!
<civodul`>jab: childhurds are a lot of fun!
<jab>civodul: I agree...hopefully I'll be able to reconfigure with the service...
<jab>I'm having some struggles currently...
<jab>let's see
<jab>I'm wanting to try out a stateful hurd image...but I seem to be struggling getting it to go...what syntax error am I making?
<tissevert>does anyone know if opam distributes binaries ?
<jab>what's opam? ocaml?
<tissevert>I managed to toy with a package in my ~/.opam folder
<tissevert>but I can't seem to import it cleanly with guix import opam
<tissevert>and I enter in a recursion of missing packages
<tissevert>so I'm kinda wondering how opam managed it
<MysteriousSilver>hello, i'm using an program which requires recompilation to edit configuration, i was wondering what's the best way to do this? patches+GUIX_PACKGE_PATH or git-fetch+custom channels?
***bsima1 is now known as bsima
<civodul>jab: what error do you get?
<civodul>tissevert: why bother with opam when you have Guix? ;-)
<civodul>is it "guix import opam" that's entering infinite recursion?
<jab>civodul: I am currently just going to try out the stateless image.
<jab>I'm surprized at how long it takes to build. I must be getting my $s worth. :)
<jab>civodul: maybe you have to build a stateless childhurd first...then after that exists in the store, then you can build a stateful childhurd...just guessing.
<civodul>jab: the error must be because you have (image (const "/path/to/image")) instead of (image "/path/to/image")
<tissevert>civodul: I'd rather be the one to avoid opam if I can avoid it but the package I was curious about had an opam package and I this time I remembered that guix had an import for opam except…
<tissevert>a ton of things among which: it's not in the official opam repositories, so I'm manually adding dependencies as long as guix build breaks, discovering exotic opam packages which aren't packaged for guix either, or with a bad version
<tissevert>so I'm the one entering the infinite recursion, of manually solving dependencies, then wondering why dependencies of dependencies break, and ending up not even knowing what problem I'm trying to solve in the first place
<dstolfa>tissevert: you can add new versions of dependencies (or update existing ones if reasonable) and use (inherit ...) in all the older versions of the package
<dstolfa>if the dependency that's in guix is too old of a version for you, maybe you can update it, or you can simply add a newer version and then have the old version inherit from the new version
<tissevert>I'd be willing to try that, if, like I said, builds weren't failing here and there leaving me in a state of the deepiest confusion
<dstolfa>what specifically is failing?
<tissevert>I've had some trouble with ocaml-containers too, apparently wanting something called ocaml-dune-configurator
<tissevert>which exists in our packages but for ocaml 4.09 only
<dstolfa>tissevert: rebuilding my local tree here to test
<tissevert>have you packaged it ?
<dstolfa>oh, i thought the package was in guix already, my bad
<dstolfa>so you're essentially hitting a build issue with some upstream ocaml package then?
<tissevert>I mean ok this one is broken, but I had been facing difficulties for at least an hour when I came here asking for guidance
<tissevert>it's more of a general question: when I made myself an environment with opam
<tissevert>I could install my target flawlessly
<dstolfa>well, using `guix import opam ...` will produce a sensible starting point for a package definition, but it might require some tweaks. i'm not sure if i can offer any more advice without digging into it more, but when i do these things, i usually do a `./pre-inst-env guix build --check <package name>` to make sure it builds as a standalone thing, and if it doesn't, then i investigate why
<tissevert>and I was wondering whether there was a way to reproduce what had happened in that environment to make a build process out of it
<tissevert>which is why I asked if someone knew whether opam was distributing source code only or if it had a way to retrieve pre-compiled binaries
<dstolfa>tissevert: i think it's source code, but don't quote me on that. my impression when installing things with opam is that it took way too long to be binary packages
<tissevert>ok, that's indeed a hint
<jab>civodul: maybe we need to update the manual.
<jab>I'll send you a patch
***apteryx_ is now known as apteryx
<mekeor[m]>has anyone joined the guix-hangout video-call yesterday? :D
<apteryx>what is the best way to have a SSH remote user's guix be the one used for non-interactive SSH commands?
<apteryx>seems hacking the .bashrc and executing scripts with an explicit !#/usr/env/bin bash shebang is one way
<apteryx>the question also applies to Guix System: ssh some-user@localhost which guix -> /run/current-system/profile/bin/guix; I'd like it to be /home/some-user/.config/guix/current/bin/guix.
<apteryx>this is usually setup for login shells on Guix System by reading /etc/profile, or /etc/profile.d/ on foreign distributions.
<jab>Hey guix!
<jab>also I'm getting closer to getting guix to manage my emails! I can send emails now, and I have dkimproxy-out running...but the email is not getting signed...yet.
<apteryx>jab: pretty cool!
<jab>but I have to be ssh-ed into the server to send the email...
<apteryx>will we get an entry in the cookbook when you get it working? That'd be awesome
<jab>For some reason I can't seem to send the email from my laptop email client. It's saying authentication failed plain...but I'll figure it out.
<jab>apteryx will do! raghavgururajan and I actually want to make an email-service-type. It'll assume various defaults. and set up all the underlying services that you need.
<jab>apteryx I'm at work now. I'm borrowing my config from roptat...I think. He actually already has a hislastname-email-service in his config. I don't have a link handy, but remind me and I'
<jab>I'll share it with you later.
<jab>and a cookbook example would be awesome. I actually want to try to create an MASSIVE cookbook entry to info manual that explains all of the DNS settings.
<jab>I found a guide online that was instrumental in helping me understand it all. I'll email said blog person and see if I can copy his blog for a manual. I think it's configuring rspamd with opensmtpd or something like that.
<apteryx>I'd be interested to proofread it and try it myself when it's ready
<apteryx>On another topic, I think this shebang may be useful to force /etc/profile and Guix environment setup when launching a script via SSH: #!/usr/bin/env -S bash -l
<apteryx>it'll cause /etc/profile to be sourced, which will cause /etc/profile.d/ to be sourced (on foreign distribution). ~/.bashrc should be sourced as well from ~/.bash_profile
<jab>apteryx I'm actually having fun using org babel to execute remote bits of code with :dir /ssh:joshua@lamora#59605:~/
<jab>I use a non-standard port. endlessh sits on port 22.
<the_tubular>Anyone knows how to mount a ZFS pool the guix way ?
<jab>the_tubular there is no officially supported way. ZFS is not and cannot be officially supported via licensing.
<the_tubular>Does that mean I can't use config.scm to mount my pool ?
<the_tubular>Because ZFS is installed and I can call the binary without problem
<the_tubular>Also, ZFS is inside the main guix channel ...
<bricewge>There was a good push earlier this year to support it on Guix System
<bricewge>But the service hasn't been merged yet
<the_tubular>So would running a bash script to mount the pools manually be the solution as of now ?
<the_tubular>Or is there something better I am not thinking of ?
<bricewge>I don't know I don't really care about ZFS, raid5atemyhomework is the one to ask on that front
<bricewge>Or maybe you could it's patch and there is documentation with it
<the_tubular>I'm trying to understand the link you sent
***jgart is now known as jgarte
***jgarte is now known as jgart
<the_tubular>Does raid5atemyhomework comes in IRC sometimes ?
<bricewge>I don't think so
<jab>the_tubular he was pretty active in the mailing list for a while.
<marusich>Anyone know how to list time zones from the tz database? Seems simple, never found a way to do it. Always end up looking at Wikipedia.
<leoprikler>big ol tree? :D
<civodul>marusich: the source of tzdata has text files that are very informative
<civodul>maybe not exactly what you're asking for though
<marusich>I see... That's fair. It's such low effort to just look it up on Wikipedia, I've never bothered...
<liltechdude>Hello, I'm recently rise up mail server and now have problem with certificate: "SSL error connecting ( unable to get local issuer certificate". Sorry for writing in this chat about that problem, but may be it's could somehow to be solved from guix part? I have already make pull and upgrade. Thunderbird works pretty well.