For starters, the tag numbers compiled into lsbpkgchk appear
incorrect for:
RPMTAG_FILEMODES
RPMTAG_FILEDEVICES
RPMTAG_FILERDEVS
The SIGTAG_MD5 "calculated value" appears to be
calculated incorrectly.
yes, there's some breakage here.
The lead values for arch/os have not been used for 9+
years. You may
check the lead values until the cows come home, the
values have not been
used since RPMv2 packaging.
I have no idea what this check is trying to accomplish:
checkRpmArchiveFilename: file
usr/share/doc/bison-2.3/THANKS not FHS compliant
a fully conforming application would only install to /opt/{package},
/var/opt/{package} and /etc/opt/{package}.
If that's what you were after (which you're not, just explaining what
it's for):
./configure --prefix=/opt/lsb/bison
and then call pkgchk as:
lsbpkgchk -L lsb-bison bison.*rpm
