Maybe there are some RPM experts on the list that can help me out
with this one. I beleive I've got a corrupt rpm database on my
alpha system (it's happened to me once B4). It now doesn't know much 
about dependancies anymore, making upgrading packages difficult.

It complains that all the packages dependant of the package you're 
trying to upgrade need some kind of library contained withing the 
package (you're trying to upgrade). 

The libs needed are really there, I mean, what is the difference 
between gnome-libs-1.1.2-1mdk and 2mdk?. At the moment my only 
solution to get the rpm database going again will to re-install 
(unless someone else has a better idea)...

Here are some more details:

> Have you ever seen this B4?

> On my alpha (for some reason things go fine on my intel) when
> I want to upgrade a package I get error messages like this:

> rpm -Uvh gnome-libs-1.2.1-2mdk.alpha.rpm
> error: failed dependencies:
>         libart_lgpl.so.2 is needed by ee-0.3.11-5mdk
>         libart_lgpl.so.2 is needed by libglade-0.13-1mdk
>         libart_lgpl.so.2 is needed by gnome-media-1.0.51-3mdk
>         libart_lgpl.so.2 is needed by gnome-linuxconf-0.23-2mdk
>         libart_lgpl.so.2 is needed by gtop-1.0.7-0.4mdk
>         libart_lgpl.so.2 is needed by gnomba-0.6.2-4mdk
>         libart_lgpl.so.2 is needed by gdm-2.0beta4-4mdk
>         libart_lgpl.so.2 is needed by glade-0.5.9-2mdk
>         libart_lgpl.so.2 is needed by gnorpm-0.9-4mdk
>         libart_lgpl.so.2 is needed by gnome-chess-0.2.4-2mdk
>         libart_lgpl.so.2 is needed by gnome-objc-1.0.40-2mdk
>         libart_lgpl.so.2 is needed by sawmill-gnome-0.26-7mdk
>         libart_lgpl.so.2 is needed by enlightenment-conf-0.15-11mdk
>         libart_lgpl.so.2 is needed by gnome-admin-1.0.3-4mdk
>         libart_lgpl.so.2 is needed by rep-gtk-gnome-0.9.1-1mdk
>         libart_lgpl.so.2 is needed by gnome-toaster-20000227-3mdk
>         libart_lgpl.so.2 is needed by g-print-0.2-5mdk
>         libart_lgpl.so.2 is needed by irssi-0.7.20.1-6mdk
>         libart_lgpl.so.2 is needed by gmc-4.5.46-1mdk
>         libart_lgpl.so.2 is needed by gnome-utils-1.0.50-4mdk
> ...

> And the list goes on. The funny thing is that I trying to
> upgrade from 1.2.1-1mdk to 1.2.1-2mdk. There is absolutely
> no difference in the files in the packages (rpm -qpl / -ql
> shows the same for both packages).

> I don't like to --force or to --nodeps packages...

> Doing an rpm --rebuilddb doesn't help.

> On my intel (which is still working fine) the /var/lib/rpm directory
> looks like this:

> drwxr-xr-x    2 root     root         4096 Jun 16 23:46 alternatives/
> -rw-r--r--    1 root     root        16384 Jun 18 12:23 conflictsindex.rpm
> -rw-r--r--    1 root     root     10027008 Jun 18 12:23 fileindex.rpm
> -rw-r--r--    1 root     root        28672 Jun 18 12:23 groupindex.rpm
> -rw-r--r--    1 root     root        49152 Jun 18 12:23 nameindex.rpm
> -rw-r--r--    1 root     root     21869832 Jun 18 10:02 packages.rpm
> -rw-r--r--    1 root     root        53248 Jun 18 12:23 providesindex.rpm
> -rw-r--r--    1 root     root     10579968 Jun 18 12:23 requiredby.rpm
> -rw-r--r--    1 root     root        16384 Jun 18 12:23 triggerindex.rpm

> On my alpha (this one has the problems) it looks like this:
> drwxr-xr-x    2 root     root         1024 Jun 17 07:39 alternatives/
> -rw-r--r--    1 root     root        32768 Jun 18 13:16 conflictsindex.rpm
> -rw-r--r--    1 root     root      2605056 Jun 18 13:16 fileindex.rpm
> -rw-r--r--    1 root     root        32768 Jun 18 13:16 groupindex.rpm
> -rw-r--r--    1 root     root        32768 Jun 18 13:16 nameindex.rpm
> -rw-r--r--    1 root     root     11763464 Jun 18 10:33 packages.rpm
> -rw-r--r--    1 root     root        32768 Jun 18 13:16 providesindex.rpm
> -rw-r--r--    1 root     root       122880 Jun 18 13:16 requiredby.rpm
> -rw-r--r--    1 root     root        32768 Jun 18 13:16 triggerindex.rpm

> Notice how many files on the alpha have 32768 as length. This is the
> same lenth as the "default" file lenth when you do a rpm --initdb
> --dbpath <somewhere>. My conclusion is that the rpm database on my alpha
> is smoked.

> >From your previous replies I understand that getting it fixed is pretty
> impossible. If there is anything I can still do to look into the
> database / figure it out I'd like to know. If the current (corrupt?)
> database is of any use to you (research??) I'll be happy to make a 
> copy.

> Otherwise I'll be re-installing soon (start downloading the latest
> alpha-iso) ;-)

Any help / pointers are welcome...

Reply via email to