Rome Update - Transaction Test Error

Support
1

Hello,

Requirements:

I have Searched the forum for my issue and found nothing related or helpful
I have checked the Resources category (Resources Index)
I have reviewed the Wiki for relevant information
I have read the the Release Notes and Errata

OpenMandriva Lx version:

Rome 25.06

Desktop environment (KDE, LXQT…)

KDE Plasma 6.3.4

Description of the issue (screenshots if relevant):

Message after running:
sudo dnf clean all ; sudo dnf --allowerasing distro-sync

Running transaction check
Transaction check succeeded.
Running transaction test
The downloaded packages were saved in cache until the next successful transaction.
You can remove cached packages by executing ‘dnf clean packages’.
Error: Transaction test error:
file /usr/lib64/liblxc.so.1 from install of lib64lxc-6.0.4-3.znver1 conflicts with file from package lib64lxc1-1:4.0.6-2.znver1

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

Operating System: OpenMandriva ROME 25.06
KDE Plasma Version: 6.3.4
KDE Frameworks Version: 6.13.0
Qt Version: 6.9.0
Kernel Version: 6.14.2-desktop-3omv2590 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 5700G with Radeon Graphics
Memory: 125.1 GiB of RAM
Graphics Processor: AMD Radeon Graphics
Manufacturer: ASUS

Updated today.

Have not encountered any problems yet, was interested in resolving issue(s).

Thanks for your help.

Mike

2

Not sure, but this command is incomplete:

sudo dnf clean all ; sudo dnf repolist ; sudo dnf dsync –refresh –allowerasing 2>&1 | tee dsync-log.txt

You can then attach the log to this topic.

3

I copied and pasted this CL string directly from your note.

Result:

Total 2.8 MB/s | 2.9 GB 17:33
Running transaction check
Transaction check succeeded.
Running transaction test
The downloaded packages were saved in cache until the next successful transaction.
You can remove cached packages by executing ‘dnf clean packages’.
Error: Transaction test error:
file /usr/lib64/liblxc.so.1 from install of lib64lxc-6.0.4-3.znver1 conflicts with file from package lib64lxc1-1:4.0.6-2.znver1

[michael@AsusX570CreatorWiFi ~]$

[michael@AsusX570CreatorWiFi ~]$ sudo dnf clean all ; sudo dnf repolist ; sudo dnf dsync –refresh –allowerasing 2>&1 | tee dsync-log.txt
[sudo] password for michael:
1814 files removed
repo id repo name
rolling-znver1 OpenMandriva Rolling - znver1
rolling-znver1-extra OpenMandriva Rolling - Extra - znver1
rolling-znver1-non-free OpenMandriva Rolling - Non-free - znver1
rolling-znver1-restricted OpenMandriva Rolling - Restricted - znver1
OpenMandriva Rolling - znver1 2.5 MB/s | 5.8 MB 00:02
OpenMandriva Rolling - Extra - znver1 932 kB/s | 1.5 MB 00:01
OpenMandriva Rolling - Restricted - znver1 40 kB/s | 36 kB 00:00
OpenMandriva Rolling - Non-free - znver1 35 kB/s | 31 kB 00:00
No match for argument: –refresh
No match for argument: –allowerasing
Error: No packages marked for distribution synchronization.
[michael@AsusX570CreatorWiFi ~]$

4

It should be –-refresh and –-allowerasing. This “rich text” editor screwed up @zeroability’s post, as it almost screwed up mine (I had to go back and add the extra dash).

1 Like
5

That’s what I expected.
Thanks for the note of confirmation.

6

Now I get:

[michael@AsusX570CreatorWiFi ~]$ sudo dnf clean all ; sudo dnf repolist ; sudo dnf dsync –-refresh -–allowerasing 2>&1 | tee dsync-log.txt
[sudo] password for michael:
0 files removed
repo id repo name
rolling-znver1 OpenMandriva Rolling - znver1
rolling-znver1-extra OpenMandriva Rolling - Extra - znver1
rolling-znver1-non-free OpenMandriva Rolling - Non-free - znver1
rolling-znver1-restricted OpenMandriva Rolling - Restricted - znver1
usage: dnf distro-sync [-c [config file]] [-q] [-v] [–version]
[–installroot [path]] [–nodocs] [–noplugins]
[–enableplugin [plugin]] [–disableplugin [plugin]]
[–releasever RELEASEVER] [–setopt SETOPTS]
[–skip-broken] [-h] [–allowerasing] [-b | --nobest]
[-C] [-R [minutes]] [-d [debug level]] [–debugsolver]
[–showduplicates] [-e ERRORLEVEL] [–obsoletes]
[–rpmverbosity [debug level name]] [-y] [–assumeno]
[–enablerepo [repo]] [–disablerepo [repo] | --repo
[repo]] [–enable | --disable] [-x [package]]
[–disableexcludes [repo]] [–repofrompath [repo,path]]
[–noautoremove] [–nogpgcheck] [–color COLOR]
[–refresh] [-4] [-6] [–destdir DESTDIR]
[–downloadonly] [–comment COMMENT] [–bugfix]
[–enhancement] [–newpackage] [–security]
[–advisory ADVISORY] [–bz BUGZILLA] [–cve CVES]
[–sec-severity {Critical,Important,Moderate,Low}]
[–forcearch ARCH]
[package …]
dnf distro-sync: error: unrecognized arguments: -–allowerasing
[michael@AsusX570CreatorWiFi ~]$

