<graywolf>Hello :) Is there a way to make guix pack produce a .zip file instead? Assuming there is not, does anyone have a neat way to convert from the .tar.gz to .zip?
<nutcase>Hi, I'm trying to understand the output on https://ci.guix.gnu.org/ . I see that core-updates and cuirass jobs are not at 100%. Should I wait for 100% before doing a guix system reconfigure? Currently (since some days) my computer wants to build texlive, ghc, python and more on its own and I want to avoid that.
<nutcase>graywolf: tar xzf foo.tar.gz && zip foo.zip $(tar tf foo.tar.gz) ?
<f1refly>graywolf: you can't without extracting and repacking because there isn't really a good way to pipe both paths and contents in a way that both zip and tar understand
<f1refly>you could use a ramdisk for reduced disk wear and increased speed though if you plan on doing this a lot
<gabber`>mothacehe: aaaahh, i see, thanks! i was somewhat confused by u-boot-ts7970-q-2g-1000mhz-c-bootloader.. i guess we don't have an example of installing the bootloader into the EFI partition somewhere? i succeed to get firmware+u-boot running (which then fails to load an image through EFI) and i'm somewhat out of ideas
<graywolf>Hm maybe I should just add .zip support to the pack
<hako>nutcase: If you are on master branch and don't have changes from core-updates branch applied, you should only care about the "master" jobset. There's also a page for substitute availability on Guix QA: <https://qa.guix.gnu.org/branch/master>.
<nutcase>as you might notice in my paste.debian, I didn't do `guix archive --authorize`, but instead I did a `sudo guix archive --authorize`. With `guix archive --authorize` I got an error: open-file: Permission denied: "/usr/local/etc/guix/acl". I created a symlink /etc/guix/acl to /usr/local/etc/guix/acl and everything is fine now (I hope).
<nutcase>sudo is correct, I know, but it didn't point me into that direction
<nutcase>trying guix archive --authorize just gave me the information, what guix archive --authorize does (without any error).
<nutcase>* ... what `sudo archive --authorize` successfully does (without any error)
<nckhexen>Or al least, I use magit but haven't seen that prompt.
<efraim>cbaines: gnutls-3.8.1 should probably be hidden
<tux1c>anybody ever had trouble with nmcli reporting `plugin missing` on wifi devices? ive seen that issue on other distros and the fix was to install `network-manager-wifi` which seems to be built in to the normal `network-manager` on guix
<nckhexen>tux1c: I use NM (and wi-fi :) and have never seen that error, even in weird/minimal rescue environments. Guix's NM isn't even set up to handle plug-ins at all. Is there any specific action that causes the error?
<nckhexen>Scratch the ‘not set up’ part, it's in a patch.
<tux1c>nckhexen: i am just trying to configure wifi, the device doesn't show up in the GUI applet I have, nor am I able to connect to any networks through nmcli (funnily though, I am able to scan for networks through nmcli)
<nckhexen>tux1c: Guix's network-manager already provides libnm-device-plugin-wifi.so, so that error isn't to be taken at face value (maybe the search path is off, maybe ‘plug-in’ is a new euphemism for proprietary firmware, …). This isn't a new (~1 week) error, is it?
<tux1c>nckhexen: I have just finished installing and setting up guix for the first time, so I wouldn't know. I'll keep looking in other directions, then. thanks :)
<nckhexen>ACTION updated NM this week, but has been running that version for 2 weeks or so without issue.
<futurile>Q: when we want to investigate a build we use '--keep-failed'and source in 'environment-variables' file. I usually do that by creating a shell first: `guix shell --container --nesting --development <package> coreutils git. The problem is I want to keep the $PATH of the shell (so I can use the coreutils commands, git etc) but when I source in `environment-variables` I lose those. At the moment I
<futurile>land-up echo'ing the shells $PATH and then cutting-n-pasting the $PATH in after sourcing `environment-variables`. Is there a clever way to *add* the environment-variables or the shells existing $PATH so I don't have to do the cut-n-paste dance?
<civodul>futurile: hi! you probably want ‘--no-grafts’ so the container gets the ungrafted inputs, just like the origin build environment
<civodul>(that might explain why you didn’t get Coreutils on $PATH)
<PotentialUser-70>Hi, I have a slow working ci substitute and I have to add --substitute-ursl='bordeaux...' to make it much faster every time, so I tried to make bordeaux default using manual about services configuration but nothing work out, can someone help?
<nckhexen>This doesn't address your error (sorry, on 'phone, hard to spot nesting & other errors) but you have a duplicate %d-s that will cause pain later. (modify-services %d-s ...) *replaces* the first %d-s in your first append.
<lechner->Hi, how may I get a copy of all guix-related bug messages (control not needed) please?
<nckhexen>PotentialUser-70: Could you paste your entire configuration? It *might* help me spot the error, or someone else might.
<nckhexen>Ideally already correctly indented if your editor can do so.
<lechner->would someone please share a snapshot of the rsync data from debbugs.gnu.org?
<nckhexen>PotentialUser-70: OK, you're basically doing (services one-list another-list), which won't work. Fields take a single value. Do you see that now? I hope so :-p So you need to cut the entire (modify-services %d-s ...) expression, then replace the first %d-s with it.
<nckhexen>(services (append (list with gnome and friends) (modify-services %d-s ...)))
<Cassio>I'm trying to install Frescobaldi, and the installation fails while trying to install `python-poppler-qt5`. When I look into the log, I find out that the problem occurs in the build phase (`build_ext` command) of the `popplerqt5` extension. The error is thus reported: POPPLER_V21_01_0 -x QTXML_AVAILABLE -c build/temp.linux-x86_64-cpython-310 -b
<pastor>Please, anyone here could give me some insight on meson and cargo? I'm packaging a meson+cargo application. Last time mirai and snape gave me some hints on how to fix the missing configure flag problem on the meson's configure phase. I had some time to try their suggestions and indeed I've managed to fix it. Now I'm blocked in the build phase
<pastor>so, the problem is that cargo tries to fetch dependencies from crate which triggers network access. This is the problem: Updating crates.io index
<pastor>warning: spurious network error (2 tries remaining): failed to resolve address for github.com: Temporary failure in name resolution; class=Net (12)
<pastor>So looking at the messon.build that causes this I guess there are many unmmet dependencies that it's downloading from crates.io which we don't have packaged for Guix as of now. Should I package them by hand?
<pastor>maybe with `guix import` and make a big patch to the mailing list with cover letter and all?
<lilyp>pastor: you may not like it, but that's what pckaging rust stuff boils down to, yes
<pastor>I understand. But is it okay to flood guix with many packages? Isn't it going to be a problem for maintainers?
<mirai>Would it be bad design if `filter-configuration-fields' were to return multiple values (as S S
<mirai>(as S S') instead of that #:negate optional?
<mirai>or (S U\S) (iow, the selection and its complement)
<lucypoo>Hey there, im just bumping python to 3.12 for my own personal use, i dont know if i have the time to set up herd vm-s to test on all systems. anyone here working on this? i have a patch file which may be useful
<lechner->Hi, what does this mean when upgrading a shepherd-root-service, please? %exception #<inferior-object #<&action-exception-error service: root action: eval key: system-error args: ("fport_write" "~A" ("Broken pipe") (32))>>
<lucypoo>so perhaps file based sockets were in use for a pipe and went wrong?
<lilyp>fport just means it's backed by an fd – pipes have fds attached to them
<zamfofex>Hmm, I noticed something (whether it was ‘git send-email’ or something else, I don’t know) added some ‘prerequisite-patch-id’ to my recent patch 66654, but they aren’t actually necessary. 🤔 Is that a big issue?
<lilyp>you got a broken pipe somewhere, probably some receiving command died during the comm
<lilyp>zamfofex: they're mostly annoying but harmless, they come from having --base=auto
<zamfofex>lilyp: Very neat! One day, I dream of being at least partially as proficient at computing.
<ulfvonbelow>whenever I reconfigure, my static networking service fails to start until I manually tear it down and then restart it. Is there a reason the teardown isn't happening automatically when the networking service is replaced?
<lilyp>IIUC reconfigure doesn't kill running services – that'd cause more trouble than it's worth for most of them
<lilyp>imagine reconfiguring and then being thrown out of your login, for example
<ulfvonbelow>okay, but for some reason it's trying to restart networking and everything that depends on it
<ulfvonbelow>and failing, because instead of stop --> unload --> load --> start, it's doing unload --> load --> start
<ulfvonbelow>since static networking fails to start when the addresses or routes already exist
<lechner->lilyp / thanks! i really struggle with writing services in Guix. Can you see what's wrong in this one for the Heimdal KDC? https://bpa.st/TDAQ
<VesselWave>Hey, Guix! Does anybody know how to make a system Shepherd service to auto-start something?
<philip>Is anyone familiar with how ALSA finds plugins? I'm working on packaging Racket's `#lang video` (https://issues.guix.gnu.org/56534#3), which is implemented using FFmpeg and PortAudio. I have it building, but trying to use it fails with errors from ALSA lib trying to find files from libasound_module_conf_pulse.so. Apparently these are from the `alsa-plugins` package, but it's looking for them under the `alsa-lib` store output.
<redacted>It looks like nginx can be made to wait for shepherd services, but certbot isn't a shepherd service. Will I have to make a certbot shepherd service to get nginx to wait for a certificate?
<mirai>redacted: nginx x certbot is a bit complicated