Your message dated Thu, 15 Feb 2024 10:06:30 +0000
with message-id <e1rayds-009jjt...@fasolo.debian.org>
and subject line Bug#1059040: fixed in libxml2 2.12.5+dfsg-0exp1
has caused the Debian Bug report #1059040,
regarding libxml2: ABI change? (undefined references)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1059040: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059040
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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

--- End Message ---
--- Begin Message ---
Source: libxml2
Source-Version: 2.12.5+dfsg-0exp1
Done: Aron Xu <a...@debian.org>

We believe that the bug you reported is fixed in the latest version of
libxml2, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1059...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Aron Xu <a...@debian.org> (supplier of updated libxml2 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Thu, 15 Feb 2024 17:44:46 +0800
Source: libxml2
Architecture: source
Version: 2.12.5+dfsg-0exp1
Distribution: experimental
Urgency: medium
Maintainer: Debian XML/SGML Group <debian-xml-sgml-p...@lists.alioth.debian.org>
Changed-By: Aron Xu <a...@debian.org>
Closes: 1059040
Changes:
 libxml2 (2.12.5+dfsg-0exp1) experimental; urgency=medium
 .
   * New upstream version 2.12.5+dfsg
   * d/rules: configure with --with-legacy --with-ftp --with-xptr-locs
     (Closes: #1059040)
   * d/libxml2.symbols: update
   * d/libxml2-doc.doc-base: update html path
   * d/control: remove M-A: same from python3-libxml2
Checksums-Sha1:
 b6c97aaca63e1621be9d62ea3446a1e1ead1e22f 2596 libxml2_2.12.5+dfsg-0exp1.dsc
 666022b4366d3e8f0cd5324f569cfedd48cf02a5 1841040 
libxml2_2.12.5+dfsg.orig.tar.xz
 784d24185a07097a02fb909cd84115a187612bf8 27264 
libxml2_2.12.5+dfsg-0exp1.debian.tar.xz
 aa496a3ca36398a0df10617f7a37f5afcd474bd7 5617 
libxml2_2.12.5+dfsg-0exp1_source.buildinfo
Checksums-Sha256:
 a578e5fac08b8a19a47c2a6b7913bf9356787877683e60b5e0ac368b644c9528 2596 
libxml2_2.12.5+dfsg-0exp1.dsc
 d92bb8f96e7113be63f4332fdfc256c23755a4666298d6e90df6271182779595 1841040 
libxml2_2.12.5+dfsg.orig.tar.xz
 6b789b74973d18d7495e2e357d496df401012323e2f9498538ed0e189ab345db 27264 
libxml2_2.12.5+dfsg-0exp1.debian.tar.xz
 8d9ae5aa020a35635b7504a161f9d74e45a988c130f7110bf41e89cbf71170e4 5617 
libxml2_2.12.5+dfsg-0exp1_source.buildinfo
Files:
 e9ecc468e42b171df8b2a5d0cda8e5de 2596 libs optional 
libxml2_2.12.5+dfsg-0exp1.dsc
 51471a4d514305a7dab26caba527e502 1841040 libs optional 
libxml2_2.12.5+dfsg.orig.tar.xz
 499c62ea8dacff9abb9b2f73c586a424 27264 libs optional 
libxml2_2.12.5+dfsg-0exp1.debian.tar.xz
 5b4fdbb2d40fe91d01db659d701cb72c 5617 libs optional 
libxml2_2.12.5+dfsg-0exp1_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEBLHAyuu1xqoC2aJ5NP8o68vMTMgFAmXN3XgACgkQNP8o68vM
TMhxEQf/V2o797Irgulnx+JDpMY+WWNALfSoBxHltQVhEkmBcin7I8SnxJeVcGj+
cOCvzbYETc1FgSRVJ3Nl35Bq/I4rkzkv9NZ8AmCKxvncfHAJCjB++TdckkU4IizR
nLZ2WeOv0s/c6kCOK+hMkV/5nzcDRmpi+IZCIv1XygWWdJRcUS4L0ajp720Srdln
l8jdtqyrRCYVwmSlQ9jyQ+Mux/udiVy5ySyRrFfuyuHn7ZmBCzUkhMvt4a8D0RI1
+sJCJbEecDl/qyyFhM77mp636RfxOm8Tc/OOIfmrvUPlCuvIS0F5/8qenkbWO/xO
LHSgJnr0mjJTMJ3JV1gJAsYEpH+G9A==
=v8YF
-----END PGP SIGNATURE-----

Attachment: pgp0LuTCR0lFq.pgp
Description: PGP signature


--- End Message ---

Reply via email to