From: "Brant Gardner" <mail@lnklnx.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 34580@debbugs.gnu.org
Subject: bug#34580: Service ssh-daemon could not be started
Date: Sat, 28 Sep 2019 07:38:49 -0500 [thread overview]
Message-ID: <754a6968-2d9e-431d-a545-7580fd81b7db@www.fastmail.com> (raw)
In-Reply-To: <87pnjkzrca.fsf@gnu.org>
Hi Ludo;
Okay, I did those steps exactly:
- clone
- patch -p1 < your-patch
- ./bootstrap
- ./configure --localstatedir=/var
- make check
- sudo -E ./pre-inst-env guix system reconfigure /path/to/myconfig.scm
- reboot
I had no issues or errors at any step and on reboot ssh-daemon tried & failed to start so all went according to plan, but /tmp does *not* have a ssh log file in it.
Not sure where this went sideways, any advice?
Thank you,
--
Brant Gardner
On Sat, Sep 28, 2019, at 04:45, Ludovic Courtès wrote:
> Hi Brant,
>
> "Brant Gardner" <mail@lnklnx.com> skribis:
>
> > Going to show my ignorance here - I've contributed some packages by
> > making things in a 'guix environment' and then extracting patches, but
> > what you need me to do is activate a configuration change in a 'live'
> > guix install (and on a service rather than a package, also new-ish to
> > me) so it sticks over a reboot. This is not something I've done
> > before and I'm not finding docs for it, can you direct me?
>
> Sure, sorry for not being clearer.
>
> So you would apply the patch I sent over a fresh checkout of Guix, like
> so:
>
> git clone https://git.savannah.gnu.org/git/guix.git
> cd guix
> patch -p1 < the-patch
>
> Then you need to build Guix from that checkout:
>
> https://guix.gnu.org/manual/en/html_node/Building-from-Git.html
>
> Finally, you can reconfigure your system from that checkout with:
>
> sudo -E ./pre-inst-env guix system reconfigure …
>
> Let me know how it goes!
>
> Thanks,
> Ludo’.
>
next prev parent reply other threads:[~2019-09-28 12:42 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-19 21:21 bug#34580: Service ssh-daemon could not be started Andreas Enge
2019-02-20 22:21 ` Leo Famulari
2019-02-20 22:48 ` Andreas Enge
2019-02-20 22:51 ` Leo Famulari
2019-02-20 23:08 ` Andreas Enge
2019-02-20 23:56 ` Leo Famulari
2019-03-14 22:11 ` Leo Famulari
2019-03-15 16:35 ` Leo Famulari
2019-02-22 6:52 ` Chris Marusich
2019-09-20 20:00 ` Brant Gardner
2019-09-24 8:08 ` Ludovic Courtès
2019-09-24 12:20 ` Brant Gardner
2019-09-26 20:48 ` Ludovic Courtès
2019-09-27 14:57 ` Brant Gardner
2019-09-28 9:45 ` Ludovic Courtès
2019-09-28 12:38 ` Brant Gardner [this message]
2019-09-28 13:54 ` pelzflorian (Florian Pelz)
2019-09-28 17:44 ` Ludovic Courtès
2019-09-28 18:23 ` Danny Milosavljevic
2019-09-28 18:31 ` Danny Milosavljevic
2019-09-28 19:47 ` Ludovic Courtès
2019-09-28 19:47 ` Ludovic Courtès
2019-09-29 13:02 ` Brant Gardner
2019-09-28 14:11 ` Ludovic Courtès
2019-10-09 14:49 ` Brant Gardner
2019-10-11 10:14 ` Ludovic Courtès
2019-10-12 12:09 ` Brant Gardner
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=754a6968-2d9e-431d-a545-7580fd81b7db@www.fastmail.com \
--to=mail@lnklnx.com \
--cc=34580@debbugs.gnu.org \
--cc=ludo@gnu.org \
/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.