Upgrade Rock/5.0 to Rock/6.0 (April 23, 2025)

Support
,
1

Hello, Rock repository symlink has been changed from 5.0 to 6.0. This explains how to do the system upgrade. We are performing some final tests on this and will notify here when that testing is complete.

  • OpenMandriva Lx version:

Rock

  • Desktop environment (KDE, LXQT…):

Only tested on Plasma5, this should work on LXQt also. We will be testing that soon.

  • Description of the issue (screenshots if relevant):

The Rock repository symlink has been changed from 5.0 to 6.0.

  • Relevant information (hardware involved, software version, logs or output…):

This is how to upgrade (dnf dsync) a Rock/5.0 system to Rock/6.0

A fresh install is better than a complete distribution upgrade. If you do not know how to transfer your needed data from your old system to a new one start learning now. It is not rocket science, but it can take some time. If you have this figured out and keep a periodically updated backup of your important data you will never get caught flat footed if things go wrong. Protect yourself and your data from digital gremlins. Transferring desktop configuration files from one Linux distribution to OMLx can lead to problems. Might work, might not, might cause user a lot of grief.

While you can upgrade your 5.0 system it is strongly with prejudice recommended that you do a fresh install. If you use Plasma desktop install Plasma6 NOT Plasma5. OM developers are racing to get to the point where they can remove Plasma5 from our repositories. Plasma5 packages will remain in Rock repositories until the next major release.

The basic 5.0 to 6.0 procedure:

sudo dnf remove falkon-kde hfsutils pyside2-core

sudo dnf dsync --allowerasing | tee dsync.log.txt

This is very important: At the end of the dsync transaction watch out for these rpm file dialogs:

Screenshot_20250423_112548
Screenshot_20250423_1125482050×1280 277 KB

Select to keep your current version for Configuration file '/etc/sane.d/dll.conf' and Configuration file '/etc/shadow' and select y for the the new or package maintainers version for `Configuration file ‘/etc/yum.repos.d/openmandriva-rock-x86_64.repo’.

sudo dnf autoremove | tee autoremove.log.txt

sudo dnf clean all

reboot

Note: The file /etc/shadow has your password and user information. If you select the new or package maintainers version you will have a blank file with no users and no root password. Don’t do that.

Note: The command sudo dnf dsync --allowerasing | tee dsync.log.txt creates the log dsync.log.txt in case there may be some problem. Likewise the command sudo dnf autoremove | tee autoremove.log.txt creates the log autoremove.log.txt.

Note: Pay attention to any packages that might be removed by the option --allowerasing or the command autoremove. If you see something that the dnf transaction would remove reinstall that package after this process is complete OR ask before proceeding. This is unlikely to happen with --allowerasing but does occasionally happen with autoremove.

1 Like
2

A genue question. Does fresh installation mean nuking all partition like (create new partition table) on drive and fresh start? Or nuking / and add old /home to the installation with some extra steps like

rm -rf ~/.config/KDE*
rm -rf ~/.config/kdeglobals ~/.config/kcheckpass ~/.config/kdesktoprc ~/.config/kinputcontext ~/.config/kmailrc ~/.config/kreadconfig ~/.config/ksmserverrc ~/.config/kwriteconfig
rm -rf ~/.config/kde* && kdeinit5

Also which ISO is safe to use.
https://abf.openmandriva.org/product_build_lists
Safe like in - not buggy, not strange behaving after install. Not like safe in - not dangerous or not malicious.

About 72h ago I use this iso as my install media OpenMandrivaLx.6.0-snapshot.20250420.3876-plasma6x11.x86_64.iso

It is not that my pc blows up or walk to the nearest pub to have beer. No, no. Everything kinda works for the most part. I just had a cascade of little stupid problems, those little buggers nagging me to the point I want to scream. So no,it didn’t go for a drink, it does not blow up in my face.
It just becomes cynical. And … I would like to avoid that :wink:

4

A fresh install refers to formatting / or root partition and doing a fresh install on that. It is OK to reuse a /home partition IF it is similar. So if the /home was for a Plasma6 system and you are installing Plasma6 that is OK. Not a good idea to use a /home from some other Linux distro for OMLx systems, that can lead to problems.

The iso you are talking about was rejected in testing. When you are using stuff that is in testing you should expect problems that is why it is still in testing. Edit: Also simply upgrading the #3876 iso with sudo dnf --refresh dsync should bring it up to date with the released isos.

Download one of the published to the public isos here or at SourceForge here.

Edit: If someone specifies any system partitions beyond / such as /boot/ or /usr of course those should be reformatted. One exception is /boot/efi you can use one
/boot/efi for multiple systems, it is designed to be used that way.

5

Please let us keep this thread focused on problems with upgrading Rock/5.0 to 6.0. Problems with an installed system or specific problems after the upgrade is complete should get their own thread. One problem per thread with a descriptive title and enough information so someone trying to help has something to work on.