Your message dated Tue, 27 Feb 2024 21:08:53 +0000
with message-id <e1rf4h3-002wlk...@fasolo.debian.org>
and subject line Bug#1064890: fixed in xmlsec1 1.2.39-3
has caused the Debian Bug report #1064890,
regarding libxmlsec1-dev,libxmlsec1-doc: both ship
/usr/share/doc/libxmlsec1-dev/examples/*
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.)
--
1064890: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064890
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libxmlsec1-dev,libxmlsec1-doc
Version: 1.2.39-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files.
>From the attached log (scroll to the bottom...):
Preparing to unpack .../libxmlsec1-doc_1.2.39-2_all.deb ...
Unpacking libxmlsec1-doc (1.2.39-2) ...
dpkg: error processing archive
/var/cache/apt/archives/libxmlsec1-doc_1.2.39-2_all.deb (--unpack):
trying to overwrite '/usr/share/doc/libxmlsec1-dev/examples/Makefile', which
is also in package libxmlsec1-dev 1.2.39-2
Errors were encountered while processing:
/var/cache/apt/archives/libxmlsec1-doc_1.2.39-2_all.deb
These files are in conflict:
usr/share/doc/libxmlsec1-dev/examples/Makefile
usr/share/doc/libxmlsec1-dev/examples/Makefile.w32
usr/share/doc/libxmlsec1-dev/examples/README.md
usr/share/doc/libxmlsec1-dev/examples/binary.dat
usr/share/doc/libxmlsec1-dev/examples/ca2cert.pem
usr/share/doc/libxmlsec1-dev/examples/cacert.pem
usr/share/doc/libxmlsec1-dev/examples/decrypt1.c
usr/share/doc/libxmlsec1-dev/examples/decrypt2.c
usr/share/doc/libxmlsec1-dev/examples/decrypt3.c
usr/share/doc/libxmlsec1-dev/examples/deskey.bin
usr/share/doc/libxmlsec1-dev/examples/encrypt1-res.xml
usr/share/doc/libxmlsec1-dev/examples/encrypt1-tmpl.xml
usr/share/doc/libxmlsec1-dev/examples/encrypt1.c
usr/share/doc/libxmlsec1-dev/examples/encrypt2-doc.xml
usr/share/doc/libxmlsec1-dev/examples/encrypt2-res.xml
usr/share/doc/libxmlsec1-dev/examples/encrypt2.c
usr/share/doc/libxmlsec1-dev/examples/encrypt3-doc.xml
usr/share/doc/libxmlsec1-dev/examples/encrypt3-res.xml
usr/share/doc/libxmlsec1-dev/examples/encrypt3.c
usr/share/doc/libxmlsec1-dev/examples/mywin32make.bat
usr/share/doc/libxmlsec1-dev/examples/rsacert.pem
usr/share/doc/libxmlsec1-dev/examples/rsakey.pem
usr/share/doc/libxmlsec1-dev/examples/rsapub.pem
usr/share/doc/libxmlsec1-dev/examples/sign1-res.xml
usr/share/doc/libxmlsec1-dev/examples/sign1-tmpl.xml
usr/share/doc/libxmlsec1-dev/examples/sign1.c
usr/share/doc/libxmlsec1-dev/examples/sign2-doc.xml
usr/share/doc/libxmlsec1-dev/examples/sign2-res.xml
usr/share/doc/libxmlsec1-dev/examples/sign2.c
usr/share/doc/libxmlsec1-dev/examples/sign3-doc.xml
usr/share/doc/libxmlsec1-dev/examples/sign3-res.xml
usr/share/doc/libxmlsec1-dev/examples/sign3.c
usr/share/doc/libxmlsec1-dev/examples/verify1.c
usr/share/doc/libxmlsec1-dev/examples/verify2.c
usr/share/doc/libxmlsec1-dev/examples/verify3.c
usr/share/doc/libxmlsec1-dev/examples/verify4-bad-res.xml
usr/share/doc/libxmlsec1-dev/examples/verify4-bad-tmpl.xml
usr/share/doc/libxmlsec1-dev/examples/verify4-res.xml
usr/share/doc/libxmlsec1-dev/examples/verify4-tmpl.xml
usr/share/doc/libxmlsec1-dev/examples/verify4.c
usr/share/doc/libxmlsec1-dev/examples/xmldsigverify.c
cheers,
Andreas
libxmlsec1-dev=1.2.39-2_libxmlsec1-doc=1.2.39-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: xmlsec1
Source-Version: 1.2.39-3
Done: Rene Engelhard <r...@debian.org>
We believe that the bug you reported is fixed in the latest version of
xmlsec1, 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 1064...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Rene Engelhard <r...@debian.org> (supplier of updated xmlsec1 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: SHA512
Format: 1.8
Date: Tue, 27 Feb 2024 21:23:46 +0100
Source: xmlsec1
Architecture: source
Version: 1.2.39-3
Distribution: experimental
Urgency: medium
Maintainer: Debian XML/SGML Group <debian-xml-sgml-p...@lists.alioth.debian.org>
Changed-By: Rene Engelhard <r...@debian.org>
Closes: 1064890
Changes:
xmlsec1 (1.2.39-3) experimental; urgency=medium
.
* dh_installexamples -plibxmlsec1-dev (closes: #1064890)
Checksums-Sha1:
f31fb89930b8436ca11abc17f42a19b02655682c 2664 xmlsec1_1.2.39-3.dsc
b7ee2fd2300fd4c2e5948d44877374424d17420f 14716 xmlsec1_1.2.39-3.debian.tar.xz
6aaca6272542ca10b84f9bc423dc5b1474b11539 7323 xmlsec1_1.2.39-3_source.buildinfo
Checksums-Sha256:
e24a5ea2eab11aaf4bbdfb5f241f0392cd7a731922891c8a128d91f0c55eed33 2664
xmlsec1_1.2.39-3.dsc
42d589e1e2218fe3f1f2d12c702cfca2cf4304dd9818aa883ca682840c26a984 14716
xmlsec1_1.2.39-3.debian.tar.xz
e5cb621ede44b997a67c1a72a3c4ea9a01d43b0f92dc783b38ac7e12e8f4b9cf 7323
xmlsec1_1.2.39-3_source.buildinfo
Files:
7b2077990ba8281dbf125ea835c2b1c4 2664 text optional xmlsec1_1.2.39-3.dsc
de0a9008191ac241f9b4e5b9dd77840c 14716 text optional
xmlsec1_1.2.39-3.debian.tar.xz
e83e8d8b0abbb5f0a6068118feb9e68a 7323 text optional
xmlsec1_1.2.39-3_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQJEBAEBCgAuFiEE4S3qRnUGcM+pYIAdCqBFcdA+PnAFAmXeR6cQHHJlbmVAZGVi
aWFuLm9yZwAKCRAKoEVx0D4+cPRuEACY4ibTcL/gBkPlvWPxRWnAsBbTzwbNKhLn
sB6xbC3bd7n9vWTDARUS2zugmVi6wCeNXgaSDMFJVhkfKsJFTUjOGeUY9fvCU3zQ
1xa2He6wk6bQS8+6eIOrzFf+r2mn6qJmVMwr+4dJJAW8ix0IzS5XLHucJROKvnKq
OSsexSKWoqaBvTYulbd5FfMI73atcOAAzE5KGBGAxAJ2wm7lZ6eEb3hIakOdUIjV
2mBbZ+KcjfSpKY7fMGvVxPepP5RaKK6m+1TTjrRVzmiOBR0SbW30cD9v0rAKuNC4
RDANTKO4gJ3jeIoojHtgrITI8IOe1J3CF0xX3YcHARDgFFAZzJtf5c9nSpw/q0GP
QpdcbTPZaxzLV9HURp/hzyjlnpMCeCVifUT4XFzZX6Quk0ZQUJtzSlOwm5s2Ij4X
FcUYhsa1o8/WF368oGZ5skP7FM0MKDKYxSuBAh70mooWOZ921FhGoQY7/WQYPnER
Zai1tlzwyFFV/qdGaImspSWd0WvMMasH7r0jgzSYWz//PaTVb+rcrU/TT6oBRchA
oC/7wrAUKExIEvu8pStcuN0mmuywZTQnwiL39KQqTI4i08qeMTlcKS/9sCPoBRjf
uFp1RXi45gM4Hl92ZY8ZhPAkhtQWc2DSYJSp+7YWiDSVgk9t96JgjV9oGoIYxsps
kRBTnTsghQ==
=3OEv
-----END PGP SIGNATURE-----
pgpze4FFdIdpO.pgp
Description: PGP signature
--- End Message ---
