Bug 98628 - up2date prints a lot of garbage while installing software
Summary: up2date prints a lot of garbage while installing software
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Raw Hide
Classification: Retired
Component: up2date   
(Show other bugs)
Version: 1.0
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Adrian Likins
QA Contact: Fanny Augustin
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-07-05 22:16 UTC by Kaj J. Niemi
Modified: 2007-04-18 16:55 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2003-07-22 13:02:40 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
the problem (6.74 KB, text/plain)
2003-07-05 22:19 UTC, Kaj J. Niemi
no flags Details

Description Kaj J. Niemi 2003-07-05 22:16:59 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030703

Description of problem:
After upgrading from 3.1.27 to 3.1.35 up2date seems to print an awful amount of
unnecessary stuff while installing/updating software.

(see attachment)

I'm guessing this isn't all that normal.. ;)

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

How reproducible:
Always

Steps to Reproduce:
1. attempt to install/upgrade any piece of software via up2date
2.
3.
    

Actual Results:  See above

Expected Results:  Shouldn't print those pesky lines starting with "what:"

Additional info:

Comment 1 Kaj J. Niemi 2003-07-05 22:19:05 UTC
Created attachment 92762 [details]
the problem

A lot of superfluous information printed here

Comment 2 Adrian Likins 2003-07-09 21:19:26 UTC
should be fixed in versions 3.1.41 or higher

Comment 3 Kaj J. Niemi 2003-07-22 13:02:40 UTC
Yup, 3.1.46 doesn't have this problem anymore.. thanks!

Closing and marking RAWHIDE :)


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