bug#56226: Env variables in declared in home-fish-configuration not being exported

2022-06-25 Thread Mbk Kamble
Hi. Env variables enumerated in home-fish-configuration are translated into set VAR VALUE statements in config.fish file. This set VAR in global scope which is fine. However, for fish shell, if variables are to be exported, the command syntax is set -x VAR VALUE So serialize-fish-env-vars in gnu

bug#56223: h-client not running with a host distribution

2022-06-25 Thread Denis 'GNUtoo' Carikli
Hi, After having done a 'guix pull', I added h-client to a system image made with guix system image, and when running that image I could launch h-client with any of the following command lines: $ h-client $ sudo -E h-client However with Parabola i686 (also after having done a 'guix pull', h-clien

bug#51466: bug#53355: guix shell --check: confusing error message

2022-06-25 Thread Maxime Devos
b...@bokr.com schreef op za 25-06-2022 om 22:06 [+0200]: > BTW, IIRC, this can be used to create an invisible file that Invisible files don't have file names, so they cannot be put in the tiny shell script: > +(format > + #f "env >~a || /usr/bin/env >~a || set >~a; \ > +echo GUIX-CHECK-DO

bug#51466: bug#53355: guix shell --check: confusing error message

2022-06-25 Thread bokr
On +2022-06-25 19:40:48 +0200, Maxime Devos wrote: > Chris Marusich schreef op za 25-06-2022 om 09:52 [-0700]: > > Yes, I agree those are good reasons to avoid a temporary file if we > > can. > > To that end, do you know if we can somehow force Guile to use a > > specific > > file descriptor for th

bug#53355: guix shell --check: confusing error message

2022-06-25 Thread Maxime Devos
Chris Marusich schreef op za 25-06-2022 om 09:52 [-0700]: > Yes, I agree those are good reasons to avoid a temporary file if we > can. > To that end, do you know if we can somehow force Guile to use a > specific > file descriptor for the pipe?  In the patch I wrote earlier, which > uses > redirecti

bug#51466: bug#53355: guix shell --check: confusing error message

2022-06-25 Thread Chris Marusich
Hi Maxime, Maxime Devos writes: > Chris Marusich schreef op za 25-06-2022 om 02:07 [-0700]: >> It turns out that it is probably not OK to rely on shell redirection >> in >> this case, after all.  For example, "dash does not support multi- >> digit >> file descriptors": >> >> https://bugs.launch

bug#55443: closed (Re: [PATCH] gnu: emacs: Fix source snippet.)

2022-06-25 Thread Remco van 't Veer
Works for me, thank you! Cheers, Remco

bug#53355: bug#51466: bug#53355: guix shell --check: confusing error message

2022-06-25 Thread Maxime Devos
Chris Marusich schreef op za 25-06-2022 om 02:07 [-0700]: > It turns out that it is probably not OK to rely on shell redirection > in > this case, after all.  For example, "dash does not support multi- > digit > file descriptors": > > https://bugs.launchpad.net/ubuntu/+source/dash/+bug/249620 I c

bug#56209:

2022-06-25 Thread angry rectangle
forgot the attachment. (use-modules (gnu) (gnu system) (gnu bootloader grub) (gnu packages dns)) (use-package-modules linux certs) (use-service-modules networking) (operating-system (kernel linux-libre) (host-name "myhostname") (timezone "America/New_York") (locale "en_US.utf8") (bootloade

bug#56209: Shepherd 0.9 not cleanly unmounting root

2022-06-25 Thread angry rectangle
Since the upgrade to shepherd 0.9, I get "recovering journal" every single time I start my computer. To be specific, "recovering journal" appears after I enter my encryption password in the initrd. I assume this means the filesystem wasn't cleanly unmounted. I am doing a proper shutdown, using ei

bug#53355: guix shell --check: confusing error message

2022-06-25 Thread Chris Marusich
Hi Ludo & Everyone, Chris Marusich writes: > Is it OK to rely on shell redirection? It turns out that it is probably not OK to rely on shell redirection in this case, after all. For example, "dash does not support multi-digit file descriptors": https://bugs.launchpad.net/ubuntu/+source/dash/+