7

When I run that command, I also get the error. Perhaps it has been removed from dnf. For now, I would say remove the -–allowerasing option.

8

Remove the --refresh option from the dsync parameter as it is not a defined parameter for distro-sync in dnf5 - which should be refreshing/checking for updated repo/package data when it runs by definition:

The distro-sync command in DNF5 serves to synchronize the installed packages with their latest available version from any enabled repository.

Distro-Sync Command — dnf5 documentation

With dnf4 I dont recall dnf being as strict and would run regardless by accepting parameters it uses and ignoring those it did not use with no feedback about it either way, I guess that behaviour changed.

With DNF5 this should be all that is required:
sudo dnf clean all ; sudo dnf repolist ; sudo dnf dsync -–allowerasing

9

Don’t use unnecessary commands. This will work and do everything the command above is trying to do.

$ sudo dnf clean all ; sudo dnf dsync --allowerasing
Removed 12 files, 8 directories (total of 23 MiB). 0 errors occurred.
Updating and loading repositories:
 OpenMandriva Rolling - Restricted - znver1                                                                                                          100% |  20.6 KiB/s |  38.7 KiB |  00m02s
 OpenMandriva Rolling - Extra - znver1                                                                                                               100% | 658.6 KiB/s |   1.5 MiB |  00m02s
 OpenMandriva Rolling - znver1                                                                                                                       100% |   2.3 MiB/s |   5.8 MiB |  00m03s
 brave                                                                                                                                               100% |  26.4 KiB/s |  54.9 KiB |  00m02s
Repositories loaded.
Nothing to do.

Explanation: The first command is sudo dnf clean all this makes command sudo dnf repolist and option --refresh redundant. sudo dnf repolist is not an action command it is a list command. Since you have already run sudo dnf clean all the repos will be listed when you run sudo dnf dsync --allowerasing. So sudo dnf repolist is a redundant command in this string.

Since you have already run sudo dnf clean all the sudo dnf dsync --allowerasing command has to refresh repository metadata so --refresh is also redundant.

Welcome to DNF5’s documentation!

This will work as a stand alone command and makes logical sense.

$ sudo dnf dsync --allowerasing --refresh
[sudo] password for ben79: 
Updating and loading repositories:
 OpenMandriva Rolling - Restricted - znver1                                                                                                          100% |   2.1 KiB/s |   2.4 KiB |  00m01s
 OpenMandriva Rolling - Extra - znver1                                                                                                               100% |   2.1 KiB/s |   2.4 KiB |  00m01s
 OpenMandriva Rolling - znver1                                                                                                                       100% |   2.1 KiB/s |   2.4 KiB |  00m01s
 brave                                                                                                                                               100% |   5.0 KiB/s |   2.0 KiB |  00m00s
Repositories loaded.
Nothing to do.

You are funning the command sudo dnf dsync with the option --allowerasing:

–allowerasing
Allow removing of installed packages to resolve any potential dependency problems.

and the option --refresh:

This updates your package list and checks for the latest versions.

It’s not just for prep, it also fixes many small issues, like boot problems or missing security updates. Always run it before major upgrades.

The explanation for --refresh came from here:

DNF5 Commands Examples For Managing Packages In Linux

10

This might work:

sudo rpm -e --nodeps lib64lxc1
sudo dnf in lib64lxc

That is not something that would be installed by default. Unless you know you need it you might try:

sudo rpm -e --nodeps lib64lxc1
sudo dnf clean all ; sudo dnf dsync --allowerasing 2>&1 | tee dsync.log.txt

and see if the package is really needed. You can always install it later. The purpose of that particular dsync command is to create the log dsync.log.txt, use that log, post it here if there is any problem along with the exact command you used.

Also do this when there is code in your forum posts:

[Forum] How to post code as code

11

Ben:

I copied and pasted the second option you posted (under “Unless you know you need it you might try:”) and ran the update:

sudo rpm -e --nodeps lib64lxc1
sudo dnf clean all ; sudo dnf dsync --allowerasing 2>&1 | tee dsync.log.txt

When I returned, the screen was dark and no response to keyboard or mouse.
I powered down the system and restarted. and it will not reboot to the GUI, only boots to CLI and asks for sign on and password, which will get me to a command line.

What do you recommend to restore the system to its previous state?

Mike

12

Probably this:

Upgrading ROME(rolling) after Nov. 9, 2025 upgrade

13

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.