From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: 63427@debbugs.gnu.org
Cc: ncdehnel@gmail.com, dev@jpoiret.xyz
Subject: bug#63427: gdk-pixbuf unable to recognize image formats (JPG, PNG, etc.)
Date: Thu, 11 May 2023 13:04:31 +0200 [thread overview]
Message-ID: <87pm77uo1s.fsf@pelzflorian.de> (raw)
In-Reply-To: <874joje1ii.fsf@jpoiret.xyz> (Josselin Poiret via Bug reports for's message of "Thu, 11 May 2023 10:05:41 +0200")
Hi all.
Josselin Poiret via Bug reports for GNU Guix <bug-guix@gnu.org> writes:
> For
> that, we use the environment variable GDK_PIXBUF_MODULE_FILE, which is a
> search-path for the package gdk-pixbuf, meaning that it is set only if
> gdk-pixbuf is installed in your profile. […] So
> we should fix this and propagate gdk-pixbuf everywhere (something which
> I'm not too much a fan of, but alas).
The cambalache package does the right thing by wrapping the program to
setenv GDK_PIXBUF_MODULE_FILE to the value it has while building the
package. glib-or-gtk build system sets GDK_PIXBUF_MODULE_FILE while
building the package. Note that gdkpixbuf and perhaps
librsvg-for-system must be in inputs.
Regards,
Florian
next prev parent reply other threads:[~2023-05-11 11:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-10 18:50 bug#63427: gdk-pixbuf unable to recognize image formats (JPG, PNG, etc.) Nathan Dehnel
2023-05-10 22:24 ` bug#63427: Sharlatan Hellseher
2023-05-11 8:05 ` bug#63427: gdk-pixbuf unable to recognize image formats (JPG, PNG, etc.) Josselin Poiret via Bug reports for GNU Guix
2023-05-11 11:04 ` pelzflorian (Florian Pelz) [this message]
2023-05-11 19:11 ` Liliana Marie Prikler
2023-05-11 21:22 ` Nathan Dehnel
2023-05-12 9:19 ` pelzflorian (Florian Pelz)
2023-05-12 21:21 ` Nathan Dehnel
2023-05-13 10:49 ` pelzflorian (Florian Pelz)
2023-05-13 13:50 ` Liliana Marie Prikler
2023-05-13 18:38 ` pelzflorian (Florian Pelz)
2023-05-15 5:18 ` Nathan Dehnel
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=87pm77uo1s.fsf@pelzflorian.de \
--to=pelzflorian@pelzflorian.de \
--cc=63427@debbugs.gnu.org \
--cc=dev@jpoiret.xyz \
--cc=ncdehnel@gmail.com \
/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).