IRC channel logs
2025-06-19.log
back to list of logs
<icy-thought>ieure how do I build the generated package locally ? <prpldmn>after upgrading my system mate does not use the nouveau driver, instead uses llvmpipe. Also gdm doesnt doesnt even display, the cursor is the only thing showing <ieure>icy-thought, Depends on where you put the file. <ieure>icy-thought, If it's in a standalone .scm file, put the symbol the package is bound to at the end, and `guix build -f blah.scm'. <Kabouik>I've used guix pack -RR some-packages -S /bin=bin and then rsynced the tar.gz to a foreigh distro where I'm not root, extracted all to ~/.local/bin, updated my PATH, and the new binaries are now found by which, but nothing happens when I run tham (no error). What could I be missing? <Kabouik>I also tried with just -R instead of -RR (which I had found in the Guix HPC documentation but I don't see what it does) and -S /bin=bin -S /etc=etc, then sourcing etc/profile, but same. <apteryx>uh, build of /gnu/store/k9xsw790i07d8n76xl3nl34c3zh85zw8-console-keymap.dvorak.drv failed <apteryx>ckbcomp: Can not find file "symbols/dvorak" in any known directory <apteryx>maybe (keyboard-layout "dvorak") no longer works, and one must now use (keyboard-layout "us" "dvorak") ? <podiki>apteryx: was this due to the upgrade (in mesa-updates) of xkbcomp (i think)? <loquatdev>I'm having a strange issue with shepherd. I'm currently using greetd-service-type to manage logging in and out on the TTY. Whenever I log into a shell and then log back out, the user's old shepherd service is still running. This happens every single time I log in or out, and I get the following error in the logs: <loquatdev>greetd: (mount.c:72): umount: /run/user/1000: target is busy. <loquatdev>greetd: (mount.c:903): unmount of none failed <loquatdev>I can do this over and over again, each time spawning a rogue shepherd process. Does anyone have any ideas as to what's going on? I should note that it will also duplicate all services specified in the home configuration, if any. <loquatdev>I discovered this issue but it does not give me a lot of hope: <jakef>ieure: hi Ian, are you familiar with DICOM? I'm looking for a review of PR #476 which adds Orthanc, a standalone DICOM server <csantosb>ieure: regarding the pr->review->approve-> merge workflow, do the approve and merge stages need to be executed by a different maintainer ? <Kabouik>Re: guix pack -RR (my message a few hours ago), I just found in another Guix-HPC blog post that the flag is for *reliably relocatable* packs. :> It doesn't seem to be documented in man guix or guix pack --help, and unless I didn't understand how to use it, it is not 100% reliable. <noe>Did you only extract the binaries from the archive? <noe>IIRC you need to keep the archive’s structure intact, I recommend you unpack the archive in a safe place then use symlinks from .local/bin to the archive/bin <Kabouik>Yes I did extract it noe, I now have a ~/.local/bin ~/.local/gnu/store ~/.local/etc, tried to source ~/.local/etc/profile just in case but that didn't help <Kabouik>I used guix pack -RR package1 package2 package3 -S /etc=etc -S /bin=bin, then just rsynced it and extracted with tar xf <noe>Yeah thats pretty good <noe>Try running it with strace to see what happens <noe>yup, looks like its not working alright <noe>doesn’t look very relocatable <noe>I guess try setting to different values GUIX_EXECUTION_ENGINE like it says on the manual <Kabouik>I haven't tried with a single package, maybe that would be more reliable, but that'd be surprising. <noe>Its supposed to wrap every binary <Kabouik>newfstatat(AT_FDCWD, "/gnu/store/ag1ppybrmka6c6vpc6r9z1gf8nkn9xv3-fish-3.7.1/bin//fish" <- is the double slash before fish expected? <noe>Probably some bad concatenation, but it acts like a normal / <Kabouik>The line ends with "-1 (No such file or directory) though" <noe>Yes, because ~/.local/gnu wasn’t mounted to /gnu, which is the job of relocatable <noe>Did you try just the bash example from the manual <Kabouik>No I hadn't found the manual you posted, sorry. Will try it now. <Kabouik>Nope, same issue with the `guix pack -RR -S /mybin=bin bash` example in the manual noe: I get no error but the binary is not actually running successfully. <noe>That's weird, can you upload your strace as a bug report? I'll take a closer look at it <Kabouik>Sure. Let me find how to report bugs with debbugs again; I need the manual. :p <Kabouik>Oh, it's done? Nice. I need to change my channels.scm too where I specifically set codeberg as mirror. <abbe__>is there a way to fill guix forgejo PR template with agit workflow ? <noe>You have an extra set of parenthesis after #:install-plan <dgr67> ,(string-append name "-" version "/") "share/icinga-php/ipl")) I get Invalid keyword: "share/icinga-php/ipl" <noe>Using list and #~ is the new style <dgr67> #~`(,(string-append name "-" version "/") "share/icinga-php/ipl")))? <dgr67>ERROR: In procedure %resolve-variable: <dgr67>noe, then I can't get name to resolve <flypaper-ultimat>dgr: you will want to ungexp `name' (and version), that is to say write (string-append #$name "-" #$version" "/") <oceane>hi, i'd like to port oniux to guix, is there a way to show <flypaper-ultimat>dgr: but even easier would be (list #:install-plan #~'(#$(string-append name "-" version") "share/icinga-php/ipl")) <oceane>i'm not really sure of what i'm going to do here, is there a comprehensive tutorial in e.g. the guix cookbook? <flypaper-ultimat>(actually i wonder if that is already in, the article uses future tense) <jakef>i am waiting for it to land! going to try packaging the ruff python linter <noe>dgr67: try using #$ instead of , <icy-thought>How do I view build logs in guix? I was trying to import a haskell package (taffybar) and it now complains about a package not being built (haskell-gi-base) and the drv is a binary file <civodul>icy-thought: when ‘guix build’ prints “View built log at /var/log/guix/…”, you can open that file with ‘zless’ on the command line <sneek>civodul, you have 2 messages! <sneek>civodul, apteryx says: should we sunset the guix-commits mailing list? I see no one subscribed to it, and it's still watching the old Savannah repository, which is a mirror. Seems a waste of resources. <icy-thought>civodul oh did not know that! Maybe we should mention 'zless' in the output <civodul>apteryx: i am subscribed to guix-commits actually, and during the GCD discussion, someone said they were hoping it would still work after migration (which it does) <apteryx>strange, I don't see the list of subscribers in the mailman admin interface; it appears empty <civodul>apteryx: no strong opinion though, so perhaps it’s worth doing a quick poll to get an idea of where we’re at <apteryx>what benefit does it have over git fetch && git log FETCH_HEAD ? <apteryx>just the nls commits often weigh like 14 MiB or more, fill a mailbox quick <civodul>not to mention the rebases of ‘go-team’ and the likes :-) <apteryx>I feel bad for the savannah folks for having to archive this forever. <civodul>(i was actually considering unsubscribing because of this) <civodul>cbaines: does the Data Service get data from guix-commits these days? <icy-thought>Where are the haskell package maintainers usually residing? <cbaines>civodul, I think it's fine to get rid off, and would be one less use of my mailserver <apteryx>cbaines, civodul I've just sent a proposition to turn it off to guix-devel <apteryx>let's see if there are some die hard users or not. <civodul>cbaines: so data.guix.gnu.org wouldn’t lose anything if we turn it off, right? <remyd1>Hello,I have a build on which derivation failed. Is there a way to remove the cache / downloaded file to rebuild it in a more cleaner way ? <j8>hello, why is the package installed via “guix package” has less precedence over packages installed via “guix home reconfigure” in PATH variable? <ieure>Does anyone have an EXWM (or other plain-WM) setup with a working system keyring? <Tre333>Guix says that is is based on Nix, how hard would it be to convert a nix package to a guix one, I am brand new to guix <ieure>It used to be that element-desktop would ask me to enter my password again to unlock the keyring when launching. The current version just says I have "an unsupported keyring" and the database cannot be opened. <ieure>Tre333, The build facilities are very different and there's not a tool to convert 1:1 that I'm aware of. `guix import' can help you create packages from various upstream sources. <podiki>ieure: there were upstream electron changes, there's some discussion on the element GitHub I saw (on a train so can't find it quickly). I had to just allow some weaker or alternative encryption but I don't have any keyring anyway <umanwizard>Hello... How can I use the core-packages-team branch for guix system reconfigure? I tried sudo guix time-machine --branch=core-packages-team -- system reconfigure ~/config-desktop.scm <umanwizard>However, this failed because ~/config-desktop.scm references some things in my personal channel which were apparently not getting picked up <umanwizard>I.e. it appeared this was not respecting my ~/config/guix/channels.scm