bug#44756: racket-7.9-src.tgz hash mismatch

Racket fails to build, due to a hash mismatch on the source tarball. Mark sha256 hash mismatch for /gnu/store/mnjlngcwv4lffn9xjf82m60dwcfmz2vd-racket-7.9-src.tgz: expected hash: 18pz6gjzqy6a62xkcmjanhr7kgxpvpmc0blrk4igz8ldcybz44if actual hash:

bug#39871: python-hacking build fails

Hello, Maxim Cournoyer writes: > Build log extract: > > OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ > OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-60} \ > ${PYTHON:-python} -m subunit.run discover -t ./ . --load-list > /tmp/guix-build-python-hacking-1.0.0.drv-0/tmp0b3_dkul >

bug#44751: tests/swh.scm hangs building guix with guile-2.2

I'm exploring building with guile 2.2 because guile-gnutls built with guile 3.0 is only available in experimental, and even there, missing for arm64. FAIL: tests/swh.scm - lookup-origin And then hangs indefinitely. I've seen it run for hours at a time. Works fine with guile 3.0. In

bug#44745: tests/lint.scm fails building guix with guile-2.2

I'm exploring building with guile 2.2 because guile-gnutls built with guile 3.0 is only available in experimental, and even there, missing for arm64. From tests/lint.log: test-name: archival: missing content location: /build/guix-EdK9LP/guix-1.2.0~rc2/tests/lint.scm:921 source: + (test-assert +

bug#44725: ocaml-cairo2 package fails to build

Hi Brett, Thank you for the fix. On Thu, 19 Nov 2020 at 13:28, Brett Gilio wrote: >> [0] >> https://github.com/kit-ty-kate/opam-repository/commit/4db9f97d242fbfd3b3100128797a4f941f66a32d >> >> [1] https://github.com/ocaml/ocaml/issues/9360 This commit message of

bug#44741: ‘copy-recursively’ #:keep-mtime? #t broken for directories

Ludovic Courtès skribis: > When passing #:keep-mtime? #t to ‘copy-recursively’, the mtime of > regular files is preserved, but the mtime of directories (and symlinks) > is not. > > This is because ‘set-file-time’ is called in the ‘down’ procedure of > ‘file-system-fold’, before the directory is

bug#44725: ocaml-cairo2 package fails to build

Brett Gilio writes: > zimoun writes: > >> Hi, >> >> On Wed, 18 Nov 2020 at 15:53, Brett Gilio wrote: >> >>> This is a test-phase issue. It looks like it might be a segmentation >>> fault from a C dependency (maybe Cairo itself)? I or somebody will look >>> a little deeper. In the meantime I am

bug#44725: ocaml-cairo2 package fails to build

zimoun writes: > Hi, > > On Wed, 18 Nov 2020 at 15:53, Brett Gilio wrote: > >> This is a test-phase issue. It looks like it might be a segmentation >> fault from a C dependency (maybe Cairo itself)? I or somebody will look >> a little deeper. In the meantime I am going to disable the test-phase

bug#22952: Backlight brightness keys in GDM and MATE require password authentication

