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

Bug#1125350: trixie-pu: package reprepro/5.4.6+really5.3.2-1+deb13u1



Package: release.debian.org
Severity: normal
Tags: trixie
X-Debbugs-Cc: reprepro@packages.debian.org
Control: affects -1 + src:reprepro
User: release.debian.org@packages.debian.org
Usertags: pu

[ Reason ]
#1125255 explains that the tracking data in reprepro's database is not
correct for the copying task. It should reference a source version
instead of a binary one.

[ Impact ]
Inconsistent database.

[ Tests ]
Use reprepro copy and compare the package list and the tracking
database.

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

[ Changes ]
Fills a database field correctly with source version instead of binary
version.
diff -Nru reprepro-5.4.6+really5.3.2/debian/changelog reprepro-5.4.6+really5.3.2/debian/changelog
--- reprepro-5.4.6+really5.3.2/debian/changelog	2025-03-15 10:40:45.000000000 +0100
+++ reprepro-5.4.6+really5.3.2/debian/changelog	2026-01-12 21:51:27.000000000 +0100
@@ -1,3 +1,9 @@
+reprepro (5.4.6+really5.3.2-1+deb13u1) trixie; urgency=medium
+
+  * Fix incorrect tracking data when copying packages (Closes: #1125255)
+
+ -- Bastian Germann <bage@debian.org>  Mon, 12 Jan 2026 21:51:27 +0100
+
 reprepro (5.4.6+really5.3.2-1) unstable; urgency=medium
 
   * Recover after bad multiple versions upload (see: #1095493)
diff -Nru reprepro-5.4.6+really5.3.2/debian/patches/series reprepro-5.4.6+really5.3.2/debian/patches/series
--- reprepro-5.4.6+really5.3.2/debian/patches/series	1970-01-01 01:00:00.000000000 +0100
+++ reprepro-5.4.6+really5.3.2/debian/patches/series	2026-01-12 21:48:33.000000000 +0100
@@ -0,0 +1 @@
+tracking-data-copying.patch
diff -Nru reprepro-5.4.6+really5.3.2/debian/patches/tracking-data-copying.patch reprepro-5.4.6+really5.3.2/debian/patches/tracking-data-copying.patch
--- reprepro-5.4.6+really5.3.2/debian/patches/tracking-data-copying.patch	1970-01-01 01:00:00.000000000 +0100
+++ reprepro-5.4.6+really5.3.2/debian/patches/tracking-data-copying.patch	2026-01-12 21:47:38.000000000 +0100
@@ -0,0 +1,26 @@
+From: Miao Wang <shankerwangmiao@gmail.com>
+Date: Sun, 11 Jan 2026 21:09:03 +0800
+Subject: Fix incorrect tracking data when copying packages
+
+Tracking database should contain codename, source package name and
+source version as the key and the containing files as the value in the
+tracking database. When packages are copied between codenames, it
+incorrectly uses binary package version, causing inconsistency between
+the package database and the tracking database.
+---
+ copypackages.c | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/copypackages.c b/copypackages.c
+index 4598fd38..e47686a3 100644
+--- a/copypackages.c
++++ b/copypackages.c
+@@ -262,7 +262,7 @@ static retvalue package_add(struct distribution *into, /*@null@*/trackingdb trac
+ 		return RET_ERROR_INTERRUPTED;
+ 	if (tracks != NULL) {
+ 		r = trackingdata_summon(tracks, package->sourcename,
+-				package->version, &trackingdata);
++				package->sourceversion, &trackingdata);
+ 		if (RET_WAS_ERROR(r))
+ 			return r;
+ 	}

Reply to: