From: Tobias Geerinckx-Rice <me@tobias.gr>
To: znavko@disroot.org
Cc: help-guix@gnu.org
Subject: Re: How to reconfigure system without downloads I did not order?
Date: Sat, 28 Nov 2020 13:14:21 +0100 [thread overview]
Message-ID: <87tut9brvm.fsf@nckx> (raw)
In-Reply-To: <b64d56975973294b1e888d08e242883a@disroot.org>
[-- Attachment #1: Type: text/plain, Size: 1223 bytes --]
Hullo znavko,
znavko--- via 写道:
> I am sorry. How to prevent the process of system upgrade and
> just remain things as they are but only adding new disk to my
> system?
Guix can't upgrade your system, it can only build a new one. It
will merely re-use parts of the old system that they have in
common (which can be and often is ‘almost everything’).
This is actually significant: you can't ask a new Guix to modify
an older Guix's system, to leave everything in place but just add
this one small thing, like you can for bare profiles. For that,
you need to reconfigure the old system with the same version of
Guix that was used to build it.
What do
$ guix system describe
and
$ guix describe
say? My guess is they will both display a different commit
because you've ‘guix pull’ed after creating the system. If so,
you can use
$ guix time-machine --commit=<system commit> -- system
reconfigure …
to apply your changes.
If the system and guix commits *do* match and you've added nothing
besides a new FILE-SYSTEM, I have no idea why Guix is
(re-)building ffmpeg. An overzealous ‘guix gc’ in the meantime?
Kind regards,
T G-R
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next prev parent reply other threads:[~2020-11-28 12:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-28 11:39 How to reconfigure system without downloads I did not order? znavko--- via
2020-11-28 12:14 ` Tobias Geerinckx-Rice [this message]
2020-11-28 12:53 ` znavko
2020-11-28 18:02 ` znavko
2020-11-28 20:48 ` jbranso
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=87tut9brvm.fsf@nckx \
--to=me@tobias.gr \
--cc=help-guix@gnu.org \
--cc=znavko@disroot.org \
/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.
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).