Hello,
Cayetano Santos <[email protected]> writes: > 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), How exactly are you checking that? I am asking since the guix inside of the image would be 1.5.0 till yesterday, that is correct. Guix package was never updated past 1.5.0 until yesterday. So till yesterday, the `guix describe` in the image would always be producing the 1.5.0 tag commit. `guix system describe` should be used to read the system provenance. > 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 So it seems there should be a cache if the build system here supports that. Or a newer tarball should be built instead of doing guix pull. > 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 This log has no guix describe for later, so it's impossible to know what guix has been used during the build. Also, what does the provenance inside of the image look like? (in /var/guix/profiles/system/provenance, or through `guix system describe`)? Rutherther
