From mboxrd@z Thu Jan 1 00:00:00 1970 From: zerodaysfordays@sdf.lonestar.org (Jakob L. Kreuze) Subject: Re: "guix deploy" is in git master Date: Mon, 08 Jul 2019 16:16:40 -0400 Message-ID: <87y318gu3b.fsf@sdf.lonestar.org> References: <87a7drn0ux.fsf@dustycloud.org> <874l3zse7o.fsf@elephly.net> <87wogujmld.fsf@elephly.net> <871rz19a4h.fsf@gnu.org> <87r270ig1d.fsf@sdf.lonestar.org> <87lfx8jphz.fsf@elephly.net> <875zoci8x6.fsf@sdf.lonestar.org> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:47750) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hka4E-0002Mf-J2 for guix-devel@gnu.org; Mon, 08 Jul 2019 16:17:01 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hka4A-0007ut-K4 for guix-devel@gnu.org; Mon, 08 Jul 2019 16:16:52 -0400 Received: from mx.sdf.org ([205.166.94.20]:55934) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1hka48-0007t2-4Q for guix-devel@gnu.org; Mon, 08 Jul 2019 16:16:48 -0400 In-Reply-To: <875zoci8x6.fsf@sdf.lonestar.org> (Jakob L. Kreuze's message of "Mon, 08 Jul 2019 16:11:01 -0400") List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Ricardo Wurmus Cc: guix-devel@gnu.org --=-=-= Content-Type: text/plain 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. Regards, Jakob --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEa1VJLOiXAjQ2BGSm9Qb9Fp2P2VoFAl0jpKgACgkQ9Qb9Fp2P 2VrZuw/9GAwgUiVz7npMxWym4VXjhZm5Tp7VIe/HbZODRlictmwmW3cqxGOYKjnh sUyeWWOzoOU53yhI1+wE6NFBll6j3K/sMvd9V4SCqyCRCYk7uF88bpdxaV4WR9uX ALp4Wbv9wBB35yE0oFCAk9Mx8OF73UKaPCMiguBkLgFUunY+psWK5agQd248ttWv TuQSijMoKsNw+67jGc1PA69Rf76nh5QrbWPL6VIla84axF7ut188gViV/NV3f6U8 DBt+nVwrpZ0igTqjvHDMDtXaZTmtRtgtbR53tCje2rkEyG8mz7g6xGmteVP1XBc7 zWEatqR7/Fe2CcnNUxek/F1H1ZYMnlG+QDzhL/dV4B8c+RwJygfvo00lOSZvJQuz pVcxA3sU5Dl8z2PPiTflDNIpSb+8hoLmIKJ3kccaZWbQQm8Bmxg7q5hjk4qXLg5R zGqrDlhTxyyDJEOgX4mFTnWeMUmylgjOzmltQhIxFpqjWHjVGrLS2UTY98gpktuU bDehNFdCGP3cgxUFgI9Bz2i6RizdqIV9MqJxU1FJePYxhza9Pp5LcbezzniYJKJ6 QUtUYJ6CmXak8RhJpkvDWEy28Ih0IRMjb58bDmA/qDsottkI26oxmEZ6Te7GPJkA ibQIGRcTJCUKevSEQQRzxVRCHt4uLPQC35uNUczxHJNDP0Md/uI= =ImKR -----END PGP SIGNATURE----- --=-=-=--