unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Brice Waegeneire <brice@waegenei.re>
To: Josselin Poiret <dev@jpoiret.xyz>
Cc: 52486-done@debbugs.gnu.org, Leo Famulari <leo@famulari.name>
Subject: [bug#52486] [PATCH] gnu: deluge: Move librsvg to native inputs.
Date: Sun, 16 Jan 2022 11:52:54 +0100	[thread overview]
Message-ID: <87ilukt0jd.fsf_-_@waegenei.re> (raw)
In-Reply-To: <20211214191713.18665-1-dev@jpoiret.xyz> (Josselin Poiret's message of "Tue, 14 Dec 2021 20:17:11 +0100")

Hello Josselin

Josselin Poiret <dev@jpoiret.xyz> writes:

> Josselin Poiret (2):
>   gnu: deluge: Move librsvg to native inputs
>   gnu: deluge: Remove reference of build-time librsvg

Thanks for the patch, it fixes the issue with librsvg as expected. Pushed as
1471219a8aabd2d8ad1f6bf1216c734ce73ae175, I've added your copyright to it.

Cheers,
- Brice




      parent reply	other threads:[~2022-01-16 10:54 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   ` [bug#52486] [PATCH v2 0/2] Fix deluge propagating a librsvg incompatible with that of gtk+ Josselin Poiret via Guix-patches via
2021-12-14 19:17     ` [bug#52486] [PATCH v2 1/2] gnu: deluge: Move librsvg to native inputs 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     ` Brice Waegeneire [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

  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=87ilukt0jd.fsf_-_@waegenei.re \
    --to=brice@waegenei.re \
    --cc=52486-done@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 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).