Your message dated Tue, 18 Jun 2024 16:21:33 +0000
with message-id <e1sjbap-0018z9...@fasolo.debian.org>
and subject line Bug#1072073: fixed in nanopb 0.4.8-2
has caused the Debian Bug report #1072073,
regarding python3-proto-plus has an undeclared file conflict on
/usr/lib/python3/dist-packages/proto/__init__.py
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.)
--
1072073: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072073
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-proto-plus
Version: 1.23.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: fileconflict
Control: affects -1 + nanopb
python3-proto-plus has an undeclared file conflict. This may result in
an unpack error from dpkg.
The file /usr/lib/python3/dist-packages/proto/__init__.py is contained
in the packages
* nanopb
* 0.4.4-2 as present in bullseye
* 0.4.7-2 as present in bookworm
* 0.4.8-1 as present in trixie|unstable
* python3-proto-plus/1.23.0-1 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: nanopb
Source-Version: 0.4.8-2
Done: Laszlo Boszormenyi (GCS) <g...@debian.org>
We believe that the bug you reported is fixed in the latest version of
nanopb, 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 1072...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Laszlo Boszormenyi (GCS) <g...@debian.org> (supplier of updated nanopb 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, 18 Jun 2024 17:14:12 +0200
Source: nanopb
Architecture: source
Version: 0.4.8-2
Distribution: unstable
Urgency: medium
Maintainer: Laszlo Boszormenyi (GCS) <g...@debian.org>
Changed-By: Laszlo Boszormenyi (GCS) <g...@debian.org>
Closes: 1072073
Changes:
nanopb (0.4.8-2) unstable; urgency=medium
.
* Do not force install proto files to wrong location (closes: #1072073).
* Update Standards-Version to 4.7.0 .
Checksums-Sha1:
a74fd6131143e7c868a7651e42bfc0b679e78771 1837 nanopb_0.4.8-2.dsc
848ead4bfe747c45caf4d9bee20651f6b6f82aae 4984 nanopb_0.4.8-2.debian.tar.xz
Checksums-Sha256:
09f97b644a88e3359147a0b3c147330ea79cd47f75f4cf87e336373c25dd6b69 1837
nanopb_0.4.8-2.dsc
46cc80b069c3ef37ee54e024e63b432fb263fa0db1805e9f188d0b4d384eac3a 4984
nanopb_0.4.8-2.debian.tar.xz
Files:
1df3519b1a7f94d1569e0cb54fa65bc1 1837 devel optional nanopb_0.4.8-2.dsc
8f2adf08fbc3e67da40e94eb910dce89 4984 devel optional
nanopb_0.4.8-2.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEfYh9yLp7u6e4NeO63OMQ54ZMyL8FAmZxrgQACgkQ3OMQ54ZM
yL+aQQ/+OAtAFBgtCuhpb38M0arrkRZidiZvEvJe2PmcfrxvgtpRgm/lUVNhXPJy
zlrucyJR/O4kTPX6Ne1LLu8ntKCBcal5XzhZ6Tvex0GJTBNIUePcsL9BQoR3Kyex
zDpb4RpApugjUjDGpD9paJLCfRzuXodwqrJVLtcRF6UunSkmZXoxTP3H1pUGrwhh
Bhm7AuHD9JKTUrGCBVdI0Kl0S3XxwOBFVxxwIk4rvspikQpzM7XEjouijdaYq43R
S6+VSmkLZZwh+0SbZSCoOmRAnYSJr+DfDcc9e7c6lef5oL4dJc/vNX86MmKjUyKv
pLUKQ/kx0LHkY6JwSATjzriGEtfluam1VtDEcb4lHI8hiMs8B7z9j2GrrsRTtlZc
O2RYE8PNFyT2tJRc1ShJiG2SwCl5c/9Q8QtwHeXt89wGm2DZVMrRc7l6InCXCQza
PUafvNa99KstC80uh9jDeIXS1QXDhqvMP5zflnz965Ofh4yz5gw5oQN4M2O1iXPZ
hqBaIUDlGGCQzDVpKomCmcujLLJA9lC2zdiHoNUD5nOa/CNrE1qMOSA1f7Sh7aW8
zCAFQhWkQgx/6PZsY+oz7CUc07BIN5ykfUVMkSFFdxccKLMbRweguE5ZMAOuexFA
IVhmt/ghc8eov19Dbr8fwluNyRmVgXnqyO+HXOwFIHbxK5RDKAk=
=dvxT
-----END PGP SIGNATURE-----
pgpx_ve9UajsD.pgp
Description: PGP signature
--- End Message ---
