GNU bug report logs - #75414
[PATCH 0/2] Add roll-back action to guix deploy

Previous Next

Full log

View this message in rfc822 format

From: Ludovic Courtès <ludo <at> gnu.org>
To: Evgeny Pisemsky <mail <at> pisemsky.site>
Cc: arunisaac <at> systemreboot.net, 75414 <at> debbugs.gnu.org
Subject: [bug#75414] [PATCH 2/2] deploy: Add roll-back action.
Date: Sat, 25 Jan 2025 00:13:34 +0100

Hi,

Evgeny Pisemsky <mail <at> pisemsky.site> skribis:

>> Hmm I would rather have ‘guix deploy --roll-back’, although that’d be
>> different from ‘guix system’, primarily because I don’t see what other
>> actions we could have, and in particular how we’d name the default
>> action (‘guix deploy deploy’? ‘guix deploy really’? ‘guix deploy
>> please’?).
>
> The default action is =system reconfigure= on remote machine(s).
>
> This patch implements =system roll-back= on remote machine(s)
>
> I really miss =system delete-generations= on remote machine(s), which
> understands =build-locally?= and does not trigger a lot of downloads
> just to update grub, which happens when I run it directly on machine.

Yes, I understand.  My question is more about how we’d name that default
action.

And also noting that this is a broader change than just adding support
for roll-back.

> #+begin_example
> guix system reconfigure --machine servers.scm
> guix machine exec servers.scm -- herd restart something
> #+end_example

‘guix machine’ might actually be a better name than ‘guix deploy’.

> To me this is more flexible than one command that does everything. I
> can imagine a situation when I just need to run some command on all
> machines without reconfiguring them, which is currently impossible.

It’s possible:

  guix deploy machines.scm -x -- herd restart something

But yes, it could very well be called ‘guix machine exec …’.

Anyway, we’re going beyond what this patch series intended to address!

Ludo’.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.