Hi Guix, Regarding a system.scm [0] file, this command
image=$(guix system image --image-type=qcow2 --image-size=16GB
--save-provenance system.scm)
Produces always the same image (corresponding to guix log tag v1.5.0),
regardless of the status of current guix. I would intuitively expect
it instead to build an up to date image, identical to current local
guix. Or at least, this was my first intuition about a rolling release.
Is this correct, or am I doing something wrong ? Is there a means to
produce an up to date image, other than building v1.5.0 followed by a
guix pull ? This approach is problematic, as the time it takes
increases with the number of commits since v1.5.0, which following the
application, finally times out [1].
Thanks !
--
Cayetano Santos
[0]
https://git.sr.ht/~sircmpwn/builds.sr.ht/tree/master/item/images/guix/system.scm
[1] https://builds.sr.ht/~sircmpwn/refresh/guix
signature.asc
Description: PGP signature
