On Aug 16, 2008, at 5:41 AM, Alexey Tourbin wrote:

> On Sat, Aug 16, 2008 at 04:12:49AM -0400, Jeff Johnson wrote:
>> (aside) btw, I'm seeing issues with damaged (truncated is my guess,
>> not looked)
>> headers retrieved from rpmdb on HEAD, rpm-5_1_4 is fine.
>
> How do I reproduce?  At least simple *read-only* rpmquery works fine.
>

> $ ./rpm -qa --qf '%{NAME}\n' >/dev/null
> $ echo $?
> 0
> $

Yes, rpm -qa is fine. I think I saw with --import, gpg-pubkey headers
are "LSB format" without header SHA1 digests.

I'm guessing the issue has to do with the +/- 8b when writing the blob
into /var/lib/rpm/Packages. That may mean that the issue tracks with
accessing the last 8b.

I'll dig out the reproducer, don't worry about the issue until then. I
know that there is sufficient checking within rpm to detect the issue.

(aside) There's a whole slew of ugly segfaults that need to be addressed
to handle the Newer! Better! Bestest! rpm.org product, sharing an rpmdb
with rpm-4.5.90 is not going to be pleasant. Too bad that rpm-4.5.90  
dbenv
handling is an inferior implementation, in this case I'd be perfectly  
happy if rpm.org
plagarized the rpm-5.x stale lock handling without acknowledgement. But
that is unlikely to happen.

73 de Jeff