On Aug 23, 2007, at 11:07 AM, Jakub Bogusz wrote:
On Thu, Aug 23, 2007 at 08:42:04AM -0400, Jeff Johnson wrote: In my case database wasn't open - rpm finished its work after db4.6 upgrade, and failed when I ran it again to upgrade some other package. I didn't use poldek during all those operations, just pure rpm invocations from bash.
Ah, that helps.
A trigger to fire
rm -f /var/lib/rpm/__db
automagically when Berkeley DB is upgraded is then likely viable.
OTOH, insturmenting a trigger for a one tome 4.6.18 -> 4.6.19 problem
that is fixed by doing
rm -f /var/lib/rpm/__db*
is perhaps overkill.
What is likely deficient is that the dbenv internals have changed
incompatibly
between 4.6.18 -> 4.6.19. An incompatibility would normally be
handled by rev'ing
the version stamp, but the incompatible change is not being tracked
by the current
version stamp of "4.6". In other words, changing Berkeley DB to version stamp a dbenv as "4.6.18" and "4.6.19" rather than "4.6" might be the best fix of all. hth 73 de Jeff
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ pld-devel-en mailing list [email protected] http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
