bug#42151: [PATCH 4/3] database: Do not use journal_model=WAL for the Hurd.
Jan Nieuwenhuizen writes: > Jan Nieuwenhuizen writes: > > Adding one additional patch to this series, hence 4/3 (see attached) > fixes the sqlite problem. For clarity -- patches 1-4 really do fix offloading to the Hurd and this... > After the build succeeds, the download fails but lets first get this > patch series done... ...is not true; you gat that when you (I) forgot to add keys in /etc/guix/ As seen on IRC, possibly Ricardo will an update for the QEMU command-line (at least for berlin), adding "--cpu base". Janneke -- Jan Nieuwenhuizen | GNU LilyPond http://lilypond.org Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.com
bug#42118: Editing pulseaudio config file fails with "No such file or directory"
So if I disable pulseaudio autostart, and start it from bash, I get these errors bash-5.0$ pulseaudio E: [pulseaudio] module-jack-sink.c: jack_client_open() failed. E: [pulseaudio] module.c: Failed to load module "module-jack-sink" (argument: ""): initialization failed. E: [pulseaudio] module-jack-source.c: jack_client_open() failed. E: [pulseaudio] module.c: Failed to load module "module-jack-source" (argument: ""): initialization failed. So pulseaudio is seeing my settings correctly, but some other problem is preventing it from working. On Wed, Jul 1, 2020 at 7:01 AM Ricardo Wurmus wrote: > > > Leo Prikler writes: > > > Am Mittwoch, den 01.07.2020, 04:33 -0500 schrieb Nathan Dehnel: > >> > Due to a bug with webkit sandboxing, we no longer put daemon.conf > >> > into > >> /etc/pulse (my bad), but rather set PULSE_CONFIG to directly point to > >> it. > >> I meant to say /gnu/store//etc/pulse/daemon.conf. > >> > >> > I am currently unsure, at which point this variable > >> gets updated (I still think you need to reboot) > >> > >> I rebooted and everything seems the same. > >> > >> Maybe the problem is pulse uses Jack1 as a dependency and I'm trying > >> to use Jack2. > > This should not be a problem. JACK2 only differs for users but not in > terms of the API when building software. In Guix we only build with > JACK1 for consistency. > > -- > Ricardo
bug#41702: `guix environment` performance issues
Hi Ludo, > I’d rather wait; perhaps you can ask Artyom whether they’re planning for > a new release soonish? “I'll see if I can fix some random test failures with Guile 2.2 that sometimes occur, and then I'll prepare a new release.” > If there’s no plan for a release within two weeks, we can go ahead with > the patch you propose. Alright, I’ll prepare a new patch if either of the two events happen. Cheers, Lars signature.asc Description: PGP signature
bug#41702: `guix environment` performance issues
Hi, Lars-Dominik Braun skribis: > and the attached patch uses the new nodelay option, if we don’t want to wait > for another guile-ssh release. I’d rather wait; perhaps you can ask Artyom whether they’re planning for a new release soonish? If there’s no plan for a release within two weeks, we can go ahead with the patch you propose. > From 2892f79f819dd2dd9420f7e74bcb6e293d377452 Mon Sep 17 00:00:00 2001 > From: Lars-Dominik Braun > Date: Thu, 2 Jul 2020 13:59:51 +0200 > Subject: [PATCH] guix: Add nodelay to SSH store connection > > * gnu/packages/ssh.scm (guile-ssh)[patches]: Add patch. > * gnu/packages/patches/guile-ssh-0.12.0-nodelay.patch: New file. > * gnu/local.mk (dist_patch_DATA): Add it. > * guix/ssh.scm (open-ssh-session): Use new nodelay option. If we take this route, the two patches (guile-ssh changes, then (guix ssh) changes) should be separate. Also #:nodelay will cause a hard failure for people using an older Guile-SSH. I wonder how to guard against that; configure check, or run-time Guile-SSH version check? > +++ b/gnu/packages/patches/guile-ssh-0.12.0-nodelay.patch It would be good to include the URL of the upstream issue Thanks! Ludo’.
