Re: [gnome-db] "Error: unrecognized db option..." in red-carpet & gnorpm

[Phillip Pi <philpi apu edu>]

> This question is not for gnome-db-list, is something for beta ximian com
> or other general list, but i will try to solve some questions..

Carlos, I am sorry about that. My problem sounded like a database (db)
problem, so I thought I would include this gnome-db-list.

Guys, I forgot to mention that I am using GNOME v1.4 if that information
is important.


> > I am having a major problem when I run red-carpet, gnorpm, and possibly
> > other commands/programs. Basically, I keep getting these two errors in
> > text mode and GUI mode:
> > 
> > error: unrecognized db option: "verify" ignored
> > error: unrecognized db option: "tmpdir" ignored

> It look like you have your RPM database corrupted
> 
> If no one gives you a better solution, try to do a "rpm --rebuilddb"

The rebuilding of the RPM database had no effect on the situation. I am
still getting the same errors.


> > When red-carpet tries to upgrade components/packages, it segfaults. I
> > noticed one of the packages it tried to install left a mess with libxml
> > when I rpm -q libxml:
> > 
> > libxml-1.8.14-ximian.1
> > libxml-1.8.15-ximian.2
> > libxml-1.8.15-ximian.2
> > libxml-1.8.15-ximian.2
> > 
> > I don't know how to clean up the duplicates since rpm -e libxml-1.8.15
> > gives me this error: "libxml-1.8.15" specifies multiple packages
> 
> With --allmatches rpm will remove all this packages.

Ah thank you for this one. Nice parameter to learn which I didn't see in
man! :) I left libxml-1.8.14-ximian.1 intact because I believe I still
need this if I need to upgrade. I have a feeling that the duplicates came
from red-carpet that had those errors and crashed (segfault and
incomplete upgrade). 


> > My RPM versions are:
> > gnorpm-0.96-1
> > red-carpet-1.1.2-ximian.1
> > 
> > I am running on Red Hat Linux v7.1 (Kernel v2.4.9). I am not sure if I
> > broke something (I probably did!). Basically, a week ago I upgraded the
> > default Kernel (v2.4.2) to v2.4.9 manually. I can confirm Kernel was
> > stable, but I am not sure if it caused this problem.
> > 
> > Another recent upgrade was upgrading KDE v2.1 to v2.2. I had to update a
> > bunch of files from ftp://ftp.kde.org including many libraries (could have
> > broken something).
> > 
> > I was unable to find any clues or posts about this on the newsgroups,
> > archived GNOME mailing lists, etc. I look forward to receiving a reply
> > soon.
> > 
> > Note: I am a Linux newbie so please don't get too technical. :)