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

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

[debbugs-tracker] bug#34927: closed (Curl is not configured to use its d


From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#34927: closed (Curl is not configured to use its dependency libssh2)
Date: Thu, 21 Mar 2019 21:03:01 +0000

Your message dated Thu, 21 Mar 2019 22:02:01 +0100
with message-id <address@hidden>
and subject line Re: bug#34927: Curl is not configured to use its dependency 
libssh2
has caused the debbugs.gnu.org bug report #34927,
regarding Curl is not configured to use its dependency libssh2
to be marked as done.

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


-- 
34927: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=34927
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: Curl is not configured to use its dependency libssh2 Date: Wed, 20 Mar 2019 16:40:52 -0400 User-agent: Mutt/1.11.4 (2019-03-13)
While working on a libssh2 update [0] I noticed that curl was not
keeping a reference to libssh2, even though libssh2 is an input of the
curl build.

Our curl package is missing the required configuration option:

------
SSH support:      no      (--with-libssh2)
------

I assume that our curl package did build with SSH support in the past,
but I'm not sure.

It's unfortunate that we have to use a graft to update libssh2 even
though only a few dozen packages refer to it, because of this curl
issue.

What should we do about curl? Should we remove libssh2 from its inputs,
or enable the build-time --with-libssh2 configuration option?

[0] 
https://bugs.gnu.org/34926

Attachment: signature.asc
Description: PGP signature


--- End Message ---
--- Begin Message --- Subject: Re: bug#34927: Curl is not configured to use its dependency libssh2 Date: Thu, 21 Mar 2019 22:02:01 +0100 User-agent: Notmuch/0.28.2 (https://notmuchmail.org) Emacs/26.1 (x86_64-pc-linux-gnu)
Leo Famulari <address@hidden> writes:

> On Thu, Mar 21, 2019 at 08:06:24PM +0100, Marius Bakke wrote:
>> This commit changed the cURL derivation, so I pushed a followup in
>> c1f4e6491cecc5d121ef371a8fb2aa0a07030d36.
>
> Oops... I did check that the libssh2 derivation had not changed, but I
> didn't expect the order of the inputs in the curl package definition to
> affect the derivation. Thanks for you quick fix!
>
>> I think using the "hidden?" property will leave the derivation
>> unchanged (as opposed to (hidden-package ...)).
>
> (hidden-package) does work to preserve the derivation — the issue was
> the inputs ordering in the curl package definition. I pushed another
> followup to use it.

Oops, indeed it does..  I must have mixed it up with something else,
thanks for correcting my flawed assumption :-)

Attachment: signature.asc
Description: PGP signature


--- End Message ---

reply via email to

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