Bug 468418

Summary:	Inconsistent numbering when doing reinstalls
Product:	[Fedora] Fedora	Reporter:	Bruno Wolff III <bruno>
Component:	rpm	Assignee:	Panu Matilainen <pmatilai>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	low	Docs Contact:
Priority:	medium
Version:	10	CC:	ffesti, james.antill, jnovy, pmatilai, tim.lauridsen
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2009-11-18 13:54:03 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Bruno Wolff III 2008-10-24 17:04:35 UTC

Description of problem:
When doing a reinstall the same number is displayed for both the erase and install of each package, where as the total displayed counts them separately.
So if you reinstall say two packages, the numbers would go 1 1 2 2, but the total displayed on each line would be 4. It would be nice if either the numbers went up 1 2 3 4 or if the total was shown as 2. I don't have a preference either way, but the current way seems wrong.

Version-Release number of selected component (if applicable):
yum-3.2.19-6.fc10.noarch

How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 seth vidal 2008-10-24 18:05:36 UTC

Sort of rpm and sort of yum. We need more callback info to get the numbering right.

Once we have that then we'll probably need to fix things in yum, too.

Comment 2 Bug Zapper 2008-11-26 04:12:09 UTC

This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle.
Changing version to '10'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 3 Bug Zapper 2009-11-18 09:19:27 UTC

This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '10'.

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 Fedora version prior to Fedora 10'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 Fedora 10 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 Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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 Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 4 James Antill 2009-11-18 13:54:03 UTC

This should be fixed in 3.2.24, which is in F10 (as this is really a weird dup of 512393).