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

Provide a method to migrate the dnf4 history database #1871

Open
jan-kolarik opened this issue Nov 18, 2024 · 2 comments
Open

Provide a method to migrate the dnf4 history database #1871

jan-kolarik opened this issue Nov 18, 2024 · 2 comments

Comments

@jan-kolarik
Copy link
Member

dnf5 now automatically migrates the dnf4 database on first use. However, user reports (e.g. here or here) indicate potential issues with incomplete or failed migrations.

To address this, it would be helpful to introduce an explicit method in dnf5 to manually trigger database migration from dnf4.

Alternatively, dnf5 could perform a dnf4 database lookup whenever it encounters a missing state in its own database. If the latter approach is chosen, we should ensure it does not impact dnf5 performance and consider making it configurable.

@luksak
Copy link

luksak commented Nov 19, 2024

Oh that feature would be great! Is there a way to replicate this manually until we have this feature?

@lantw44
Copy link

lantw44 commented Nov 24, 2024

dnf5 now automatically migrates the dnf4 database on first use.

Does DNF 5 really migrate things, including the history database? I installed a Fedora 40 VM, upgraded it to Fedora 41, and dnf history showed nothing. I hope there will be a tool which can make dnf history show the same thing as dnf4 history like how the YUM to DNF migration was done.

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

No branches or pull requests

3 participants