Bug 44562 - rpm: header.c:259: regionSwab: Assertion `ie.info.type >= 0 && ie.info.type <= 9' failed.
Summary: rpm: header.c:259: regionSwab: Assertion `ie.info.type >= 0 && ie.info.type <...
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: rpm (Show other bugs)
(Show other bugs)
Version: 7.1
Hardware: i386 Linux
medium
medium
Target Milestone: ---
Assignee: Jeff Johnson
QA Contact: David Lawrence
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-06-14 07:32 UTC by Lance A. Brown
Modified: 2007-04-18 16:33 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2001-06-14 14:46: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 Lance A. Brown 2001-06-14 07:32:46 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.76 [en] (X11; U; Linux 2.4.2-2 i586; Nav)

Description of problem:
After doing an initial install of Ximian Gnome 1.4 I am now receiving the
following assertion failure from use of rpm that modifies the rpm
databases:

rpm: header.c:259: regionSwab: Assertion `ie.info.type >= 0 && ie.info.type
<= 9' failed.

This appears to be happening to the libxml-1.8.13-ximian.2 package.


How reproducible:
Always

Steps to Reproduce:
1. run 'rpm -qa' 
The listing will stop after displaying libxml-1.8.13-ximian.2 and present
the Assertion failure.
2.
3.
	

Actual Results:  ...
rep-gtk-gnome-0.15-ximian.4
helix-sweetpill-1.0-ximian.2
imlib-1.9.10-ximian.2
libxml-1.8.13-ximian.2
rpmq: header.c:259: regionSwab: Assertion `ie.info.type >= 0 &&
ie.info.type <= 9' failed.
Aborted


Expected Results:  Should have completed without error.

Additional info:

Comment 1 Jeff Johnson 2001-06-14 14:00:27 UTC
Try doing a --rebuilddb with a recent version of rpm-4.0.3 from Raw Hide, as all
the ximian induced problems that I've been able to capture are fixed
there.

Comment 2 Lance A. Brown 2001-06-14 14:46:27 UTC
ALRIGHT!!!!!!!  Thanks for the tip!  You have corrected my problem.


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