IRC channel logs
2025-09-07.log
back to list of logs
<ekaitz>vagrantc: what do you mean? where is inherit defined? isn't it part of guix/records.scm? <sneek>ekaitz, csantosb says: -P1 pkg1 -P1 pkg2 ... with a high number of packages becomes unpractical <ekaitz>vagrantc: but was that your question? or I'm answering something you didn't ask? <vagrantc>i tried searching with "git grep 'define.*inherit' <vagrantc>now the part is ... how do i get inherit into my system config? <ekaitz>so you won't find it within a define <vagrantc>i have working configs with inherit, but there is nothing obvious in the (use-* that pull it in <ekaitz>hmmm that's hard to explain and i'm not very good at macros either <ekaitz>but it feels like inherit doesn't really exist alone <vagrantc>and trying to move it to a more simplified ocnfiguration <ekaitz>but in the context of a guix/record <vagrantc>ice-9/boot-9.scm:1685:16: In procedure raise-exception: <ekaitz>i'd say inherit is just part of a record definition, not a procedure <vagrantc>it is also entirely possible i toped something... <ekaitz>vagrantc: yes! look at gnu/services.scm modify-services <ekaitz>and there's where you have the inherit defined <ekaitz>vagrantc: the inherit has to be inside of a record definition, and yours isn't <vagrantc>just. want. to. do. a. simple. thing. :( <ekaitz>it's more or less the same I mentioned before, the inherit lives inside a record definition, if you are not in one, you cannot use it <vagrantc>yeah, thanks ... i will have to admit a big understanding gap here, though. :) <ekaitz>vagrantc: you are "just" missing a (guix-configuration ...) around the inherit <ekaitz>a guix-configuration is a record <vagrantc>yes, i missed that from the system where it was working <ekaitz>vagrantc: if you want to "fully" understand it, you could think that `inherit` can only happen in something that returns a guix/record <ekaitz>most of the guix configurations are records <ekaitz>the deeper understanding is that inherit is syntax that can only appear inside syntax that produces the records <vagrantc>makes sense, just hard to get my head around that based on the error spewed out :) <ekaitz>similar to what JavaScript enhanced object literals do <vagrantc>and going on the rabbit hole adventure "where does inherit come from..." <ekaitz>the good thing of this kind of errors is that you can use them as an excuse to learn more <vagrantc>sometimes i have it in me, though i thnk i hit a wall with guile/guix years ago... <ekaitz>if it helps, I didn't know about how did all this work and that's why I tried to help you <vagrantc>i lean pretty heavy on the community aspect for things like that <vagrantc>ekaitz: glad someone was able to learn from my struggles :) <FuncProgLinux>did copy-build-system change? It's throwing me a Unbound variable: copy-build error but I don't have anything remotely named like that :O <FuncProgLinux>nvm I was missing a module inside my build-system arguments -facepalm- <FuncProgLinux>Why would guix not find a file present inside the checkout? if (invoke "ls") shows the file there š¤ <efraim>getting an error in enosys-ioctl in util-linux's test suite on powerpc-linux <Aidansw>Hi, I want to package an AGPL licensed project(Joplin-App) the issue is "JoplinĀ® is a trademark of JOPLIN SAS registered in the European Union, with <Aidansw>filing number 018544315. ... The Joplin logos and icons are copyright (c) Laurent Cozic, all rights reserved, <Aidansw>and may not be used without a permission." in the license.Ā Would this inhibit it from being on the Guix main channel?Ā Because I remember that being one of the issues with Firefox <danlitt>I've installed icedove with `guix install icedove` but when I try to run it, I see: icedove: symbol lookup error: /gnu/store/5h2w4qi9hk1qzzgi1w83220ydslinr4s-glibc-2.33/lib/libpthread.so.0: undefined symbol: __libc_pthread_init, version GLIBC_PRIVATE. Is this probably a bug, should I report it on codeberg? <Deltafire>interesting, libpthread is located at /gnu/store/z051rpiy1109ph5dkkpwbyp7h89rqgxn-gcc-toolchain-15.1.0/lib/libpthread.so.0 for me <awth13>hi! is there any other setup required for libvirt VMs aside from adding your user to "libvirt" and adding the libvirt service to the operating-system? <danlitt>@Deltafire I was pretty sure I had updated recently (guix pull was only a week ago) but perhaps I hadn't done a system reconfigure. I'll try that first :) <Deltafire>just realised mine is still on the 2nd Sept commit 7f86f1eae0d7bec64e9c5ecdc7a535be32976e62 due to a breakage in another package <Deltafire>also.. just noticed that the guix describe links are clickable :) <c0co>does software that's written in Go require any heavy lifting with build processes for a Guix package or is Go self-sufficient enough that it's as simple as a repository entry + package definition? <awth13>qemu is installed and working (with or without KVM), libvirtd daemon is running, socket for qemu:///system exists but then as soon as I try to do something with this socket in virt-manager, libvirtd crashes <serok>hello, my `guix pull --list-generations` and `sudo guix pull --list-generations` give different results how to fix it ? <serok>really it's normal? because currently I cannot do `sudo guix system reconfigure` neither rollback, yes I'm using guix OS <Rutherther>serok: sudo guix system reconfigure uses your user's guix, not root's, sudo guix pull is irrelevant for it. Really, sudo guix pull is unnecessary on Guix System, as long as you don't actually switch to root <Rutherther>serok: if you cannot do that, what error does it give? <serok>`guix system: error: unrecognized boot parameters at '/var/guix/profiles/system-2-link/parameters'` <serok>there is a hint to do `guix pull` but it doesn't helpĀ :/ <awth13>Rutherther: is it possible to run system reconfigure as root? I understand why I don't want to do that 99% of the time but wonder if it is possible at all <serok>I was trying it already but guix reconfigure as root lead to the same error <serok>and the `parameters` file is empty <awth13>serok: sorry my question is unrelated to your issue -- you should not have to run reconfigure as root <Rutherther>serok: the logic for that that hint coming up is too simplistic. It doesn't make sense for you. You have a corrupt parameters file, you need to get rid of it <Rutherther>serok: the easiest way to do that is probably going to be to boot to previous generation and then remove the generation with empty parameters file. Can you do that? <Rutherther>awth13: I don't really understand what you mean run as root, you always run it with sudo, so it's ran as root. Sure you could also login as root completely, it doesn't matter. Just make sure to use the proper guix, if you pull just as a user, you should probably use the user's guix instead of root's to be up to date to that <serok>the problem is that my newest generations is corrupted freezing on some Xorg failure and I cannot do anything with mouse nor keyboard <serok>so I can boot only with previous generations that is locked because of this `parameters` file <awth13>Rutherther: for context, yesterday we were trying to change the username of a user on a Guix system and ran the reconfigure from this user's shell, which led to some issues <Rutherther>serok: the previous generation is not 'locked up' because of this 'parameters' file. All generations are 'locked up' now, you wouldn't be able to reconfigure from any generation... What generation number are you booted to now? <awth13>Like not being able to `sudo reboot` after reconfigure completed <awth13>I assume this is that rare case when running reconfigure logged in as root would be preferable <Rutherther>awth13: yeah, I can imagine that, removing a user who is logged in doesn't seem ideal. If it's the main user, I would probably switch to root and do "/var/guix/profiles/per-user/<the user>/current-guix/bin/guix system reconfigure ..." <awth13>Rutherther: thanks, this makes sense! <serok>so I've just switched to root and do "/var/guix/profiles/per-user/<the user>/current-guix/bin/guix system reconfigure ..." but I'm getting still the same error <serok>it's weird because my guix os on my current generations works ok, I can test new packages, build images, etc but I cannot rollback or reconfigure the system anymore <Rutherther>it's not weird, an assumption guix is making is violated. You need to make it not violated - remove the generation with wrong parameters. You're not going to workaround this by switching to root <Rutherther>unfortunately guix is not made to withstand file corruptions like that <serok>`rm: cannot remobe '/var/guix/profiles/system-2-link/parameters': Read-only file system` <Rutherther>I never said to remove the parameters file, I said to remove the generation... please just answer the questions I make so I can help you <serok>how to do it, how to remove a specific generation ? <Rutherther>normally you would do guix system --delete-generation, but that's not going to work now, so you just rm /var/guix/profiles/system-2-link <serok>thanks that seems to work, it's reconfiguring now <Rutherther>anyone here understands perl cross-compilations? I am trying to get a package to cross compile; It seems to use $Config{lddlflags} and such, and those seem to have the glibc relevant to build platform in them, not target one :/ <makx>What are the plans for openssl 3.5 in guix? is it "hard" to bump 3.0 to 3.5? Any (other) good place where I can find out about this? <tln>Hello folks, two questions: 1. anyone else having an issue with their gnome and/or mate config reconfiguring/instantiating? Keep getting error conflicting entry for libxml2. 2. Even if I remove gnome from my config and successfully reconfigure, I'm "stuck" on kernel 6.15.11 <sneek>tln, lechner says: / thanks! <Rutherther>tln: as for linux version, how are you referring to it? linux-libre symbol is on 6.15, so you would have to do linux-libre-6.16 to get 6.16 <tln>Rutherther many thanks! My duckduckgo-fu is off. I'll make sure to check codeberg specifically from now on. I'm just performing an upgrade via "guix pull" and then "sudo guix system reconfigure /etc/config.scm" and not getting latest kernel. After guix pull, the latest news is that 6.16 is current <Rutherther>tln: I don't see such message in news, looking at the latest commit. I only see that linux libre 6.16 will be made default soon, not that it already has been <tln>Rutherther just read the full commit.... Indeed it says it is available but not made default yet.... reading comprehension is hard..... <tln>Rutherther thanks for the quick response and knowledge <FuncProgLinux>I'm impatient about the mate fixes. I wanted to upstream two more missing packages :( although I just think I either discovered a bug or I'm misunerstanding guix's file system hierarchy <ieure>FuncProgLinux, What do you think the bug is? <FuncProgLinux>ieure: I've spent like half a year hunting down the applets not showing bug that has been since 2022 (afaik). I ended up doing some package variants inheriting the packages from Guix. When reading the output for some of them Guix tells you that no binaries under /libexec were wrapped. But it reports a different number if you do set the configure variable explicitly as #:configure-flags #~(list (string-append "--libexecdir=" #$output "/libexec") <FuncProgLinux>In the end all it took was an environment variable for the applets. It did force me to practice how to package things in Guix though... <ieure>FuncProgLinux, What's the default libexecdir set to? That stuff should all end up under the prefix dir, which the build-system sets for you. <ieure>Could be an upstream bug if libexecdir isn't prefixed. <FuncProgLinux>ieure: That I don't know for sure. I've read the configure.ac files but no mention of that is present. I just noticed after setting it myself explicitly. I've packaged .deb and .rpm before so I based my derivatives on such practices (bad idea)