#1100640 database corrupted somehow

Package:
reprepro
Source:
reprepro
Description:
Debian package repository producer
Submitter:
Harald Dunkel
Date:
2025-05-12 17:33:02 UTC
Severity:
normal
#1100640#5
Date:
2025-03-16 13:54:58 UTC
From:
To:
uploading a source package into my local repo for sid fails with

% reprepro includedsc sid iproute2_6.13.0-1.1.dsc
BDB1015 references: duplicate sort specified but not supported in database
db_open(/var/www/debian/db/references.db:references)[22]: Invalid argument
There have been errors!

Where the heck does this come from? This is fatal, I am stuck.


Regards

Harri

#1100640#10
Date:
2025-03-17 11:55:58 UTC
From:
To:
We believe that the bug you reported is fixed in the latest version of
reprepro, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1100640@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Bastian Germann <bage@debian.org> (supplier of updated reprepro package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)
Format: 1.8
Date: Mon, 17 Mar 2025 12:07:55 +0100
Source: reprepro
Architecture: source
Version: 5.4.7-1
Distribution: experimental
Urgency: medium
Maintainer: Bastian Germann <bage@debian.org>
Changed-By: Bastian Germann <bage@debian.org>
Closes: 1100640
Changes:
 reprepro (5.4.7-1) experimental; urgency=medium
 .
   * Import new version 5.4.7 (Closes: #1100640)
Checksums-Sha1:
 19c93b9a2b1dc83565f1453a3403e1b1b7a62e3d 1793 reprepro_5.4.7-1.dsc
 1c7c83552f8af4b255dc59e917738c02fabc7cf8 462316 reprepro_5.4.7.orig.tar.xz
 3e9c494d0fe591150c3d230b2f93dae4825103b5 15280 reprepro_5.4.7-1.debian.tar.xz
 dbfdb0c54816b7abc684fe1916ed1d70e757736b 5099 reprepro_5.4.7-1_source.buildinfo
Checksums-Sha256:
 e94a7cd5b0ecff0c67dea755c903d15df3011ab029048b4b8960b4549ed5e030 1793 reprepro_5.4.7-1.dsc
 df87e4168a580366cdeb3fdc31c5fa99b7d73140e7a7ca5d85ce64bb25370d6f 462316 reprepro_5.4.7.orig.tar.xz
 38d6f842a2d0ddfd2f8c8c3956dd16c6631af16a816838aad875ae6bc4fce925 15280 reprepro_5.4.7-1.debian.tar.xz
 218cbb54f4ffb90461672d0819e86ade4e06b055ff64fc318b828e04fc497b06 5099 reprepro_5.4.7-1_source.buildinfo
Files:
 69ba72501bcd21648f3c1fc76d631b5a 1793 utils optional reprepro_5.4.7-1.dsc
 a11fb3caf7df160798d5e75f135024eb 462316 utils optional reprepro_5.4.7.orig.tar.xz
 74336d7b07f627a897edee094b15e153 15280 utils optional reprepro_5.4.7-1.debian.tar.xz
 3a9f806b1d1ecb604aea7f78b17b5743 5099 utils optional reprepro_5.4.7-1_source.buildinfo
-----BEGIN PGP SIGNATURE-----

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmfYA5YQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFCAQDADGhg93gR4K51haKqxRPRk4pdZaIRJnkVur
bhdvbnMiBPLtTsAzv3N/gWAG9ZT3+qdA/ZjvtjdAouT97zSWzRpIEFMqEYQMgogE
T3spjkNfIWzPT2AAKmV4BZWfvad/x0WJCyW63ENGEOsDCk89oUi5flGoEqjZQi8g
u6+/qeFyyjd3BZKfwYmxPHSeMha/C2D4b0cZWqtNMrE1zX1TKlVTatNT/LwwFHlu
u1Ev5LRb3n03uzXfoZtMgQDpBz+fCCU0QETEWTs4slMHw48ELziHO8msXaWpKEK2
j4v+PAl4NwmTGUCrRll45vowCtQb0Zaxepm8isQcWXPUSu0FSZHm/TSn6bDwGXOx
/VslKVLelMU5DkZUvEdx6yOd6jQhQkJt7UP8WWt42IBnpAT2Z3dJuNBqrr+0yaAy
fL7xGBzN/TWSTsNNpEX/c7fmrnMm1BvP+XGbPYu/mxhZhb7T5laEaLX/imzT2BaO
TXLtEVbJS0CLPqZc2sTpqkE2ghuYpFk=
=hQNZ
-----END PGP SIGNATURE-----

#1100640#15
Date:
2025-03-17 11:30:10 UTC
From:
To:
I get the same thing:

BDB1015 references: duplicate sort specified but not supported in database
db_open(./db/references.db:references)[22]: Invalid argument
There have been errors!

This is new since I upgraded yesterday from 5.4.6-2 to 5.4.6+really5.3.2-1.
Manually downgrading to 5.4.6-3 (in Trixie) works around the bug for me.

#1100640#20
Date:
2025-03-17 12:43:19 UTC
From:
To:
Please switch to experimental reprepro if you experience this bug.
#1100640#25
Date:
2025-03-17 20:18:58 UTC
From:
To:
Still weird. Sample session below.

Using reprepro version 5.4.6+really5.3.2-1, just to show:

dpkg@tweety:/local/home/dpkg$ reprepro list sid  | grep iproute2
sid|main|amd64: iproute2-dbgsym|6.13.0-1.1 6.13.0-1.1
sid|main|amd64: iproute2|6.13.0-1.1 6.13.0-1.1
sid|main|source: iproute2|6.13.0-1.1 6.13.0-1.1
dpkg@tweety:/local/home/dpkg$ reprepro removesrc sid iproute2
BDB1015 references: duplicate sort specified but not supported in database
db_open(/var/www/debian/db/references.db:references)[22]: Invalid argument
There have been errors!


After the upgrade to version 5.4.7-1:

dpkg@tweety:/local/home/dpkg$ reprepro removesrc sid iproute2
Warning: tracking data might be inconsistent:
cannot find 'iproute2-dbgsym=6.13.0-1.1_amd64' in 'sid|main|amd64', but 'pool/main/i/iproute2/iproute2-dbgsym_6.13.0-1.1_amd64.deb' should be there.
Warning: tracking data might be inconsistent:
cannot find 'iproute2=6.13.0-1.1_amd64' in 'sid|main|amd64', but 'pool/main/i/iproute2/iproute2_6.13.0-1.1_amd64.deb' should be there.
There was an inconsistency in the tracking data of 'sid':
'pool/main/i/iproute2/iproute2-dbgsym_6.13.0-1.1_amd64.deb' has refcount > 0, but was nowhere found.
There was an inconsistency in the tracking data of 'sid':
'pool/main/i/iproute2/iproute2_6.13.0-1.1_amd64.deb' has refcount > 0, but was nowhere found.
Exporting indices...
Deleting files no longer referenced...
dpkg@tweety:/local/home/dpkg$ reprepro list sid  | grep iproute2
sid|main|amd64: iproute2 6.13.0-1.1
sid|main|amd64: iproute2-dbgsym 6.13.0-1.1


Running checkpool did not help:

dpkg@tweety:/local/home/dpkg$ reprepro check sid
dpkg@tweety:/local/home/dpkg$ reprepro checkpool
dpkg@tweety:/local/home/dpkg$ reprepro removesrc sid iproute2
Nothing about source package 'iproute2' found in the tracking data of 'sid'!
This either means nothing from this source in this version is there,
or the tracking information might be out of date.
dpkg@tweety:/local/home/dpkg$ reprepro list sid  | grep iproute2
sid|main|amd64: iproute2 6.13.0-1.1
sid|main|amd64: iproute2-dbgsym 6.13.0-1.1


dpkg@tweety:/local/home/dpkg$ cd
dpkg@tweety:~$ cd iproute2/
dpkg@tweety:~/iproute2$ reprepro includedsc sid iproute2_6.13.0-1.1.dsc
Exporting indices...
dpkg@tweety:~/iproute2$ reprepro includedeb sid iproute2*.deb
Skipping inclusion of 'iproute2-dbgsym' '6.13.0-1.1' in 'sid|main|amd64', as this version already exists.
Skipping inclusion of 'iproute2' '6.13.0-1.1' in 'sid|main|amd64', as this version already exists.

dpkg@tweety:~/iproute2$ reprepro removesrc sid iproute2
Exporting indices...
Deleting files no longer referenced...
dpkg@tweety:~/iproute2$ reprepro list sid | grep iproute2
sid|main|amd64: iproute2 6.13.0-1.1
sid|main|amd64: iproute2-dbgsym 6.13.0-1.1


Regards

Harri

#1100640#34
Date:
2025-03-22 05:26:53 UTC
From:
To:
Hello,

I ran into this after having upgraded to trixie earlier this week and
can confirm that the version in experimental appears to resolve the
issue.  Are you expecting that version to make it into trixie?

#1100640#39
Date:
2025-03-23 12:48:05 UTC
From:
To:
Hi Sean,

Am 22.03.25 um 06:26 schrieb Sean Whitton:

I am only going to import the experimental version to unstable/trixie if a solution for #1095493 is found.

This bug(#1100640) only affects people who have upgraded their database layout and people coming from bookworm will not
be hit by it as it has virtually no changes from the last bookworm version.

Regards,
Bastian

#1100640#44
Date:
2025-03-24 01:07:30 UTC
From:
To:
Hello,

Ah, fair enough.  I'll see if I can revert to the un-upgraded database
from my backups.

#1100640#49
Date:
2025-05-01 11:29:06 UTC
From:
To:
Hi,

Could you clarify what you mean here? In what cases would the database layout
be upgraded?

Does the issue only happen for people who were tracking testing (or unstable)
and got upgraded to 5.4.x and then back down to 5.3.x (due to the 5.4.x+really
upload)?

In that case, I agree that this wouldn't really be an issue for the trixie
release.

Thanks,

Ivo

#1100640#54
Date:
2025-05-01 13:57:47 UTC
From:
To:
Am 01.05.25 um 13:29 schrieb Ivo De Decker:

Exactly.

#1100640#59
Date:
2025-05-01 14:35:15 UTC
From:
To:
Hi,

Thanks for the clarifcation.

In that case, I'm going to downgrade the bug.

Cheers,

Ivo

#1100640#66
Date:
2025-05-12 16:52:50 UTC
From:
To:
Unfortunately I don't have a backup ofthe repo of 4 months ago.
Every helpful comment how to recover my repository would be
very welcome.

#1100640#71
Date:
2025-05-12 17:28:54 UTC
From:
To:
	Fixed in version reprepro/5.4.7-1

in this bug report? This is misleading.

Thank you