unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] system: grub: Use librsvg to convert SVG to PNG
Date: Mon, 31 Oct 2016 22:57:01 +0100	[thread overview]
Message-ID: <87oa20npw2.fsf@gnu.org> (raw)
In-Reply-To: <20161025000724.GA23897@jasmine> (Leo Famulari's message of "Mon, 24 Oct 2016 20:07:24 -0400")

Leo Famulari <leo@famulari.name> skribis:

> On Tue, Oct 25, 2016 at 01:24:15AM +0200, Ludovic Courtès wrote:
>> > Is there are reason for not using guile-rsvg and guile-cairo?  Otherwise
>> > I think it would be preferable (they’d need to be autoloaded so that
>> > ‘make’ doesn’t fail when they’re missing, but that’s OK.)
>> >
>> > I found an example that Andy had posted:
>> >
>> >   https://lists.gnu.org/archive/html/guix-devel/2015-08/msg00753.html
>> 
>> I hacked this a little bit a pushed as
>> ffde82c9ecf99524220e463055f4f18c8c9e7a81.
>
> A welcome change! But I think it needs a little more time in the
> kitchen:
>
> $ guix pull

[...]

> In unknown file:
>    ?: 0 [scm-error misc-error #f "~A ~S" ("no code for module" (rsvg)) #f]
>
> ERROR: In procedure scm-error:
> ERROR: no code for module (rsvg)

Indeed it wasn’t fully cooked.  ;-)  I see your message just now, but
others reported it on IRC and it got fixed in
8ce84bf1f5705f5280e8bf8f150ec2e859b045ee.

Ludo’.

  reply	other threads:[~2016-10-31 21:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-02  8:02 [PATCH] system: grub: Use librsvg to convert SVG to PNG Mark H Weaver
2016-09-02 12:56 ` Ludovic Courtès
2016-10-24 23:24   ` Ludovic Courtès
2016-10-25  0:07     ` Leo Famulari
2016-10-31 21:57       ` Ludovic Courtès [this message]
2016-09-02 15:24 ` Vincent Legoll
2016-09-03 12:59   ` Vincent Legoll
2016-09-05  9:31     ` Vincent Legoll
2016-09-05 20:30 ` Leo Famulari

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=87oa20npw2.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=leo@famulari.name \
    /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).