From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: libidn update broke curl
Date: Tue, 3 Aug 2021 19:44:24 -0600 [thread overview]
Message-ID: <ad6d9c98-a200-15ac-164a-f26bcc552204@SystematicSw.ab.ca> (raw)
In-Reply-To: <87r1fav0hj.fsf@Rainer.invalid>
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.]
next prev parent reply other threads:[~2021-08-04 1:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-03 11:54 Миронов Леонид Владимирович
2021-08-03 16:05 ` Brian Inglis
2021-08-03 18:36 ` Achim Gratz
2021-08-04 1:44 ` Brian Inglis [this message]
2021-08-04 5:11 ` ASSI
2021-08-04 15:44 ` Brian Inglis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ad6d9c98-a200-15ac-164a-f26bcc552204@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).