On Wed, Nov 18, 2020 at 10:14:32PM +0100, Marius Bakke wrote: > To work around it locally, try adding: > > (simple-service 'gsd-polkit polkit-service-type > (list gnome-settings-daemon)) > > to the (services ...) section of your system configuration. Thank you. You are

bug#44742: Cuirass crashed when run interactively

Hello, When running Cuirass (3fd0eb1) directly from a command line, I have the following error: --8<---cut here---start->8--- 2020-11-19T18:34:29 exception arguments: (#f "Wrong number of arguments to ~A" (#) #f) In ice-9/boot-9.scm: 1731:15 12

bug#44741: ‘copy-recursively’ #:keep-mtime? #t broken for directories

When passing #:keep-mtime? #t to ‘copy-recursively’, the mtime of regular files is preserved, but the mtime of directories (and symlinks) is not. This is because ‘set-file-time’ is called in the ‘down’ procedure of ‘file-system-fold’, before the directory is populated. ‘populate-store’ is

bug#39885: Bioconductor URI, fallback and time-machine

Hi, Some explanations of the issue are provided here: Since we are currently updating to 3.12, maybe it is the occasion to fix the issue. See option a) below. On Tue, 03 Mar 2020 at 16:59, zimoun wrote: > Currently, the URI scheme (see

bug#44737: Packages grafted twice during system install

Hello! While installing 1.2.0rc2 (I selected GNOME), I noticed that different derivations of the same packages are grafted (screenshot below). I don’t think it should block 1.2.0 but we should definitely find out why this happens as this increases installation time and possible disk usage.

bug#35308: GDM refuses to log in with propagated glib

Hello, I digged further, and tracked propagated inputs from "python-matplotlib". So, it propagates "python-cairo", which in turn propagates "cairo", and then "glib". Also, no propagated input from "glib" has an issue with GDM, this is the stop point. So, basically, if your manifest is:

bug#44735: gilbc of the running system got wiped while building a package, system broken

Hi! I found the root cause of this issue: I made a typo and inadvertently did a “./configure --localstatedir=/vaar”. The manual should warn that using a wrong (or omitted) --localstatedir may destroy the guix installation and possibly the whole guix system. What can be done to prevent that a

bug#44735: gilbc of the running system got wiped while building a package, system broken

Hi! I didn’t look close enough before or didn’t wait long enough, but booting the previous system failed, actually. I now tried to boot some more system generations and even the oldest one: None of my previous system generations is booting any longer. The system is bricked. Bye Stefan

bug#44735: gilbc of the running system got wiped while building a package, system broken

Hi! I resolved the problem by copying gnu/store/cb88z63hyg1icd2kkahiink2p291mhr2-glibc-2.31 from https://alpha.gnu.org/gnu/guix/guix-binary-1.2.0rc2.aarch64-linux.tar.xz into gnu/store on the NFS server. The system is running again. Now I retried my commands and I am able to reproduce the

bug#43565: cuirass: Fibers scheduling blocked.

Hey, > In cuirass/utils.scm: >320:22 1 (_) > In unknown file: >0 (make-stack #t) > ERROR: In procedure make-stack: > In procedure struct-vtable: Wrong type argument in position 1 (expecting > struct): #f I think this error is caused by setting: --8<---cut

bug#44723: Latest binary tarball & Hurd qcow2 image unavailable (502)

Hey zimoun, > Where is the configuration? Repo maintenance? Elsewhere? Yes it's here: https://git.savannah.gnu.org/cgit/guix/maintenance.git/tree/hydra/modules/sysadmin/services.scm Thanks, Mathieu

bug#23196: [Hunting bug#23196]: GNOME "Sharing" settings is blank

Hi Leo, Thank you for the detailed explanations. On Wed, 18 Nov 2020 at 11:28, Leo Prikler wrote: > The Sharing dialog now consists of two buttons, which at least change > some settings, along with the text field, that is still blank. That > being said, I am far from able to assert, that

bug#44725: ocaml-cairo2 package fails to build

Hi, On Wed, 18 Nov 2020 at 15:53, Brett Gilio wrote: > This is a test-phase issue. It looks like it might be a segmentation > fault from a C dependency (maybe Cairo itself)? I or somebody will look > a little deeper. In the meantime I am going to disable the test-phase > and mark this issue as

bug#44723: Latest binary tarball & Hurd qcow2 image unavailable (502)

Hi, On Thu, 19 Nov 2020 at 09:05, Ludovic Courtès wrote: >> Does it make sense to only keep the latest? And GC all the older one >> except the stable one (pinned). > > We could change ‘cleanup-cuirass-roots’ (the mcron job I showed) to keep > at least one ‘hurd-barebones.qcow2’ root. Help

bug#44723: Latest binary tarball & Hurd qcow2 image unavailable (502)

Hi, zimoun skribis: > On Wed, 18 Nov 2020 at 18:46, Ludovic Courtès wrote: > >> I guess it’s OK for Guix System ISO images because a fresh one gets >> built at each evaluation, roughly, but perhaps the Hurd images are not >> rebuilt frequently enough and the changes that they’re GC’d are

bug#44735: gilbc of the running system got wiped while building a package, system broken

Hi! After trying to just build a package (with a modified guix, but this is certainly unrelated), the system broke catastrophically: stefan@guix ~/development/guix$ sudo -E ./pre-inst-env guix-daemon --build-users-group=guixbuild & stefan@guix ~/development/guix$