GNU bug report logs - #50468
Should `guix deploy` save to the deployed server the operating-system, or the entire file passed into the command?

Previous Next

Package: guix;

Reported by: Katherine Cox-Buday <cox.katherine.e <at> gmail.com>

Date: Wed, 8 Sep 2021 03:10:01 UTC

Severity: normal

To reply to this bug, email your comments to 50468 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to bug-guix <at> gnu.org:
bug#50468; Package guix. (Wed, 08 Sep 2021 03:10:01 GMT) Full text and rfc822 format available.

Acknowledgement sent to Katherine Cox-Buday <cox.katherine.e <at> gmail.com>:
New bug report received and forwarded. Copy sent to bug-guix <at> gnu.org. (Wed, 08 Sep 2021 03:10:01 GMT) Full text and rfc822 format available.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Katherine Cox-Buday <cox.katherine.e <at> gmail.com>
To: bug-guix <at> gnu.org
Subject: Should `guix deploy` save to the deployed server the
 operating-system, or the entire file passed into the command?
Date: Tue, 07 Sep 2021 22:09:08 -0500
*Observed Behavior:*

Invoking `guix deploy my-config.scm` will store `my-config.scm` in the
deployed server's store, and links that as
`/run/current-system/configuration.scm`.

*Expected Behavior*

I expected the deployed server to only be made aware of the requested
`operating-system` declaration. In other words, `my-config.scm` contains
a list of machines, and each machine has an `operating-system`
declaration. I would expect each deployed machine to only have a copy of
their, and only their, `operating-system` declaration, fully resolved
from Guile variables into strings and such.

*Justification*

`guix deploy` expects a file that "evaluates to a list of machine
objects". Because of this, it is expected that multiple machines are
declared in a single file. These machines may not be related to each
other, and they may even have information that should be kept from one
another. Therefore, deploying the entire file's contents to a deployed
machine's remote store is incorrect behavior.

Further, `guix deploy` works if the file given does something like
`(load "my-private-stuff.scm")`. It will resolve the Guile variables
before deploying, and everything will work. But the `configuration.scm`
on the deployed server will only have a reference to the `load` which
won't be in the store. The unresolved Guile variables will be listed
where they are used.

*Workaround*

Each machine can reside in a separate file, and then `guix deploy` can
be executed for each file with:

find . -iregex '.*\.scm' -print -execdir guix deploy "{}" \;

-- 
Katherine




This bug report was last modified 2 years and 223 days ago.

Previous Next


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