Bug 3215 - Missing information when you have to decide between packages during updating
Summary: Missing information when you have to decide between packages during updating
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal enhancement
Target Milestone: ---
Assignee: Thierry Vignaud
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-29 12:29 CEST by Wolfgang Bornath
Modified: 2022-03-16 16:29 CET (History)
5 users (show)

See Also:
Source RPM: rpmdrake
CVE:
Status comment:


Attachments

Description Wolfgang Bornath 2011-10-29 12:29:59 CEST
Description of problem:

Quite often during updates (GUI and urpmi) you are asked to select one of several versions of a package. Example as of today:
-----------------
1) lib64edata-cal%[edatacalmajor}-3.3.1.1-1mga2.x86_64

2) lib64edata-cal14-3.3.1.1-2.mga2.x86_64
-----------------

The GUI provides a button "Information" but there is nothing available. Of course you can open rpmdrake to see a description of the package but most times the descriptions of the packages in question are identical (see description of the example packages).

Question:
How could a user make a decision like that when he does not get anything to build this decision on? 

What is needed is 
 - either a more detailed description which shows the difference or 
 - one button which leads to a description of the difference or
 - something in the description like "If you are unsure use (1)"

This problem has been biting me for quite some time because it was present in Mandriva and is present in Mageia 1 as well.

Hopefully I used the correct component (the bug does not match any of the given components)
Manuel Hiebel 2011-10-31 11:06:56 CET

Assignee: bugsquad => thierry.vignaud
Source RPM: (none) => urpmi

Thierry Vignaud 2011-11-22 13:53:44 CET

Source RPM: urpmi => rpmdrake

Comment 1 Jeff Johnson 2012-01-07 18:52:34 CET
tracked at https://bugs.launchpad.net/rpm/+bug/913199

CC: (none) => n3npq

Comment 2 Russ Herrold 2012-01-08 18:06:11 CET
the issue hereis a build system error ...%[edatacalmajor} ... was undefined, was it not?

CC: (none) => herrold

Comment 3 Wolfgang Bornath 2012-01-08 18:20:59 CET
I don't think so because this issue has been around for years in Mandrake, Mandriva and now Mageia. Of course I don't know about the technical background, so it could be that all of them had/have the same error :)

CC: (none) => molch.b

Comment 4 Jeff Johnson 2012-01-08 18:55:44 CET
(aside)
The reason for the tracking != the original problem.
There's a need to map more information into synthesis/hdlists
used by URPMI related to "How could a user ..." question
Comment 5 Marja Van Waes 2012-05-26 13:08:58 CEST
Hi,

This bug was filed against cauldron, but we do not have cauldron at the moment.

Please report whether this bug is still valid for Mageia 2.

Thanks :)

Cheers,
marja

Keywords: (none) => NEEDINFO

Manuel Hiebel 2012-06-12 21:26:18 CEST

Keywords: NEEDINFO => (none)

Thierry Vignaud 2012-09-07 17:07:54 CEST

Summary: MIssing information when you have to decide between packages during updating => Missing information when you have to decide between packages during updating

Comment 6 Lewis Smith 2019-04-06 13:41:13 CEST
This bug is very old (2011) & very long neglected (2012).
The point is valid, and I think applies for package installation as well. I am always baffled by the choice offered, and half suspect that bare <Enter> takes the first one. Given this detail: "Of course you can open rpmdrake to see a description of the package but most times the descriptions of the packages in question are identical", it is difficult to suggest what more we can do - it defies easy description.
Can we close this as 'old'?

CC: (none) => lewyssmith, thierry.vignaud

Comment 7 sturmvogel 2022-03-16 16:29:02 CET
No reactions since 3 years after Lewis called for it. 

Closing OLD. Feel free to reopen if necessary.

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


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