From: Ricardo Wurmus <rekado@elephly.net>
To: "Jakob L. Kreuze" <zerodaysfordays@sdf.lonestar.org>
Cc: guix-devel@gnu.org
Subject: Re: "guix deploy" is in git master
Date: Mon, 08 Jul 2019 22:23:48 +0200 [thread overview]
Message-ID: <87imscjmwb.fsf@elephly.net> (raw)
In-Reply-To: <87y318gu3b.fsf@sdf.lonestar.org>
Jakob L. Kreuze <zerodaysfordays@sdf.lonestar.org> writes:
> zerodaysfordays@sdf.lonestar.org (Jakob L. Kreuze) writes:
>
>> Well, we can pick and choose which exceptions we continue on. For
>> services not being started, we can probably carry on with the
>> deployment. I think, ideally, in the situations where 'guix deploy'
>> should stop, we should try to clean up a bit? Though I'm not yet sure
>> how we'd go about that aside from rolling back the system generation.
>
> On that note, perhaps I'll hold off for now on a patch to better handle
> SSH authentication errors. Error reporting is the common issue here.
Sounds good. A more general strategy is needed here.
--
Ricardo
next prev parent reply other threads:[~2019-07-08 20:24 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-06 6:17 "guix deploy" is in git master Christopher Lemmer Webber
2019-07-05 23:33 ` Jakob L. Kreuze
2019-07-05 23:34 ` Jakob L. Kreuze
2019-07-06 9:29 ` Ricardo Wurmus
2019-07-06 11:51 ` Jakob L. Kreuze
2019-07-06 9:23 ` Christopher Lemmer Webber
2019-07-06 17:22 ` Ricardo Wurmus
2019-07-06 17:17 ` Christopher Lemmer Webber
2019-07-07 0:12 ` Mark H Weaver
2019-07-07 7:55 ` Ricardo Wurmus
2019-07-07 6:55 ` Christopher Lemmer Webber
2019-07-08 17:15 ` Jakob L. Kreuze
2019-07-07 8:05 ` Ricardo Wurmus
2019-07-07 14:45 ` Ludovic Courtès
2019-07-08 17:37 ` Jakob L. Kreuze
2019-07-08 19:27 ` Ricardo Wurmus
2019-07-08 20:11 ` Jakob L. Kreuze
2019-07-08 20:16 ` Jakob L. Kreuze
2019-07-08 20:23 ` Ricardo Wurmus [this message]
2019-07-10 13:51 ` Thompson, David
2019-07-10 17:39 ` Jakob L. Kreuze
2019-07-11 4:27 ` Christopher Lemmer Webber
2019-07-11 15:43 ` Ludovic Courtès
2019-07-11 16:58 ` Jakob L. Kreuze
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=87imscjmwb.fsf@elephly.net \
--to=rekado@elephly.net \
--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).