Bug 15053 - rpmdrake shows wrong number of ongoing operations when uninstalling packages
Summary: rpmdrake shows wrong number of ongoing operations when uninstalling packages
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2015-01-16 05:35 CET by Pavel Kreuzt
Modified: 2016-01-04 03:49 CET (History)
3 users (show)

See Also:
Source RPM: rpmdrake-6.13-1.mga5.src.rpm
CVE:
Status comment:


Attachments

Description Pavel Kreuzt 2015-01-16 05:35:50 CET
Description of problem: When doing multiple operations of installing / uninstalling packages it is expected the ongoing operations windows to show messages following the scheme "installing package X (Y/Z)" but the last number (Z) seems to refer only to packages to uninstall. When doing only install or only uninstall it works correctly.


Version-Release number of selected component (if applicable): 6.13-1


How reproducible: Open rpmdrake and select some changes to do, including packages to uninstall. Hit "apply" and see the popup window messages.


Reproducible: 

Steps to Reproduce:
claire robinson 2015-01-16 11:10:37 CET

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

Comment 1 Angelo Naselli 2015-01-16 12:09:23 CET
there is no information about the number of packages into the popup dialog after apply is pressed. Are you meaning also that you performed the installation?
Comment 2 Angelo Naselli 2015-01-16 13:58:50 CET
hmm code in cauldron has changed, i have to make the test in cauldron first. Sorry for the noise
I wonder if rpmdragora has the same side effect with the old code...
Comment 3 Samuel Verschelde 2015-05-31 22:27:30 CEST
Is this bug still present in Mageia 5 / cauldron?

Keywords: (none) => NEEDINFO

Comment 4 Nic Baxter 2016-01-04 03:49:38 CET
Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution.

Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information.

Closing as OLD.

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


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