Upgrade to Mageia 9 using dnf-system-upgrade

[Bequimao]

I tested an upgrade to Mageia 9 with dnf. The system had KDE Plasma and Gnome installed.

I had to invoke

Code: Select all

# dnf system-upgrade download --releasever=cauldron --allowerasing

After release the call would be with --releasever=9, of course. The upgrade itself started after

Code: Select all

# dnf system-upgrade reboot


the upgrade counter stalled at [865/6103] lib64plymouth5. The transaction however continued and ended successfully. This is an irritating bug, but I would not try to reproduce it, and I do not expect that it would be resolved by Mageia.

You have to reconfigure the repos manually with

Code: Select all

# dnf repo-manager --set-enabled ( or --set-disabled)


The result should look like

Code: Select all

# dnf repolist
repo id                                                                       
repo name
cauldron-x86_64                                                                 
Mageia Cauldron - x86_64
cauldron-x86_64-nonfree                                                         
Mageia Cauldron - x86_64 - Nonfree
cauldron-x86_64-tainted                                                         
Mageia Cauldron - x86_64 - Tainted


One has further to invoke

Code: Select all

# rpmdb --rebuilddb

This was already mentioned elsewhere and also valid for urpmi.

Best regards,
Bequimão

NB: I intended to send this text to the Mageia mailing list, but it didn't work for me.

[sturmvogel]

The procedure how to upgrade from MGA8 to MGA9 is described in the release notes...
https://wiki.mageia.org/en/Mageia_9_Rel ... _.28CLI.29

The procedure how to upgrade to cauldron is described in the wiki:
https://wiki.mageia.org/en/Cauldron#Upg ... _using_DNF

[doktor5000]

One has further to invoke

Code: Select all

# rpmdb --rebuilddb

This was already mentioned elsewhere and also valid for urpmi.

Why did you have to do that in particular?
This should be fixed according to https://bugs.mageia.org/show_bug.cgi?id=29364 and https://bugs.mageia.org/show_bug.cgi?id=31024

[Bequimao]

Why did you have to do that in particular?
This should be fixed according to https://bugs.mageia.org/show_bug.cgi?id=29364 and https://bugs.mageia.org/show_bug.cgi?id=31024

There was a warning everytime when I invoked dnf. Something about converting database to sqlite.
It looks as if only fixed for urpmi.

[doktor5000]

Well, then you should probably report that. I don't see any open bugreport regarding sqlite and dnf, and nothing in errata.
Also check https://wiki.mageia.org/en/Mageia_9_Rel ... _to_SQLite

[morgano]

Thank you for testing
To make your work really help,

1) If valid, it is important to get the database hickup fixed and/or noted in errata/release notes.
I see from https://bugs.mageia.org/show_bug.cgi?id=31024#c9 that for online upgrade urpmi handle it. So in your case DNF should, but maybe it need that upgrade script. Can you test again on your setup, but following the instructions in release notes (using the script) and report back here. If still problems, please make a bug report get it more investigated.


2) did you note if https://bugs.mageia.org/show_bug.cgi?id=28272 is still valid?
if not, we can remove that note from https://wiki.mageia.org/en/Mageia_9_Err ... _using_DNF

[Bequimao]

1) I saw the message as output of # dnf config-manager or # dnf repolist, as I recall. It was marked explicitly as a warning. When I started the next upgrade, I had already converted the rpm database. I think a note in errata would be sufficient.

2) libsolv is indeed the great advantage of dnf. When the situation arises, dnf gives a detailed description, finds a valid subset of packages to upgrade, and gives a hint to a solution.
As an example see https://bugs.mageia.org/show_bug.cgi?id=32057.

I also tested # dnf system-upgrade form Mga 7 to Cauldron before the release of Mga 8. I don't recall to have two kernel flavours installed. I also checked my comments and reports in bugzilla. I will do another test in a VM, which takes less time, but not this week. After the release I always start with a fresh install.

