Users: Upgrading from one version of OM Lx to another is not what is meant by a system upgrade. A system upgrade is upgrading packages within a given version such as OM Lx 4.2. If you are upgrading from OM Lx 4.1 to 4.2 or from OM Lx 4.2 to Rolling that is a distribution upgrade. Very different and requires specific commands, options, ect. That is or will be covered elsewhere.
Doing system upgrades should be done at a minimum monthly but we recommend weekly.
If you are going to report a problem with or following a system upgrade (or distro-sync) please include the following information:
What version of OM Lx? Current versions are Cooker(developer), Rolling(advanced user), and Lx 4.2(stable).
How were you upgrading? Command line in Konsole(terminal)? Discover? dgfdragora?
What packages were in your upgrade? Very important.
Post the entire error message.
If upgrading from command line did you run
dnf clean all ; sudo dnf clean allfirst? Very important to do this.
OpenMandriva recommends that for users to avoid problems with upgrades that you do so from command line in Konsole(terminal). Only Lx 4.2 users should ever use Discover and dnfdragra but we do not recommend this. Why? Because the vast majority of forum or IRC posts about upgrading system include “with Discover” or “with dnfdragora”. Both are difficult to keep working properly and we are a small all part time, volunteer group. No paid employees to help you.
To upgrade from command line with an easy to copy and post from log in your home directory called
First run this command:
$ dnf clean all ; sudo dnf clean all
Then for system upgrade:
$ sudo dnf upgrade | tee /home/your_user_name/upgrade.log
Or if you use distro-sync:
$ sudo dnf distro-sync | tee /home/your_user_name/upgrade.log
Where you replace
your_user_name with your actual user name.
Note: This command will overwrite the file
upgrade.log in your home directory every time you run the command. Normally you only need to keep a log of the most recent upgrade until you are sure there are no problems. However you may want to give the file a unique name every time so you save all the logs. Like update.log, update1.log, update2.log, ect. Perhaps save them for a month or two not forever.
Note: There is a /var/log/dnf.log kept so information about all dnf transactions is available if needed. This log is difficult for users to follow hence the recommended command to create the simple file