From: "Ludovic Courtès" <ludo@gnu.org>
To: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
Cc: Mathieu Othacehe <othacehe@gnu.org>, 59784@debbugs.gnu.org
Subject: bug#59784: [version 1.4.0rc1] Retrying a failed install fails
Date: Tue, 13 Dec 2022 10:48:43 +0100 [thread overview]
Message-ID: <87k02vy6pw.fsf@gnu.org> (raw)
In-Reply-To: <87pmcny73z.fsf@gnu.org> ("Ludovic Courtès"'s message of "Tue, 13 Dec 2022 10:40:16 +0100")
Hi again,
Ludovic Courtès <ludo@gnu.org> skribis:
> It looks like the store is in a broken state, with its database not
> matching its actual contents. The ‘install-system’ procedure is
> supposed to protect against that by making a backup of the database
> before starting the installation and restoring it afterwards. (It
> apparently worked for me when I interrupted ‘guix system init’ by
> hitting C-c.)
Actually, look at the excerpt from final.scm:
;; Restart guix-daemon so that it does no keep the MNT namespace
;; alive.
(restart-service 'guix-daemon)
(copy-file saved-database database-file)
We’re restarting the daemon *before* we have restored the database,
which is wrong: depending on how lucky you are, guix-daemon might load
the old database (all this depends on what exactly happens when sqlite
opens the database, but I think there’s a possibility that it will load
or cache a few things and thus fail to see the changes ‘copy-file’
introduces.)
So my guess is that things will be much better if we swap these two
lines.
Florian, it would be great if you could try that and run a new image
generated version ‘version-1.4.0’ with these two lines changed. To
produce the image, run:
./pre-inst-env guix system image -t iso9660 --label=Guix \
gnu/system/install.scm
Ludo’.
next prev parent reply other threads:[~2022-12-13 9:49 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-02 17:52 bug#59784: [version 1.4.0rc1] Retrying a failed install fails pelzflorian (Florian Pelz)
2022-12-09 9:42 ` Ludovic Courtès
2022-12-09 11:11 ` Ludovic Courtès
2022-12-10 8:39 ` pelzflorian (Florian Pelz)
2022-12-13 9:40 ` Ludovic Courtès
2022-12-13 9:48 ` Ludovic Courtès [this message]
2022-12-13 22:22 ` pelzflorian (Florian Pelz)
2022-12-13 23:16 ` Ludovic Courtès
2022-12-14 13:36 ` pelzflorian (Florian Pelz)
2022-12-14 21:47 ` pelzflorian (Florian Pelz)
2022-12-14 23:50 ` Ludovic Courtès
2022-12-15 17:46 ` pelzflorian (Florian Pelz)
2022-12-15 20:44 ` pelzflorian (Florian Pelz)
2022-12-16 16:57 ` Ludovic Courtès
2022-12-16 20:28 ` pelzflorian (Florian Pelz)
2022-12-17 11:01 ` Ludovic Courtès
2022-12-17 19:36 ` pelzflorian (Florian Pelz)
2022-12-17 16:15 ` Ludovic Courtès
2022-12-17 19:27 ` pelzflorian (Florian Pelz)
2022-12-17 21:30 ` Ludovic Courtès
2022-12-18 0:23 ` Ludovic Courtès
2022-12-16 13:55 ` Maxime Devos
2022-12-16 20:17 ` pelzflorian (Florian Pelz)
2022-12-18 16:41 ` pelzflorian (Florian Pelz)
2022-12-12 12:07 ` pelzflorian (Florian Pelz)
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k02vy6pw.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=59784@debbugs.gnu.org \
--cc=othacehe@gnu.org \
--cc=pelzflorian@pelzflorian.de \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.