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 666723861031
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=610ab4eb
	a=T+ovY1NZ+FAi/xYICV7Bgg==:117 a=T+ovY1NZ+FAi/xYICV7Bgg==:17
	a=IkcTkHD0fZMA:10 a=bofx8gS0ZHAy-ljYS4IA:9 a=QEXdDO2ut3YA:10
Subject:	Re: [ANNOUNCEMENT] Updated: libidn{, 12, -devel, -doc}
	mingw64-{x86_64, i686}-libidn 1.38
To:	The Cygwin Mailing List <cygwin AT cygwin DOT com>
References:	<announce DOT 20210802111927 DOT 50466-1-Brian DOT Inglis AT SystematicSW DOT ab DOT ca>
	<60eee993-c788-97d5-8ea0-e708564e54b1 AT dronecode DOT org DOT uk>
	<e2a20fe9-4de5-4ff8-e1da-79f415c51b03 AT SystematicSw DOT ab DOT ca>
	<9db380d9-c314-3e87-9aa1-b71d96aafd95 AT dronecode DOT org DOT uk>
From:	Brian Inglis <Brian DOT Inglis AT SystematicSw DOT ab DOT ca>
Organization:	Systematic Software
Message-ID:	<7d220598-ed1a-d717-4ca4-ef2bfb47ac1f@SystematicSw.ab.ca>
Date:	Wed, 4 Aug 2021 09:40:26 -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:	<9db380d9-c314-3e87-9aa1-b71d96aafd95@dronecode.org.uk>
X-CMAE-Envelope:	MS4xfFCkWtR3voAFS+V62ooM0KDmfOau5cmWSqDn5/J/+8DRd2MxdAQeg4HypV0WIcG0Df9BYx6z/FcixrIUjp55BatERGIeBq+CusoBD1m1Uh5yrkG+ksSv
	97609EWdWV6P63h0C+MjOb8PAbNk1zoetu81VMsqc4W4YOtsoI1EU05IcPX+ZWvBIvb2V5pm+Sx1XNyHruZu8v7929UTm6S6eck=
X-Spam-Status:	No, score=-1159.3 required=5.0 tests=BAYES_00, BODY_8BITS,
	KAM_DMARC_STATUS, KAM_LAZY_DOMAIN_SECURITY, KAM_NUMSUBJECT, NICE_REPLY_A,
	RCVD_IN_BARRACUDACENTRAL, RCVD_IN_MSPIKE_H2, 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
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:	The Cygwin Mailing List <cygwin AT cygwin DOT com>
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>
X-MIME-Autoconverted:	from base64 to 8bit by delorie.com id 174Fejll013504

On 2021-08-04 06:41, Jon Turney wrote:
> On 03/08/2021 17:14, Brian Inglis wrote:
>> On 2021-08-03 09:56, Jon Turney wrote:
>>> On 02/08/2021 18:19, Cygwin libidn2 Maintainer wrote:
>>>> The following packages have been upgraded in the Cygwin distribution:
>>>>
>>>> * libidn            1.38
>>>> * libidn12            1.38
>>>> * libidn-devel        1.38
>>>> * libidn-doc            1.38
>>>> * mingw64-x86_64-libidn    1.38
>>>> * mingw64-i686-libidn    1.38
>>>>
>>>> and the following package has been obsoleted from the Cygwin 
>>>> distribution:
>>>>
>>>> * libidn11            1.33
>>>
>>> I've reverted that obsoletion, by removing 'obsoletes: libidn11' from 
>>> the hint for libidn12, since it apparently still has some uses.
> 
> ... and removed the empty libidn11-1.1.38-1 package (generated by 
> cygport for compatibility with obsolete versions of setup)
> 
> ... and added a 'replace-versions: 1.38-1' hint to libidn11 (in case 
> someone installed the above before I remembered to remove them)
> 
>> Can users just rerun Cygwin Setup so that it will update setup.ini and 
>> reinstall cygidn-11.dll?
> 
> Yes, that should fix any broken installs.
> 
>> Is obsoleting previous dlls something that we should not do on a 
>> package ABI break?
> 
> Correct, do not do that.
> 
> In this context, 'package A obsoletes package B' means 'package B 
> provides everything that package A did, so if A is installed, uninstall 
> A and install B'.
> 
> This behaviour is not unique to Cygwin packaging.
> 
>> How should maintainers handle such situations in cygport?
> 
> You don't need to mention the old soversion in the updated cygport at all.
> 
> (a heuristic in calm identifies old soversions, and exempts them from 
> the (annoying) "all install packages from a source package must have a 
> unique current version" check)
> 
> (Yes, that means that those old soversions, and the corresponding 
> source, linger in the repository indefinitely.  yselkowitz would 
> occasionally manually locate old soversions which aren't required by any 
> other package (or which could be made so with some rebuilds), and purge 
> them from the repo, but ... that service is no longer running :))

Thanks Jon for the fix.
*Sorry* to all users impacted to have caused the issue.

-- 
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

- Raw text -