From: Jan Nieuwenhuizen <janneke@gnu.org>
To: "Jakob L. Kreuze" <zerodaysfordays@sdf.lonestar.org>
Cc: guix-devel@gnu.org
Subject: Re: “Towards Guix for DevOps”
Date: Sat, 27 Jul 2019 19:23:42 +0200 [thread overview]
Message-ID: <87zhkzcrxd.fsf@gnu.org> (raw)
In-Reply-To: <87sgqr1q0s.fsf@sdf.lonestar.org> (Jakob L. Kreuze's message of "Sat, 27 Jul 2019 11:00:19 -0400")
Jakob L. Kreuze writes:
Hi Jakob,
> Glad to hear you were able to get it working! And thanks for sharing
> those scripts. I spin up GuixSD virtual machines very frequently to work
> on this, and these look like they'd make that workflow much easier.
Oh, good. Yes, I wanted to try it for a while already but didn't get to
it and it's worth for anyone to give it a try.
>> Here's what deploying to a 0.16 machine gives me
>> guix/remote.scm:66:17: In procedure %remote-eval:
>> Throw to key `srfi-34' with args `(#<inferior-object #<condition &action-exception-error [service: user-homes action: start key: match-error args: ("match" "no matching pattern" "#<<user-account> name: \"root\" password: \"\" uid: 0 group: \"root\" supplementary-groups: () comment: \"System administrator\" home-directory: #<procedure home-directory (x)> create-home-directory?: #t shell: \"/gnu/store/qn1ax1fkj16x280m1rv7mcimfmn9l2pf-bash-4.4.23/bin/bash\" system?: #f>")] 716f00>>)'.
>> + ssh -i id_rsa -p 10022 root@localhost guix system list-generations
>>
>> After manually reconfiguring the machine to 1.0 it works, but that
>> already starts to feel clumsy :)
>
> I believe this is the same issue that Ricardo ran into when deploying to
> ci.guix.gnu.org. Sorry about that. Better error handling is something
> I'm working on at the moment.
Ah, right. I think I even saw that. Sorry for the noise.
> Though, I'm not quite sure what to do about this issue in particular, as
> (if I understand correctly) we concluded that this was a problem with
> the 'user-homes' service, and the idea of rolling out a workaround
> specific to that in 'guix deploy' doesn't sit particularly well with me.
Yes.
Greetings,
janneke
--
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.com
prev parent reply other threads:[~2019-07-27 17:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-12 17:10 “Towards Guix for DevOps” Ludovic Courtès
2019-07-13 5:29 ` Pierre Neidhardt
2019-07-13 17:11 ` Jakob L. Kreuze
2019-07-13 20:58 ` Pierre Neidhardt
2019-07-16 12:55 ` zimoun
2019-07-16 15:46 ` Jakob L. Kreuze
2019-07-24 18:59 ` Ricardo Wurmus
2019-07-24 19:19 ` Jakob L. Kreuze
2019-07-24 17:11 ` Ludovic Courtès
2019-07-24 18:37 ` zimoun
2019-07-24 19:19 ` Jakob L. Kreuze
2019-07-26 9:10 ` Alex Sassmannshausen
2019-07-26 14:17 ` Jakob L. Kreuze
2019-07-27 10:47 ` Jan Nieuwenhuizen
2019-07-27 15:00 ` Jakob L. Kreuze
2019-07-27 17:23 ` Jan Nieuwenhuizen [this message]
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=87zhkzcrxd.fsf@gnu.org \
--to=janneke@gnu.org \
--cc=guix-devel@gnu.org \
--cc=zerodaysfordays@sdf.lonestar.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 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).