From: Maxime Devos <maximedevos@telenet.be>
To: Florian Hoertlehner <hoertlehner@gmail.com>
Cc: 52267@debbugs.gnu.org
Subject: bug#52267: Acknowledgement (disk image installer for rock64 fails)
Date: Wed, 08 Dec 2021 19:20:13 +0000 [thread overview]
Message-ID: <3e0d6f2d8879ca8f83ad3d9cc7e8c88c3e8639fc.camel@telenet.be> (raw)
In-Reply-To: <CADXXfWkw+q8TuYZp1Cnujq+7QFMQkLQScYw-vKAejUqzMr8Epg@mail.gmail.com>
Florian Hoertlehner schreef op wo 08-12-2021 om 19:26 [+0100]:
> Do you know how I would do that? Do ai have to change th guix channel
> Definition for that? Would this still allow me to roll back in case
> something fails terribly? Or could it be that core-updates-frozen
> will crash my Main machine all together? Man's thanks!
The least risky method I know of, is to pull guix into a _separate_
profile ,
and use that guix to build the installation image:
$ guix pull --profile=./guix-cuf --branch=core-updates-frozen
[wait for the pull to finish]
[alternatively, you could use 'guix time-machine']
$ ./guix-cuf/bin/guix system disk-image --target=aarch64-linux-gnu -e
'(@ (gnu system install) rock64-installation-os)'
That way, the core-updates-frozen guix will only be used for building
the installation image, and nothing else.
I don't see how that could crash your main machine, though I don't know
if it will work on your rock64.
Greetings,
Maxime
next prev parent reply other threads:[~2021-12-08 19:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-04 0:03 bug#52267: disk image installer for rock64 fails Florian Hoertlehner
2021-12-04 2:41 ` pelzflorian (Florian Pelz)
2021-12-04 11:39 ` pelzflorian (Florian Pelz)
2021-12-04 21:02 ` pelzflorian (Florian Pelz)
[not found] ` <handler.52267.B.16385762085695.ack@debbugs.gnu.org>
2021-12-04 17:02 ` bug#52267: Acknowledgement (disk image installer for rock64 fails) Florian Hoertlehner
2021-12-08 13:56 ` Florian Hoertlehner
2021-12-08 17:27 ` Maxime Devos
2021-12-08 18:26 ` Florian Hoertlehner
2021-12-08 19:20 ` Maxime Devos [this message]
2021-12-08 19:42 ` Florian Hoertlehner
[not found] ` <CADXXfWmam+VE=vnbqyJyhBQPGGK+E1QMsrzvtMdatou7t7vn4w@mail.gmail.com>
[not found] ` <5f34f1895a26d5e4fbd51b409b18b64f79290861.camel@telenet.be>
2021-12-09 7:45 ` Maxime Devos
2021-12-09 7:49 ` Maxime Devos
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3e0d6f2d8879ca8f83ad3d9cc7e8c88c3e8639fc.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=52267@debbugs.gnu.org \
--cc=hoertlehner@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).