After running an upgrade (using mgaapplet), eom-1.8.1-2.1.mga5 is still installed in the upgraded system. eom-1.18.2-1.mga6 is available in the repository, but does not get selected when running 'urpmi --auto-select'. However, if you then manually install eom-1.18.2-1.mga6, eom-1.8.1-2.1.mga5 gets removed, so the obsoletes are working. eom-1.8.1-2.1.mga5 provides mate-image-viewer[== 1.8.1-2.1.mga5], but eom-1.18.2-1.mga6 provides mate-image-viewer[== 0:1.18.2-1.mga6]. Is the leading '0:' the cause of the problem?
(In reply to Martin Whitaker from comment #0) > After running an upgrade (using mgaapplet), eom-1.8.1-2.1.mga5 is still > installed in the upgraded system. eom-1.18.2-1.mga6 is available in the > repository, but does not get selected when running 'urpmi --auto-select'. > However, if you then manually install eom-1.18.2-1.mga6, eom-1.8.1-2.1.mga5 > gets removed, so the obsoletes are working. > > eom-1.8.1-2.1.mga5 provides mate-image-viewer[== 1.8.1-2.1.mga5], but > eom-1.18.2-1.mga6 provides mate-image-viewer[== 0:1.18.2-1.mga6]. Is the > leading '0:' the cause of the problem? Assigning to the registered eom maintainer.
Assignee: bugsquad => tarakbumbaCC: (none) => marja11
No, the 0 would only be a problem if it was on the mga5 package. This one is myserious.
Reassigning to all packagers collectively as the original maintainer is not available anymore (thanks for all your work Atilla!).
Assignee: tarakbumba => pkg-bugs
Both mga5 and mga6 are EOL.
Resolution: (none) => OLDStatus: NEW => RESOLVED