[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1061487: marked as done (bookworm-pu: package rpm/4.18.0+dfsg-1+deb12u1)

Your message dated Sat, 10 Feb 2024 13:11:21 +0000
with message-id <E1rYn8b-002yc9-S6@coccia.debian.org>
and subject line Released with 12.5
has caused the Debian Bug report #1061487,
regarding bookworm-pu: package rpm/4.18.0+dfsg-1+deb12u1
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 owner@bugs.debian.org
immediately.)


-- 
1061487: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061487
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian.org@packages.debian.org
Usertags: pu
X-Debbugs-Cc: rpm@packages.debian.org, team+pkg-rpm@tracker.debian.org, roam@debian.org
Control: affects -1 + src:rpm

[ Reason ]
Version 4.18 of RPM changed the format of its internal database
from the traditional BerkeleyDB one to a new SQLite implementation.
For compatibility purposes, including the ability to automatically
migrate an old database to a new one during an upgrade, RPM needs to
be able to read the old-format database. Some more information may
be found in #1061258.

Due to my omission when packaging the RPM update to 4.18.0,
the corresponding configure-script option was not included when
building the Debian RPM package.

[ Impact ]
Users who upgrade from RPM 4.16.0 or earlier to 4.18.0 cannot use
their database of packages already installed via RPM.

[ Tests ]
None so far.

[ Risks ]
Although the `--enable-bdb-ro` option that allows RPM to read
old-style BerkeleyDB files using its own parser is marked as
experimental in the documentation, it is considered stable enough
to use by other Linux distributions, both RPM-based and those that,
like Debian, only provide RPM as a convenience to the users.
IMHO any risk of data corruption or incorrect behavior is minimal.

[ 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 (old)stable
  [x] the issue is verified as fixed in unstable

[ Changes ]
Pass the `--enable-bdb-ro` option to the GNU configure script, thus
building the internal BerkeleyDB parser that RPM will use to read
the old-style database of installed packages.


diff -Nru rpm-4.18.0+dfsg/debian/changelog rpm-4.18.0+dfsg/debian/changelog
--- rpm-4.18.0+dfsg/debian/changelog	2023-01-05 20:29:48.000000000 +0200
+++ rpm-4.18.0+dfsg/debian/changelog	2024-01-25 14:18:24.000000000 +0200
@@ -1,3 +1,10 @@
+rpm (4.18.0+dfsg-1+deb12u1) bookworm; urgency=medium
+
+  * Team upload.
+  * Enable the read-only BerkeleyDB backend. Closes: #1061258
+
+ -- Peter Pentchev <roam@debian.org>  Thu, 25 Jan 2024 14:18:24 +0200
+
 rpm (4.18.0+dfsg-1) unstable; urgency=medium
 
   * Team upload.
diff -Nru rpm-4.18.0+dfsg/debian/rules rpm-4.18.0+dfsg/debian/rules
--- rpm-4.18.0+dfsg/debian/rules	2023-01-05 20:29:48.000000000 +0200
+++ rpm-4.18.0+dfsg/debian/rules	2024-01-25 14:18:24.000000000 +0200
@@ -26,6 +26,7 @@
 	--with-vendor=debian \
 	--enable-shared \
 	--enable-python \
+	--enable-bdb-ro \
 	CPPFLAGS="$(CPPFLAGS)"
 
 configure_paths += \

Attachment: signature.asc
Description: PGP signature


--- End Message ---
--- Begin Message --- 
Version: 12.5

The upload requested in this bug has been released as part of 12.5.

--- End Message ---
Reply to: