When upgrading via DNF/CLI using instructions from release notes the update fails on transaction test due package cairosvg having package conflict on file /usr/bin/cairosvg. This seems to about difference in package filenames as case sensitivity. Should I solve this by erasing the old package having the issue. How to do that? Component: CairoSVG-2.5.1-1.mga8.noarch conflicts with file from package cairosvg-2.2.1-1.1.mga7.noarch How reproducible: has been there since 20 march 2021 Steps to Reproduce: Follow the instructions on release notes for DNF upgrade. <SNIP> 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 check error: file /usr/bin/cairosvg from install of CairoSVG-2.5.1-1.mga8.noarch conflicts with file from package cairosvg-2.2.1-1.1.mga7.noarch <SNIP>
Thank you for the report. I suspect that removing the M7 package before the upgrade will take out more than you want. If you can live with that (re-install them after the upgrade), you can remove 'cairosvg' with Add/Remove software by UNticking it, then action the operation. But be very careful about what else it wants to remove, and only do it if you are happy with what is proposed, and re-installing them post-upgrade. You get a summary list of packages to be removed to confirm - or abort - before the operation is done, so you can back out easily. This SRPM is committed by different packagers, so assigning this globally. CC'in Aurélien for the upgrade umbrella bug.
Assignee: bugsquad => pkg-bugsCC: (none) => ouaurelienSource RPM: python-cairosvg-2.2.1-1.1.mga7.src.rpm => python-cairosvg-2.2.1-1.1.mga7.src.rpm, python-cairosvg-2.5.1-1.mga8.src.rpmSeverity: normal => majorSummary: DNF/CLI Upgrade from 7 to 8 fails with package CairoSVG => Upgrade from 7 to 8 (DNF/CLI) fails on package M8 CairoSVG conflict with M7 cairosvg
Priority: Normal => HighBlocks: (none) => 28393
Keywords: (none) => IN_ERRATA8CC: (none) => fri
Continuing with the remove the problem idea and after some reading of the DNF manuals I came up with command line: dnf remove --noautoremove cairosvg My knowledge about DNF is limited so I have not tried this. Would this do what is needed? The idea would be to limit number of removed packages. At present I have a useable M7 installation so breaking it is not wanted. Then I would need a line to restart the installation from cached packages.
Should be fixed with python-cairosvg-2.5.1-1.1.mga8 in Core/Updates_testing repo!
CC: (none) => geiger.david68210
Assignee: pkg-bugs => qa-bugs
Advisory: ======================== This update fixes a packaging issue which prevents to upgrade properly from mga7 to mga8 due to some conflicting files. ======================== Packages in 8/core/updates_testing: ======================== cairosvg-2.5.1-1.1.mga8.noarch.rpm python3-cairosvg-2.5.1-1.1.mga8.noarch.rpm Source RPM: ======================== python-cairosvg-2.5.1-1.1.mga8.src.rpm
(In reply to David GEIGER from comment #3) > Should be fixed with python-cairosvg-2.5.1-1.1.mga8 in Core/Updates_testing > repo! Agreed. Tested in Virtualbox M7 to M8 path using CLI method with cairosvg-2.2.1-1.1.mga7.noarch.rpm and python3-cairosvg-2.2.1-1.1.mga7.noarch.rpm installed in M7. No issue. cairosvg-2.5.1-1.1.mga8.noarch.rpm python3-cairosvg-2.5.1-1.1.mga8.noarch.rpm correctly installed. Validating.
Whiteboard: (none) => MGA8-64-OKKeywords: (none) => advisory, validated_updateCC: (none) => sysadmin-bugs
An update for this issue has been pushed to the Mageia Updates repository. https://advisories.mageia.org/MGAA-2021-0065.html
Resolution: (none) => FIXEDStatus: NEW => RESOLVED
Noted in errata.