Bug 245698 - repomanage: mal-formated error messages
Summary: repomanage: mal-formated error messages
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: yum-utils (Show other bugs)
(Show other bugs)
Version: 7
Hardware: All Linux
low
low
Target Milestone: ---
Assignee: Seth Vidal
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-06-26 06:03 UTC by Ralf Corsepius
Modified: 2007-11-30 22:12 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2007-06-26 19:20:31 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)

Description Ralf Corsepius 2007-06-26 06:03:48 UTC
Description of problem:

Running repomanage on a repo containing a corrupted rpm, I just received this
mal-formated error message:

# repomanage -o xxx > list
error: rpmts_HdrFromFdno: MD5 digest: BAD
Expected(bef0a124ac09d2a02c739c86f82643dd) != (d7e3fc1564fcd12ef71a10acbe05505d)
('E', 'r', 'r', 'o', 'r', ' ', 'o', 'p', 'e', 'n', 'i', 'n', 'g', ' ', 'p', 'a',
'c', 'k', 'a', 'g', 'e', ' ', 'a', 'l', 'l', '/', 'f', 'e', 'd', 'o', 'r', 'a',
'/', 'F', 'e', 'd', 'o', 'r', 'a', '/', 'g', 'c', 'o', 'm', 'p', 'r', 'i', 's',
'-', 's', 'o', 'u', 'n', 'd', '-', 's', 'v', '-', '8', '.', '2', '.', '2', '-',
'2', '.', 'f', 'c', '7', '.', 'i', '3', '8', '6', '.', 'r', 'p', 'm')


Version-Release number of selected component (if applicable):
yum-utils-1.1.5-1.fc7
yum-3.2.0-1.fc7

Comment 1 Seth Vidal 2007-06-26 19:20:31 UTC
fixed in cvs. You can apply this patch:
https://lists.dulug.duke.edu/pipermail/yum-cvs-commits/2007-June/001786.html

to get it working nicely. The problem was the change in python 2.5's
BaseException class.

Thanks for reporting this.




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