all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Vincent Legoll <vincent.legoll@gmail.com>
Cc: 41413-done@debbugs.gnu.org
Subject: bug#41413: guix-install.sh broken on Gentoo
Date: Wed, 05 May 2021 00:56:11 -0400	[thread overview]
Message-ID: <87zgx9kcd0.fsf@gmail.com> (raw)
In-Reply-To: <c5247b7e-91f9-fd4f-eec8-1caa995f6f7a@gmail.com> (Vincent Legoll's message of "Sat, 30 May 2020 10:24:28 +0200")

Hi Vincent,

Vincent Legoll <vincent.legoll@gmail.com> writes:

> Hello Tobias, ZC,
>
> I created a gentoo VM (i686 / following gentoo handbook) and tried
> the official upstream guix installer.
>
> It worked properly, not detecting the OS init system, I think this is
> because the gentoo handbook made me install cronie instead of plain
> cron, so there's no "/etc/init.d/cron" file. And so it did not try to
> install the guix-daemon service init.d file through update-rc.d.
> And told me to run the daemon manually, which worked OK.
>
> Running it with a local guix-install.sh + binary tarball with my
> pending changes (which includes openrc support). It also worked
> properly, detecting the OS as being openrc managed and doing what
> is needed.
>
> So, I'll still cook up a patch to fix sysvinit detection, because
> assuming sysvinit on the mere presence of /etc/init.d/cron is not
> really the right thing to do. (and the fix will need to be tested
> on a sysvinit-based distro, which I'll do)
>
> But on the other hand, I don't know what to do with this bug report,
> I cannot reproduce the exact problem, and I'm not trying all the other
> available cron variants from gentoo (bcron, dcron, fcron).
>
> So either ZC tells us more about his setup and shows us more output
> to be able to understand what did go wrong, or we cannot help further.
>
> Couldn't keep ZC CC'ed as the issue was created without his email
> address, let's hope he follows it via another way...

It seems the installer is working fine as per your tests and that the
original issue cannot be reproduced.  I'm closing this bug.

Thank you,

Maxim




  reply	other threads:[~2021-05-05  4:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-19 23:27 bug#41413: guix-install.sh broken on Gentoo Tobias Geerinckx-Rice via Bug reports for GNU Guix
2020-05-19 23:45 ` ZC via web
2020-05-20  0:09   ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2020-05-20 22:14 ` Vincent Legoll
2020-05-30  8:24 ` Vincent Legoll
2021-05-05  4:56   ` Maxim Cournoyer [this message]
2021-05-05  7:43     ` Vincent Legoll

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

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

  git send-email \
    --in-reply-to=87zgx9kcd0.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=41413-done@debbugs.gnu.org \
    --cc=vincent.legoll@gmail.com \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.