Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

On update: Internal error of the underlying BerkeleyDB database #25

Open
cluck opened this issue Sep 27, 2023 · 1 comment
Open

On update: Internal error of the underlying BerkeleyDB database #25

cluck opened this issue Sep 27, 2023 · 1 comment

Comments

@cluck
Copy link

cluck commented Sep 27, 2023

I just updated Debian from bullseye to bookworm and shortly after that (having called the bookworm version of reprepro successfully from my unchanged scripts) I updated just the reprepro package to the Debian experimental version (5.4.2-1). Immediately my scripts triggered the below error during calls to reprepro includedeb. But after a few repetitions of the same command (I tried to bring up a reproducible case) I suddenly found that the error had stopped from appearing (I did not downgrade in the meantime, reprepro: This is reprepro version 5.4.2).

My gut feeling is that we're looking at a "database" update that crashes in between a "transaction" which no ACID properties, thus after each crash the "old" record is gone, but the "new" record never landed in the "database".

BDB0696 Duplicate data items are not supported with sorted data
Internal error of the underlying BerkeleyDB database:
Within references.db subtable references at put: BDB0067 DB_KEYEXIST: Key/data pair already exists
@cluck
Copy link
Author

cluck commented Sep 27, 2023

After re-reading Issue #18 I realize that calling reprepro check and reprepro export while preparing the bug report may have been the commands that "fixed" the database instead.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant