Jan Wielkiewicz writes:
>> This means the daemon isn’t running.
>>
>> If you use SELinux in enforcing mode then the daemon is probably
>> prevented from starting.
> I'm not aware of this - I just picked all default settings, not that
> the choice was big.
It’s not Guix, it’s Fedora. Fedora s
On Tue, 30 Jun 2020 14:07:44 +0200
Ricardo Wurmus wrote:
>
> Hi Jan,
Hi!
>
> This means the daemon isn’t running.
>
> If you use SELinux in enforcing mode then the daemon is probably
> prevented from starting.
I'm not aware of this - I just picked all default settings, not that
the choice was
Hi Jan,
> I ran the script as root, it installed everything properly, but running
> "guix pull" ends up with an error message: "guix pull: failed to connect
> to `/var/guix/daemon-socket/socket': No such file or directory".
This means the daemon isn’t running.
If you use SELinux in enforcing m
I'm guessing that the systemd service to start the guix daemon failed...
Is there a way that you can manually enable & start the systemd daemon that
guix ships with?
June 29, 2020 6:05 PM, "Jan Wielkiewicz"
wrote:
> Hello,
>
> I'm trying to install Guix on Fedora using the install script, bu
Hello,
I'm trying to install Guix on Fedora using the install script, but
something is not right.
I ran the script as root, it installed everything properly, but running
"guix pull" ends up with an error message: "guix pull: failed to connect
to `/var/guix/daemon-socket/socket': No such file or di
