bug#63198: cups-service-type uses PAM-enabled 'cups' by default which prevents authentication

Hello, Maxim Cournoyer writes: Hi, muradm writes: Fixes . Makes CUPS service to extend pam-root-service-type providing minimal configuration to authenticate users. Since PAM authentication is provided, cups package can be used as default. *

bug#63530: Missing library in package procps

Gabriel Wicki writes: > Hi > > Trying to upgrade a somewhat outdated system (from March 23) I noticed > igt-gpu-tools failed to build. Investigating a bit the build fails due > to some "proc/readproc.h" include missing. I think i managed to fix the > failure in procps's Makefile, but testing

bug#63530: Missing library in package procps

Hi Trying to upgrade a somewhat outdated system (from March 23) I noticed igt-gpu-tools failed to build. Investigating a bit the build fails due to some "proc/readproc.h" include missing. I think i managed to fix the failure in procps's Makefile, but testing the patched build results in a

bug#63529: awscli doesn’t use global certificate store on foreign distro

On a foreign distro, awscli does not use the global certificate store. It seems to only use certifi.pem from the python-certifi package. There seems to be no way to override the certificate store. This makes awscli unusable on foreign distros. -- Ricardo

bug#63526: hubbub build failure when doing guix package -u

key lines: COMPILE: test/tokeniser2.c COMPILE: test/tokeniser3.c COMPILE: test/tree.c COMPILE: test/tree2.c COMPILE: test/tree-buf.c test/tokeniser2.c: In function ‘token_handler’: test/tokeniser2.c:444:46: error: ‘t.data.character.ptr’ may be used uninitialized [-Werror=maybe-uninitialized]

bug#59278: gcc@7 and higher are not hidden packages

Hi, On Tue, 15 Nov 2022 at 00:53, bbb ee wrote: > in version c81457a5883ea43950eb2ecdcbb58a5b144bcd11 of guix, gcc-toolchain > depends gcc: > ``` > $ DEFAULT_CHANNELS=/tmp/default_channels.scm > $ echo "%default-channels" > $DEFAULT_CHANNELS > # I force guix to use only %default-channels here

bug#20255: 'search-paths' should respect both user and system profile.

Hi, Josselin Poiret writes: > Hi, > > 宋文武 via Bug reports for GNU Guix writes: > >> Hello, commit 40310efde9b4a4f2cf98081d6cd10f843685ebb6 fix this by merge >> search-paths from multiple profiles by `guix package --search-paths`, in >> ~/.bashrc and ~/.zprofile (skeletons, so existed systems

bug#20255: 'search-paths' should respect both user and system profile.

Hi, 宋文武 via Bug reports for GNU Guix writes: > Hello, commit 40310efde9b4a4f2cf98081d6cd10f843685ebb6 fix this by merge > search-paths from multiple profiles by `guix package --search-paths`, in > ~/.bashrc and ~/.zprofile (skeletons, so existed systems need manual > update). > > > Close now!

bug#63451: Guix pull not successful

sure. I just did a btrfs scrub which didnt find anything (not sure if things have fixed themselves day to day though). i also did guix gc --verify which did not report anything. if the error is possibly filesystem related - i did disable my btrfs compression earlier that day since it was

bug#63198: cups-service-type uses PAM-enabled 'cups' by default which prevents authentication

Hi, muradm writes: > Fixes . > > Makes CUPS service to extend pam-root-service-type providing minimal > configuration to authenticate users. Since PAM authentication is > provided, cups package can be used as default. > > * gnu/services/cups.scm

bug#63198: cups-service-type uses PAM-enabled 'cups' by default which prevents authentication

Hi, muradm writes: > This change broke cups for me like this: > > I [13/May/2023:16:14:27 +0300] [Client 16] Started > "/gnu/store/9kdm8k84j2xqlax4zaarchw00cfs62zz-cups-server-bin/lib/cups/daemon/cups-deviced" > > (pid=21409, file=14) > E [13/May/2023:16:14:27 +0300] [CGI] cups-brf must be

bug#63198: cups-service-type uses PAM-enabled 'cups' by default which prevents authentication

Hi, muradm writes: > Could you please elaborate more on "loop on authenticating my user" > from above and "prevents users from authenticating" from commit > message? Does it mean that you could not authenticate as your user > at all, or does it relates to authentication at http://localhost:631

bug#63274: [PATCH] gnu: dia: Update to 0.97.3-4.b903dd8

Hello, gentle ping (and I forgot to Cc: the gnome team) Thanks! Gio' Giovanni Biscuolo writes: [...] -- Giovanni Biscuolo Xelera IT Infrastructures signature.asc Description: PGP signature

bug#20255: 'search-paths' should respect both user and system profile.

Hi, 宋文武 writes: > Hello, commit 40310efde9b4a4f2cf98081d6cd10f843685ebb6 fix this by merge > search-paths from multiple profiles by `guix package --search-paths`, in > ~/.bashrc and ~/.zprofile (skeletons, so existed systems need manual > update). > > > Close now! Cool, thanks for the

bug#63261: Recent changes to git config cause errors for non-committers

Hi Leo, Leo Famulari writes: > Can someone help me by pointing to the original discussion of this > change? It was the team.scm issue in https://issues.guix.gnu.org/58813 that led to this change. -- Thanks, Maxim

bug#63514: alacritty>=0.12.0 does not work with Wayland

On Mon, May 15, 2023 at 09:18:01AM +0200, Lars-Dominik Braun wrote: > Hi Efraim, > > since the upgrade from alacritty 0.9 to 0.12 it does not work any more > with the DISPLAY environment variable unset (i.e. without xwayland). The > error message is: > > thread 'main' panicked at 'Failed to

bug#63516: Static networking should wait for interfaces to be up

Hi! With shepherd 0.10.0 starting services in parallel, I observed ‘networking’ (from ‘static-networking-service-type’) starting too early, before the corresponding interfaces were available: --8<---cut here---start->8--- [ 21.863249] shepherd[1]: Service

bug#63514: alacritty>=0.12.0 does not work with Wayland

On Mon, May 15, 2023 at 11:07:50AM +0200, Lars-Dominik Braun wrote: > Hi, > > > easy reproducer: 'DISPLAY="" alacritty' gives the same error. > > that’s exactly what I used under Wayland, otherwise it’ll fall back > to XWayland with ugly font rendering (because of my hidpi monitor). > > > Do

bug#63514: alacritty>=0.12.0 does not work with Wayland

Hi, > easy reproducer: 'DISPLAY="" alacritty' gives the same error. that’s exactly what I used under Wayland, otherwise it’ll fall back to XWayland with ugly font rendering (because of my hidpi monitor). > Do you know if the X11 error is also a problem? Not sure what you mean. As I wrote it

bug#63514: alacritty>=0.12.0 does not work with Wayland

On Mon, May 15, 2023 at 09:18:01AM +0200, Lars-Dominik Braun wrote: > Hi Efraim, > > since the upgrade from alacritty 0.9 to 0.12 it does not work any more > with the DISPLAY environment variable unset (i.e. without xwayland). The > error message is: > > thread 'main' panicked at 'Failed to

bug#63514: alacritty>=0.12.0 does not work with Wayland

Hi Efraim, since the upgrade from alacritty 0.9 to 0.12 it does not work any more with the DISPLAY environment variable unset (i.e. without xwayland). The error message is: thread 'main' panicked at 'Failed to initialize any backend! Wayland status: NoWaylandLib X11 status: XOpenDisplayFailed',