David Boles wrote:
I am *not* an expert here. Only an old time user. The plugins are
'painless'. I have never had one of them cause problems. Fail? Sometimes
maybe. But not break anything. As well as yum.
Trying to install it now with yum fails with the below.
yum install kipi-plugins
Loading "skip-broken" plugin
Loading "refresh-updatesd" plugin
Setting up Install Process
Parsing package install arguments
Resolving Dependencies
--> Running transaction check
---> Package kipi-plugins.i386 0:0.1.4-2.fc8 set to be updated
--> Processing Dependency: libkexiv2.so.1 for package: kipi-plugins
--> Processing Dependency: libkdcraw.so.1 for package: kipi-plugins
--> Finished Dependency Resolution
Error: Missing Dependency: libkexiv2.so.1 is needed by package kipi-plugins
Error: Missing Dependency: libkdcraw.so.1 is needed by package kipi-plugins
[root@HP-JCF7 ~]# locate libkexiv2.so
/usr/lib/libkexiv2.so.1
/usr/lib/libkexiv2.so.1.1.1
[root@HP-JCF7 ~]# rpm -q --whatprovides /usr/lib/libkexiv2.so.1
error: file /usr/lib/libkexiv2.so.1: No such file or directory
[root@HP-JCF7 ~]# rpm -q --whatprovides /usr/lib/libkexiv2.so.1.1.1
error: file /usr/lib/libkexiv2.so.1.1.1: No such file or directory
[root@HP-JCF7 ~]# updatedb
[root@HP-JCF7 ~]# locate libkexiv2.so
/usr/lib/libkexiv2.so.3
/usr/lib/libkexiv2.so.3.0.0
[root@HP-JCF7 ~]# rpm -q --whatprovides /usr/lib/libkexiv2.so.3
libkexiv2-0.1.6-1.fc8
Rpm is what can do, if you really do 'bad things' with it without knowing
exactly what you are doing, will break things.
The previous removal was just using rpm -e. Both digikam and
kipi-plugins were successfully removed. I could have used yum -y update
--skip-broken successfully after removing the packages, but it seemed
like overkill to use yum, since it already pulled in the packages to cache.
Your example, from above, 'might' work. Or it 'might not' work. It might
take some tweaks. But it would not break anything. 'Excluding' means don't
do anything with this. 'Force' and 'nodeps' are the really bad commands
for the uneducated users.
I believe running yum with those parameters would have failed anyway
with the prior example. Yum could not do anything about the updated
libkexiv2 package which caused problems with the two rpms.
Related to rpm and its powers. I know to try to stay in its conventional
options for the most part. Tomboy did get booted with extreme options
though. Mono then removed properly with yum remove.
Computers are different. Installed packages are different. Many things are
different. That is why 'it works for me' and it might not 'work for you'
happens.
I believe most errors now are legitimate since Robert is seeing the same
errors. yum exclude for the libkexiv2 package and skip-broken for the
xurl* problem would probably work.
Another thing to consider. Sometimes mirrors are not updated just when you
connect. Try later works more times than people like to admit. :-)
The requested updates matched this rawhide report now and at the time
the problem was originally discussed. Mirror sync problems are something
to take into consideration though with update retrieval.
Jim
--
Linux - because software problems should not cost money.
-- Shlomi Fish
--
fedora-test-list mailing list
fedora-test-list@xxxxxxxxxx
To unsubscribe:
https://www.redhat.com/mailman/listinfo/fedora-test-list
