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

Tracker: rpm DB backend change #1964

Closed
imcleod opened this issue Jan 22, 2020 · 5 comments
Closed

Tracker: rpm DB backend change #1964

imcleod opened this issue Jan 22, 2020 · 5 comments

Comments

@imcleod
Copy link

imcleod commented Jan 22, 2020

After much delay, I'm creating a tracker issue for the upcoming change in the RPM database backend. Reference to their upstream PR: rpm-software-management/rpm#899

It's unclear to me how this might affect rpm-ostree based systems.

@jlebon
Copy link
Member

jlebon commented Jun 19, 2020

One fallout of this was https://bugzilla.redhat.com/show_bug.cgi?id=1838691.

@nullr0ute
Copy link

what's the plans with this one?

@jlebon
Copy link
Member

jlebon commented Oct 23, 2020

@nullr0ute See coreos/fedora-coreos-tracker#623. For now, we're making use of rpmdb: bdb as added in #2221. If you don't have update barriers, you probably want to stick with bdb for a while (maybe a whole Fedora release) as well to allow nodes to transition smoothly.

@jlebon
Copy link
Member

jlebon commented Oct 23, 2020

Going to close this one since I think this is handled at the rpm-ostree level now. We can chat about OS-level policies around this in the appropriate trackers.

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

4 participants