As Ludo mentioned on IRC, this issue could be caused by parallel
compilation on our 64-core server. At first it seemed related to using
the '--url' option, but I just was able to reproduce this problem using
only 'guix pull'. I'll look into how I can reduce the number of cores
used for compilation
On Tue, Jul 11, 2017 at 06:04:47PM +0200, Joshua Sierles wrote:
> I tried 'guix pull' and it worked fine. Then, tried using a git commit
> from master's tip, which should be the same contents. This link contains
> the outputs for both attempts.
>
> https://gist.github.com/jsierles/0177424733612947
I tried 'guix pull' and it worked fine. Then, tried using a git commit
from master's tip, which should be the same contents. This link contains
the outputs for both attempts.
https://gist.github.com/jsierles/0177424733612947d61af8533084841e
--
Joshua Sierles
jos...@joshua.si
Thanks for looking at this Ludo.
In systemd the systemd-logind.service looks a little like this:
[Service]
ExecStart=/usr/lib/systemd/systemd-logind
BusName=org.freedesktop.login1
It looks as though it simply executes the systemd-logind program.
Shouldn't our shepherd service simply
Danny Milosavljevic skribis:
> * gnu/packages/groff.scm (groff)[arguments]: Add phase "setenv".
> ---
> gnu/packages/groff.scm | 9 -
> 1 file changed, 8 insertions(+), 1 deletion(-)
>
> diff --git a/gnu/packages/groff.scm b/gnu/packages/groff.scm
> index 67dd1dbfa..6e1a60e9b 100644
> --
Hi Diego,
Diego Nicola Barbato skribis:
> l...@gnu.org (Ludovic Courtès) writes:
>
>> Hello Diego,
>>
>> Diego Nicola Barbato skribis:
>>
>>> When running the command "guix pull && guix package -i python@2 python"
>>> instead of installing the latest version of python2 and python3, as it
>>> us
Hi,
(Please keep 27580-d...@debbugs.gnu.org Cc’d.)
William skribis:
> Shouldn't our shepherd service simply execute elogind-program-wrapper?
> This may also be right because elogind handles things like the laptop
> lid being closed, which should be handled even if no one has logged in
> yet.
G
