Bug#1051537: reprepro: upgrade from 5.3.1 to 5.4.2 leaves the database in an inconsistent state

Package: reprepro Version: 5.4.2-1 Followup-For: Bug #1051537 Control: tags -1 patch For some reason the patch was not attached. Here it is in text form: *** 000-migrate-references.patch --- a/database.c +++ b/database.c @@ -1949,6 +1949,8 @@ retvalue database_openreferences(void) { r

Bug#1051537: reprepro: upgrade from 5.3.1 to 5.4.2 leaves the database in an inconsistent state

Package: reprepro Version: 5.4.2-1 Followup-For: Bug #1051537 Control: tags -1 patch I noticed that reprepro doesn't automatically migrate the database if needed after version upgrades. Instead, it raises an error and asks the user to call one of the translate* commands. Therefore I would propose

Bug#1051537: Acknowledgement (reprepro: upgrade from 5.3.1 to 5.4.2 leaves the database in an inconsistent state upon src inclusion)

I think I can confirm the bug is due to the flag I mentioned in the report. Using the `berkeleydb` package I wrote the following migrate.py python3 script: #!/usr/bin/env python3 import os import sys from berkeleydb import db as bdb def get_paths(db_dir):     db_dir = os.path.realpath(db_d

Bug#1051537: reprepro: upgrade from 5.3.1 to 5.4.2 leaves the database in an inconsistent state upon src inclusion

Package: reprepro Version: 5.4.2-1 Severity: important Tags: upstream After upgrading from v5.3.1 to v5.4.2, the issue already described in https://github.com/ionos-cloud/reprepro/issues/9 arises despite having been fixed in the source code. In more detail, if you create the repository database u