* Fwd: Errors in cURL dependency chain
[not found] <5de321b2.1c69fb81.3f589.a809@mx.google.com>
@ 2019-12-01 2:15 ` Steven Penny
2019-12-01 14:15 ` Jon Turney
2020-01-09 16:56 ` David Rothenberger
0 siblings, 2 replies; 3+ messages in thread
From: Steven Penny @ 2019-12-01 2:15 UTC (permalink / raw)
To: cygwin; +Cc: daveroth, yselkowitz
Here is a dependency chain:
1. curl
2. libcurl4
3. libopenldap2_4_2
4. libsasl2_3
5. libopenssl100
I have two issues with this. First, "libopenssl100" is obsolete:
@ libopenssl100
sdesc: "Obsoleted by libssl1.0"
David, can this be resolved? Second, while looking at "libopenssl100" I noticed
another issue:
@ libopenssl100
requires: libssl1.0
depends2:
My understanding is that "depends2" is the proper dependency endpoint, and that
"requires" is only kept for legacy parsers. Yaakov, can you advise?
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Fwd: Errors in cURL dependency chain
2019-12-01 2:15 ` Fwd: Errors in cURL dependency chain Steven Penny
@ 2019-12-01 14:15 ` Jon Turney
2020-01-09 16:56 ` David Rothenberger
1 sibling, 0 replies; 3+ messages in thread
From: Jon Turney @ 2019-12-01 14:15 UTC (permalink / raw)
To: Steven Penny, The Cygwin Mailing List
On 01/12/2019 02:15, Steven Penny wrote:
> Here is a dependency chain:
>
> 1. curl
> 2. libcurl4
> 3. libopenldap2_4_2
> 4. libsasl2_3
> 5. libopenssl100
>
> I have two issues with this. First, "libopenssl100" is obsolete:
>
> @ libopenssl100
> sdesc: "Obsoleted by libssl1.0"
>
> David, can this be resolved? Second, while looking at "libopenssl100" I noticed
> another issue:
>
> @ libopenssl100
> requires: libssl1.0
> depends2:
>
> My understanding is that "depends2" is the proper dependency endpoint, and that
> "requires" is only kept for legacy parsers. Yaakov, can you advise?
This understanding is correct, but incomplete.
If you look at libssl1.0, you will see it has:
> @ libssl1.0
> obsoletes: libopenssl100
We don't depends2: on something which obsoletes:, as that can lead to a
solver conflict (See [1]).
[1]
https://cygwin.com/git/gitweb.cgi?p=cygwin-apps/calm.git;a=commitdiff;h=d75abceedb46749982669236c5c102796a1fbfb1;hp=f92ad1d5c292ed54e7a62f5c52280efab8267f37
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Fwd: Errors in cURL dependency chain
2019-12-01 2:15 ` Fwd: Errors in cURL dependency chain Steven Penny
2019-12-01 14:15 ` Jon Turney
@ 2020-01-09 16:56 ` David Rothenberger
1 sibling, 0 replies; 3+ messages in thread
From: David Rothenberger @ 2020-01-09 16:56 UTC (permalink / raw)
To: cygwin
On 11/30/2019 6:15 PM, Steven Penny wrote:
> Here is a dependency chain:
>
> 1. curl
> 2. libcurl4
> 3. libopenldap2_4_2
> 4. libsasl2_3
> 5. libopenssl100
>
> I have two issues with this. First, "libopenssl100" is obsolete:
>
> @ libopenssl100
> sdesc: "Obsoleted by libssl1.0"
>
> David, can this be resolved?
I have rebuilt libsasl2_3 against openssl 1.1
--
David Rothenberger ---- daveroth@acm.org
Hain't we got all the fools in town on our side? And hain't that a big
enough majority in any town?
-- Mark Twain, "Huckleberry Finn"
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2020-01-09 16:56 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <5de321b2.1c69fb81.3f589.a809@mx.google.com>
2019-12-01 2:15 ` Fwd: Errors in cURL dependency chain Steven Penny
2019-12-01 14:15 ` Jon Turney
2020-01-09 16:56 ` David Rothenberger
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).