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 8C738385043E
Authentication-Results:	sourceware.org;
	dmarc=none (p=none dis=none) header.from=nexgo.de
Authentication-Results:	sourceware.org; spf=pass smtp.mailfrom=nexgo.de
DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=nexgo.de;
	s=vfde-smtpout-mb-15sep; t=1628015822;
	bh=kN56jAvbcpjOpxcf0gTIQE0xX2t0DSmT0jHVkZKg5/c=;
	h=From:To:Subject:References:Date:In-Reply-To;
	b=keKlbchWktk6R9ORoNQJpXchfY6F11f8w4WqnQ88M/RxuOocd28RR8F1POgk4Yb+A
	sOMqTYxjMYHUpJrKpvU/t2kLAxGLm3iBCYF+GbykTVLV6sOBrWvOd7ehk5BlDLll6a
	SI3obH630a7FgD4KnbhB0fyFUfpJbXEuiddy9RvU=
From:	Achim Gratz <Stromeko AT nexgo DOT de>
To:	cygwin AT cygwin DOT com
Subject:	Re: libidn update broke curl
References:	<05788187e0be4bc4b925c79b66b3cc91 AT severstal DOT com>
	<3d8b7a73-f934-e82e-06e3-c8030919c933 AT SystematicSw DOT ab DOT ca>
Date:	Tue, 03 Aug 2021 20:36:56 +0200
In-Reply-To:	<3d8b7a73-f934-e82e-06e3-c8030919c933@SystematicSw.ab.ca> (Brian
	Inglis's message of "Tue, 3 Aug 2021 10:05:29 -0600")
Message-ID:	<87r1fav0hj.fsf@Rainer.invalid>
User-Agent:	Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux)
MIME-Version:	1.0
X-purgate-type:	clean
X-purgate-Ad:	Categorized by eleven eXpurgate (R) http://www.eleven.de
X-purgate:	This mail is considered clean (visit http://www.eleven.de for
	further information)
X-purgate:	clean
X-purgate-size:	1530
X-purgate-ID:	155817::1628015821-00007455-B9B29C00/0/0
X-Spam-Status:	No, score=-3032.6 required=5.0 tests=BAYES_00, DKIM_SIGNED,
	DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, RCVD_IN_DNSWL_LOW, RCVD_IN_MSPIKE_H2,
	SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham 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>
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>

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?

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


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptations for KORG EX-800 and Poly-800MkII V0.9:
http://Synth.Stromeko.net/Downloads.html#KorgSDada

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