bug#30728: Modification for guix installation script.

Hi Tatiana, Tatiana Sholokhova writes: > Hello! My name is Tatiana. > > I have installed guix for the first time and noticed that the installation > script at > https://git.savannah.gnu.org/cgit/guix.git/tree/etc/guix-install.sh did not > work for me. So, I had to make

bug#30728: Modification for guix installation script.

Hi Clément, > As I said to Chris (Cc'ed), I don't think it's a good idea to install > Guix in root's home directory. Instead, we should probably honor the > USER and HOME environment variables, so that the command can be run as a > non-root user (with sudo) in a consistent way. What do you

bug#30728: guix-install.sh doesn't work if run with "sudo"

Hi Chris, Chris Marusich writes: > Clément Lassieur writes: > >> Clément Lassieur writes: >> >>> Hi, >>> >>> My system is Ubuntu 16.04. >>> >>> I ran './guix-install.sh' and got the message: "This script must be run >>> as

bug#30922: LUKS-encrypted root fails using device numbering, needs luksUUID

Hello, Jan Nieuwenhuizen skribis: > After booting I get > > Device /dev/nvme0n1p1 doesn't exist or access denied This message comes from ‘cryptsetup’. The ‘init’ script for the config you posted does this: --8<---cut here---start->8---

bug#30949: libp11-kit error

Hello list, This error shows when I try to configure debian's flatpak: $ /usr/bin/flatpak remote-add --if-not-exists flathub https://flathub.o rg/repo/flathub.flatpakrepo /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.26' not found (required by

bug#30916: Request: add a short description field for os-configuration

Hello, What about offering a way to specific the label of the new menu entry, or otherwise a suffix or prefix of the label? That is, you’d do: guix system reconfigure -m "The config that works just fine, I think." config.scm and that string would be used as the label itself in the GRUB

bug#30728: Modification for guix installation script.

Hi Ricardo and Marius, Marius Bakke writes: > The binary installation tarball only comes with a profile for 'root'. Indeed, but it's easy to copy it for any user isn't it? > The problem is that the installation script assumes $HOME will expand to > ~root when sourcing the

bug#30939: shepherd: detailed output should be placed into well-known location and not tty

Hi ng0, ng0 skribis: > Problem, not just when a service is misbehaving after successful system > reconfigure: > > $ sudo herd start smtpd > Password: > Service smtpd could not be started. > herd: failed to start service smtpd > > > > This is on virtual terminal in X11, as well as

bug#30728: Modification for guix installation script.

Hello! Could you please make that change on top of the current version of the > Guix sources as a git commit? Then you can run “git format-patch -1” to > format it as a patch in a format that we can apply. You can send the > resulting patch file as an attachment to a reply to this email. > This

bug#30006: bzip2 does not provide libbz2.so

Ludovic Courtès writes: > There’s no such function, which is unfortunate. But I agree it’s nicer > to preserve symlinks in this case. > > Perhaps we should actually do: > > (with-directory-excursion libdir > (symlink … "libbz2.so")) Thanks for the feedback everyone. I

bug#30939: shepherd: detailed output should be placed into well-known location and not tty

Hi Ludovic, Ludovic Courtès transcribed 790 bytes: > Hi ng0, > > ng0 skribis: > > > Problem, not just when a service is misbehaving after successful system > > reconfigure: > > > > $ sudo herd start smtpd > > Password: > > Service smtpd could not be started. > > herd: failed to

bug#30311: efi-less grub install fails

Any news on how to proceed on this grub target thing? I think the patch below is harmless enough and makes each grub package self-consistent (the non-efi grub doesn't try to use efi, the grub-efi tries to use efi and grub-hybrid tries to use efi, then). >From