From: Mark H Weaver <mhw@netris.org>
To: Jack Hill <jackhill@jackhill.us>
Cc: 47115@debbugs.gnu.org
Subject: bug#47115: Failure building grub-img.png when reconfiguring
Date: Sun, 14 Mar 2021 20:11:48 -0400 [thread overview]
Message-ID: <87y2epqnq8.fsf@netris.org> (raw)
In-Reply-To: <alpine.DEB.2.21.2103141914430.8138@marsh.hcoop.net>
Hi Jack,
Jack Hill <jackhill@jackhill.us> writes:
> On Sun, 14 Mar 2021, Mark H Weaver wrote:
>
>> (1) You must *delete* the "older" system generations and user profiles
>> e.g. by running "guix system delete-generations" and "guix package
>> --delete-generations", or else "guix gc" won't clear them from your
>> store. It is not enough to merely switch to an older system
>> generation and profiles.
>>
>> (2) You'll also need to actually reboot into the older system
>> generation, because /run/booted-system will continue to protect
>> (from GC) the system that you last booted into, even after you
>> switch systems.
>>
>> Did you do those things before running "guix gc"?
>
> Oops, I left out those details. Yes, I did both those things.
It occurs to me that we missed something: the profiles in
~/.config/guix/current that are managed by "guix pull". It might be
that code within Guix itself was miscompiled (e.g. gnu/build/svg.scm),
or else that a profile in ~/.config/guix/current is still holding a
reference to something else that was miscompiled, (e.g. guile-cairo).
I suggest "guix pull --commit=453e101fc3f7dac9aabcd6122cf05fb7925103c7",
and then "guix package -p ~/.config/guix/current --delete-generations"
to delete any generations of Guix at commits that came after the Cairo
graft (use "guix pull --list-generations" to list them). Do this for
all user accounts (including root) that have a ~/.config/guix/current
directory. Then, try "guix gc" again.
Thanks,
Mark
next prev parent reply other threads:[~2021-03-15 0:14 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-12 22:58 bug#47115: Failure building grub-img.png when reconfiguring Jack Hill
2021-03-12 23:05 ` Leo Famulari
2021-03-13 0:24 ` Mark H Weaver
2021-03-13 0:33 ` Jack Hill
2021-03-13 4:05 ` Jack Hill
2021-03-13 7:41 ` Mark H Weaver
2021-03-13 20:08 ` Jack Hill
2021-03-14 4:27 ` Jack Hill
2021-03-14 20:49 ` Jack Hill
2021-03-14 21:14 ` Jack Hill
2021-03-14 22:00 ` Jack Hill
2021-03-14 22:05 ` Mark H Weaver
2021-03-14 23:18 ` Jack Hill
2021-03-15 0:11 ` Mark H Weaver [this message]
2021-03-15 3:38 ` Jack Hill
2021-03-15 3:52 ` Jack Hill
2021-03-15 20:48 ` Jack Hill
2021-03-16 1:41 ` Jack Hill
2021-03-16 2:40 ` Jack Hill
2021-03-16 8:26 ` bug#47115: Grafts without deduplication can lead to breakage in Guile (was: Failure building grub-img.png when reconfiguring) Mark H Weaver
2021-03-16 9:18 ` bug#47115: Redundant library grafts leads to breakage " Mark H Weaver
2021-03-20 11:01 ` bug#47115: Redundant library grafts leads to breakage Ludovic Courtès
2021-03-14 22:18 ` bug#47115: Failure building grub-img.png when reconfiguring Leo Famulari
2021-03-13 0:25 ` Jack Hill
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=87y2epqnq8.fsf@netris.org \
--to=mhw@netris.org \
--cc=47115@debbugs.gnu.org \
--cc=jackhill@jackhill.us \
/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).