Bug 1754

Summary:	urpmq --requires-recursive doesn't show everything that would be installed
Product:	Mageia	Reporter:	AL13N <alien>
Component:	RPM Packages	Assignee:	Thierry Vignaud <thierry.vignaud>
Status:	RESOLVED OLD	QA Contact:
Severity:	normal
Priority:	Normal	CC:	davidwhodgins, marja11, n3npq, nic
Version:	Cauldron	Keywords:	NEEDINFO
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:	urpmi	CVE:
Status comment:

Description AL13N 2011-06-11 22:52:29 CEST

it seems that urpmq --requires-recursive doesn't always give a complete picture of what would be installed if you'd urpmi something. this one seems to be because it can't seem to follow a "choice" completely.

imho urpmq should follow what --auto would do for urpmi since it would make results of urpmq more in line to what urpmi would do. (which is imho what you're using this for.)

as you can see from below example, bootsplash is apparenlty not required for task-kde4-minimal, but it is, if you follow the choices.

(since kernel is required for bootsplash, it follows that task-kde4-minimal actually requires kernel, even though you can't see that with --requires-recursive; which in my chrooted environment is not what i wanted...)

reproducing steps:
(prepare clean chroot for testing)
[ ]# mkdir /chroot
[ ]# urpmi.addmedia --urpmi-root /chroot --distrib --mirrorlist '$MIRRORLIST'
[ ]# urpmi --no-suggests --urpmi-root /chroot basesystem-minimal locales-en urpmi

(testing)
[ ]# urpmq --urpmi-root /chroot --no-suggests --requires-recursive task-kde4-minimal | grep kde4-config
netbook-kde4-config|Default-kde4-config
[ ]# urpmq --urpmi-root /chroot --no-suggests --requires-recursive Default-kde4-config | grep bootsplash
bootsplash
[ ]# urpmq --urpmi-root /chroot --no-suggests --requires-recursive netbook-kde4-config | grep bootsplash
bootsplash
[ ]# urpmq --urpmi-root /chroot --no-suggests --requires-recursive task-kde4-minimal | grep bootsplash
[ ]#

Comment 1 claire robinson 2011-10-06 16:28:47 CEST

This bug will affect QA dependency checking script/process too which could lead to false positives being asked to be linked from release media to updates unnecessarily for bug 2317, or worse - false negatives leading to failed upgrades from mandriva or not being able to select updates in mageia if any are missed.

Manuel Hiebel 2011-10-06 16:33:57 CEST

Assignee: bugsquad => thierry.vignaud

Dave Hodgins 2011-10-09 08:55:08 CEST

CC: (none) => davidwhodgins

Comment 2 AL13N 2011-10-17 12:43:33 CEST

bumping and putting in higher priority, i guess there is no maintainer for this?

Priority: Normal => High

Thierry Vignaud 2011-10-17 18:49:13 CEST

Priority: High => Normal

Comment 3 Jeff Johnson 2012-01-07 19:50:06 CET

tracked at https://bugs.launchpad.net/rpm/+bug/913224

CC: (none) => n3npq

Comment 4 Marja Van Waes 2012-04-21 20:50:46 CEST

3 monthly ping

CC: (none) => marja11

Comment 5 Marja Van Waes 2012-07-06 15:04:08 CEST

Please look at the bottom of this mail to see whether you're the assignee of this  bug, if you don't already know whether you are.


If you're the assignee:

We'd like to know for sure whether this bug was assigned correctly. Please change status to ASSIGNED if it is, or put OK on the whiteboard instead.

If you don't have a clue and don't see a way to find out, then please put NEEDHELP on the whiteboard.

Please assign back to Bug Squad or to the correct person to solve this bug if we were wrong to assign it to you, and explain why.

Thanks :)

**************************** 

@ the reporter and persons in the cc of this bug:

If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us.

@ the reporter of this bug

If you didn't reply yet to a request for more information, please do so within two weeks from now.

Thanks all :-D

Comment 6 AL13N 2012-07-06 19:59:47 CEST

it seems to me that the choices are just being ignored... perhaps it should ask which one, and allow --auto as well to not ask.

Comment 7 Manuel Hiebel 2012-11-05 16:51:50 CET

This message is a reminder that Mageia 1 is nearing its end of life. 
In approximately 25 days from now, Mageia will stop maintaining and issuing 
updates for Mageia 1. At that time this bug will be closed as WONTFIX (EOL) if it 
remains open with a Mageia 'version' of '1'.

Package Maintainer: If you wish for this bug to remain open because you plan to 
fix it in a currently maintained version, simply change the 'version' to a later 
Mageia version prior to Mageia 1's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not 
be able to fix it before Mageia 1 is end of life.  If you would still like to see 
this bug fixed and are able to reproduce it against a later version of Mageia, 
you are encouraged to click on "Version" and change it against that version 
of Mageia.

Although we aim to fix as many bugs as possible during every release's lifetime, 
sometimes those efforts are overtaken by events. Often a more recent Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

--
Mageia Bugsquad

AL13N 2012-11-05 20:10:18 CET

Version: 1 => Cauldron

Comment 8 Thierry Vignaud 2013-03-25 22:01:22 CET

works for me as of perl-URPM-4.27 + urpmi-7.23

Keywords: (none) => NEEDINFO

Comment 9 Nic Baxter 2015-03-31 02:13:42 CEST

No comments for ever. Obviously there is no need to keep open. Housekeeping wins.

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