bug#46737: Services breakage from the PostgreSQL socket-directory configuration change

Hey, When reconfiguring recently, I ran in to issues with the Guix Data Service and probably the Patchwork service too. Looking at the change, I think it's clear there's a problem, because some system tests were changed, and I'm guessing they were changed so that they passed [1]. 1:

bug#46706: asciidoc 8.6.10: source hash mismatch

On Wed, Feb 24, 2021 at 12:05:44AM +0100, Björn Höfling wrote: > thanks for this package. This information was quite useful when > diffing. This is "interesting": We referenced the git-checkout not > by commit, but by version-tag. They redirected the repository to > >

bug#46706: asciidoc 8.6.10: source hash mismatch

On Mon, 22 Feb 2021 13:10:44 -0500 Leo Famulari wrote: > On Mon, Feb 22, 2021 at 06:03:09PM +0100, Björn Höfling wrote: > > Note: we also have asciidoc@9.0.1 (package asciidoc-py3). It might > > be possible to use v9 instead of the old asciidoc@8? > > > > Björn > > > > $ ./pre-inst-env guix

bug#46650: Extending package transformation options

Hi, On Sat, 20 Feb 2021 at 14:57, Ludovic Courtès wrote: > Guix as returned by ‘guix pull’ and ‘guix time-machine’ depends on > GnuTLS. So here, we have a special case: to build Guix itself, you need > to build GnuTLS first, and there’s no way to pass ‘--without-tests’ at > that level. > > I’m

bug#46631: Python CVE-2021-3177

On Mon, Feb 22, 2021 at 09:08:14AM +0100, Ludovic Courtès wrote: > You can keep (inherit …) because the effect of ‘package/inherit’ is just > to preserve replacements, which is unnecessary here. I used to know that... it's been a while and I forgot, and had trouble understanding the

bug#46712: Removed service extensions are not unloaded from Shepherd upon reconfiguring

Hi! At the Shepherd level, there’s no notion of service extension. Normally, after reconfiguring, “herd restart guix-daemon” (really “restart”, not “stop” + “start”) should start the new service, which doesn’t have all these ‘--chroot-directory’ options. Note that the guix-daemon process you

bug#44559:

Ludovic Courtès writes: > Hi, > > Christopher Baines skribis: > >> Ludovic Courtès writes: >> >>> Perhaps we could start by testing this hypothesis on a separate build >>> farm. Chris, Mathieu, WDYT? >> >> I'm currently thinking about attempting these kind of things (testing >> building

bug#44559:

Hi, Christopher Baines skribis: > Ludovic Courtès writes: > >> Perhaps we could start by testing this hypothesis on a separate build >> farm. Chris, Mathieu, WDYT? > > I'm currently thinking about attempting these kind of things (testing > building derivations under different conditions)

bug#36117: [PATCH 3/4] gnu: qemu: Add a static output.

Maxim Cournoyer skribis: > The static output is equivalent to what other distributions commonly package > as 'qemu-user-static'. > > * gnu/packages/virtualization.scm (qemu)[outputs]: Add a static output. > [phases]{configure}: Configure the main build as an out-of-source build. Move > all

bug#36117: [PATCH 4/4] services/qemu-binfmt: Use the F flag and the static output of QEMU.

Hi Maxim, Maxim Cournoyer skribis: > Fixes . > > Before this change, the 'binfmt_misc' entries registered for QEMU would not be > usable in container contexts outside of guix-daemon (without manually bind > mounting file names). > > For example: > > $ docker

bug#46563: file-system declarations do not currently support cifs mounts

Katherine Cox-Buday skribis: > Ludovic Courtès writes: > >> Katherine Cox-Buday skribis: >> >>> Ludovic Courtès writes: >>> Unfortunately that’s not enough. Like NFS, CIFS requires special support, which is currently missing from (gnu build file-systems). >>> >>> I