Bug 157583

Summary:	Extra-long package name makes progress bar jump up
Product:	[Fedora] Fedora	Reporter:	Mary Ellen Foster <mefoster>
Component:	anaconda	Assignee:	Anaconda Maintenance Team <anaconda-maint-list>
Status:	CLOSED NEXTRELEASE	QA Contact:	Mike McLean <mikem>
Severity:	low	Docs Contact:
Priority:	medium
Version:	4
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2005-08-15 15:24:54 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 Mary Ellen Foster 2005-05-12 20:46:27 UTC

+++ This bug was initially created as a clone of Bug #154459 +++

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050328
Firefox/1.0.2 Fedora/1.0.2-3

Description of problem:
During the progress-bar stage of installing, if a package being installed has an
especially long name, it wraps onto two lines. This causes the progress bar to
blip upwards briefly, and then back down as the next package has a shorter
description.

This happened too fast for me to see which package it was, but it looked like
many of the Java development packages

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


How reproducible:
Didn't try

Steps to Reproduce:


Additional info:

Comment 1 Jeremy Katz 2005-05-23 19:00:39 UTC

What language is this with?

Comment 2 Mary Ellen Foster 2005-05-23 19:10:16 UTC

English -- possibly British English, I can't remember if that choice gets made
before that point in the install or not.

I can't remember what packages it was that made it jump, but I'm convinced I saw
it; I suspect things like
jakarta-commons-validator-javadoc-1.1.3-1jpp_1fc
and others in the jakarta-commons-* family.

Comment 3 Jeremy Katz 2005-05-23 20:19:40 UTC

I'm not seeing here although I can believe that it could happen.  Put in the
change to ensure that the string stays short enough such that the change
shouldn't occur, although that's a workaround at best.