Bug#1059040: [xml/sgml-pkgs] Bug#1059040: libxml2: ABI change? (undefined references)
Hi, Am 12.01.24 um 17:56 schrieb Thorsten Glaser: On Fri, 12 Jan 2024, Rafael Laboissière wrote: experimental, the configure script does detect the absence of the xmlNanoFTPNewCtxt function in the libxml2 library (version 2.12.3+dfsg-0exp1) and disables the call to the xmlNanoFTP* functions. However, this rebuilt will not be automatically triggered without a bump in the SONAME version of libxml2. In summary, the introduction of version 2.12 of libxml2 in unstable will need a proper and coordinated transition. No, this will still break partial upgrades. Indeed. First runtime error bug report I got: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061242 Regards, Rene
Bug#1059040: libxml2: ABI change? (undefined references)
* Thorsten Glaser [2024-01-12 17:56]: On Fri, 12 Jan 2024, Rafael Laboissière wrote: experimental, the configure script does detect the absence of the xmlNanoFTPNewCtxt function in the libxml2 library (version 2.12.3+dfsg-0exp1) and disables the call to the xmlNanoFTP* functions. However, this rebuilt will not be automatically triggered without a bump in the SONAME version of libxml2. In summary, the introduction of version 2.12 of libxml2 in unstable will need a proper and coordinated transition. No, this will still break partial upgrades. Losing symbols needs a major shlib version change *including*, in Debian, changing the binary package name so that the old and new shlibs are coïnstallable. And this needs to be exercised in experimental first, not only when introducing this to unstable. Alternatively, bring the symbols back. Thanks for the clarification, this is exactly what I meant. I apologized for not being clear enough. Best, Rafael Laboissière
Bug#1059040: libxml2: ABI change? (undefined references)
On Fri, 12 Jan 2024, Rafael Laboissière wrote: > experimental, the configure script does detect the absence of the > xmlNanoFTPNewCtxt function in the libxml2 library (version > 2.12.3+dfsg-0exp1) and disables the call to the xmlNanoFTP* functions. > However, this rebuilt will not be automatically triggered without a > bump in the SONAME version of libxml2. > > In summary, the introduction of version 2.12 of libxml2 in unstable > will need a proper and coordinated transition. No, this will still break partial upgrades. Losing symbols needs a major shlib version change *including*, in Debian, changing the binary package name so that the old and new shlibs are coïnstallable. And this needs to be exercised in experimental first, not only when introducing this to unstable. Alternatively, bring the symbols back. bye, //mirabilos -- 15:41⎜ Somebody write a testsuite for helloworld :-)
Bug#1059040: libxml2: ABI change? (undefined references)
Rafael * Rene Engelhard [2023-12-25 23:48]: Hi, Am 25.12.23 um 22:57 schrieb Rene Engelhard: I didn't file it for the plain build issue. Nevertheless, if it broke so many projects you probably should do a full-fledged rebuild and send Well, mitigated by 2.12.3, but still. But again, this is completely off-topic to what I filed in this bug which is the ABI break. Which *maybe* could be ignored. Maybe one can do Breaks: after a rebuild (then you might get a problem inbetween only when in this case libreoffice is to be rebuilt. But here libreoffice fails its tests even). But not until one knows what is affected. *You* need to do a test as the library maintainer/the one who wants to update it, not me. The current issue has the potential of introducing a *huge* breakage in the distribution, due to the chain of (build-)dependencies. For instance, I tried to rebuild the plplot package in my up-to-date experimental chroot, in order to make it comply with the upcoming gnat-12 ⇒ gnat-13 transition. I ran into this, when trying to install the build-dependencies for plplot : $ pdebuild […] Setting up octave (8.4.0-1+b1) ... /usr/bin/octave-cli: symbol lookup error: /lib/libGraphicsMagick-Q16.so.3: undefined symbol: xmlNanoFTPInit, version LIBXML2_2.4.30 dpkg: error processing package octave (--configure): […] Errors were encountered while processing: octave E: Sub-process /usr/bin/dpkg returned an error code (1) If a new version of graphicsmagick were uploaded to experimental, then the problem would go away. Indeed, when the graphicsmagick package is rebuilt in experimental, the configure script does detect the absence of the xmlNanoFTPNewCtxt function in the libxml2 library (version 2.12.3+dfsg-0exp1) and disables the call to the xmlNanoFTP* functions. However, this rebuilt will not be automatically triggered without a bump in the SONAME version of libxml2. In summary, the introduction of version 2.12 of libxml2 in unstable will need a proper and coordinated transition. Best, Rafael Laboissière
Bug#1059040: libxml2: ABI change? (undefined references)
Hi, Am 25.12.23 um 22:57 schrieb Rene Engelhard: I didn't file it for the plain build issue. Nevertheless, if it broke so many projects you probably should do a full-fledged rebuild and send Well, mitigated by 2.12.3, but still. But again, this is completely off-topic to what I filed in this bug which is the ABI break. Which *maybe* could be ignored. Maybe one can do Breaks: after a rebuild (then you might get a problem inbetween only when in this case libreoffice is to be rebuilt. But here libreoffice fails its tests even). But not until one knows what is affected. *You* need to do a test as the library maintainer/the one who wants to update it, not me. Regards, Rene
Bug#1059040: libxml2: ABI change? (undefined references)
On Mon, 25 Dec 2023, Rene Engelhard wrote: > In any case, *this* bug is about the ABI change: removed symbols/versions > other > stuff relies on. > > Long story short: libxml2 2.12 has still a long road to go with much work on > your side until you can upload it to unstable. Sounds like it needs a solib major version and package name change for coïnstallability, upgrades, etc. *or* a fix that restores the prior ABI. Perhaps first ask upstream whether the removal was desired (and in which case they would do the version bump). bye, //mirabilos -- 15:41⎜ Somebody write a testsuite for helloworld :-)
Bug#1059040: libxml2: ABI change? (undefined references)
Hi, Am 25.12.23 um 22:33 schrieb Rene Engelhard: The tests are still failing and there is no patch anywhere yet, see Sorry, link got lost: https://bugs.documentfoundation.org/show_bug.cgi?id=158423 and c) you ignore the actual issue here at hand and that is that the new libxml2 breaks the ABI, causing at least libxmlsec to be needed to be rebuilt. I didn't file it for the plain build issue. Nevertheless, if it broke so many projects you probably should do a full-fledged rebuild and send patches before uploading to unstable and putting this on all maintainers (or by making them get a FTBFS bug by Lucas once a rebuild happens at which time people won't remember the libxml2 update) In any case, *this* bug is about the ABI change: removed symbols/versions other stuff relies on. Long story short: libxml2 2.12 has still a long road to go with much work on your side until you can upload it to unstable. Regards, Rene
Bug#1059040: libxml2: ABI change? (undefined references)
Hi,
Am 25.12.23 um 16:31 schrieb Aron Xu:
Hi Rene,
On Wed, Dec 20, 2023 at 3:39 AM Rene Engelhard wrote:
Am Tue, Dec 19, 2023 at 08:03:56PM +0100 schrieb Rene Engelhard:
LibreOffice builds (patch available), but doesn't yet build with 2.12.
"... but doesn't yet succeed the tests with 2.12"
That didn't change, see below.
[...]
Do we have removed symbols/removed versions here? (libxmlsec.so.1 was
not rebuilt)
After a rebuild of libxmlsec1 this link succeeds...
I see that you've committed this patch[1] to libreoffice, does this
Which is the above patch I mentioned to fix the *BUILD* with libxml2.
After that applied I ran into the issue which resulted in thig bug
report (see below in c))
The tests are still failing and there is no patch anywhere yet, see
It would actually be helpful to read because that one is said a) here
and b) in the commit ("|Only the build, not the tests (yet)!")|
mean I can proceed to upload this version of libxml2 to unstable
without further action? Or is there anything else I should coordinate
with you to prevent breakage?
and c) you ignore the actual issue here at hand and that is that the new
libxml2 breaks the ABI, causing at least libxmlsec to be needed to be
rebuilt.
Regards,
Rene
Bug#1059040: libxml2: ABI change? (undefined references)
Hi Rene, On Wed, Dec 20, 2023 at 3:39 AM Rene Engelhard wrote: > > Am Tue, Dec 19, 2023 at 08:03:56PM +0100 schrieb Rene Engelhard: > > LibreOffice builds (patch available), but doesn't yet build with 2.12. > > "... but doesn't yet succeed the tests with 2.12" > > > S=/home/rene/LibreOffice/git/libreoffice-24-2 && I=$S/instdir && > > W=$S/workdir && /usr/bin/ccache x86_64-linux-gnu-g++ -pthread > > -flto=jobserver -fuse-linker-plugin -O2 -Wl,-z,origin > > '-Wl,-rpath,$ORIGIN/../Library' -Wl,-rpath-link,$I/program -Wl,-z,defs > > -Wl,-rpath-link,/lib:/usr/lib -Wl,-z,combreloc -Wl,--hash-style=gnu > > -Wl,-Bsymbolic-functions -L$W/LinkTarget/StaticLibrary -L$I/sdk/lib > > -L$I/program -L$I/program -L$W/LinkTarget/Library -ffat-lto-objects > > -Wl,-z,relro$W/CxxObject/xmlsecurity/workben/pdfverify.o > > -Wl,--start-group-Wl,--end-group -Wl,--no-as-needed -luno_cppu > > -luno_cppuhelpergcc3 -luno_sal -lxmlsecurity -lmergedlo -o > > $W/LinkTarget/Executable/pdfverify > > /usr/bin/ld: /lib/x86_64-linux-gnu/libxmlsec1.so.1: undefined reference to > > `xmlIOFTPMatch@LIBXML2_2.4.30' > > /usr/bin/ld: /lib/x86_64-linux-gnu/libxmlsec1.so.1: undefined reference to > > `xmlNanoFTPCleanup@LIBXML2_2.4.30' > > /usr/bin/ld: /lib/x86_64-linux-gnu/libxmlsec1.so.1: undefined reference to > > `xmlIOFTPOpen@LIBXML2_2.4.30' > > /usr/bin/ld: /lib/x86_64-linux-gnu/libxmlsec1.so.1: undefined reference to > > `xmlIOFTPClose@LIBXML2_2.4.30' > > /usr/bin/ld: /lib/x86_64-linux-gnu/libxmlsec1.so.1: undefined reference to > > `xmlIOFTPRead@LIBXML2_2.4.30' > > /usr/bin/ld: /lib/x86_64-linux-gnu/libxmlsec1.so.1: undefined reference to > > `xmlNanoFTPInit@LIBXML2_2.4.30' > > collect2: error: ld returned 1 exit status > > make[3]: *** > > [/home/rene/LibreOffice/git/libreoffice-24-2/solenv/gbuild/LinkTarget.mk:853: > > > > /home/rene/LibreOffice/git/libreoffice-24-2/workdir/LinkTarget/Executable/pdfverify] > > Error 1 > > > > Do we have removed symbols/removed versions here? (libxmlsec.so.1 was > > not rebuilt) > > After a rebuild of libxmlsec1 this link succeeds... > I see that you've committed this patch[1] to libreoffice, does this mean I can proceed to upload this version of libxml2 to unstable without further action? Or is there anything else I should coordinate with you to prevent breakage? Regards, Aron Xu [1]https://salsa.debian.org/libreoffice-team/libreoffice/libreoffice/-/commit/56d340483b0285c079c7ac08ddf441457d40b955
Bug#1059040: libxml2: ABI change? (undefined references)
Am Tue, Dec 19, 2023 at 08:03:56PM +0100 schrieb Rene Engelhard: > LibreOffice builds (patch available), but doesn't yet build with 2.12. "... but doesn't yet succeed the tests with 2.12" > S=/home/rene/LibreOffice/git/libreoffice-24-2 && I=$S/instdir && W=$S/workdir > && /usr/bin/ccache x86_64-linux-gnu-g++ -pthread -flto=jobserver > -fuse-linker-plugin -O2 -Wl,-z,origin '-Wl,-rpath,$ORIGIN/../Library' > -Wl,-rpath-link,$I/program -Wl,-z,defs -Wl,-rpath-link,/lib:/usr/lib > -Wl,-z,combreloc -Wl,--hash-style=gnu -Wl,-Bsymbolic-functions > -L$W/LinkTarget/StaticLibrary -L$I/sdk/lib -L$I/program -L$I/program > -L$W/LinkTarget/Library -ffat-lto-objects -Wl,-z,relro > $W/CxxObject/xmlsecurity/workben/pdfverify.o -Wl,--start-group > -Wl,--end-group -Wl,--no-as-needed -luno_cppu -luno_cppuhelpergcc3 -luno_sal > -lxmlsecurity -lmergedlo -o $W/LinkTarget/Executable/pdfverify > /usr/bin/ld: /lib/x86_64-linux-gnu/libxmlsec1.so.1: undefined reference to > `xmlIOFTPMatch@LIBXML2_2.4.30' > /usr/bin/ld: /lib/x86_64-linux-gnu/libxmlsec1.so.1: undefined reference to > `xmlNanoFTPCleanup@LIBXML2_2.4.30' > /usr/bin/ld: /lib/x86_64-linux-gnu/libxmlsec1.so.1: undefined reference to > `xmlIOFTPOpen@LIBXML2_2.4.30' > /usr/bin/ld: /lib/x86_64-linux-gnu/libxmlsec1.so.1: undefined reference to > `xmlIOFTPClose@LIBXML2_2.4.30' > /usr/bin/ld: /lib/x86_64-linux-gnu/libxmlsec1.so.1: undefined reference to > `xmlIOFTPRead@LIBXML2_2.4.30' > /usr/bin/ld: /lib/x86_64-linux-gnu/libxmlsec1.so.1: undefined reference to > `xmlNanoFTPInit@LIBXML2_2.4.30' > collect2: error: ld returned 1 exit status > make[3]: *** > [/home/rene/LibreOffice/git/libreoffice-24-2/solenv/gbuild/LinkTarget.mk:853: > /home/rene/LibreOffice/git/libreoffice-24-2/workdir/LinkTarget/Executable/pdfverify] > Error 1 > > Do we have removed symbols/removed versions here? (libxmlsec.so.1 was > not rebuilt) After a rebuild of libxmlsec1 this link succeeds... Regards, Rene
Bug#1059040: libxml2: ABI change? (undefined references)
Package: libxml2
Version: 2.12.3+dfsg-0exp1
Severity: serious
Dear Maintainer,
Hi,
LibreOffice builds (patch available), but doesn't yet build with 2.12.
But that is not the point of this issue.
While test building current 24.2 snapshot which will become 24.2 rc1
later this week I get
[build LNK] Executable/pdfverify
S=/home/rene/LibreOffice/git/libreoffice-24-2 && I=$S/instdir && W=$S/workdir
&& mkdir -p $W/Dep/LinkTarget/Executable/ && RESPONSEFILE=/tmp/gbuild.yEebjc
&& SYSTEM_BOOST="TRUE"
LD_LIBRARY_PATH=${LD_LIBRARY_PATH:+$LD_LIBRARY_PATH:}"$I/program:$I/program"
$W/LinkTarget/Executable/concat-deps ${RESPONSEFILE} >
$W/Dep/LinkTarget/Executable/pdfverify.d.tmp && rm -f ${RESPONSEFILE}
mv
/home/rene/LibreOffice/git/libreoffice-24-2/workdir/Dep/LinkTarget/Executable/pdfverify.d.tmp
/home/rene/LibreOffice/git/libreoffice-24-2/workdir/Dep/LinkTarget/Executable/pdfverify.d
S=/home/rene/LibreOffice/git/libreoffice-24-2 && I=$S/instdir && W=$S/workdir
&& /usr/bin/ccache x86_64-linux-gnu-g++ -pthread -flto=jobserver
-fuse-linker-plugin -O2 -Wl,-z,origin '-Wl,-rpath,$ORIGIN/../Library'
-Wl,-rpath-link,$I/program -Wl,-z,defs -Wl,-rpath-link,/lib:/usr/lib
-Wl,-z,combreloc -Wl,--hash-style=gnu -Wl,-Bsymbolic-functions
-L$W/LinkTarget/StaticLibrary -L$I/sdk/lib -L$I/program -L$I/program
-L$W/LinkTarget/Library -ffat-lto-objects -Wl,-z,relro
$W/CxxObject/xmlsecurity/workben/pdfverify.o -Wl,--start-group
-Wl,--end-group -Wl,--no-as-needed -luno_cppu -luno_cppuhelpergcc3 -luno_sal
-lxmlsecurity -lmergedlo -o $W/LinkTarget/Executable/pdfverify
/usr/bin/ld: /lib/x86_64-linux-gnu/libxmlsec1.so.1: undefined reference to
`xmlIOFTPMatch@LIBXML2_2.4.30'
/usr/bin/ld: /lib/x86_64-linux-gnu/libxmlsec1.so.1: undefined reference to
`xmlNanoFTPCleanup@LIBXML2_2.4.30'
/usr/bin/ld: /lib/x86_64-linux-gnu/libxmlsec1.so.1: undefined reference to
`xmlIOFTPOpen@LIBXML2_2.4.30'
/usr/bin/ld: /lib/x86_64-linux-gnu/libxmlsec1.so.1: undefined reference to
`xmlIOFTPClose@LIBXML2_2.4.30'
/usr/bin/ld: /lib/x86_64-linux-gnu/libxmlsec1.so.1: undefined reference to
`xmlIOFTPRead@LIBXML2_2.4.30'
/usr/bin/ld: /lib/x86_64-linux-gnu/libxmlsec1.so.1: undefined reference to
`xmlNanoFTPInit@LIBXML2_2.4.30'
collect2: error: ld returned 1 exit status
make[3]: ***
[/home/rene/LibreOffice/git/libreoffice-24-2/solenv/gbuild/LinkTarget.mk:853:
/home/rene/LibreOffice/git/libreoffice-24-2/workdir/LinkTarget/Executable/pdfverify]
Error 1
Do we have removed symbols/removed versions here? (libxmlsec.so.1 was
not rebuilt)
Regards,
Rene
