From: Josselin Poiret via Guix-patches via <guix-patches@gnu.org>
To: Leo Famulari <leo@famulari.name>
Cc: 52486@debbugs.gnu.org, Josselin Poiret <dev@jpoiret.xyz>
Subject: [bug#52486] [PATCH v2 0/2] Fix deluge propagating a librsvg incompatible with that of gtk+
Date: Tue, 14 Dec 2021 20:17:11 +0100 [thread overview]
Message-ID: <20211214191713.18665-1-dev@jpoiret.xyz> (raw)
In-Reply-To: <YbjaxAxmJ9V2A1Vr@jasmine.lan>
Hello again,
This time, a modified patch that selects the proper librsvg as is done
in the gtk definition, but adapted for native-inputs, as well as
another that removes the reference to the librsvg needed at build
time.
`guix size /gnu/store/azyp0avyr91jzwwdb3q82al44r3a8g1h-deluge-2.0.3`
reports only one librsvg, that of GTK.
I've tested this by adding a torrent, checking that it does in fact
download. The UI looks ok, so I guess it should work.
Best,
Josselin
Josselin Poiret (2):
gnu: deluge: Move librsvg to native inputs
gnu: deluge: Remove reference of build-time librsvg
gnu/packages/bittorrent.scm | 20 ++++++++++++++++----
1 file changed, 16 insertions(+), 4 deletions(-)
--
2.34.0
next prev parent reply other threads:[~2021-12-14 19:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-14 17:21 [bug#52486] [PATCH] gnu: deluge: Move librsvg to native inputs Josselin Poiret via Guix-patches via
2021-12-14 17:56 ` Leo Famulari
2021-12-14 19:17 ` Josselin Poiret via Guix-patches via [this message]
2021-12-14 19:17 ` [bug#52486] [PATCH v2 1/2] " Josselin Poiret via Guix-patches via
2021-12-14 19:17 ` [bug#52486] [PATCH v2 2/2] gnu: deluge: Remove reference of build-time librsvg Josselin Poiret via Guix-patches via
2022-01-16 17:58 ` Leo Famulari
2022-01-16 21:41 ` [bug#52486] [PATCH] gnu: deluge: Move librsvg to native inputs Brice Waegeneire
2022-01-16 10:52 ` bug#52486: " Brice Waegeneire
2022-01-16 10:52 ` [bug#52486] " Brice Waegeneire
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=20211214191713.18665-1-dev@jpoiret.xyz \
--to=guix-patches@gnu.org \
--cc=52486@debbugs.gnu.org \
--cc=dev@jpoiret.xyz \
--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 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.