Re: Bad rpmdb, where'd this come from?

[Tom Diehl <tdiehl rogueind com>]

On Sun, 26 May 2002, Jeff Johnson wrote:

> On Sun, May 26, 2002 at 12:59:02PM -0400, Tom Diehl wrote:
> 
> The initial fix in rpm (after investigating) was to remove the fprintf.
> I guess that's the type of solution you prefer, no messages, no problem.
> 
> :-)

Ignorance is bliss!! :-)

> > So am I understanding you correctly thinking that if I ever used a package
> > w/o the fix even upgrading to the latest and greatest rpm package will not
> > prevent the error message from displaying at some point??
> > 
> > If so does --rebuilddb help at all? It would seem to have cleared up the 
> > errors for Harry.
> > 
> 
> Describing persistance is complicated, here's the short and less precise
> answer:
> 
> Use rpm-4.0.4-7x.18 from now on, do a single --rebuilddb, and you
> should never see the problem again.

I like this one a lot better. That answers my question.

Thanks,

-- 
.............Tom	"Nothing would please me more than being able to 
tdiehl@rogueind.com	hire ten programmers and deluge the hobby market 
			with good software." -- Bill Gates 1976

   			We are still waiting ....