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
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,
Hi,
With the recent adoption of $PAGER in `guix search` I'm experiencing an issue.
The some of the firsts lines are not shown if the output long enough to cover
the full screen so I can't see the first package name. It forces me to scroll
down and up again.
If I run `guix search | less` works
Ekaitz,
Ekaitz Zarraga 写道：
With the recent adoption of $PAGER in `guix search` I'm
experiencing an issue. The some of the firsts lines are not
shown if the output long enough to cover the full screen so I
can't see the first package name. It forces me to scroll down
and up again.
[…]
Is
Hello,
We are pleased to announce a Hackathon about Reproducible Science.
We propose to collectively tackle some issues on *Friday, July 3rd*:
- identify stumbling blocks in using Guix to write end-to-end
pipelines,
- document how to achieve this,
- feed the Guix-Past channel by other old
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
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
We at UTHSC are game. We are struggling with an old version of the
GeneNetwork web service 1.x which is now running on a 10 year old
CentOS. The backup time machine server died recently.
GenNetwork1 depends on Python 2.4(!) with modules that have not been
updated this century, and an older
