You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: