public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Cc: "Миронов Леонид Владимирович" <lv.mironov@severstal.com>
Subject: Re: libidn update broke curl
Date: Tue, 3 Aug 2021 10:05:29 -0600	[thread overview]
Message-ID: <3d8b7a73-f934-e82e-06e3-c8030919c933@SystematicSw.ab.ca> (raw)
In-Reply-To: <05788187e0be4bc4b925c79b66b3cc91@severstal.com>

On 2021-08-03 05:54, Миронов Леонид Владимирович via Cygwin wrote:
> In the yesterday's libidn11 to libidn12 update cygidn-11.dll was replaced with cygidn-12.dll.
> Unfortunately cygidn-11.dll is still referenced by cyggsasl-7.dll which breaks curl (via cygcurl-4.dll)

Sorry Leonid Vladimirovic if that affected your installation or work.

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?
Maintainers: is that something that we should not do on a package ABI 
break?
How should maintainers handle such situations in cygport?

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.

Packages impacted would include:

$ cygcheck-dep -qcOSn libidn11 libgmime3.0_0 libgs9 libgsasl7 
libloudmouth1_0 libpodofo0.9.{5,6} libpurple0 libinfinity0.6_0 libgvc6 
libMagickCore6_2 libMagickCore6_5 libMagickCore6_6 libMagickCore7_7 
libspectre1 libinfgtk3_0.6_0 libcurl4
  libidn11: is needed for ( libgmime3.0_0 libgs9 libgsasl7 
libloudmouth1_0 libpodofo0.9.3 libpodofo0.9.4 libpodofo0.9.5 
libpodofo0.9.6 libpurple0 monotone msmtp mutt whois )
  libgmime3.0_0: is needed for ( gambas3-gb-mime girepository-GMime3.0 
grilo0.3-plugins libgmime3.0-devel libtotem-plparser18 
libxplayer-plparser18 )
  libgs9: is needed for ( ghostscript gimp libgs-devel libgvc6 
libMagickCore6_2 libMagickCore6_5 libMagickCore6_6 libMagickCore7_7 
libspectre1 texlive xfig )
  libgsasl7: is needed for ( gsasl libcurl4 libgsasl-devel 
libinfinity0.6_0 )
  libloudmouth1_0: is needed for ( abiword-plugins libloudmouth1-devel )
  libpodofo0.9.5: is needed for ( krename scribus )
  libpodofo0.9.6: is needed for ( libpodofo-devel podofo )
  libpurple0: is needed for ( finch libpurple-devel pidgin 
pidgin-bonjour pidgin-facebook pidgin-funyahoo-plusplus pidgin-gadugadu 
pidgin-indicator pidgin-sametime pidgin-skypeweb pidgin-tcl telepathy-haze )
  libinfinity0.6_0: is needed for ( gobby0.5 infinoted0.6 
libinfgtk3_0.6_0 libinfinity0.6-devel )
  libgvc6: is needed for ( gda-browser5.0 graphviz guile-gv gvedit 
libgvc-devel libMagickCore7_7 libvala0.38_0 lua-gv ocaml-gv perl-gv 
php-gv python2-gv python27-gv python3-gv python36-gv python37-gv ruby-gv 
tcl-tcldot )
  libMagickCore6_2: is needed for ( libMagickC++6_6 libMagickWand6_2 )
  libMagickCore6_5: is needed for ( libMagickWand6_5 psiconv )
  libMagickCore6_6: is needed for ( libautotrace3 libMagickC++6_8 
libMagickWand6_6 )
  libMagickCore7_7: is needed for ( ImageMagick libMagick-devel 
libMagickC++7_4 libMagickWand7_7 perl-Image-Magick )
  libspectre1: is needed for ( atril cantor libevdocument3_4 
libgoffice0.10_10 libspectre-devel okular4-part okular5-part qpdfview 
zathura-ps )
  libinfgtk3_0.6_0: is needed for ( gobby0.5 libinfgtk3_0.6-devel )
  libcurl4: is needed for ( asymptote audacious-plugins cdo clamav cmake 
cmake-gui curl feh gambas3-gb-net-curl geoipupdate gimp-gmic git gmic 
gnupg google-breakpad-tools gstreamer1.0-plugins-bad-free-extras klavaro 
libcfitsio7 libcfitsio9 libcgmic2 libcurl-devel libgdal20 libgdal26 
libgdal28 libgdal29 libgit2_23 libgit2_24 libgit2_25 libgmic1 libgmic2 
libmediainfo0 libnetcdf11 libnetcdf13 libnetcdf15 libnetcdf19 liboauth0 
libofx-tools libpoppler106 libpoppler62 libpoppler66 libpoppler68 
libpoppler73 libpoppler99 libproj22 libquvi0.9_4 libraptor2_0 
libtesseract-ocr_4 libvirt0 libwsman_client4 mariadb-common mpd ncmpcpp 
nmh octave osslsigncode perl-WWW-Curl php-curl qmmp quvi R rtorrent 
transmission transmission-gtk transmission-qt transmission-remote-gtk 
tumbler vorbis-tools weechat )

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

  reply	other threads:[~2021-08-03 16:05 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 [this message]
2021-08-03 18:36   ` Achim Gratz
2021-08-04  1:44     ` Brian Inglis
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=3d8b7a73-f934-e82e-06e3-c8030919c933@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --cc=cygwin@cygwin.com \
    --cc=lv.mironov@severstal.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).