On 03. 02. 21 10:13, Panu Matilainen wrote:
Hey all,
Just woke up to the fact that F34 is about to be branched, and that we
originally planned to phase out BDB rpmdb support to read-only in Fedora 34 [1].
That's too close to comfort for me, and might be considered too late for other
reasons too. So a slight change of plans, lets postpone this to F35, and handle
this right away after F34 has been branched. Rpm >= 4.17 which is to be expected
later in F35 will not *have* read-write BDB support at all, so disabling it
early gives folks a little of leeway where things can still be temporarily
reverted if something unexpected breaks.
Should we file a separate system-wide change for this, or can we proceed on the
basis that this was already accepted as a part of the sqlite change [1]?
I'd say this is already accepted as a part of the sqlite change, but please open
a placeholder issue at https://pagure.io/fedora-docs/release-notes to make sure
we document this in the release notes of Fedora 35.
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx