Bug 10020 - urpmi and rpmdrake should prefer same (newest?) version of dependancy packages
Summary: urpmi and rpmdrake should prefer same (newest?) version of dependancy packages
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 3
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Thierry Vignaud
QA Contact:
URL:
Whiteboard:
Keywords: Triaged
Depends on:
Blocks:
 
Reported: 2013-05-08 10:31 CEST by Morgan Leijström
Modified: 2015-03-31 16:05 CEST (History)
0 users

See Also:
Source RPM: rpmdrake-5.48-1.mga3.src.rpm
CVE:
Status comment:


Attachments

Description Morgan Leijström 2013-05-08 10:31:55 CEST
Description of problem: 
  If more version of dependancy package is available,
urpmi --auto will install newest, and
drakrpm defaults to eldest version.

Version-Release number of selected component: current mga3;
rpmdrake-5.48-1.mga3.src.rpm
urpmi-7.26-1.mga3.src.rpm


How reproducible: when alternative package versions are available


Steps to Reproduce:
1) In terminal # urpmi yaflight, it asks for package alternatives in this:
 1- lib64pq9.2_5-9.2.4-1.mga3.x86_64
 2- lib64pq9.1_5-9.1.9-1.mga3.x86_64
 3- lib64pq9.0_5-9.0.13-1.mga3.x86_64
 4- lib64pq8.4_5-8.4.17-1.mga3.x86_64
and if urpmi is run with --auto (--test) it choose the newest (9.2.5)

2) Run rpmdrake, intend to install yaflight, and it asks same question, but order them backwards, and preselect the *eldest* version.

Reproducible: 

Steps to Reproduce:
Comment 1 Manuel Hiebel 2013-05-11 22:53:55 CEST
indeed

Keywords: (none) => Triaged
Version: Cauldron => 3
Assignee: bugsquad => thierry.vignaud

Comment 2 Marja Van Waes 2015-03-31 16:05:34 CEST
Mageia 3 changed to end-of-life (EOL) status 4 months ago.
http://blog.mageia.org/en/2014/11/26/lets-say-goodbye-to-mageia-3/ 

Mageia 3 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
The Mageia Bugsquad

Status: NEW => RESOLVED
Resolution: (none) => OLD


Note You need to log in before you can comment on or make changes to this bug.