Bug 2376 - Two lib64jpeg packages in main and contrib can lead to confusion
: Two lib64jpeg packages in main and contrib can lead to confusion
Status: RESOLVED FIXED
Product: Desktop Bugs
Classification: ROSA Desktop
Component: Main Packages
: Fresh
: All Linux
: Normal normal
: ---
Assigned To: ROSA Linux Bugs
: ROSA Linux Bugs
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-07-25 12:33 MSD by Denis Silakov
Modified: 2013-07-25 13:56 MSD (History)
0 users

See Also:
RPM Package:
ISO-related:
Bad POT generating:
Upstream:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Denis Silakov 2013-07-25 12:33:07 MSD
The following issue has been discovered when working on bug #2366.
We have two packages with lib64jpeg62 name:

 main/release/lib64jpeg62-1.2.1-1-rosa2012.1.x86_64.rpm
 contrib/release/lib64jpeg62-6b-47-rosa2012.1.x86_64.rpm

and two devel package for them, but these packages have different names - lib64jpeg-devel and lib64jpeg62-devel.

lib64jpeg62-1.2.1 has Epoch==1 so it is considered to be newer by urpmi. And with the new behavior, urpmi refuses to install older lib64jpeg62-6b-47 since newer lib64jpeg62-1.2.1 is available in repositories.

Ideally, urpmi should also refuse to install older devel package; but devel packages have different names, so urpmi doesn't even compare them. If launched without '--auto', "urpmi 'devel(libjpeg(64bit))' asks user which package to choose - lib64jpeg-devel-1.2.1-1 or lib64jpeg62-devel-6b-47. However, the second package cannpt be installed since it depends on older libjpeg.

Maybe we should improve urpmi to handle such cases somehow, or maybe we should fix packages in repositories.
Comment 1 Denis Silakov 2013-07-25 13:56:19 MSD
Conflict with package from the main repository should be resolved now - package from contrib doesn't provide 'devel(libjpeg)' anymore, so there should be no cases when user can choose it through dependencies.