DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org EA42C39730EC
Subject: Re: [ANNOUNCEMENT] Updated: libidn{, 12, -devel, -doc}
 mingw64-{x86_64, i686}-libidn 1.38
To: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>,
        The Cygwin Mailing List <cygwin@cygwin.com>
References: <announce.20210802111927.50466-1-Brian.Inglis@SystematicSW.ab.ca>
 <60eee993-c788-97d5-8ea0-e708564e54b1@dronecode.org.uk>
 <e2a20fe9-4de5-4ff8-e1da-79f415c51b03@SystematicSw.ab.ca>
From: Jon Turney <jon.turney@dronecode.org.uk>
Message-ID: <9db380d9-c314-3e87-9aa1-b71d96aafd95@dronecode.org.uk>
Date: Wed, 4 Aug 2021 13:41:55 +0100
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: <e2a20fe9-4de5-4ff8-e1da-79f415c51b03@SystematicSw.ab.ca>
Content-Language: en-GB
Precedence: list
Content-Type: text/plain; charset="utf-8"; Format="flowed"
Errors-To: cygwin-bounces+archive-cygwin=delorie.com@cygwin.com
Sender: "Cygwin" <cygwin-bounces+archive-cygwin=delorie.com@cygwin.com>
Content-Transfer-Encoding: 8bit

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

> I would like to know the correct approach to take to mitigate this and 
> future such situations, before I create a libidn -2 package release.


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