Red Hat Bugzilla – Bug 42511
rpm free list error message
Last modified: 2007-04-18 12:33:26 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux 2.2.14-5.0 i586; en-US; 0.8)
Description of problem:
I ran rpm --rebuilddb but nothing happened.
I read to do this in the mailing lists.
I append a tarball of my database
I was using Ximian gnome 1.4
Steps to Reproduce:
I still need a pointer to a tar ball of your database
tar czvf /tmp/rpmdb.tar.gz rpm
I am trying to send, but only have a 56k modem, and my mozilla fails when Im
doing it. When you say a 'pointer' you mean the tar file?, because it's 7 MB
long. Can I send it by email to some direction you tell me?. I don't know if
it's correct, because received an error message.
Please, if the answer is going to be that big, send it to email@example.com, or
they'll throw me away from yahoo!,!. Thanks
A pointer is a URL that names the tarball. If you put the file someplace
where I can fetch, I will do so. Otherwise try mail to <firstname.lastname@example.org>
Hello there! Did somebody receive the mail with the tarball?
Apologies for the delay. Your problem is fixed in rpm-4.0.3-0.38. I'll have a
copy for 6.2 available on ftp.rpm.org in the next day or so.
So, the solution is upgrade to 4.0.3-0.38, but we both know I can't use rpm on
my system... so I understand I should use a tarball and overwrite my rpm
install (tar -xcvf... and something more to force overwriting, "RTFM"), and,
after that, I can rebuild my database (rpm --rebuilddb).
1. Is this correct?
2. Can I blame Ximian Redcarpet, and use from now on only the Red Hat updater
to be sure?
If it would help, I can mail you a fixed copy of your packages.rpm, drop
me a note <email@example.com> if you want me to do so.
No it's not entirely Ximian's fault, there's a number of pieces to this problem
some of which go back 3 or 4 years, others that have to do with Ximina zigging
while I zagged. I'm glad that the rpm problems are finally
being solved. Meanwhile, Red Carpet looks promising, but I'd look for a copy
linked against 4.0.3 after rease in the next couple of weeks.