Package: libsbig4t64
Version: 4.9.9-5
Severity: serious
Tags: patch
User: helm...@debian.org
Usertags: dep17p1
Control: affects -1 + libsbig4
Hi Thorsten,
in your last upload, you accidentally added a file loss condition. In
accepting the t64 package rename and in the same upload doing the
/usr-move a file loss scenario (DEP17 P1) for the five firmware files
and 51-sbig-debian.rules was introduced. Since libsbig is not normally
involved in system boot, I recommend using the simplest mitigation of
upgrading Replaces to Conflicts (DEP17 M7). While this is not safe in
all cases, upgrades performed using apt-like tools such as aptitude will
work. I'm attaching a patch for your convenience. Users of unstable who
have lost these files due to upgrading to the affected version, will
automatically fix their system on the next upgrade.
Helmut
diff --minimal -Nru libsbig-4.9.9/debian/changelog
libsbig-4.9.9/debian/changelog
--- libsbig-4.9.9/debian/changelog 2024-07-12 18:49:12.000000000 +0200
+++ libsbig-4.9.9/debian/changelog 2024-08-19 16:02:36.000000000 +0200
@@ -1,3 +1,11 @@
+libsbig (4.9.9-5.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Upgrade Replaces to Conflicts to mitigate /usr-move induced file loss.
+ (DEP17 P1 M7, Closes: #-1)
+
+ -- Helmut Grohne <hel...@subdivi.de> Mon, 19 Aug 2024 16:02:36 +0200
+
libsbig (4.9.9-5) unstable; urgency=medium
* upload to unstable
diff --minimal -Nru libsbig-4.9.9/debian/control libsbig-4.9.9/debian/control
--- libsbig-4.9.9/debian/control 2024-07-12 18:49:12.000000000 +0200
+++ libsbig-4.9.9/debian/control 2024-08-19 16:02:26.000000000 +0200
@@ -16,8 +16,7 @@
Package: libsbig4t64
Provides: ${t64:Provides}
-Replaces: libsbig4
-Breaks: libsbig4 (<< ${source:Version})
+Conflicts: libsbig4 (<< ${source:Version})
Architecture: amd64 armhf arm64
Depends: ${shlibs:Depends}, ${misc:Depends}
, fxload
