As reported in bug 22658 comment 11, I'm trying to remove remaining mga5 packages after upgrading from Mageia 5 to 6. Tracked down one package that is causing a cascade of other packages to fail to be removed without removing a lot of mga6 packages. The package libmp3lame0 cannot be installed due to Installation failed: libmp3lame0 is obsoleted by (installed) lib64lame0-3.100-1.mga5.tainted.x86_64
Assignee: bugsquad => lists.jjorge
(In reply to Dave Hodgins from comment #0) > The package libmp3lame0 cannot be installed due to > Installation failed: libmp3lame0 is obsoleted by (installed) > lib64lame0-3.100-1.mga5.tainted.x86_64 I wonder why you have both libmp3lame0 and lib64mp3lame0 ?
I don't. [root@x3 ~]# rpm -qa|grep lame|sort gstreamer0.10-lame-0.10.19-18.1.mga6.tainted gstreamer0.10-twolame-0.10.19-18.1.mga6.tainted gstreamer1.0-lame-1.10.3-2.mga6.tainted gstreamer1.0-twolame-1.10.3-2.mga6.tainted lame-3.100-1.mga6 lib64lame0-3.100-1.mga5.tainted lib64twolame0-0.3.13-7.mga6 libquicktime-lame-1.2.4-21.mga6.tainted twolame-0.3.13-7.mga6 vlc-plugin-twolame-3.0.0-1.mga6.tainted Looking at this more ... [root@x3 ~]# urpmq --not-available|grep lame0 lib64lame0-3.100-1.mga5.tainted.x86_64 [root@x3 ~]# urpmq -y lame0|sort lib64mp3lame0 lib64twolame0 libmp3lame0 libtwolame0 The problem appears to be that the package was renamed from lib64lame0 to lib64mp3lame0, but that isn't being recognized as it's replacement by urpmi.
Ok, I think this is because both packages have the same version. The commit was done by wally, ccing him. http://svnweb.mageia.org/packages?view=revision&revision=1074205 As it only prevents cleaning, I think it does not deserves an update. The workaround is : rpm --nodeps -e lib64lame0-3.100-1.mga5.tainted.x86_64 urpmi lib64mp3lame0
Status: NEW => RESOLVEDCC: (none) => jani.valimaaResolution: (none) => WONTFIX
While it's easy to workaround, I think this should be fixed. If I'm reading the guidelines correctly, https://wiki.mageia.org/en/Packaging_guidelines#Obsoleting_a_package when a package's name changes the correct procedure is to add a versioned obsoletes for the old package. While the impact is minimal, it affects all users who upgraded from Mageia 5 who had the package installed. As we are planning on building/releasing Mageia 6.1 it would be good to get this fixed soon. It may have more of an impact later when systems are being upgraded from Mageia 6 to 7.
Resolution: WONTFIX => (none)Status: RESOLVED => REOPENED
The problem is that mga6's lame obsoletes only lame < 3.99.5-12 and it was updated to 3.100-1 in mga5. We could remove versioned obsoletes from mga6 pkg so we don't need to update obsoletes every time we update lame in mga5.
Pushed lame-3.100-1.1.mga6 with unversioned obsoletes to core/updates_testing for mga6. Please test.
Pushed lame-3.100-1.2.mga6 to remove references to tainted media from descriptions.
Confirmed the lib64lame0-3.100-1.mga5.tainted was replaced by the lib64mp3lame0-3.100-1.2.mga6.x86_64.rpm update. Advisory committed to svn. Validating the update.
Whiteboard: (none) => MGA6-64-OKKeywords: (none) => advisory, validated_updateCC: (none) => sysadmin-bugs
Assignee: lists.jjorge => qa-bugs
Just fyi, this problem was preventing the removal of 260 mga5 packages from my system. With this fixed, I've now been able to remove all remaining mga5 packages from this system, so while it was a minor bug, the impact it had via urpmi cascading dependencies was major.
An update for this issue has been pushed to the Mageia Updates repository. https://advisories.mageia.org/MGAA-2018-0052.html
Resolution: (none) => FIXEDStatus: REOPENED => RESOLVED