emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[debbugs-tracker] bug#26091: closed (Add pkg-config file for libidn2)


From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#26091: closed (Add pkg-config file for libidn2)
Date: Tue, 14 Mar 2017 20:39:02 +0000

Your message dated Tue, 14 Mar 2017 21:38:09 +0100
with message-id <address@hidden>
and subject line Re: bug#26091: Add pkg-config file for libidn2
has caused the debbugs.gnu.org bug report #26091,
regarding Add pkg-config file for libidn2
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
26091: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=26091
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: Add pkg-config file for libidn2 Date: Mon, 13 Mar 2017 21:33:33 +0100 User-agent: Notmuch/0.24 (https://notmuchmail.org) Emacs/25.1.1 (x86_64-unknown-linux-gnu)
On 'core-updates', software such as 'wget' and 'ffmpeg' are unable to
find 'gnutls', which is really due to libidn2 not having a pkg-config
file.

This patch adds one.

Attachment: 0001-gnu-libidn2-Create-pkg-config-file.patch
Description: Text Data

Attachment: signature.asc
Description: PGP signature


--- End Message ---
--- Begin Message --- Subject: Re: bug#26091: Add pkg-config file for libidn2 Date: Tue, 14 Mar 2017 21:38:09 +0100 User-agent: Notmuch/0.24 (https://notmuchmail.org) Emacs/25.1.1 (x86_64-unknown-linux-gnu)
Ludovic Courtès <address@hidden> writes:

> Marius Bakke <address@hidden> skribis:
>
>> Ludovic Courtès <address@hidden> writes:
>
> [...]
>
>>> If upstream libidn2 does not install libidn2.pc, then I’m rather against
>>> adding it.  It’s a decision for upstream to make.
>
> [...]
>
>> Apparently upstream added a "libidn2.pc" recently, so this would only be
>> a temporary workaround until 0.17 is released:
>>
>> https://gitlab.com/jas/libidn2/commit/84b396c528dfed9ea6e8248f0522d120c9bd6186
>
> Oh perfect, that addresses my concern.  In that case, let’s just do what
> you suggested in the first place or apply this patch.  Make sure to
> leave a comment stating that upstream will be providing the .pc file
> afterwards.

Done! I didn't know that upstream had added this file either, so thanks
for taking the time to question this patch.

Pushed to 'core-updates' as 77c5d63f4d76f2905d975316347948cc913c6d20.

Attachment: signature.asc
Description: PGP signature


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]