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.000000000 +0900
-__docbDefaultSAXHandler T
-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.30 T
-docbDefaultSAXHandler@@LIBXML2_2.4.30 D
-docbDefaultSAXHandlerInit@@LIBXML2_2.4.30 T
-elementDecl@@LIBXML2_2.4.30 T
-endDocument@@LIBXML2_2.4.30 T
-endElement@@LIBXML2_2.4.30 T
-entityDecl@@LIBXML2_2.4.30 T
-externalSubset@@LIBXML2_2.4.30 T
-getColumnNumber@@LIBXML2_2.4.30 T
-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.30 T
-getSystemId@@LIBXML2_2.4.30 T
-globalNamespace@@LIBXML2_2.4.30 T
-hasExternalSubset@@LIBXML2_2.4.30 T
-hasInternalSubset@@LIBXML2_2.4.30 T
-htmlDecodeEntities T
-ignorableWhitespace@@LIBXML2_2.4.30 T
-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
-xmlBufErase T
-xmlBufInflate T
-xmlBufWriteCHAR T
-xmlBufWriteChar T
-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.30 T
-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.30 T
-xmlNamespaceParseNCName@@LIBXML2_2.4.30 T
-xmlNamespaceParseNSDef@@LIBXML2_2.4.30 T
-xmlNamespaceParseQName@@LIBXML2_2.4.30 T
-xmlNanoFTPCheckResponse@@LIBXML2_2.4.30 T
-xmlNanoFTPCleanup@@LIBXML2_2.4.30 T
-xmlNanoFTPClose@@LIBXML2_2.4.30 T
-xmlNanoFTPCloseConnection@@LIBXML2_2.4.30 T
-xmlNanoFTPConnect@@LIBXML2_2.4.30 T
-xmlNanoFTPConnectTo@@LIBXML2_2.4.30 T
-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.30 T
-xmlNanoFTPGetResponse@@LIBXML2_2.4.30 T
-xmlNanoFTPGetSocket@@LIBXML2_2.4.30 T
-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.30 T
-xmlNanoFTPQuit@@LIBXML2_2.4.30 T
-xmlNanoFTPRead@@LIBXML2_2.4.30 T
-xmlNanoFTPScanProxy@@LIBXML2_2.4.30 T
-xmlNanoFTPUpdateURL@@LIBXML2_2.4.30 T
-xmlNewGlobalNs@@LIBXML2_2.4.30 T
-xmlParseNamespace@@LIBXML2_2.4.30 T
-xmlParseQuotedString@@LIBXML2_2.4.30 T
-xmlParserHandleReference@@LIBXML2_2.4.30 T
-xmlSAX2InitDocbDefaultSAXHandler@@LIBXML2_2.6.0 T
-xmlScanName@@LIBXML2_2.4.30 T
-xmlSetEntityReferenceFunc@@LIBXML2_2.4.30 T
-xmlSetFeature@@LIBXML2_2.4.30 T
-xmlUpgradeOldNs T
-xmlXPtrAdvanceNode T
-xmlXPtrBuildNodeList@@LIBXML2_2.4.30 T
-xmlXPtrEvalRangePredicate@@LIBXML2_2.4.30 T
-xmlXPtrFreeLocationSet@@LIBXML2_2.4.30 T
-xmlXPtrLocationSetAdd@@LIBXML2_2.4.30 T
-xmlXPtrLocationSetCreate@@LIBXML2_2.4.30 T
-xmlXPtrLocationSetDel@@LIBXML2_2.4.30 T
-xmlXPtrLocationSetMerge@@LIBXML2_2.4.30 T
-xmlXPtrLocationSetRemove@@LIBXML2_2.4.30 T
-xmlXPtrNewCollapsedRange@@LIBXML2_2.4.30 T
-xmlXPtrNewLocationSetNodeSet@@LIBXML2_2.4.30 T
-xmlXPtrNewLocationSetNodes@@LIBXML2_2.4.30 T
-xmlXPtrNewRange@@LIBXML2_2.4.30 T
-xmlXPtrNewRangeNodeObject@@LIBXML2_2.4.30 T
-xmlXPtrNewRangeNodePoint@@LIBXML2_2.4.30 T
-xmlXPtrNewRangeNodes@@LIBXML2_2.4.30 T
-xmlXPtrNewRangePointNode@@LIBXML2_2.4.30 T
-xmlXPtrNewRangePoints@@LIBXML2_2.4.30 T
-xmlXPtrRangeToFunction@@LIBXML2_2.4.30 T
-xmlXPtrWrapLocationSet@@LIBXML2_2.4.30 T
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
Regards,
Mamoru
_______________________________________________
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
