bug#58203: Cuirass fails to respect (target-x86-32?) in some circumstances

Hi Marius, (Cc: Mathieu for the search box issue below.) Marius Bakke skribis: > Ludovic Courtès skriver: [...] >> The good news is that with today’s ‘staging’, everything’s fine: > > Not quite: > > https://ci.guix.gnu.org/search?query=system%3Ai686-linu

bug#58149: guix pull error

Hi Matthieu, I figured there’s an easier option: guix build \ /gnu/store/n8vdar2f60mvq62g7mngpqwykbm9rw1q-guix-1.2.0rc2-1.0d4b1af sudo -i guix package -r guix -i \ /gnu/store/n8vdar2f60mvq62g7mngpqwykbm9rw1q-guix-1.2.0rc2-1.0d4b1af This will install Guix 1.2 in root’s profile (with

bug#42162: gforge.inria.fr to be taken off-line in Dec. 2020

Hello, Maxim Cournoyer skribis: > zimoun writes: > >> Hi, >> >> On Thu, 29 Sep 2022 at 23:10, Maxim Cournoyer >> wrote: >> >>> Wholly agreed, this thread is already too long and the original problem >>> was fixed. Closing. >> >> I disagree, the original problem is not fixed; as I explained.

bug#58149: guix pull error

Hi, Matthieu Haefele skribis: > Le 03/10/2022 à 16:03, Ludovic Courtès a écrit : [...] >> You should be able to get around it by first building things locally: >> >>guix build --no-substitutes \ >> $(guix gc --derivers >> /gnu/store/r658y3cgpnf

bug#58204: guix system reconfigure hangs silently when substitute server is unreachable

Hi, Maxim Cournoyer skribis: > While fixing up Berlin today, I had to use '--no-substitutes' on the > daemon started per 'info (guix)Chrooting', otherwise it'd hang up > without printing any of the warnings (totally silent). Using strace, I > could see: > > guix substitute: warning:

bug#58149: guix pull error

Matthieu Haefele skribis: >> So you’re right, we have to go a bit further back in time! Apparently >> v1.2.0 will do, so: >> >>guix pull --commit=a099685659b4bfa6b3218f84953cbb7ff9e88063 >> > Not better unfortunately... > > (base) mhaefele@mdlspc113:ksp $ sudo -i guix pull >

bug#58149: guix pull error

Hi, Matthieu Haefele skribis: >> I would suggest doing a two-step upgrade; first upgrade to 1.3.0: >> >>sudo -i guix pull --commit=a0178d34f582b50e9bdbb0403943129ae5b560ff > > Are you sure this commit is old enough ? I still get the same error. > By the way, a general question, where can

bug#58149: Letting clients warn about old daemons

Hi, (Cc: Mathieu O. + Maxim.) Matthieu Haefele skribis: > I worked intensively with guix this summer, I did not get any > deprecation warnings, I am quite sure. And I still do not get any. So > might be a good idea to check the deprecation machinery. > > (base) mhaefele@mdlspc113:~ $ guix

bug#58090: Missing bin/ffplay in ffmpeg@4

Hi, Zhu Zihao skribis: > citreu@asus-laptop:~$ guix describe > Generation 1149月 26 2022 13:24:04 (当前) > guix 754ce58 > repository URL: https://mirror.guix.org.cn/git/guix > branch: master > commit: 754ce586e013582b0f6d28337fdc46db35395997 > citreu@asus-laptop:~$ guix

bug#58040: "guix style" puts closing parentheses on the wrong line

Hi, Maxime Devos skribis: > and running "guix style -f a.scm" on it, it becomes > > (define (find-latest-release releases) > (fold (match-lambda* (((key . value) result) > (cond > ((even-minor-version? key) >(match

bug#58205: reconfiguration stuck unless using '--no-grafts'

Hi, Maxim Cournoyer skribis: > While working on Berlin today from a chroot, and with --no-substitutes > used for guix-daemon, I wasn't able to complete the 'guix system > reconfigure' step; it'd hand on a read call (seen using strace): > > statfs("/gnu/store", {f_type=BTRFS_SUPER_MAGIC,

bug#57490: UPower ignores ‘critical-power-action’

Hi! Maxime Devos skribis: > On 05-09-2022 14:56, Ludovic Courtès wrote: >> I’d like to test whether UPower invokes the intended critical action, >> but I’m not sure how to simulate a low battery level. Thoughts? > > I've found a 'Virtual Battery Driver': https://lw

bug#42162: gforge.inria.fr to be taken off-line in Dec. 2020

Hi, zimoun skribis: > On Thu, 29 Sep 2022 at 23:10, Maxim Cournoyer > wrote: > >> Wholly agreed, this thread is already too long and the original problem >> was fixed. Closing. > > I disagree, the original problem is not fixed; as I explained. What would you think of opening specific issues

bug#58203: Cuirass fails to respect (target-x86-32?) in some circumstances

Marius Bakke skribis: > Hello, > > I noticed Cuirass attempts to run imath tests on i686-linux: > > https://ci.guix.gnu.org/build/739643/details Following the links, this corresponds to , itself corresponding to commit

bug#58149: guix pull error

Hi, Matthieu Haefele skribis: > (base) mhaefele@mdlspc113:work $ > /var/guix/profiles/per-user/root/current-guix/bin/guix-daemon --version > > guix-daemon (GNU Guix) 1.0.1 It’s indeed a pre-lzip version¹. Normally, ‘guix’ commands have been printing a message reading “Your Guix daemon is

bug#42162: gforge.inria.fr to be taken off-line in Dec. 2020

Hi, zimoun skribis: > This “meta” bug raises 2 levels of issues for long-term: > > 1. save the source code, > 2. save the current binary substitutes. Maybe we can close this bug and open an issue for each of these, or discuss them on guix-devel until there are actionable items that come out

bug#58084: guix deploy fails, leaving the newly installed system generation active

Hi, Maxim Cournoyer skribis: > Maxim Cournoyer writes: > > [...] > >>> … which is fine, except that there was already a pre-existing >>> /etc/modprobe.d directory (coming from openSuSE, the distro that was >>> initially installed on this machine), which caused this activation code >>> to

bug#58149: guix pull error

Hi, Matthieu Haefele skribis: > Well, I installed guix on my laptop (with ubuntu) the very standard > way described on guix website. It was back in January 2020. OK. Lzip support was added sometime in 2019: . Could you

bug#58149: guix pull error

Hi Matthieu & Simon, zimoun skribis: >> (base) mhaefele@mdlspc113:work $ guix pull [...] >> guix/ui.scm:1747:12: In procedure run-guix-command: >> unsupported compression scheme lzip Matthieu, how did you install guix-daemon? The daemon provided in the binary installation tarball at

bug#57978: bug#58017: [PATCH 0/2] Retry nar downloads upon failure

Hi, Ludovic Courtès skribis: > substitute: Split nar download. > substitute: Retry downloading when a nar is unavailable. Pushed as 8bd4126917f59f4af9a4323c3d5699201862dca2. The ‘guix’ package has yet to be updated. Thanks, Ludo’.

bug#58036: kernel module not found "pata_acpi" in linux-libre-5.19.10

Hi, Ludovic Courtès skribis: > Maxim Cournoyer skribis: [...] >> gnu/build/linux-modules.scm:257:5: kernel module not found "pata_acpi" >> "/gnu/store/nmdy7c4i34y12w8af7zl6sl9fmrp8wa0-linux-libre-5.19.10/lib/modules" >> builder for `/gnu/sto

bug#58044: Localization: "info guix" always shows the manual in English regardless of the user locale

Hi, Luis Felipe skribis: >> https://lists.gnu.org/archive/html/bug-texinfo/2019-05/msg00011.html >> > >> is relevant. > > Thanks for the info, Florian, I had no idea about that :) Your expectations are legitimate though; I think it’d be worth bringing it up again on bug-texi...@gnu.org if you

bug#58048: The boot process can't delete old /tmp when it contains non-UTF-8 file names

Maxime Devos skribis: > On 24-09-2022 23:12, Maxime Devos wrote: >> Will try to catch the exact warning message and write a reproducer >> at the next boot, for now I write it here before I forget about it. > > Two reproducers: > > (1) Compile ripgrep and somehow let it fail (but after it creates

bug#58084: guix deploy fails, leaving the newly installed system generation active

Hi, Maxim Cournoyer skribis: > While attempting to deploy to overdrive1, using the 9971141 commit in > the maintenance repo, I encountered the following error: > > maxim@hurd ~/src/guix-maintenance/hydra$ guix time-machine > --commit=08d515233241ee0921b8b5ab706f98170c62437c -- deploy -L

bug#58036: kernel module not found "pata_acpi" in linux-libre-5.19.10

Maxim Cournoyer skribis: >>> gnu/build/linux-modules.scm:257:5: kernel module not found "pata_acpi" >>> "/gnu/store/nmdy7c4i34y12w8af7zl6sl9fmrp8wa0-linux-libre-5.19.10/lib/modules" >>> builder for `/gnu/store/x9qdj37d6l2yacc73bx284ggj6vkhcdv-linux-modules.drv' >>> failed with exit code 1 >>

bug#58036: kernel module not found "pata_acpi" in linux-libre-5.19.10

Hi, Maxim Cournoyer skribis: > While attempting to reconfigure the overdrive1 aarch64 machine, I got: > > substitute: ^Msubstitute: ESC[Kupdating substitutes from > 'https://ci.guix.gnu.org'... 0.0%^Msubstitute: ESC[Kupdating substitutes > from 'https://ci.guix.gnu.org'... 100.0% > @

bug#57922: Shepherd doesn't seem to correctly handle waitpid itself

Hi, Josselin Poiret skribis: > Maxim Cournoyer writes: > >> This leads me to believe that Shepherd does not block until the process >> is actually dead to mark the process as stopped (it just waitpid on the >> group pid with WNOHANG), which means it won't block if the child process >> hasn't

bug#57978: [bug#58017] [PATCH 2/2] substitute: Retry downloading when a nar is unavailable.

Hi Maxime, Maxime Devos skribis: >> +(test-equal "substitute, first URL has narinfo but nar is 404, both URLs >> authorized" >> + "Substitutable data." >> + (with-narinfo* >> + (string-append %narinfo "Signature: " >> + (signature-field %narinfo)) >> +

bug#57978: [PATCH 2/2] substitute: Retry downloading when a nar is unavailable.

Hi! zimoun skribis: >> + (with-narinfo* >> + (string-append %narinfo "Signature: " >> + (signature-field >> + %narinfo >> + #:public-key %wrong-public-key)) >> + %main-substitute-directory >> + >> +(with-http-server

bug#57576: bug#57599: [PATCH] openpgp: Add support for ECDSA with NIST curves.

Hi! All things considered, I prefer to drop this patch. In the unlikely event that we’ll get more requests to support these curves, we can always revisit the issue. What we should do, though, is improve error reporting in case an unsupported curve or algorithm is encountered. Thanks, Ludo’.

bug#57217: home-openssh-service-type creates .ssh/config with wrong permissions

Ludovic Courtès skribis: > To address the issue at hand, we would need to map UID 0 of the host as > UID 0 of the guest, but I’m not sure this can be done. I believe it cannot be done: we can only map a single UID (at least unless/until we use subordinate UIDs.) Back to the original p

bug#58031: LibreOffice 7.3.5.2 is not reproducible

There’s a single file that differs: --8<---cut here---start->8--- $ guix describe Generation 228 Sep 12 2022 08:17:50(current) guix e3ed1d0 repository URL: https://git.savannah.gnu.org/git/guix.git branch: master commit:

bug#57217: home-openssh-service-type creates .ssh/config with wrong permissions

Hi Elias, Elias Kueny skribis: > The files are created with too open permissions, so ssh refuses to run: > > $ ssh xxx > Bad owner or permissions on ~/.ssh/config > > $ ls -l .ssh > lrwxrwxrwx 1 user users 59 Aug 14 18:17 authorized_keys -> >

bug#57922: Shepherd doesn't seem to correctly handle waitpid itself

Hi, Josselin Poiret skribis: > Maxim Cournoyer writes: [...] >> 1. It requires to be installed in the signal handlers for each >> processes, with something like: >> >> --8<---cut here---start->8--- >> (unless %sigchld-handler-installed? >> (sigaction

bug#57978: [PATCH 2/2] substitute: Retry downloading when a nar is unavailable.

Fixes Reported by Attila Lendvai . Previously, if a narinfo was available but its corresponding nar was missing (for instance because the narinfo was cached and the server became unreachable in the meantime), 'guix substitute --substitute' would try to download

bug#57978: [PATCH 1/2] substitute: Split nar download.

* guix/scripts/substitute.scm (download-nar): New procedure, with most of the code moved from... (process-substitution): ... here. Call it. --- guix/scripts/substitute.scm | 52 +++-- 1 file changed, 32 insertions(+), 20 deletions(-) diff --git

bug#57978: [PATCH 0/2] Retry nar downloads upon failure

issues such as transient networking failures. Comments? Thanks, Ludo’. Ludovic Courtès (2): substitute: Split nar download. substitute: Retry downloading when a nar is unavailable. guix/scripts/substitute.scm | 157 +++- tests/substitute.scm

bug#57978: the fallback machanism for substitute servers doesn't work?

Hi, Attila Lendvai skribis: > guix substitute: warning: ci.guix.gnu.org: connection failed: No route to host > qemu-minimal-7.1.0-doc 3.4MiB >876.6MiB/s 00:00 > [##] 100.0% >

bug#57827: Shepherd 0.9.2 possible regressions

Hi, Mathieu Othacehe skribis: > Regarding those four, I was able to reproduce the issue this way: > > $ guix repl > (stop-service 'guix-daemon) > (start-service 'guix-daemon (list (number->string (getpid Or from the shell: herd stop guix-daemon herd start guix-daemon $$ I was able to

bug#57490: UPower ignores ‘critical-power-action’

Ludovic Courtès skribis: > I pushed these patches: > > eedf71f948 * services: upower: Default to a percentage-based policy. > 4765242540 * services: upower: Update default percentage values. > > I’m not sure whether they help, but they might: using a > time-

bug#57543: emacs-telega is broken

Hello, Giovanni Biscuolo skribis: > IMHO yes, we should revert the tdlib upgrade /or/ keep a packaged > tdlib@1.8.0 used by emacs-telega v. 0.8.3 [...] > If I don't get it wrong, I still have commit access to the guis repo so > I could revert the commit on tdlib, but I'd like to have an OK. >

bug#57581: Failing to build the website

Hi, "pelzflorian (Florian Pelz)" skribis: > zimoun writes: >> The culprit seems the package ’qtserialport’ in ’packages-builder’ from >> (apps packages builder). Maybe introduced by commit >> 1ef04fb2288dade3ad2883026ae286a68ef13a1e. > > This was a first failing commit for me too, but the

bug#57077: guix-jupyter fails a test

Hi, Ludovic Courtès skribis: > Andreas Enge skribis: > >> guix-jupyter currently fails to build with the error message below. While I >> noticed it when updating python-sympy, the problem was already present >> before. > > It looks like the Jupy

bug#57677: GIMP retains reference to GCC

>From ca. commit 2183db8d2ab773f41e4320367645880b06959bfc: --8<---cut here---start->8--- $ guix size gimp | head -4 store item totalself /gnu/store/wdm2s2si8fqsrcd5xpc29ivmpkf20s8d-mesa-21.3.8

bug#57576: bug#57599: [PATCH] openpgp: Add support for ECDSA with NIST curves.

Hi, Thanks a lot for the explanations, Andreas! As you write, the decision will be “political” as there’s no scientific evidence to guide us. I’d like to see what other free software OpenPGP implementors decided (primarily Sequoia; GnuPG/Libgcrypt implement them). Ludo’.

bug#57316: (core-updates) dejagnu@1.6.3 sometimes fails to build

Maxime Devos skribis: > I cannot reproduce the test failure locally myself. > > * gnu/packages/dejagnu.scm (dejagnu)[#:out-of-source?]: > Do an out-of-source build, as recommended upstream, and > add a link to the upstream bug report. Pushed in ‘core-updates’ as

bug#57576: bug#57599: [PATCH] openpgp: Add support for ECDSA with NIST curves.

Hi, (Cc’ing Andreas for extra advice.) Maxime Devos skribis: > We disallow signing with SHA-1, because it is known to be vulnerable > and as there are alternatives that are considered good, even if this > limits what users can do with their OpenPGP keys. Right, we know it’s affordable to

bug#57576: bug#57599: [PATCH] openpgp: Add support for ECDSA with NIST curves.

Hi, ECDSA and the NIST curves (and in fact a large part of NIST’s crypto standardization work¹) are actually considered with skepticism by some: https://en.wikipedia.org/wiki/Elliptic_Curve_Digital_Signature_Algorithm#Concerns That makes me wonder whether supporting them is a good idea,

bug#57467: 'guix shell' does not honor default behavior when given a specific command to run

Maxime Devos skribis: > On 05-09-2022 15:06, Ludovic Courtès wrote: >> The main difficulty here is that, should we eventually decide to change >> behaviors, we’ll have to devise a migration timeline etc. (As an >> example, we chose to keep ‘guix environment’ until at l

bug#57576: Missing support for NIPT-P384 gpg algorithm in Guix channel authentication.

Hi, Zhu Zihao skribis: > I'm working with my private channel, And I update my gpg key using > NIPT-P384 algorithm. But `guix time-machine` complains that: [...] > 226:4 6 (authenticate-commit # # …) >129:23 5 (commit-signing-key _ # …) > In guix/openpgp.scm: >562:26 4

bug#57467: 'guix shell' does not honor default behavior when given a specific command to run

Hi David, Thanks for your feedback on this. "Thompson, David" skribis: > So there are some competing expectations here. The status quo is that > non-interactive invocations of 'guix shell' will not load a guix.scm or > manifest.scm file unless explicitly told to via --file/--manifest following

bug#57490: UPower ignores ‘critical-power-action’

Hi, Ludovic Courtès skribis: > One issue remains: UPower should have called elogind’s “PowerOff” method > for ordered shutdown before total power outage, but either that didn’t > happen or elogind didn’t do it right (which is weird, because ‘loginctl > poweroff’ DTRT.) I pushed t

bug#57583: Guix cannot resume after hibernation

Hi, Josselin Poiret skribis: > Yusuf Talha via Bug reports for GNU Guix writes: > >> I haven't encountered this problem on any other distros.  You probably >> realized that I encrypted my disk.  Hibernation wasn't working while I was >> using Guix without encryption a few months ago either. 

bug#57593: Racket 8.6 is not reproducible

Hey, Just noticed that Racket does not build in a reproducible fashion: --8<---cut here---start->8--- $ guix describe Generation 227 Sep 04 2022 23:39:52(current) guix aae98c2 repository URL: https://git.savannah.gnu.org/git/guix.git branch:

bug#57095: 'terminal-window-size' throws ENOTTY ("Inappropriate ioctl for device")

Hi, Maxime Devos skribis: > Maybe my answer on IRC is relevant here: > > https://logs.guix.gnu.org/guile/2022-09-01.log#231503 Interesting. It’s a Guile bug, and a tricky one. Here’s what Andy wrote on IRC: civodul, wingo says: i believe it is a bug. in a pre-unwind handler, you

bug#55898: Services depending on new Shepherd features may fail until reboot

Hi Maxim, Maxim Cournoyer skribis: >> Currently, new services don’t fail to run: we arrange so that new >> services always “work”, whether they’re talking to an old shepherd or a >> new one. The user experience (bugs aside) should be good: services are >> always reloaded. > > This depends on

bug#57095: 'terminal-window-size' throws ENOTTY ("Inappropriate ioctl for device")

Hi, Josselin Poiret skribis: > We also use a big wrapping `with-error-handling` to display errors > properly in the case when they are not caught. The difference is that > `with-error-handling` adds a non-unwinding handler, while catch is > unwinding. My first thought was that non-unwinding

bug#57090: 'guix style' pretty-printer always renders integers as base10

Hi, Ludovic Courtès skribis: > Now, we could tweak the pretty printer so that it recognizes patterns > where numbers or strings should be printed in a certain way. I did that in c3b1cfe76b7038f4030d7d207ffc417fed9a7ead. Lemme know how you like it! :-) Ludo’.

bug#57474: compute-guix-derivation fails due to insufficient memory

Hi, "Michael F. Lamb" skribis: > I was following the instructions in the Guix Reference Manual for running > Guix in a VM using the pre-built qcow2 VM image: > > https://guix.gnu.org/manual/en/guix.html#Running-Guix-in-a-VM > > The documentation instructs me to create a qemu VM with the option

bug#55898: Services depending on new Shepherd features may fail until reboot

Howdy! Maxim Cournoyer skribis: > I had something different on mind; I was thinking of some added field to > our shepherd-service object where the minimal version of Shepherd > required could be specified, e.g. "0.9.1". > > The check could be abstracted in the shepherd-service implementation, >

bug#57356: libtool-2.4.7 removed as a "duplicate"?

Hi, Michael Ford skribis: > In commit 5b6b731c7d8ecbae0ead1600b4cd2f70c66d51ca, the libtool-2.4.7 > package was removed as a "duplicate". The commit message doesn't explain at > all why libtool 2.4.7 was being removed, or what it was a duplicate of? As > of latest master, libtool is still

bug#57315: guix upgrade --dry-run output is basically useless

Hi, zimoun skribis: > Just to mention this report is somehow a duplicate of bug#40612 [1]. > Maybe, they could be merged. WDYT? Yes, please. >> (If you’re curious, see >> for details.) > > Nice read! Quoting: > > [...] do a first

bug#57306: guix pull to old commit fails due to unsupported manifest format

Hi, zimoun skribis: > On Wed, 31 Aug 2022 at 13:06, Ludovic Courtès wrote: > >> I fixed it in 67a6828b2bb821274757f686f7c685b664339a96 using the same >> trick as earlier. > > It means version 3 is used all the time, right? Yes. > Well, I miss when

bug#57490: UPower ignores ‘critical-power-action’

Ludovic Courtès skribis: > Setting ‘hybrid-sleep-state’ to '("mem") doesn’t help though: > “CanHybridSleep” still returns “na”. I’m looking at ‘can_sleep_state’ > in elogind without seeing why it doesn’t return true. Having changed elogind’s “LogLevel” to “debug” with a

bug#57480: Wrong Type To Apply on Reconfigure

Hi, 宋文武 skribis: > Julien Lepiller writes: > >> I don't know how to fix it, but here is what I think is the issue: >> >> in guix/scripts/system/reconfigure.scm: >> >> #:autoload (guix describe) (current-channels) >> ... >> (define* (check-forward-update ... >>(current-channels

bug#57306: guix pull to old commit fails due to unsupported manifest format

Hi, Arun Isaac skribis: >> I do not think it is related to guix-daemon and I think it is expected; >> indeed it could be considered as a bug. The command-line, >> >> guix pull --commit=xyz -p /tmp/test >> >> writes /tmp/test/manifest using the current Guix (say manifest 4) and >> not using

bug#57315: guix upgrade --dry-run output is basically useless

Hi, Csepp skribis: > I'd like to figure out what Guix will try to build before I run an > upgrade on my netbook, so I always use --dry-run. I'm pretty sure in > the past it used to show more information, but today it just showed that > it will download 20 megs, without saying what package that

bug#57315: guix upgrade --dry-run output is basically useless

Hi, "bdju" skribis: > On Sun Aug 21, 2022 at 1:39 AM CDT, Csepp wrote: >> This should go without saying, but this is pretty bad UX. >> >> Is there something that can be done about this? The upgrade process on >> less powerful machines is pretty awful currently. > Agreed. Upgrading on Guix can

bug#57490: UPower ignores ‘critical-power-action’

Ludovic Courtès skribis: > Looking at the code, it could be because the ‘CanHybridSleep’ method > returns false, but why that would happen is unknown to me. Indeed, if we run ‘dbus-monitor --system’ and ‘herd restart upower-daemon’ (in QEMU), we see this: --8<--

bug#57490: UPower ignores ‘critical-power-action’

Ludovic Courtès skribis: > As discussed on IRC with Tobias, UPower appears to ignore our > ‘critical-power-action’ setting. On my machine, I left the default > (‘HybridSleep’) but upowerd dismisses it and chooses ‘PowerOff’: Furthermore, powering off is actually ungraceful: ‘hal

bug#57490: UPower ignores ‘critical-power-action’

As discussed on IRC with Tobias, UPower appears to ignore our ‘critical-power-action’ setting. On my machine, I left the default (‘HybridSleep’) but upowerd dismisses it and chooses ‘PowerOff’: --8<---cut here---start->8--- $ guix system describe Generation

bug#56444: Gitolite home directory permissions

Hi there! Please let’s avoid guessing each other’s willingness to do one thing or another. I agree with David that we should accept simple local fixes like this one, while keeping the “better solution” in sight. It’s a tradeoff, and the goal is to make sure we can all move forward. So I’m all

bug#55898: Services depending on new Shepherd features may fail until reboot

Maxime Devos skribis: > On 30-08-2022 09:33, Ludovic Courtès wrote: > >> So are you suggesting replacing: >> >>(defined? 'make-inetd-constructor) >> >> by something like: >> >>(version> >> or is it something different that yo

bug#55898: Services depending on new Shepherd features may fail until reboot

Hi Maxim, Maxim Cournoyer skribis: > Agreed, but the context differs wildly: while Autoconf or browsers for > example really are facing a diversity of configuration, the version of > Shepherd used in Guix System is known and controlled. So the only > problems bound to happen are in this

bug#55898: Services depending on new Shepherd features may fail until reboot

Hi, Maxim Cournoyer skribis: > Ludovic Courtès writes: [...] >> Yes. The issue is that we’re more free-style than systemd: we’re >> basically loading code live in the running Shepherd. So we have to >> write that code such that it works with older Shepherd versions.

bug#55848: AArch64 Honeycomb builders are inactive

Hello! Ludovic Courtès skribis: > I’m currently reconfiguring pankow and grunewald⁰ from berlin with ‘guix > deploy’ to include the fix above¹, but it’s gonna take a while as it’s > currently building GCC… That eventually succeeded and pankow is now reconfigured with the right daemon

bug#57071: Xscreensaver not working since latest patch

Heya, Ludovic Courtès skribis: > Rick Huijzer skribis: > >> It seems that xscreensaver-auth needs to be setuid instead of the main >> xscreensaver binary. The screen-locker-service in xorg.scm sets the >> provided package setuid and sets the required pam configura

bug#55848: [cuirass] workers stalled

Hi, Ricardo Wurmus skribis: > Ludovic Courtès writes: > >> Ludovic Courtès skribis: >> >>> guix-daemon is configured to use the default substitute URLs, >>> https://ci.guix.gnu.org and https://bordeaux.guix.gnu.org, which we know >>> are unre

bug#53210: installer: referring to N-1 guix is problematic.

Hello, Mathieu Othacehe skribis: >> Let me know if you have comments! > > Thanks for taking care of this! > > Looks like we have a small regression on 'system-tests and 'guix > specifications: > > https://ci.guix.gnu.org/eval/528053/log/raw > https://ci.guix.gnu.org/eval/528056/log/raw > > I

bug#57071: Xscreensaver not working since latest patch

Hi Rick & Roman, Rick Huijzer skribis: > It seems that xscreensaver-auth needs to be setuid instead of the main > xscreensaver binary. The screen-locker-service in xorg.scm sets the > provided package setuid and sets the required pam configuration for the > provided package. The problem is that

bug#57068: Resizing mcron job in vm-image.tmpl interferes with settings

Hi Maxim, Maxim Cournoyer skribis: > The vm-image.tmpl is the template we use for our graphical Guix demo > QEMU image that can be downloaded from our site > (https://guix.gnu.org/en/download/ -> > https://ftp.gnu.org/gnu/guix/guix-system-vm-image-1.3.0.x86_64-linux.qcow2). > > This commit was

bug#57068: Resizing mcron job in vm-image.tmpl interferes with settings

Hi, Maxim Cournoyer skribis: >> There’s a third problem that I initially thought was unrelated: >> >> 3. The mcron job starts running before ‘xorg-server’ is up, and that >> can cause Xorg to fail to start. >> >> Namely, if you run the command above, you’ll see that Xorg starts and >>

bug#57067: Missing Xfce icons

Hi, 宋文武 skribis: > Ludovic Courtès writes: > >> In current ‘master’ (ca. 6db3b34d7203639ef4286c237a6e536259f92352), in a >> VM created with: >> >> guix system vm gnu/system/examples/vm-image.tmpl >> >> Xfce is lacking a few icons in window decoratio

bug#57091: Git authentication reports subkey fingerprints

Hi, Maxime Devos skribis: > On 09-08-2022 23:07, Ludovic Courtès wrote: >> Hello, >> >> As Tobias explains at >> <https://mail.gnu.org/archive/html/help-guix/2022-08/msg00073.html> and >> as can be seen from ‘.guix-authorizations’, the (guix openpgp) a

bug#57093: 'guix style --whole-file' hangs indefinitely if parenthesis is unmatched

Hi Mohammed, Mohammed AMAR-BENSABER skribis: > guix style --whole-file package.scm hangs indefinitely if parenthesis is > unmatched. Relevant commit a15542d26df42dabdb5e2f76d150ae200230c3b0. Oops, fixed in ebda12e1d2c64480bb7d5977e580d8b2eabeb503: --8<---cut

bug#57095: another "inappropriate ioctl" bug :)

Hi! Josselin Poiret skribis: > We also use a big wrapping `with-error-handling` to display errors > properly in the case when they are not caught. The difference is that > `with-error-handling` adds a non-unwinding handler, while catch is > unwinding. My first thought was that non-unwinding

bug#57117: ‘guix deploy’ doesn’t honor (build-locally? #f) in the presence of grafts

In current ‘master’ (ca. f0ae9da3210cc6d87ca519545203daf9751f3465), when passed a set of ‘machine-ssh-configuration’ machines, ‘guix deploy’ ends up trying to build locally even if those machines have: (build-locally? #f) Passing ‘--no-grafts’ works around the problem. Ludo’.

bug#55848: AArch64 honeycomb machines aren’t building stuff

Hi! Ludovic Courtès skribis: > guix-daemon is configured to use the default substitute URLs, > https://ci.guix.gnu.org and https://bordeaux.guix.gnu.org, which we know > are unreachable. > > I’ve theoretically addressed this here: > > > https://git.savannah.gnu.org/c

bug#56866: [Shepherd] inetd connections not correctly counted?

Hi, Ludovic Courtès skribis: > We recently experienced a bug on berlin.guix where we’d be locked out of > SSH access because shepherd (0.9.1) would say that the maximum > connection number on the sshd inetd service had been reached. On berlin.guix, which is getting hammered, we see th

bug#57071: Xscreensaver not working since latest patch

Hi Rick, Rick Huijzer skribis: > The latest xscreensaver patch rendered > xscreensaver unusable on my systems. When I try to unlock my screen I am > greeted with the message 'xscreensaver: don't login as root', even though I > don't invoke it as root. > > >

bug#57077: guix-jupyter fails a test

Hi! Andreas Enge skribis: > guix-jupyter currently fails to build with the error message below. While I > noticed it when updating python-sympy, the problem was already present > before. It looks like the Jupyter protocol changed, probably in d54b8754fdba52d89aafaaf80b6c8e89bcea92bd, which was

bug#57090: [BUG] Default Notation for chmod in guix style?

Hi, "(" skribis: > On Tue Aug 9, 2022 at 9:59 PM BST, Maxime Devos wrote: >> 'chmod' is not mentioned anywhere in (guix scripts style), so I'd think >> it's just an oversight. The authority on the matter would be Ludovic >> Courtès > > Is it possibl

bug#57091: Git authentication reports subkey fingerprints

Hello, As Tobias explains at and as can be seen from ‘.guix-authorizations’, the (guix openpgp) and (guix git-authenticate) machinery reports the fingerprint of subkeys on signatures (when subkeys are used) rather than the

bug#57039: `make check' yields two failed tests.

Maxime Devos skribis: > On 09-08-2022 15:50, Ludovic Courtès wrote: >>> + (entry (tag "tag-for-first-news-entry") >>> + (title (en "Old news.") (eo "Malnova?oj.")) >> The question mark h

bug#57039: `make check' yields two failed tests.

Hi, Pierre-Henry Fröhring skribis: > test-name: channel-news, one entry > location: /home/phf/src/guix/tests/channels.scm:323 > source: > + (test-assert > + "channel-news, one entry" [...] > + (entry (tag "tag-for-first-news-entry") > +

bug#57046: Spanish documentation uses exclusive language

Hola, "pelzflorian (Florian Pelz)" skribis: > * the main Spanish translation po/guix/es.po uses usuario > > * the French translation switches between “utilisateur·rices”, > “utilisatrices et utilisateurs” and more often masculine “utilisateurs” > > * the Portuguese, Russian, German

bug#53210: installer: referring to N-1 guix is problematic.

Hi Josselin & all, I ended up pushing the following patches: fdafd40432 maint: Use a pretty version string in ISO and VM images. 95a03aa5c5 system: install: Always use 'current-guix'. 57f1892d36 gnu: guix: Default 'current-guix' is built using the current channels. 64a070717c channels:

bug#57068: Resizing mcron job in vm-image.tmpl interferes with settings

Ludovic Courtès skribis: > Commit 945ad48cd8029fa77a643e00c7fd350e98cacca0 added an mcron job to > ‘vm-image.tmpl’ that resets screen size every second. I’m don’t fully > understand the problem this was addressing, but it has two drawbacks: > > 1. Kicking in every second

bug#57068: Resizing mcron job in vm-image.tmpl interferes with settings

Hello! Commit 945ad48cd8029fa77a643e00c7fd350e98cacca0 added an mcron job to ‘vm-image.tmpl’ that resets screen size every second. I’m don’t fully understand the problem this was addressing, but it has two drawbacks: 1. Kicking in every second is inefficient. 2. Resetting the screen size

bug#56799: (gnu services configuration) usage of *unspecified* is problematic

Hello, I just hit this while running ‘guix home reconfigure’ from f0ae9da3210cc6d87ca519545203daf9751f3465: home-config.scm:24:16: error: invalid value unset for field 'address-family' It’s an ‘openssh-host’ record: (openssh-host (name "xyz") (host-name "xyz.example.org") (user

<    4   5   6   7   8   9   10   11   12   13   >