[Bug 1044] New: pkgchk reporting errors when checking appbat packages

[email protected]
Newsgroups gmane.linux.lsb.test-suite
Message-ID <[email protected]>
OtherBugsDependingO 620
             nThis:


When pkgchk is run against the rpm packages from appbat it reports three 
errors for all packages across all architectures. The errors are as follows:

Error: checkRpmIdx() unexpected Index tag=269 type=6 offset=0 count=1
Error: checkRpmIdx() Required Index RPMTAG_HEADERI18NTABLE not found
Error: checkRpmIdx() unexpected Index tag=1015 type=6 offset=1b1 count=1

These same errors, as well as additional ones, are reported for the rpm 
packages that ship with RHEL 4 and SLES 9.

The first error about unknown index 269 has to do with not having 
RPMTAG_SHA1HEADER defined in the spec. According to a note from Jeff Johnson 
tags starting at 256 contain signature info duplicated from the signature 
header. We should at least acknowledge that this section type exists, even if 
we don't check it since we already checked it in the signature header.

The second error about not having the RPMTAG_HEADERI18NTABLE type tag happens 
because it is not there. I believe rpm assumes the locale is C if no 
RPMTAG_HEADERI18NTABLE is present. According to the spec this tag is required, 
but the packages I have examined on RHEL and SLES do not include it. If it is 
required, then the appbat will need to determine how to get it added, probably 
through a spec file change.

The third error about unknown tag 1015 is related to the RPMTAG_PACKAGER. This 
value is set from the Packager: field in the spec file. For the appbat it is 
set to "Appbat Team <[email protected]>". The spec may need to add 
this section so pkgchk can recognize it.   
 
--    
Configure bugmail: http://bugs.linuxbase.org/userprefs.cgi?tab=email   
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.