bug#44985: ANSI sequences in unattended-upgrades.log?

Hi! The unattended-upgrades.log file is quite unreadable due to ANSI sequences. Probably use of them should be disabled when output is a log file? /Simon signature.asc Description: PGP signature

bug#44986: [PATCH] doc: Give references and examples for services-to-restart.

Hi! I started using unattended-upgrades, and was confused which service names (config.scm vs herd) to use. I think this small documentation patch would help others. What do you think? /Simon From c414dd60652ecdd124b189b2c46ce30ae9db986d Mon Sep 17 00:00:00 2001 From: Simon Josefsson Date: Tue,

bug#48214: inetutils-1.9.4 build fails

Bone Baboon via Bug reports for GNU Guix writes: > If inetutils follows semantic version numbering then that would suggest > a breaking change to the inetutils API moving from 1.9.4 to 2.0. FWIW, inetutils is not following semantic versioning, and 2.0 is expected to be a simple drop-in for 1.9.4

bug#62160: Guix reference manual link from guix.gnu.org?

Hi I often go to guix.gnu.org to read the (excellent!) Guix manual. This leads to this click pattern: guix.gnu.org -> Help -> GNU Guix Manual 1.4.0 which leads me to a page (written in english) to chose language of the manual -- https://guix.gnu.org/en/manual/ -- and when I chose English I get a

bug#71556: GNOME Konsol crashes

Hi. GNOME Konsol has crashed for me, bringing down all 10+ windows I had open (and plenty of ongoing work halted...). I've now seen this twice, so I suppose it counts as reproducible, even though I don't know how to trigger it. I recall that it happened when I used the mouse to maybe resize wind

bug#71556: GNOME Konsol crashes

> 21 juni 2024 kl. 06:32 skrev Liliana Marie Prikler > : > > Am Freitag, dem 14.06.2024 um 18:34 +0200 schrieb Simon Josefsson: >> Hi. >> >> GNOME Konsol has crashed for me, bringing down all 10+ windows I had >> open (and plenty of ongoing work halted...). I've now seen this >> twice, so I su

bug#63331: Guile-GnuTLS/Git circular dependency

Ludovic Courtès writes: > We need to solve that. For now, the only fix I can think of is having > ‘guile-gnutls’ built from a “make dist”-provided tarballs. Apparently > we can add assets at ; would you > like to upload a tarball and accompanying signatur

bug#63331: Guile-GnuTLS/Git circular dependency

Ludovic Courtès writes: > We need to solve that. For now, the only fix I can think of is having > ‘guile-gnutls’ built from a “make dist”-provided tarballs. Apparently > we can add assets at ; would you > like to upload a tarball and accompanying signatur

bug#63331: Guile-GnuTLS/Git circular dependency

> ice-9/boot-9.scm:1685:16: In procedure raise-exception: > Unbound variable: protocol/ssl3 Maybe ssl3 is disabled (as it probably should be) in guix's gnutls? While I built the package on a Guix system using system GnuTLS, I didn't build it through Guix's packaging, so maybe there is some differ

bug#64691: use https:// instead of git:// in shepherd www

Hello, and congratulations on the shepherd 0.10.2 release! How about using https for git clone instructions, instead of the old non-secured way? See patch below. The "Download" link on goes to which doesn't exist. How

bug#71556: GNOME Konsol crashes

I saw the problem a couple of more times, but I have switched away from kgx (which I think is called Konsol not Console?) to the old Terminal app and haven’t had any issues since. I’m okay closing this bug report unless there is some more information from anyone else who have time to debug the

bug#75090: [bug#75426] [PATCH] docker: Build tarballs reproducibly.

Ludovic Courtès writes: > Fixed in 285a1cb449f60798dc83f7f1016700b4ab2374a8. Hi! Wonderful, confirmed working. These two pipelines produce bit-by-bit identical docker pack images for stage1 of my guix gitlab container images now: https://gitlab.com/debdistutils/guix/container/-/jobs/904245486

bug#75080: guix pull fails on arm64 due to cmake DEB self-tests

Ludovic Courtès writes: > Hi, > > Simon Josefsson skribis: > >> I get a build failure regarding "cmake-bootstrap" shown here: >> >> https://gitlab.com/debdistutils/guix/container/-/jobs/8717616613 >> >> I cannot reproduce this on my own arm64 machine running Trisquel. >> >> It seems only cmake's

