Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 103714

Summary:	rpm -i --repackage prints lots of (debugging?) junk
Product:	[Retired] Red Hat Linux Beta	Reporter:	Alexandre Oliva <aoliva>
Component:	up2date	Assignee:	Adrian Likins <alikins>
Status:	CLOSED DUPLICATE	QA Contact:	Fanny Augustin <fmoquete>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	beta1
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:	2006-02-21 18:58:26 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 Alexandre Oliva 2003-09-04 05:55:35 UTC

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030703

Description of problem:
After enabling the repackage-for-rollback feature in up2date, I noticed up2date
-u <package> started printing a lot of junk while installing packages (long
after repackaging old packages), that it didn't before I enabled this feature. 
These messages should probably be removed at some point.

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

How reproducible:
Always

Steps to Reproduce:
1.Enable repackaging of RPMs for rollback in up2date
2.up2date -u some-package

Actual Results:  Ugly, nonsensical messages (hex numbers?) printed while
installing the package

Expected Results:  Clean output from up2date

Additional info:

Comment 1 Jeff Johnson 2003-09-05 13:08:50 UTC

up2date for diagnosis ...

Comment 2 Adrian Likins 2003-09-09 19:30:19 UTC


*** This bug has been marked as a duplicate of 103876 ***

Comment 3 Red Hat Bugzilla 2006-02-21 18:58:26 UTC

Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.