Package: release.debian.org
Severity: normal
User: release.debian....@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: eztr...@packages.debian.org
Control: affects -1 + src:eztrace
Hello,
I have uploaded eztrace_2.0+repack-12 to unstable, for
inclusion in bookworm.
[ Reason ]
As detailed in Bug#1034956, there is a missing breaks+replace between
the libeztrace0 package and the libeztrace-dev package.
What happened is that usr/lib/*/libeztrace-*.so (plugins) were
moved from the latter to the former in version 2.0-1, but adding
breaks replaces was missed.
[ Impact ]
The impact happens if libeztrace0 gets upgraded before libeztrace-dev:
| (Reading database ... 5608 files and directories currently installed.)
| Preparing to unpack .../libeztrace0_2.0+repack-11_amd64.deb ...
| Unpacking libeztrace0:amd64 (2.0+repack-11) over (1.1-10-2) ...
| dpkg: error processing archive ./libeztrace0_2.0+repack-11_amd64.deb
(--unpack):
| trying to overwrite '/usr/lib/x86_64-linux-gnu/libeztrace-memory.so', which
is also in package libeztrace-dev:amd64 1.1-10-2
| dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
It usually doesn't happen in practice because since libeztrace-dev
depends on the same version of libeztrace0, apt would upgrade the latter
before the former.
[ Tests ]
This was tested by hand by installing libeztrace0 on a bullseye system
with --auto-deconfigure and with libeztrace-dev installed.
[ Risks ]
The code is very trivial.
[ Checklist ]
[X] all changes are documented in the d/changelog
[X] I reviewed all changes and I approve them
[X] attach debdiff against the package in testing
Thanks!
unblock eztrace/2.0+repack-12
diff -Nru eztrace-2.0+repack/debian/changelog
eztrace-2.0+repack/debian/changelog
--- eztrace-2.0+repack/debian/changelog 2022-12-20 16:17:31.000000000 +0100
+++ eztrace-2.0+repack/debian/changelog 2023-04-27 16:07:04.000000000 +0200
@@ -1,3 +1,11 @@
+eztrace (2.0+repack-12) unstable; urgency=medium
+
+ * control: Add missing breaks+replaces between libeztrace0 and
+ libeztrace-dev, missed when moving /usr/lib/*/*.so from the latter to the
+ former (Closes: Bug#1034956)
+
+ -- Samuel Thibault <sthiba...@debian.org> Thu, 27 Apr 2023 16:07:04 +0200
+
eztrace (2.0+repack-11) unstable; urgency=medium
* control: Always depend on otf2, eztrace now always requires it actually.
diff -Nru eztrace-2.0+repack/debian/control eztrace-2.0+repack/debian/control
--- eztrace-2.0+repack/debian/control 2022-12-20 16:17:31.000000000 +0100
+++ eztrace-2.0+repack/debian/control 2023-04-27 16:06:20.000000000 +0200
@@ -53,6 +53,8 @@
Architecture: any
Multi-Arch: same
Depends: ${shlibs:Depends}, ${misc:Depends}
+Breaks: libeztrace-dev (<< 2.0-1)
+Replaces: libeztrace-dev (<< 2.0-1)
Pre-Depends: ${misc:Pre-Depends}
Description: Automatic execution trace generation for HPC - runtime libraries
EZTrace is a tool that aims at generating automatically execution traces
