Bug 140160 - up2date-4.3.53-1 doesn't update current package progress bar
Summary: up2date-4.3.53-1 doesn't update current package progress bar
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: up2date
Version: 4.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: Pradeep Kilambi
QA Contact: Ken Reilly
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-11-20 13:10 UTC by Bernd Bartmann
Modified: 2013-02-27 00:49 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-20 15:54:45 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Bernd Bartmann 2004-11-20 13:10:00 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5)
Gecko/20041111 Firefox/1.0

Description of problem:
While installing all the available update packages for RHES4B2. I
noticed that the progress bar for the package that is currently
installed is not updated.

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


How reproducible:
Always

Steps to Reproduce:
1. run up2date and install some updates
2.
3.
    

Additional info:
Comment 1 Uwe Beck 2004-11-20 15:53:39 UTC 
Also during the packages downloads the progress bar for the package
that is currently downloads is not updated.
Comment 2 Bernd Bartmann 2004-11-20 16:02:14 UTC 
Yes, I meant during download nor during install.
Comment 3 Bernd Bartmann 2004-11-20 16:02:50 UTC 
s/nor/not/
Comment 5 Jiri Pallich 2012-06-20 15:54:45 UTC 
Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life. 
Please See https://access.redhat.com/support/policy/updates/errata/

If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.
Note You need to log in before you can comment on or make changes to this bug.