Patrick Shanahan wrote:

Full quote re off-list reply...

* Julien Michielsen [04-12-08 09:26]:

...

...

* Julien Michielsen [04-12-08 08:37]:

...

When I tried to install an rpm: # rpm -ivh dl/ImageMagick-6.3.0-5m.i686.rpm error: Failed dependencies: libjasper-1.701.so.1 is needed by ImageMagick-6.3.0-5m.i686

This made me search for libjasper, and I saw this lib did exist:

locate libjasper-1.701.so.1 /usr/lib/libjasper-1.701.so.1

Appearently this lib had been installed earlier, and came from libjasper-1.900.1-81. Then, perhaps the existing libjasper is not completely installed or is not in the rpm database. Does: rpm -q libjasper report libjasper-1.701 or something else? RPM does not check physical file existance, but checks entries in the rpm database. No: it points to 1.900.1-81 rpm -q libjasper

...

...

May this a bug in suse-11, that for example PATH-pointers do not detect existing libs? not if the above supposition is true.

Try installing/reinstalling the *required* version of libjasper. Tried to do so: rpm -ivh dl/libjasper-1.701.0-3.i586.rpm Preparing... ########################################### [100%] package libjasper-1.900.1-81 (which is newer than

Patrick Shanahan wrote: libjasper-1.900.1-81 libjasper-1.701.0-3) is already installed file /usr/lib/libjasper-1.701.so.1 from install of libjasper-1.701.0-3 conflicts with file from package libjasper-1.900.1-81

The two rpm's (libjasper-1.701.0-3 and libjasper-1.900.1-81) are not very different: both of them contain the same libjasper # rpm -qlp dl/libjasper-1.701.0-3.i586.rpm |grep libja /usr/lib/libjasper-1.701.so.1 /usr/lib/libjasper-1.701.so.1.0.0 /usr/lib/libjasper.a /usr/lib/libjasper.la /usr/lib/libjasper.so # rpm -qlp libjasper-1.900.1-81.i586.rpm|grep libja /usr/lib/libjasper-1.701.so.1 /usr/lib/libjasper.so.1 /usr/lib/libjasper.so.1.0.0 /usr/lib/libjasper-1.701.so.1 /usr/lib/libjasper-1.701.so.1.0.0

I'd rather have libjasper-1.701 installed, but then I'd first need to uninstall libjasper-1.900. Yast won't let me do so because 84 packages depend on it. I am afraid that a rpm -ivh --force dl/libjasper-1.701.0-3.i586.rpm would do more harm than good. Or not necessarily?

rpm -ivh --oldpackage libjasper-1.701.0-3.i586.rpm

...

Thank you -- Julien Michielsen julien_at_michkloo.xs4all.nl

Please continue on-list conversations started on-list. Others may be insterested in the thread while not participating and off-list

conversations do not appear in the archives, ie: are not searchable.

man rpm would have provided you the option "--oldpackage" as would: rpm --help

I tried the --oldpackage parameter, but in vain: rpm -ivh --oldpackage dl/libjasper-1.701.0-3.i586.rpm Preparing... ########################################### [100%] file /usr/lib/libjasper-1.701.so.1 from install of libjasper-1.701.0-3 conflicts with file from package libjasper-1.900.1-81 Would I make a mess if I provided the --force parameter?

as to the similarities/differences of the two versions, there is a failure of proper dependencies/requirements in one of the packages, probably the 1.900.1 libjasper for not specifying it provides 1.701.so.

If this failure hadn't existed, the installation would have proceeded without errors? -- Julien Michielsen julien_at_michkloo.xs4all.nl -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org