From: zimoun <zimon.toutoune@gmail.com>
To: Marco van Hulten <marco@hulten.org>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: protect generations
Date: Tue, 7 Jan 2020 13:11:55 +0100 [thread overview]
Message-ID: <CAJ3okZ30WJUQxtD7qZDoCKuMKo7-nrA+q0zxQ03bCY48g7LxvQ@mail.gmail.com> (raw)
In-Reply-To: <20200105224236.2e4fb9c2@jasniac.instanton>
Hi,
On Sun, 5 Jan 2020 at 22:42, Marco van Hulten <marco@hulten.org> wrote:
> One of the great features of Guix is that one can roll back his
> profile. But I did a garbage collection (gc) that was too aggressive
> such that a relevant old profile disappeared. I presume this is gone
> forever.
From my understanding, yes gone but not necessary forever.
How did you instantiate the profile? Using a manifest file? Did the
profile use only one Guix commit or several?
How aggressive it was? What did you run?
> Is it possible to lock certain generations (of certain users) such that
> 'guix gc' would not touch it?
Interesting whislist.
Currently, the easiest way to protect the state of a profile is to
write down a manifest file, IMHO.
If this manifest file track the Guix commit and the targeted packages,
then you can re-instantiate this very profile whereever and whenever
you want to.
Hope that helps.
All the best,
simon
next prev parent reply other threads:[~2020-01-07 12:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-05 21:42 protect generations Marco van Hulten
2020-01-07 12:11 ` zimoun [this message]
2020-01-12 14:57 ` Marco van Hulten
2020-01-14 16:38 ` zimoun
2020-01-15 8:38 ` Efraim Flashner
2020-01-15 10:54 ` zimoun
2020-01-11 23:50 ` Marius Bakke
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=CAJ3okZ30WJUQxtD7qZDoCKuMKo7-nrA+q0zxQ03bCY48g7LxvQ@mail.gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=help-guix@gnu.org \
--cc=marco@hulten.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).