bug#37569: Mount does not honor 'user' option.

2019-10-01 Thread Diego Nicola Barbato
Hello Danny, Danny Milosavljevic writes: > Hmm, how is that solved with other distributions? Is "mount" suid root there? Indeed, in Debian both mount and umount are suid root: $ stat -c "%a %U:%G %n" /bin/*mount 4755 root:root /bin/fusermount 4755 root:root /bin/mount 4755 root:root

bug#37565: [use profile manifest] upstream VCS informations only available after a guix pull

2019-10-01 Thread Ludovic Courtès
Hi, YOANN P skribis: >>> YOANN P skribis: >>> Not sure if it should be considerated as a bug but it seems that the >>> upstream VCS information are only available after a "guix pull". >> >>You mean that ‘guix describe’ doesn’t work for ‘guix’ not obtained from ‘guix >>pull’, right? >> > >

bug#37505: "make check" fails on a fresh Guix checkout

2019-10-01 Thread Ludovic Courtès
Hello! Konrad Hinsen skribis: > OK, I triple-checked: there still is a problem. There are two places in > pull.scm that used '~*'. The attached patch removes the second one. Oops, my bad. > From 370579d7ac4e01fd66bdf4518d31f7d3bc17a65a Mon Sep 17 00:00:00 2001 > From: Konrad Hinsen > Date:

bug#37569: Mount does not honor 'user' option.

2019-10-01 Thread Danny Milosavljevic
Hmm, how is that solved with other distributions? Is "mount" suid root there? pgpO07B97QGhK.pgp Description: OpenPGP digital signature

bug#37505: "make check" fails on a fresh Guix checkout

2019-10-01 Thread Konrad Hinsen
Konrad Hinsen writes: > Konrad Hinsen writes: > >> Unfortunately, a very similar error still blocks compiling a fresh Guix >> checkout: > > Sorry, false alarm. I have been typing in the wrong terminal window. OK, I triple-checked: there still is a problem. There are two places in pull.scm that

bug#37569: Mount does not honor 'user' option.

2019-10-01 Thread Diego Nicola Barbato
Hey Guix, I have added the following to `file-systems' in my operating-system config: --8<---cut here---start->8--- (file-system (device "127.0.0.1")

bug#37565: [use profile manifest] upstream VCS informations only available after a guix pull

2019-10-01 Thread YOANN P
>De : Ludovic Courtès >Envoyé : mardi 1 octobre 2019 09:28 >À : YOANN P >Cc : 37...@debbugs.gnu.org <37...@debbugs.gnu.org> >Objet : Re: bug#37565: [use profile manifest] upstream VCS informations only >available after a guix pull > >Hi, > >> YOANN P skribis: >> Not sure if it should be

bug#37505: "make check" fails on a fresh Guix checkout

2019-10-01 Thread Konrad Hinsen
Konrad Hinsen writes: > Unfortunately, a very similar error still blocks compiling a fresh Guix > checkout: Sorry, false alarm. I have been typing in the wrong terminal window. Too many Guix installations in my life ;-) Konrad.

bug#37505: "make check" fails on a fresh Guix checkout

2019-10-01 Thread Konrad Hinsen
Ludovic Courtès writes: > Konrad Hinsen skribis: > >> e...@boldquot.po:2849: format specifications in 'msgstr[0]' are not a subset >> of those in 'msgid_plural' >> e...@boldquot.po:2856: format specifications in 'msgstr[0]' are not a subset >> of those in 'msgid_plural' >>

bug#37505: "make check" fails on a fresh Guix checkout

2019-10-01 Thread Ludovic Courtès
Hello, Konrad Hinsen skribis: > e...@boldquot.po:2849: format specifications in 'msgstr[0]' are not a subset > of those in 'msgid_plural' > e...@boldquot.po:2856: format specifications in 'msgstr[0]' are not a subset > of those in 'msgid_plural' >

bug#37550: [core-updates] [PATCH] gnu: gcc: Fix i686-linux cross compiler.

2019-10-01 Thread Ludovic Courtès
Hello, Thanks for pushing this patch! Jan Nieuwenhuizen skribis: > ./pre-inst-env guix build --target=i686-unknown-linux-gnu hello Note that on x86_64 you can perform native builds for i686 with “guix build -s i686-linux hello”. You probably already know it but I thought I’d mention it

bug#37565: [use profile manifest] upstream VCS informations only available after a guix pull

2019-10-01 Thread Ludovic Courtès
Hi, YOANN P skribis: > Not sure if it should be considerated as a bug but it seems that the upstream > VCS information are only available after a "guix pull". You mean that ‘guix describe’ doesn’t work for ‘guix’ not obtained from ‘guix pull’, right? > If it is not a bug, it will be nice to