From: Leo Famulari <leo@famulari.name>
To: Jack Hill <jackhill@jackhill.us>
Cc: 47115@debbugs.gnu.org
Subject: bug#47115: Failure building grub-img.png when reconfiguring
Date: Fri, 12 Mar 2021 18:05:02 -0500 [thread overview]
Message-ID: <YEvznooRt4wUjDtA@jasmine.lan> (raw)
In-Reply-To: <alpine.DEB.2.21.2103121747190.8138@marsh.hcoop.net>
On Fri, Mar 12, 2021 at 05:58:27PM -0500, Jack Hill wrote:
> This is with Guix bb5d84a0489a629d30bc2e978807caf20f46e329. My last
> successful reconfigure was with 80739ea480a7db667b83b45e3a08be740449f689.
> The output of the reconfigure run is attached. Reconfiguring without grafts
> succeeds.
I wonder if it's related to the changes in the recent Cairo graft, from
commit bc16eacc99e801ac30cbe2aa649a2be3ca5c102a?
next prev parent reply other threads:[~2021-03-12 23:09 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 [this message]
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
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=YEvznooRt4wUjDtA@jasmine.lan \
--to=leo@famulari.name \
--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).