Your message dated Thu, 06 Feb 2025 21:27:58 +0100
with message-id <8de80fd3b4c8f7b3835ce3baeeeaec01b615bf50.ca...@debian.org>
and subject line Re: pinfo and python3-plaso have an undeclared file conflict
on /usr/bin/pinfo
has caused the Debian Bug report #1093745,
regarding pinfo and python3-plaso have an undeclared file conflict on
/usr/bin/pinfo
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.)
--
1093745: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1093745
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pinfo,python3-plaso
Severity: serious
User: debian...@lists.debian.org
Usertags: fileconflict
The file /usr/bin/pinfo is contained in the packages
* pinfo/0.6.13-1.3+b1 as present in unstable
* python3-plaso/20241006-2 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.
Please figure out which of these packages should properly own the
affected file and reassign the bug as appropriate. When doing so, please
add the other package to the set of affected packages using "Control:
affects -1 + <packagename>" to avoid the filing of duplicates.
The other package should stop installing the file. In case the file is
being moved between packages, Breaks and Replaces should be declared. In
this case, please refer to policy section 7.6 for details. Another
useful resource is https://wiki.debian.org/PackageTransition.
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: plaso
Source-Version: 20241006-3
Done: Hilko Bengen <ben...@debian.org>
A typo in the changelog entry prevented this bug from being closed
automatically.
Below summary of the changes has been copied over from bug #1093743.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Fri, 24 Jan 2025 00:49:07 +0100
Source: plaso
Architecture: source
Version: 20241006-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Security Tools
<team+pkg-secur...@tracker.debian.org>
Changed-By: Hilko Bengen <ben...@debian.org>
Closes: 1093743
Changes:
plaso (20241006-3) unstable; urgency=medium
.
* Eliminate file conflicts by prefixing all binaries with "plaso-"
(Closes: #1093743, #1093743)
Checksums-Sha1:
ddbacd85b0a88c9eaba8f8fb6893ee2078bd1d93 3685 plaso_20241006-3.dsc
2088b7825703b7249d35bce51503d7ce9efc8031 18792 plaso_20241006-
3.debian.tar.xz
7b014eac987ae45a141f6c947eeafdce88adfc4e 12422 plaso_20241006-
3_source.buildinfo
Checksums-Sha256:
2ed09479d45f41cc3e668bfe432c2b936297b5390d5c239299f1bc9d924a7857 3685
plaso_20241006-3.dsc
45c55a34977f6213d8dde5ecae83cb27c8ab120d9a2915aca7a5698d4e965db2 18792
plaso_20241006-3.debian.tar.xz
2b2fec66a1cc8d3e186d6934c30aede5dff3bd03bec0ca24df6eb338f13d6cda 12422
plaso_20241006-3_source.buildinfo
Files:
28a6bbdf447cec447dbf28ed2fa660ef 3685 admin optional plaso_20241006-
3.dsc
62a68069d60aba57a86b8b274a1a4f0a 18792 admin optional plaso_20241006-
3.debian.tar.xz
9b1da40e33d8e4e52d6d2d165e3f9170 12422 admin optional plaso_20241006-
3_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEErnMQVUQqHZbPTUx4dbcQY1whOn4FAmeS1tAACgkQdbcQY1wh
On5CxRAAuGQNEdATnf8xrv5IA65nQGxJbeolneI8Zdq2KfNq5Vh+MeMyI8vTRV2x
GqXK2iZY8RBn518deG3qoC50dAV9gtlMHKRbZ6CtYW8NJBNim+M1I2kQHt9fviGI
d0w69saQBAmmTpaNTSkiwNqUDAMvP93ZTfqp9CIu0Zy5/VUJqIeKfmkUEEIuca3x
a4o6USYJSypo8kqdzHMZ5SqjvpOVO61k+JG9Ci5WqsuFWPb0Vx0vOh92Lw9Qy2R0
PuHFEHydqOP/epv58QZNYyyEWVGfVLGJ92Qcvj1/oeWE/H8015k6L6GQ/MOr6+HP
Qv7blIouJnGNzjCDYBZ500PXRz7mjGpL7Bt6/vc3CJBBgVK5ZhDZGwA7tPPrBMGf
5hpH7iRzLZt/2etbN9j0hbNGrAVvf04T9MbJQXJhkN/BOfoJJXCN0oWJu16jwaFZ
BVLHWfM6KlHU+wdFpG4FkwitsJNgbv7kKvu7pBnp8tBrM8GHgUu4mVL4rAAyZR15
W82E65S3iT1xEaueKcRmZ7UvO93oofj2mBLRvk+JzfVAUyMeHlEQGUfso8UbYa/w
ChgrJL3TwfiJo6ezofZ9GYTCaQF1low4X13jeGf2pHdYOn0A+73cf2aKuny35N0h
q1R1Gjmol43lDVZruLdS3TPX82FeOn5dL+1HiZBSJ5bBOxV3uKs=
=seWT
-----END PGP SIGNATURE-----
--
GPG Fingerprint
3DF5 E8AA 43FC 9FDF D086 F195 ADF5 0EDA F8AD D585
signature.asc
Description: This is a digitally signed message part
--- End Message ---
