X-Recipient: archive-cygwin AT delorie DOT com
X-Original-To: cygwin AT cygwin DOT com
Delivered-To: cygwin AT cygwin DOT com
DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org A87BF3857C73
Authentication-Results: sourceware.org; dmarc=none (p=none dis=none)
 header.from=SystematicSw.ab.ca
Authentication-Results: sourceware.org;
 spf=none smtp.mailfrom=systematicsw.ab.ca
X-Authority-Analysis: v=2.4 cv=Ac10o1bG c=1 sm=1 tr=0 ts=6109f0f9
 a=T+ovY1NZ+FAi/xYICV7Bgg==:117 a=T+ovY1NZ+FAi/xYICV7Bgg==:17
 a=IkcTkHD0fZMA:10 a=94nOnFI1EgyDtX4ev68A:9 a=QEXdDO2ut3YA:10
Subject: Re: libidn update broke curl
To: cygwin AT cygwin DOT com
References: <05788187e0be4bc4b925c79b66b3cc91 AT severstal DOT com>
 <3d8b7a73-f934-e82e-06e3-c8030919c933 AT SystematicSw DOT ab DOT ca>
 <87r1fav0hj DOT fsf AT Rainer DOT invalid>
From: Brian Inglis <Brian DOT Inglis AT SystematicSw DOT ab DOT 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
X-CMAE-Envelope: MS4xfFA9lloU7Ml6XdXEujNEDQ05pYLiNIq6EiCyE9uZwgvtaTGdsf4NsAuAtcuvHFrctZzdXtnpORQUNodfbg0Swla/NRJtHeFmszmKb+b5h3+VAWpUfxGZ
 pYkS4stOQ3x3y0/J97o9T1Fh7B0XvoZxc2UYyFfmD97ziPr0QVK4GLfooE5YK4Mv9qWX62lKhdsn4siumFR/3l5e20uRm5sl+58=
X-Spam-Status: No, score=-1161.0 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS,
 KAM_LAZY_DOMAIN_SECURITY, NICE_REPLY_A, RCVD_IN_BARRACUDACENTRAL,
 RCVD_IN_MSPIKE_H4, RCVD_IN_MSPIKE_WL, SPF_HELO_NONE, SPF_NONE,
 TXREP autolearn=no autolearn_force=no version=3.4.4
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on
 server2.sourceware.org
X-BeenThere: cygwin AT cygwin DOT com
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Unsubscribe: <https://cygwin.com/mailman/options/cygwin>,
 <mailto:cygwin-request AT cygwin DOT com?subject=unsubscribe>
List-Archive: <https://cygwin.com/pipermail/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe: <https://cygwin.com/mailman/listinfo/cygwin>,
 <mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
Reply-To: cygwin AT cygwin DOT com
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Errors-To: cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com
Sender: "Cygwin" <cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT 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