Your message dated Thu, 03 Oct 2024 12:06:32 +0000
with message-id <e1swkbi-00awgy...@fasolo.debian.org>
and subject line Bug#1078866: fixed in libgctp 2.0.0-11
has caused the Debian Bug report #1078866,
regarding libgctp-dev has an undeclared file conflict on
/usr/lib/x86_64-linux-gnu/libgctp-2.0.0.so
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.)
--
1078866: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1078866
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libgctp-dev
Version: 2.0.0-10
Severity: serious
User: debian...@lists.debian.org
Usertags: fileconflict
Control: affects -1 + libgctp-2.0.0
libgctp-dev has an undeclared file conflict. This may result in an
unpack error from dpkg.
The file /usr/lib/x86_64-linux-gnu/libgctp-2.0.0.so is contained in the
packages
* libgctp-2.0.0
* 2.0.0-6 as present in bookworm|bullseye
* 2.0.0-6+b1 as present in trixie
* libgctp-dev/2.0.0-10 as present in unstable
These packages can be unpacked concurrently, because there is no
relevant Replaces or Conflicts relation. Attempting to unpack these
packages concurrently results in an unpack error from dpkg, because none
of the packages installs a diversion for the affected file.
Kind regards
The Debian Usr Merge Analysis Tool
This bug report has been automatically filed with no human intervention.
The source code is available at https://salsa.debian.org/helmutg/dumat.
If the filing is unclear or in error, don't hesitate to contact
hel...@subdivi.de for assistance.
--- End Message ---
--- Begin Message ---
Source: libgctp
Source-Version: 2.0.0-11
Done: Alastair McKinstry <mckins...@debian.org>
We believe that the bug you reported is fixed in the latest version of
libgctp, 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 1078...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Alastair McKinstry <mckins...@debian.org> (supplier of updated libgctp 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, 03 Oct 2024 12:44:02 +0100
Source: libgctp
Architecture: source
Version: 2.0.0-11
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers
<debian-science-maintain...@lists.alioth.debian.org>
Changed-By: Alastair McKinstry <mckins...@debian.org>
Closes: 1078866
Changes:
libgctp (2.0.0-11) unstable; urgency=medium
.
* Drop unused pre-depends
* Add Replaces to libgctp-dev. Closes: #1078866
* Move to d/watch version 4
Checksums-Sha1:
4691543c5efb918a6d24d4afe350a7f1aef66257 2028 libgctp_2.0.0-11.dsc
03bff3f4a0f7011bd3b3fea5904c64580c71e874 3908 libgctp_2.0.0-11.debian.tar.xz
Checksums-Sha256:
77e0aa86b11207776fcc233eae6024c7042900e692d40656a506852a11731f2d 2028
libgctp_2.0.0-11.dsc
b9d2713f4d93e6c64a6e9d1b001baeb2d4d5eccf20c3f8ea8b1945d24881d8c6 3908
libgctp_2.0.0-11.debian.tar.xz
Files:
6ff6e7b690b20098aa20c42330ab99ff 2028 utils optional libgctp_2.0.0-11.dsc
5626ddd76b54aa114c955c6c5e129877 3908 utils optional
libgctp_2.0.0-11.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEgjg86RZbNHx4cIGiy+a7Tl2a06UFAmb+hIAACgkQy+a7Tl2a
06VeDg/7BxerAjj6nBbhawb8IccsZhOJWoCWFknNWmxjURdouzqDwndZNhuBkGaB
8jVCRS/1kHskSPQdxaQDxWSMQTHGepZg1zU0Jv2KTd8eQ7rm0bW3pa6ONvVo4SYC
fekN+f883CD2O3xFw5AuRL8A7EMqY5I3h77fe4BKHmZBFDGTkutCRB1n2eS0UdGP
wXNQOS5flTiDNedWPq/TfVqvMfjRhZDYxFsqD5PpUZfbTm18Tw7teGclY5BZpXRi
jEEDPbxfetGS9rOiw9ZYEX/jbM9r4CNrB74460XN4yry+QRjayE9NpXKejzem7fQ
OLnVdwykWv/CZoYwuaKKHd1nq4ObMo9m5+s+VCmSIiyhBLPPU1RQiSeReyOldcyO
35JLNF2Odz3scmRVIL1s6pq3pKTm0n4AoPn6t+ftJ7d4jRLmX1DHzo/DLqFBCtRu
9Q633ejHORxdg3d/rSMLU7TB0H0P2EaJemvnCBJKJ6aOn1ELQ0Rh3RQ8d7s/SraQ
Nl3/JplS0QNsgTjjnwkXFHZVMGJxIwDPid0KI12L3zh/ZGBga96ZbMTw4zzsoJSX
dmkcwMQf31hPLUtL2BaKaB0JJrGTSEytoqGE0yrA1GQBgyV11RFmTKN6kSwZVDx2
oP7XzUF0OCd1SZJnuNzlbKPFmpmoPbLZHi/sURMAnDbSZwctbC0=
=GQ1r
-----END PGP SIGNATURE-----
pgp0CcTRi1DHj.pgp
Description: PGP signature
--- End Message ---
