Hi Attila, Attila Lendvai <att...@lendvai.name> writes:
> is there a way to make `guix system image` work from a guix checkout that > contains unauthorized commits? > > or is there an equivalent of channel intro commits in this context? > > or something else? I believe you would have to follow a similar process as what I did at https://issues.guix.gnu.org/71299#1. > Testing this is also a pain as well because it involves changing the > build daemon. In my experience the easiest way is: > > 1. Change the commit field for the guix package in > package-management.scm to the commit you want to check > > 2. Update the url field for the guix package to > "file:///path/to/guix/clone" > > 3. Forcefully disable authentication in guix/build-system/channel.scm > > 4. Generate an installer image via $ ./pre-inst-env guix system image > gnu/system/install.scm --image-type=iso9660, then boot from that image > and observe the output. I encountered this issue because the guix daemon put into a system image is based on the "guix" package, not the guix used to build said system image. If I recall correctly I disabled authentication by setting the default authenticate? value in build-channels to #f. You might be able to get away with just step 3 depending on what exactly you are changing in your checkout. -- Take it easy, Richard Sent Making my computer weirder one commit at a time.
