bug#51787: Disk performance on ci.guix.gnu.org

Hello Ricardo, > Should we attempt to overwrite /gnu/store and rely exclusively on > substitutes from the cache? Yes, I don't see any other options. Before that, what might be nice could be: 1. Ensure that all Berlin /var/cache/guix/publish directory is synchronized on Bordeaux. We are now at

bug#52791: nextcloud-client not building on master

Hello Nicholas, Nicholas von Klitzing writes: > Updating the package to 3.2.0 (the version where the PR was merged) solves > the issue. This patch is attached. > > I'll see if I get to updating it to 3.4.1 > * gnu/packages/sync.scm (nextcloud-client): Update to 3.2.0. > --- > gnu/packages/sync

bug#52801: Bug report

Today's guix pull gives the following bug. shegeley@zone51 ~$ guix pull Updating channel 'nonguix' from Git repository at 'https://gitlab.com/nonguix/nonguix'... Updating channel 'guix' from Git repository at 'https://git.savannah.gnu.org/git/guix.git'... Building from these channels: guix

bug#52801: Guile inconsistently misbehaves in case of escapes and carriage returns, breaking "guix pull"

retitle 52801 Guile inconsistently misbehaves in case of escapes and carriage returns, breaking "guix pull" severity 52801 important thanks Grigory Shepelev schreef op zo 26-12-2021 om 13:14 [+0300]: Today's guix pull gives the following bug. Seems like an instance of

bug#52797: texlive broken install

Thanks for the hint Tobias, I am currently on a foreign installation of Guix after some time on Guix System, and did not appreciate that guix-daemon ran off of the root user's guix. Simply running `guix pull` as root and restarting the daemon fixed this issue. I see Jéŕemy posted in the 'help' ma

bug#52797: texlive broken install

Michael, Michael Zappa 写道： I am currently on a foreign installation of Guix after some time on Guix System, and did not appreciate that guix-daemon ran off of the root user's guix. Simply running `guix pull` as root and restarting the daemon fixed this issue. \o/ I see Jéŕemy posted in the

bug#52807: Guix home executables are not executable

I'd like to use `guix home` to symlink an executable into my home directory. Following simple configuration stored at `~/.dotfiles/home-configuration.scm` > (use-modules > (gnu home) > (gnu packages) > (gnu home services) > (gnu services) > (guix gexp) > (gnu home services shells)) >

bug#52808: Guix home should not assume that all targets are dot files

The following configuration results in a `~/.run` symlink being created. My expectation is that a `~/run` symlink is created instead. (ie. not a dotfile) > (home-environment > (services > (list (service > home-bash-service-type > (home-bash-configuration >

bug#52807: Guix home executables are not executable

Hi, On 2021-12-26, 12:03 -0500, "Nick Zalutskiy" wrote: > I'd like to use `guix home` to symlink an executable into my home > directory. > > Following simple configuration stored at > `~/.dotfiles/home-configuration.scm` > > (use-modules >(gnu home) >

bug#52539: Fwd: Comments in /etc/passwd don't get updated

Thanks for the explanation. This rationale sounds reasonable to me. If someone with proper permission has modified a user account's comment, it could be important to preserve that customization. As I pointed out in an earlier message, I believe this behavior contradicts the documentation of the `u

bug#52807: Guix home executables are not executable

Indeed I missed this in the manual. Thank you! I was trying to figure out how to close this... no luck. -Nick On Sun, Dec 26, 2021, at 4:44 PM, Aleksandr Vityazev wrote: > Hi, > > On 2021-12-26, 12:03 -0500, "Nick Zalutskiy" wrote: > >> I'd like to use `guix home` to symlink an executable

bug#52483: GnuPG 2.2.30 cannot do symmetric encryption

On Sun, Dec 19, 2021 at 03:36:25PM -0500, Leo Famulari wrote: > On Sun, Dec 19, 2021 at 03:25:42PM -0500, Maxim Cournoyer wrote: > > > I tested with GnuPG 2.2.23 by building all packages that depend directly > > > on GnuPG. There were no new failures on x86_64-linux when using GnuPG > > > 2.2.32. >

bug#50433: shotcut 21.06.29 missing bin files

Fixed in bc74c191df789ff200da6f81c3cf599eae39ca8e. Closing.