bug#54783: [v2 0/2] Clarify zram priority

Hello Maxim, Thanks for looking at this. Here's a v2. Maxim Cournoyer writes: > I'm curious, what does delaying the field buys us here? Is it to avoid > printing the warning multiple times when the record is evaluated? Right, and this would get worse if someone ended up inheriting from

bug#55616: gcc-12-strmov-store-file-names.patch is missing?

Hi, Tim Rakowski skribis: > $ guix uprade > The following packages will be upgraded: >... >gcc-toolchain 11.2.0 → 12.1.0 >... > guix upgrade: error: gcc-12-strmov-store-file-names.patch: patch not found > > As far as I can tell, >

bug#55616: gcc-12-strmov-store-file-names.patch is missing?

Hi, I'm currently observing the following problem: $ guix describe Generation 8May 24 2022 20:15:17(current) guix 01793ed repository URL: https://git.savannah.gnu.org/git/guix.git branch: master commit: 01793ed03e8aa0960bff7adc21fd270e1527e68e $ guix uprade The following

bug#55441: [cuirass] hang in "In progress..."; runs out of pgsql connections

Hi! Ludovic Courtès skribis: > Fixed in Guix commit a4994d739306abcf3f36706012fb88b35a970e6b with a > test that reproduces the issue. > > Commit d02b7abe24fac84ef1fb1880f51d56fc9fb6cfef updates the ‘guix’ > package so we should be able to reconfigure berlin now and hopefully > (crossing

bug#55444: elogind startup race between shepherd and dbus-daemon

Hi, Am Montag, dem 16.05.2022 um 10:26 +0200 schrieb Ludovic Courtès: > [...] > So it would seem that the solution to this is to prevent dbus-daemon > from starting elogind.  We can do that by changing > org.freedesktop.login1.service so that it has “Exec=true” instead of > “Exec=elogind

bug#55504: Test suite of emacs-deferred does not progress

Liliana Marie Prikler skribis: > Am Mittwoch, dem 18.05.2022 um 13:19 -0300 schrieb Jorge P. de Morais > Neto: >> The log file [1] is empty. >> >> 1: /var/log/guix/drvs/7r/bhrk48qvqhgix5c33yh9m3nq5crzny-emacs- >> deferred- >> 0.5.1.drv.gz > emacs-deferred also times out on CI [2]. > > [2]

bug#54783: [PATCH v2 1/2] system: Align zram priority with swap-space spec to clarify.

* gnu/services/linux.scm (zram-device-configuration) [priority]: Adapt to use #f or an integer from 0 to 32767. Add sanitizer to warn for the change and delay the field. (zram-device-configuration->udev-string): Adapt as above. * doc/guix.texi (Zram Device Service): Change priority description to

bug#54783: [PATCH v2 2/2] doc: Remove double copyright.

* doc/guix.texi: Remove doubled Josselin Poiret copyright line. --- doc/guix.texi | 1 - 1 file changed, 1 deletion(-) diff --git a/doc/guix.texi b/doc/guix.texi index 5f0120a3bd..b960c546a8 100644 --- a/doc/guix.texi +++ b/doc/guix.texi @@ -99,7 +99,6 @@ Copyright @copyright{} 2021 Alice

bug#39117: GNOME Files: No file thumbnails

Hello There was a patch in June 2020 that added bubblewrap as input to gnome- dektop. It was reported that the patch was enabling thumbnails in Nautilus. So, this issue should had been resolved. https://issues.guix.gnu.org/41756 But thumbnails are still not generated for me with Nautilus (GNOME

bug#55609: ruby-stackprof sometimes fails to build (armv7h)

Looks like a rather flaky test, depending on GC behaviour and timing. So I think for now the test could simply be disabled, at least for arm? Greetings, Maxime. signature.asc Description: This is a digitally signed message part

bug#55399: guix system reconfigure fails on channel validation

Hi again, seg 23 mai 2022 às 16:18:52 (165532), l...@gnu.org enviou: > ... > (For now commit b6bfe9ea6a1b19159455b34f1af4ac00ef9b94ab changes > Guile-Git in Guix to depend on libgit2 1.3 as a workaround.) After upgrading guile-git, the attached patches disables owner validation and reverts

bug#54786: Installation tests are failing

Hi, Ludovic Courtès writes: > Hi, > > Mathieu Othacehe skribis: > >> Thanks for the fix! The jami and jami-provisioning tests are also broken >> because of what looks like to be the same issue: >> >> One does not simply initialize the client: Another daemon is detected >>

bug#55618: Allow patching from mummi issues

Hi ! I was tring to fix a local build using an online patch on mummi, this way : (define-public my-emacs-list-utils (package (inherit emacs-list-utils) (name "my-emacs-list-utils") (version "0.4.6") (source (origin (method git-fetch) (uri (git-reference

bug#55583: guix-daemon doesn't cleanly error-out on case-insensitive file systems.

Maxime Devos writes: Create a file /gnu/store/case-sensitivity-test (if it doesn't already exist). Open /gnu/store/CASE-SENSITIVITY-TEST. If it succeeds, you have a case-sensitive file system. Hah. I was so wrapped up in thinking about kernel or POSIX APIs I missed the obvious thing.

bug#55499: excessively large manifests due to propagation

Ludovic Courtès writes: > Hi! > > Ricardo Wurmus skribis: > >> A profile consisting only of four R packages (r-seurat, r-cistopic, >> r-monocle3, and r-cicero-monocle3) results in a “manifest” file that >> weighs 7.1MB. At the MDC I repeatedly encountered manifest files that >> are exceeding

bug#54305: disk utility fail format fat

Hello The upstream implemented the check for vfat and closed the issue. https://gitlab.gnome.org/GNOME/gnome-disk-utility/-/commit/15462f9c87c08c5af77a31993c1d87cb34d04861 (It is not included in Disks version 42.0, so I haven't tested it yet.) Roman У нд, 2022-03-13 у 18:56 +0200, Roman

bug#55609: ruby-stackprof fails fails to build (armv7h)

title 55609 ruby-stackprof fails fails to build (armhf-linux) Actually, it fails reproducibly: $ guix build ruby-stackprof@0.2.17 --system=armhf-linux --check --no-grafts --check 1) Failure: StackProfTest#test_gc

bug#54651: Guix pull failing on ARM 32bit with "Please report the COMPLETE output above by email"

Denis 'GNUtoo' Carikli schreef op ma 23-05-2022 om 21:08 [+0200]: > And here's the log: > > $ bzcat  /var/log/guix/drvs/m1/iyn6y1s3ajl6v0lv5658zq2cngdpq3-ruby- > stackprof-0.2.17.drv.bz2 I've created a separate bug report for this: . signature.asc

bug#55609: ruby-stackprof fails fails to build (armv7h)

retitle 55609 "ruby-stackprof fails fails to build (armhf-linux)" thanks Actually, it fails reproducibly: $ guix build ruby-stackprof@0.2.17 --system=armhf-linux --check --no-grafts --check 1) Failure: StackProfTest#test_gc

bug#55609: ruby-stackprof sometimes fails to build (armv7h)

Reported upstream at signature.asc Description: This is a digitally signed message part

bug#55609: ruby-stackprof sometimes fails to build (armv7h)

To reproduce: $ guix build ruby-stackprof@0.2.17 --system=??? # if it was substituted $ guix build ruby-stackprof@0.2.17 --system=??? --no-grafts --check where I don't know what the value of ??? is (maybe armhf-linux?). Maybe it fails on other architectures too, but I cannot reproduce it on

bug#55609: ruby-stackprof fails fails to build (armv7h)

title 55609 ruby-stackprof fails fails to build (armhf-linux) thanks Actually, it fails reproducibly: $ guix build ruby-stackprof@0.2.17 --system=armhf-linux --check --no-grafts --check 1) Failure: StackProfTest#test_gc

bug#55499: excessively large manifests due to propagation

Hi! Ricardo Wurmus skribis: > A profile consisting only of four R packages (r-seurat, r-cistopic, > r-monocle3, and r-cicero-monocle3) results in a “manifest” file that > weighs 7.1MB. At the MDC I repeatedly encountered manifest files that > are exceeding 24MB. Commit

bug#54783: ZRAM default priority wrong

Hi, Josselin Poiret writes: > * gnu/services/linux.scm > (zram-device-configuration) [priority]: Adapt to use #f or an integer > from 0 to 32767. Add sanitizer to warn for the change and delay the > field. > (zram-device-configuration->udev-string): Adapt as above. > * doc/guix.texi (Zram