Not sure why this needs to be mentioned, but obviously rebuilding the db
continuously is a test scenario, not intended for everyday use. However, it
does show that rebuilding the db, for example for transitioning from BDB to
another db, may cause weird issues if an rpm operation happens at the
As per above, rpm simply does not know enough about the surrounding world to be
able to decide when it's safe to automatically convert a database, that will
always need an explicit action by something/someone external. The general
purpose detection logic improvement in the first commit has been
Closed #1012.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/1012#event-5206176687___
Rpm-maint mailing list
@weblate pushed 4 commits.
1f5828c4b1a44d7a11a6cc3f45a2c2491e47ff2a Translated using Weblate (Finnish)
38b01e26289d8ccbc043b8212d5c82cfd5ef943e Translated using Weblate (Finnish)
1ce1bacfa34ada14968eccb6704c54f64b45a9df Translated using Weblate (Sinhala)
Closed #1664.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/1664#event-5205877532___
Rpm-maint mailing list
Closed #1663.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/1663#event-5205869133___
Rpm-maint mailing list
Replaced by #1763, but thanks for the patch nevertheless.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Closed #1638.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/1638#event-5205835903___
Rpm-maint mailing list
Closed #1636 via #1763.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/1636#event-5205831508___
Rpm-maint mailing list
Merged #1763 into master.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/1763#event-5205831491___
Rpm-maint mailing list
I know people have all manner of hacks to recover after BDB failures. When you
switch to something else, you need to stop using those BDB kludges because they
do all sorts of things (like database rebuilds) which should NOT happen as a
part of normal operation and end up only hurting instead of
FWIW, I tried to fix this in `tdnf` (https://github.com/vmware/tdnf) by calling
`rpmtxnBegin()` just after `rpmtsCreate()`, and `rpmtxnEnd()` just before
`rpmtsFree()`, and I still see this problem.
Is see this in both Fedora 33 with sqlite and in Photon 4 with bdb. It does not
seem related to
12 matches
Mail list logo
