> Made for an interesting Saturday. ;)
I can believe that.
I solved this problem. I've included my solution (not for the faint of
heart) as a reference.
The problem WAS with my rpm database, as had been suggested. But it
existed in the Packages database, so --rebuilddb (which doesn't rebuild
that file) didn't fix it.
History (I'm sure this led to the
I just updated to 0.22mdk of popt* and rpm*. Still the problem exists.
Has anybody had a chance to interpret the strace output I sent?
On Thu, 2001-08-30 at 00:48, Lonnie Borntreger wrote:
> On Tue, 2001-08-28 at 04:44, Fabrice FACORAT wrote:
> > Le Mardi 28 Août 2001 08:41, vous avez écrit :
I haven't followded the rest of this thread, so excuse me if I repeat what
has already been said or something which is completely useless !!!
I had loads of problems with rpm and like you part of the problem was popt.
To get rpm working 100% again required an rpm --rebuilddb after updating popt
Le Mardi 28 Août 2001 08:41, vous avez écrit :
> I'm assuming by the lack of response on this for three weeks that I
> either have a problem that nobody cares about, nobody else is having,
> nobody can come up with a fix for, or several/all the above.
>
> Since sending this, I've updated the popt
I'm assuming by the lack of response on this for three weeks that I
either have a problem that nobody cares about, nobody else is having,
nobody can come up with a fix for, or several/all the above.
Since sending this, I've updated the popt and rpm packages to 0.21mdk,
but it still acts the same.
Linux user since kernel 0.99pl13, Mandrake user since 3/2001, Cooker
user since 4/2001
System: LM Cooker (almost completely up to current on every package I
have installed)
Kernel: Custom 2.4.9
I'm stumped. In general, everything is fine - except for those times I
update one of those "don't ever
