From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ricardo Wurmus Subject: Re: "guix deploy" is in git master Date: Mon, 08 Jul 2019 21:27:36 +0200 Message-ID: <87lfx8jphz.fsf@elephly.net> References: <87a7drn0ux.fsf@dustycloud.org> <874l3zse7o.fsf@elephly.net> <87wogujmld.fsf@elephly.net> <871rz19a4h.fsf@gnu.org> <87r270ig1d.fsf@sdf.lonestar.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:36640) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hkZIt-0006WL-0b for guix-devel@gnu.org; Mon, 08 Jul 2019 15:28:00 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hkZIq-0006zQ-6D for guix-devel@gnu.org; Mon, 08 Jul 2019 15:27:58 -0400 In-reply-to: <87r270ig1d.fsf@sdf.lonestar.org> 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: "Jakob L. Kreuze" Cc: guix-devel@gnu.org Hi Jakob, > Ricardo Wurmus writes: > >> I tried again and it started building things but then aborted like >this: [=E2=80=A6] >> guix/remote.scm:66:17: In procedure %remote-eval: >> Throw to key `srfi-34' with args `(# name: \"root\" password: \= "\" uid: 0 group: \"root\" supplementary-groups: () comment: \"System admin= istrator\" home-directory: # create-home-dire= ctory?: #t shell: \"/gnu/store/qn1ax1fkj16x280m1rv7mcimfmn9l2pf-bash-4.4.23= /bin/bash\" system?: #f>")] 1837f00>>)'. >> >> Do you know what might be wrong here? > > Ludovic Court=C3=A8s writes: > >> I suspect the bug has nothing to do with =E2=80=98remote-eval=E2=80=99. = Namely, if the >> machine you=E2=80=99re reconfigure is running Guix from before commit >> 6061d01512081c93c53fdd1d4302b36696403061 (March 2019), then restart >> the =E2=80=98user-homes=E2=80=99 services fails with this error for obsc= ure reasons >> that I forgot. > > The throw is coming from 'upgrade-shepherd-services' making a call to > 'start-service', so I think that Ludovic is on the right track. What > version of Guix is the remote running, Ricardo? If it's a recent commit, > I worry that a bad 'user-homes' service file was sent over, or perhaps > not sent over at all... The remote=E2=80=99s Guix is pretty old, so it=E2=80=99s likely that Ludo i= s right. So, I actually reconfigured these machines semi-successfully, eh? Neat! > Regardless, it's undesirable to have the deployment aborted half-way > through. Ludovic -- I've wrapped my calls to 'unload-service' in > 'false-if-exception'. =E2=80=9Cfalse-if-exception=E2=80=9D isn=E2=80=99t great because it swallow= s the errors. I=E2=80=99d still very much like to see the errors =E2=80=93 I just don=E2=80=99t want = to see a backtrace is all. Similarly, it would be great if =E2=80=9Cguix deploy=E2=80=9D would continu= e deploying other machines in the list even if one of them couldn=E2=80=99t be deployed= due to an error. I have a list of 24 machines and a few of them fail with the user-homes error above. Would be nice if all the other deployments would still go through, because they are independent. (On the other hand, the current behaviour might be desirable in case there=E2=80=99s a problem with =E2=80=9Cguix deploy=E2=80=9D itself. Rathe= r break just one machine instead of wrecking the whole site. Dunno.) > As a side note, congratulations on being the first person to upgrade a > machine with 'guix deploy', Ricardo! Yay! -- Ricardo