bug#75090: [bug#75426] [PATCH] docker: Build tarballs reproducibly.

fre 2025-01-31 klockan 17:12 +0100 skrev Ludovic Courtès: > Hi, > > Simon Josefsson skribis: > > > Hi!  I suspect something went wrong with this patch, now 'guix > > pack' > > fail and give the error below.  Maybe the 'cf' has to come first? > > > > https://gitlab.com/debdistutils/guix/containe

bug#74925: failed to compute the derivation for Guix

Hi I am running 'guix pull' on arm64 from Debian, and ran into the backtrace below. The following commands reproduce it inside a fresh Debian trixie container in a GitLab shared runner: apt-get update apt-get install -y guix podman ca-certificates (guix-daemon --disable-chroot --build-users-grou

bug#74949: guix describe crash if HOME is unset OR /etc/passwd is missing

Hi I get the backtrace below. Setting either HOME to something, or adding an entry to /etc/passwd for the running user, silences this. I don't think it should fail like this, should it? Is a reasonable behaviour to assume HOME means "/" when unset? How to handle missing /etc/passwd entries pro

bug#74948: guix pack docker environment variable setting

Hi I believe the guix-pack docker format allows setting environment variables in the resulting image, is that right? I can't find any way to set them using the `guix pack` tool, am I missing it? Would a new `guix pack --setenv HOME=/` parameter be useful? Such a parameter could be docker-specif

bug#74952: [PATCH] guix-install.sh: Use "command -v nologin" instead of "which nologin".

Hi! In a small container image, I do not have the 'which' tool installed. I believe 'command -v' is always available since it is /bin/sh standard. How about changing the idiom for user/group additions from 'which' to 'command -v'? See attached patch. /Simon From 2bc261126a84a4a9a33acea9f107ad4b

bug#75090: [bug#75426] [PATCH] docker: Build tarballs reproducibly.

Hi! I suspect something went wrong with this patch, now 'guix pack' fail and give the error below. Maybe the 'cf' has to come first? https://gitlab.com/debdistutils/guix/container/-/jobs/8988707317 /Simon tar: You must specify one of the '-Acdtrux', '--delete' or '--test- label' options Try 't

bug#75080: guix pull fails on arm64 due to cmake DEB self-tests

Hi! I'm running the following commands on a arm64 GitLab shared runner node: export LC_ALL=C.UTF-8 apt-get update apt-get install -y guix podman ca-certificates (guix-daemon --disable-chroot --build-users-group=_guixbuild & guix pull --url=https://gitlab.com/debdistutils/guix/mirror.git \ || (ls

bug#74925: failed to compute the derivation for Guix

Ludovic Courtès writes: > Hello, > > Simon Josefsson skribis: > >> (guix-daemon --disable-chroot --build-users-group=_guixbuild &) >> guix pull --url=https://gitlab.com/debdistutils/guix/mirror.git > > [...] > >> In ./guix/store.scm: >> 2095:12 7 (_ #) >> 1437:13 6 (map/accumulate-builds #

bug#75090: Make 'guix pack -f docker' tarballs reproducible?

Hi I am creating docker archives using: guix pack guix bash-minimal coreutils-minimal net-base --save-provenance -S /bin=bin -S /share=share -f docker --image-tag=guix --max-layers=8 --verbosity=2 To my surprise the output was not reproducible between re-runs. The reason is because of the time

bug#76343: shepherd 1.0.2 --help: warning: call to environ while multiple threads are running; further behavior unspecified.

Hi It seems shepherd in Debian print the following on a simple --help: 132s warning: call to environ while multiple threads are running; 132s further behavior unspecified. I can't find the error message in guile-fibers or shepherd source code. Any ideas where it comes from and how to fi

bug#76343: shepherd 1.0.2 --help: warning: call to environ while multiple threads are running; further behavior unspecified.

Tomas Volf <~@wolfsden.cz> writes: > Simon Josefsson via Bug reports for GNU Guix writes: > >> Hi >> >> It seems shepherd in Debian print the following on a simple --help: >> >> 132s warning: call to environ while multiple threads are running; >

bug#76343: shepherd 1.0.2 --help: warning: call to environ while multiple threads are running; further behavior unspecified.

tor 2025-02-27 klockan 17:26 +0100 skrev Ludovic Courtès: > Hi Simon, > > Simon Josefsson skribis: > > > Thank you! Does this make shepherd Debian packages useless, or can > > we suggest people to ignore the warning? Any simple way to patch it > > out from within shepherd? The Debian freeze is i

bug#76735: Shepherd parallel make help2man issue

Hi I got the build error below. Presumably it happens because the jobs to create the tools has not finished before the help2man jobs has started. I will patch around this in the Debian packaging to serialize the build: override_dh_auto_build: # build tools that help2man needs first

bug#75080: guix pull fails on arm64 due to cmake DEB self-tests

"Leo Famulari" writes: > On Wed, Feb 26, 2025, at 03:41, Simon Josefsson wrote: >> Hi. What do you mean by disabled isolation? In the initial e-mail I >> quoted the set of commands used which involved: >> >> (guix-daemon --disable-chroot --build-users-group=_guixbuild & >> >> Is that what you m

bug#76735: Shepherd parallel make help2man issue

Ludovic Courtès writes: > Hi Simon, > > Simon Josefsson skribis: > >> I got the build error below. Presumably it happens because the jobs to >> create the tools has not finished before the help2man jobs has started. > > Am I right that you’re building from a Git checkout? This was during build

bug#76343: shepherd 1.0.2 --help: warning: call to environ while multiple threads are running; further behavior unspecified.

Ludovic Courtès writes: > Hi, > > Simon Josefsson skribis: > >> A shephard-specific patch would be the simplest at this point, I think. >>   >> Do you have some idea how to do that? I agree it seems like a Debian- >> specific patch for now. > > The patch below appears to do the trick. I guess

bug#76343: shepherd 1.0.2 --help: warning: call to environ while multiple threads are running; further behavior unspecified.

Thank you! Does this make shepherd Debian packages useless, or can we suggest people to ignore the warning? Any simple way to patch it out from within shepherd? The Debian freeze is in two weeks and it would be nice to give a good first impression to people try it shepherd from Debian… i could t

bug#75080: guix pull fails on arm64 due to cmake DEB self-tests

Leo Famulari writes: > On Wed, Feb 05, 2025 at 12:18:41AM +0100, Simon Josefsson via Bug > reports for GNU Guix wrote: >> Looking more carefully at the errors, I notice this part: >> >>actual-err>cpack-cfg> set(DPKG_EXECUTABLE "/usr/bin/dpkg

bug#77132: Shepherd: flaky self tests

Ludovic Courtès writes: >> I've often seen failure in the 'log-rotation.sh' self-tests on my own >> system (see attachment for log), > > It fails while checking the number of remaining open file descriptors: > > + herd -s t-socket-3705122 stop three > ++ file_descriptor_count > ++ ls -l /proc/370

bug#77132: Shepherd: flaky self tests

Ludovic Courtès writes: > Hi Simon, > > (- guix-devel) > > Simon Josefsson writes: > >> I instrumented the Debian package build system to patch the script to >> print debug info, below is that log output, is this better? > > I made a mistake: in ‘file_descriptor_count’, the line to add should be

bug#77132: Shepherd: flaky self tests

Ludovic Courtès writes: > Also, I wonder if the problem could be a race condition, which would be > fixed like this: > > diff --git a/tests/services/log-rotation.sh b/tests/services/log-rotation.sh > index 375f563..178bb49 100644 > --- a/tests/services/log-rotation.sh > +++ b/tests/services/log-r

bug#77132: Shepherd: flaky self tests

Ludovic Courtès writes: > Hi Simon, > > Simon Josefsson writes: > >> Ludovic Courtès writes: > > [...] > >>> ++ wc -l >>> + test 22 -le 18 >>> >>> This is the same as . >>> >>> Could you instrument it as I suggested there? >> >> I'm still seeing this with 1.0.

bug#77132: Shepherd: flaky self tests

Ludovic Courtès writes: > Hi Simon, > > Simon Josefsson writes: > >> Below is the log file. > >> + shepherd --version >> ;;; WARNING: loading compiled file >> /usr/lib/x86_64-linux-gnu/guile/3.0/site-ccache/fibers.go failed: >> ;;; In procedure load-thunk-from-memory: incompatible bytecode vers

bug#63331: Guile-GnuTLS/Git circular dependency

Hi. I noticed this bug because it was mentioned in the guile-gnutls packaging: ;; url-fetch is used here to avoid a circular dependency with ;; git-download, see https://issues.guix.gnu.org/63331 (method url-fetch) (uri (string-append "mirror://gnu/gnutls/guile-gnutls-" versio