unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: Jan Wielkiewicz <tona_kosmicznego_smiecia@interia.pl>
Cc: guix-devel@gnu.org
Subject: Re: Installer script on Fedora doesn't work properly
Date: Tue, 30 Jun 2020 14:07:44 +0200	[thread overview]
Message-ID: <87a70koiy7.fsf@elephly.net> (raw)
In-Reply-To: <20200630000453.5f64b55b@interia.pl>


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 mode then the daemon is probably
prevented from starting.

> I think the installer script should *just work at all times* - this is
> crucial to make Guix popular on other distros.

Sure.  We have a draft SELinux policy for systems like yours, but it is
probably no longer current as Fedora’s SELinux policy is not frozen in
time.  I encourage you to try it and help debug it to adjust it for
current versions of Fedora.

> My suggestion: if it's not already done, consider adding automated
> tests, checking whether the installer script works on major
> distributions (on a VM) and if Guix works there. This should be checked
> every release.

These recommendations wouldn’t help in your case.  We can’t feasibly
maintain a farm of different distros (some with SELinux and some
without) where we install Guix all the time.

-- 
Ricardo


  parent reply	other threads:[~2020-06-30 12:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-29 22:04 Installer script on Fedora doesn't work properly Jan Wielkiewicz
2020-06-30 10:55 ` jbranso
2020-06-30 12:07 ` Ricardo Wurmus [this message]
2020-06-30 21:27   ` Jan Wielkiewicz
2020-06-30 22:30     ` Ricardo Wurmus

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87a70koiy7.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=guix-devel@gnu.org \
    --cc=tona_kosmicznego_smiecia@interia.pl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).