all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Jack Hill <jackhill@jackhill.us>
To: "Dr. Arne Babenhauserheide" <arne_bab@web.de>
Cc: 47115@debbugs.gnu.org, 47853@debbugs.gnu.org
Subject: bug#47115: bug#47853: guix system reconfigure build of `/gnu/store/inppfcz5yk5a20cwhv1dwqn8zq6jcdxl-grub.cfg.drv' failed
Date: Sat, 17 Apr 2021 19:39:55 -0400 (EDT)	[thread overview]
Message-ID: <alpine.DEB.2.21.2104171934190.8414@marsh.hcoop.net> (raw)
In-Reply-To: <87v98k341u.fsf@web.de>

[-- Attachment #1: Type: text/plain, Size: 1069 bytes --]

On Sun, 18 Apr 2021, Dr. Arne Babenhauserheide wrote:

> On my system building grub fails because grub-image.png fails.

[…]

> Backtrace:
>           2 (primitive-load "/gnu/store/larqpc2wjhnc6jmj4885k8lynd1?")
> In gnu/build/svg.scm:
>     53:6  1 (svg->png _ "/gnu/store/0f2bpqpgflza414sk0hwms3rdizg1x?" ?)
> In unknown file:
>           0 (rsvg-handle-render-cairo #<rsvg-handle 7ffff0b56280> #)
>
> ERROR: In procedure rsvg-handle-render-cairo:
> Wrong type (expecting finalized smob): #<cairo-context 7ffff0b561c0>

Oh dear. I ran into a similar problem (at least that resulted in the same 
Guile error message in #47115) to do with grafts and a store that was not 
using the hard links for de-duplication. Essentially the de-duplication 
masked an issue with differing files being included in the closure.

Can you provide more information about your system? I'm particularly 
interested in whether you're using store de-duplication, but other 
specifics about your system might be interesting. Do you know when you 
last successfully reconfigured?

Best,
Jack

      reply	other threads:[~2021-04-17 23:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-17 23:05 bug#47853: guix system reconfigure build of `/gnu/store/inppfcz5yk5a20cwhv1dwqn8zq6jcdxl-grub.cfg.drv' failed Dr. Arne Babenhauserheide
2021-04-17 23:39 ` Jack Hill [this message]

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=alpine.DEB.2.21.2104171934190.8414@marsh.hcoop.net \
    --to=jackhill@jackhill.us \
    --cc=47115@debbugs.gnu.org \
    --cc=47853@debbugs.gnu.org \
    --cc=arne_bab@web.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.