[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Ltib] libXt "failed dependencies"
From: |
Alan Carvalho de Assis |
Subject: |
Re: [Ltib] libXt "failed dependencies" |
Date: |
Tue, 14 Jul 2009 12:04:55 -0300 |
Hi Stuart,
On 7/14/09, Stuart Hughes <address@hidden> wrote:
> Hi Alan,
>
> I can explain the difference in behaviour. When running -m scdeploy,
> the rpm file in installed with a "fabricated" spec file that has:
>
> Autoreqprov : no
>
> This effectively disables the provides/requires checks that happen in a
> normal run. This is something you would want during package development.
>
> The real question is why you're failing this dependency. Run:
>
> ls -l rootfs/libc*
>
It appears ok:
$ ls -l rootfs/lib/libc*
-rwxr-xr-x 1 root root 1352528 2007-05-09 15:27 rootfs/lib/libc-2.5.so
lrwxrwxrwx 1 root root 17 2009-07-09 13:26
rootfs/lib/libcom_err.so.2 -> libcom_err.so.2.1
-rwxr-xr-x 1 root root 27734 2009-07-09 13:26 rootfs/lib/libcom_err.so.2.1
-rwxr-xr-x 1 root root 26252 2007-05-09 15:27 rootfs/lib/libcrypt-2.5.so
lrwxrwxrwx 1 root root 15 2009-07-09 13:18
rootfs/lib/libcrypt.so.1 -> libcrypt-2.5.so
lrwxrwxrwx 1 root root 11 2009-07-09 13:18 rootfs/lib/libc.so.6
-> libc-2.5.so
> You should see libc.so.6 in there and it should be a link to a real file
> (for example: libc-2.3.6.so). If it is not there, then base_libs has
> not been installed. If it is, then for some reason base_libs has not
> inserted this provide into the rpm database. You can check with:
> rpm --root `pwd`/rootfs -q base_libs --provides | grep libc.so
>
It returns ok as well:
$ rpm --root `pwd`/rootfs -q base_libs --provides | grep libc.so
libc.so.6
libc.so.6(GLIBC_2.4)
libc.so.6(GLIBC_2.5)
libc.so.6(GLIBC_PRIVATE)
To make sure there is any issue on my system I installed a virtual
machine (Ubuntu 9.04) and started from scratch and the same error
again.
Do you have any idea to solve it?
Best Regards,
Alan