Greetings, Bequimão

NB: I never upgrade with the installer, as I exclusively use dnf.

[morgano]

(using the script)

I used wrong word, I meant plugin;
# dnf install 'dnf-command(system-upgrade)'

[morgano]

https://bugs.mageia.org/show_bug.cgi?id=29364#c8

For DNF users, we already recommend the "system-upgrade" method, which transparently handles this correctly.

Described here.

[Bequimao]

I just finished another test in a VM. The whole transaction was successful, and the package upgrade counter did not stall.

Code: Select all

# dnf install 'dnf-command(system-upgrade)'
Last metadata expiration check: 0:00:34 ago on Wed 26 Jul 2023 11:15:22 AM -03.
Package python3-dnf-plugin-system-upgrade-4.0.13-1.mga8.noarch is already installed.
Dependencies resolved.
Nothing to do.
Complete!

# dnf system-upgrade download --releasever=cauldron --allowerasing


The previous installation of mageia-repos-cauldron is not necessary, as the version no. is not hardcoded in /etc/yum.d/mageia*.repo. You'll find $releasever there. I won't mix the command and options, though it looks, as if the exact order is irrelevant.

@ Sturmvogel: I started my tests based on the dnf documentation from Fedora. The wiki article didn't exist then.

https://bugs.mageia.org/show_bug.cgi?id=28272 does not occur, as there is no crda. You may close the bug as fixed (old). I forgot that this bug report was based on my tests. Seems that I am getting old ...

The database migration is missing, see

Code: Select all

[root@mga8-kde-vm ~]# dnf repolist
warning: Found bdb_ro Packages database while attempting sqlite backend: using bdb_ro backend.
repo id                               repo name
cauldron-updates-x86_64               Mageia Cauldron - x86_64 - Updates
cauldron-x86_64                       Mageia Cauldron - x86_64
mageia-x86_64                         Mageia 9 - x86_64
mageia-x86_64-nonfree                 Mageia 9 - x86_64 - Nonfree
mageia-x86_64-tainted                 Mageia 9 - x86_64 - Tainted
updates-x86_64                        Mageia 9 - x86_64 - Updates
updates-x86_64-nonfree                Mageia 9 - x86_64 - Nonfree - Updates
updates-x86_64-tainted                Mageia 9 - x86_64 - Tainted - Updates

One has to align the repo configuration

Code: Select all

[root@mga8-kde-vm ~]# rpmdb --rebuilddb
warning: Converting database from bdb_ro to sqlite backend
[root@mga8-kde-vm ~]#
[root@mga8-kde-vm ~]# dnf config-manager --set-disabled cauldron-updates-x86_64
[root@mga8-kde-vm ~]# dnf config-manager --set-disabled mageia-x86_64 mageia-x86_64-nonfree mageia-x86_64-tainted
[root@mga8-kde-vm ~]# dnf config-manager --set-disabled updates-x86_64 updates-x86_64-nonfree updates-x86_64-tainted
[root@mga8-kde-vm ~]# dnf config-manager --set-enabled cauldron-x86_64-nonfree cauldron-x86_64-tainted
[root@mga8-kde-vm ~]#
[root@mga8-kde-vm ~]# dnf repolist
repo id                                                           repo name
cauldron-x86_64                                                   Mageia Cauldron - x86_64
cauldron-x86_64-nonfree                                           Mageia Cauldron - x86_64 - Nonfree
cauldron-x86_64-tainted                                           Mageia Cauldron - x86_64 - Tainted


Best regards,
Bequimão

[morgano]

https://bugs.mageia.org/show_bug.cgi?id=28272 does not occur, as there is no crda. You may close the bug as fixed (old)

Thank you

Closed bug as old and removed it from 9 errata.

[Bequimao]

Well, I failed to search for crda. It is a kernel module. Anyway, the issue is solved.