DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org A87BF3857C73
Subject: Re: libidn update broke curl
To: cygwin@cygwin.com
References: <05788187e0be4bc4b925c79b66b3cc91@severstal.com>
 <3d8b7a73-f934-e82e-06e3-c8030919c933@SystematicSw.ab.ca>
 <87r1fav0hj.fsf@Rainer.invalid>
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
Organization: Systematic Software
Message-ID: <ad6d9c98-a200-15ac-164a-f26bcc552204@SystematicSw.ab.ca>
Date: Tue, 3 Aug 2021 19:44:24 -0600
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101
 Thunderbird/78.12.0
MIME-Version: 1.0
In-Reply-To: <87r1fav0hj.fsf@Rainer.invalid>
Content-Language: en-CA
Precedence: list
Reply-To: cygwin@cygwin.com
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Errors-To: cygwin-bounces+archive-cygwin=delorie.com@cygwin.com
Sender: "Cygwin" <cygwin-bounces+archive-cygwin=delorie.com@cygwin.com>

On 2021-08-03 12:36, Achim Gratz wrote:
> Brian Inglis writes:
>> But I didn't believe Cygwin Setup would replace packages that are
>> still dependencies of installed packages, unless you explicitly ask it
>> to remove obsolete packages, rather than unneeded dependencies.
>>
>> Unless it was due to my marking libidn12 as obsoleting libidn11?
> 
> You never do that in this situation, since it tells setup to install
> libidn12 while removing libidn11, which it dutifully did.  Why'd you
> even get the idea that you should obsolete libidn11?

I assumed that existing package dependencies would override the 
obsoletion of libidn11, rather than the obsoletion overriding.

>> Maintainers: is that something that we should not do on a package ABI
>> break?
> 
> No, not at all.  You never obsolete library packages unless they really
> need to be removed and replaced by something else.
> 
>> How should maintainers handle such situations in cygport?
> 
> Nothing to do there, move along.  the older library version continues to
> exist and is used until all packages that depend on it have updated.
> 
>> I would like to know the correct approach to take to mitigate this and
>> future such situations before I create a curl -2 package release.
> 
> What you should check is that there is no transitive dependency to
> libidn11 left in the dependency chain for anything that depends on a
> package that uses the newer version.  If that is possible you ideally
> need to update all involved packages together.

Thanks, now I know not to do that.

Is Jon's change all that is required, or do I need to build and upload a 
libidn11 to replace the obsoleted version, as well as a current libidn12 
release with the obsolete removed?

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]

-- 
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple