Re: libxml2-2.10.3-1.fc36 breaks (part of) GraphicsMagick
On Tuesday, 01 November 2022 at 10:06, Petr Pisar wrote: > V Tue, Nov 01, 2022 at 05:31:08PM +0900, Mamoru TASAKA napsal(a): > > Michael J Gruber wrote on 2022/10/29 5:19: > > > With this libxml2 update: [...] > > This is perhaps due to the following change: > > https://gitlab.gnome.org/GNOME/libxml2/-/commit/a0a0f3be93753e387e31e7de95904a24b3c876dd > > > [...] > > > > I think libxml2 2.10.x (with current configuration) should not have brought > > into > > F37/36/35 branches. Currently at least the following action is required. +1 > > * Either rebuilding all packages requiring the above symbol > > * Or fixing libxml2 2.10.x +1, rebuild libxml2 --with-ftp in %configure call. > > * Or introduce epoch on libxml2 and downgrade to 2.9.x > > > https://bugzilla.redhat.com/show_bug.cgi?id=2136800 https://bugzilla.redhat.com/show_bug.cgi?id=2139546 rpmsodiff test containing removed symbols should trigger negative karma automatically. Regards, Dominik -- Fedora https://getfedora.org | RPM Fusion http://rpmfusion.org There should be a science of discontent. People need hard times and oppression to develop psychic muscles. -- from "Collected Sayings of Muad'Dib" by the Princess Irulan ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: libxml2-2.10.3-1.fc36 breaks (part of) GraphicsMagick
V Tue, Nov 01, 2022 at 05:31:08PM +0900, Mamoru TASAKA napsal(a):
> Michael J Gruber wrote on 2022/10/29 5:19:
> > With this libxml2 update:
> > ```
> > gm convert -list format
> > ...
> > gm convert: Unable to load module
> > ("/usr/lib64/GraphicsMagick-1.3.38/modules-Q16/coders/url.la: file not
> > found")
> > ```
> > In fact, `url.so` is there but cannot be dlopen'ed. This works after
> > downgrading libxml2 to 2.9.
> > I noticed because my scribus failed to start today, and this was somehow
> > tough to track down.
> > I still don't know whether libxml2 had an abi change without soname bump
> > and whether a simple rebuild of GM would solve this (in particular, which
> > one to file a big against). But since it was diificult to spot and more
> > packages could be broken (without a clear FTI/FTBFS) I wanted to give a
> > heads up here.
>
>
> Confirmed, as I've noticed that now rubygem-rmagick is now FTBFS.
> So I tried narrowing the issue and the minimum reproducer is:
>
> $ ldd -r /usr/lib64/ImageMagick-6.9.12/modules-Q16/coders/url.so | grep
> undefined
> undefined symbol: xmlNanoFTPInit, version LIBXML2_2.4.30
> (/usr/lib64/ImageMagick-6.9.12/modules-Q16/coders/url.so)
> undefined symbol: xmlNanoFTPClose, version LIBXML2_2.4.30
> (/usr/lib64/ImageMagick-6.9.12/modules-Q16/coders/url.so)
> undefined symbol: xmlNanoFTPGet, version LIBXML2_2.4.30
> (/usr/lib64/ImageMagick-6.9.12/modules-Q16/coders/url.so)
> undefined symbol: xmlNanoFTPNewCtxt, version LIBXML2_2.4.30
> (/usr/lib64/ImageMagick-6.9.12/modules-Q16/coders/url.so)
> undefined symbol: xmlNanoFTPConnect, version LIBXML2_2.4.30
> (/usr/lib64/ImageMagick-6.9.12/modules-Q16/coders/url.so)
>
> (i.e. ImageMagick is now broken)
>
> This is perhaps due to the following change:
> https://gitlab.gnome.org/GNOME/libxml2/-/commit/a0a0f3be93753e387e31e7de95904a24b3c876dd
>
[...]
>
> I think libxml2 2.10.x (with current configuration) should not have brought
> into
> F37/36/35 branches. Currently at least the following action is required.
>
> * Either rebuilding all packages requiring the above symbol
> * Or fixing libxml2 2.10.x
> * Or introduce epoch on libxml2 and downgrade to 2.9.x
>
https://bugzilla.redhat.com/show_bug.cgi?id=2136800
-- Petr
signature.asc
Description: PGP signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
Re: libxml2-2.10.3-1.fc36 breaks (part of) GraphicsMagick
Michael J Gruber wrote on 2022/10/29 5:19:
With this libxml2 update:
```
gm convert -list format
...
gm convert: Unable to load module
("/usr/lib64/GraphicsMagick-1.3.38/modules-Q16/coders/url.la: file not found")
```
In fact, `url.so` is there but cannot be dlopen'ed. This works after
downgrading libxml2 to 2.9.
I noticed because my scribus failed to start today, and this was somehow tough
to track down.
I still don't know whether libxml2 had an abi change without soname bump and
whether a simple rebuild of GM would solve this (in particular, which one to
file a big against). But since it was diificult to spot and more packages could
be broken (without a clear FTI/FTBFS) I wanted to give a heads up here.
Confirmed, as I've noticed that now rubygem-rmagick is now FTBFS.
So I tried narrowing the issue and the minimum reproducer is:
$ ldd -r /usr/lib64/ImageMagick-6.9.12/modules-Q16/coders/url.so | grep
undefined
undefined symbol: xmlNanoFTPInit, version LIBXML2_2.4.30
(/usr/lib64/ImageMagick-6.9.12/modules-Q16/coders/url.so)
undefined symbol: xmlNanoFTPClose, version LIBXML2_2.4.30
(/usr/lib64/ImageMagick-6.9.12/modules-Q16/coders/url.so)
undefined symbol: xmlNanoFTPGet, version LIBXML2_2.4.30
(/usr/lib64/ImageMagick-6.9.12/modules-Q16/coders/url.so)
undefined symbol: xmlNanoFTPNewCtxt, version LIBXML2_2.4.30
(/usr/lib64/ImageMagick-6.9.12/modules-Q16/coders/url.so)
undefined symbol: xmlNanoFTPConnect, version LIBXML2_2.4.30
(/usr/lib64/ImageMagick-6.9.12/modules-Q16/coders/url.so)
(i.e. ImageMagick is now broken)
This is perhaps due to the following change:
https://gitlab.gnome.org/GNOME/libxml2/-/commit/a0a0f3be93753e387e31e7de95904a24b3c876dd
... and in fact lots of other symbols are also removed...
$ rpmsodiff libxml2-2.9.14-3.fc37.x86_64.rpm libxml2-2.10.3-1.fc37.x86_64.rpm | grep
"^-"
--- libxml2-2.9.14-3.fc37/libxml2.so.2 2022-07-22 05:06:27.0 +0900
-__docbDefaultSAXHandlerT
-attribute@@LIBXML2_2.4.30 T
-attributeDecl@@LIBXML2_2.4.30 T
-cdataBlock@@LIBXML2_2.4.30 T
-characters@@LIBXML2_2.4.30 T
-checkNamespace@@LIBXML2_2.4.30 T
-comment@@LIBXML2_2.4.30T
-docbDefaultSAXHandler@@LIBXML2_2.4.30 D
-docbDefaultSAXHandlerInit@@LIBXML2_2.4.30 T
-elementDecl@@LIBXML2_2.4.30T
-endDocument@@LIBXML2_2.4.30T
-endElement@@LIBXML2_2.4.30 T
-entityDecl@@LIBXML2_2.4.30 T
-externalSubset@@LIBXML2_2.4.30 T
-getColumnNumber@@LIBXML2_2.4.30T
-getEntity@@LIBXML2_2.4.30 T
-getLineNumber@@LIBXML2_2.4.30 T
-getNamespace@@LIBXML2_2.4.30 T
-getParameterEntity@@LIBXML2_2.4.30 T
-getPublicId@@LIBXML2_2.4.30T
-getSystemId@@LIBXML2_2.4.30T
-globalNamespace@@LIBXML2_2.4.30T
-hasExternalSubset@@LIBXML2_2.4.30 T
-hasInternalSubset@@LIBXML2_2.4.30 T
-htmlDecodeEntities T
-ignorableWhitespace@@LIBXML2_2.4.30T
-initdocbDefaultSAXHandler@@LIBXML2_2.4.30 T
-inithtmlDefaultSAXHandler@@LIBXML2_2.4.30 T
-initxmlDefaultSAXHandler@@LIBXML2_2.4.30 T
-internalSubset@@LIBXML2_2.4.30 T
-isStandalone@@LIBXML2_2.4.30 T
-namespaceDecl@@LIBXML2_2.4.30 T
-notationDecl@@LIBXML2_2.4.30 T
-processingInstruction@@LIBXML2_2.4.30 T
-reference@@LIBXML2_2.4.30 T
-resolveEntity@@LIBXML2_2.4.30 T
-setDocumentLocator@@LIBXML2_2.4.30 T
-setNamespace@@LIBXML2_2.4.30 T
-startDocument@@LIBXML2_2.4.30 T
-startElement@@LIBXML2_2.4.30 T
-unparsedEntityDecl@@LIBXML2_2.4.30 T
-xmlBufAddHead T
-xmlBufEraseT
-xmlBufInflate T
-xmlBufWriteCHART
-xmlBufWriteCharT
-xmlCleanupPredefinedEntities@@LIBXML2_2.4.30 T
-xmlDecodeEntities@@LIBXML2_2.4.30 T
-xmlEncodeEntities@@LIBXML2_2.4.30 T
-xmlGetFeature@@LIBXML2_2.4.30 T
-xmlGetFeaturesList@@LIBXML2_2.4.30 T
-xmlHandleEntity@@LIBXML2_2.4.30T
-xmlIOFTPClose@@LIBXML2_2.4.30 T
-xmlIOFTPMatch@@LIBXML2_2.4.30 T
-xmlIOFTPOpen@@LIBXML2_2.4.30 T
-xmlIOFTPRead@@LIBXML2_2.4.30 T
-xmlInitializePredefinedEntities@@LIBXML2_2.4.30T
-xmlNamespaceParseNCName@@LIBXML2_2.4.30T
-xmlNamespaceParseNSDef@@LIBXML2_2.4.30 T
-xmlNamespaceParseQName@@LIBXML2_2.4.30 T
-xmlNanoFTPCheckResponse@@LIBXML2_2.4.30T
-xmlNanoFTPCleanup@@LIBXML2_2.4.30 T
-xmlNanoFTPClose@@LIBXML2_2.4.30T
-xmlNanoFTPCloseConnection@@LIBXML2_2.4.30 T
-xmlNanoFTPConnect@@LIBXML2_2.4.30 T
-xmlNanoFTPConnectTo@@LIBXML2_2.4.30T
-xmlNanoFTPCwd@@LIBXML2_2.4.30 T
-xmlNanoFTPDele@@LIBXML2_2.5.5 T
-xmlNanoFTPFreeCtxt@@LIBXML2_2.4.30 T
-xmlNanoFTPGet@@LIBXML2_2.4.30 T
-xmlNanoFTPGetConnection@@LIBXML2_2.4.30T
-xmlNanoFTPGetResponse@@LIBXML2_2.4.30 T
-xmlNanoFTPGetSocket@@LIBXML2_2.4.30T
-xmlNanoFTPInit@@LIBXML2_2.4.30 T
-xmlNanoFTPList@@LIBXML2_2.4.30 T
-xmlNanoFTPNewCtxt@@LIBXML2_2.4.30 T
-xmlNanoFTPOpen@@LIBXML2_2.4.30 T
-xmlNanoFTPProxy@@LIBXML2_2.4.30T
-xmlNanoFTPQuit@@LIBXML2_2.4.30 T
-xmlNanoFTPRead@@LIBXML2_2.4.30 T
-xmlNanoFTPScanProxy@@LIBXML2_2.4.30
