I run the following command to update my computer:

sudo yum update

Usually, it works great. I'm getting an error at the moment and I'm not quite sure what to do about it. I'm also not able to update my linux (fedora core 6) PC.

The error is:


Transaction Check Error:
file /usr/share/java/avalon-logkit.jar from install of excalibur-avalon-logkit-2.2.1-0.r508111.2jpp conflicts with file from package avalon-logkit-1.2-4jpp.3


Any help will be greatly appreciated. Thanks in advance.

You need to update to exclude the package with the conflict. That will get your whole update working. You can also remove the offending package, update, then install the offender and hope there is no conflict in the updated configuration.

You are doing a tidy-up between updates arn't you?

http://www.linux-club.de/ftopic84673.html
... this is a solution, using the smart update manager in OpenSUSE

Simon,

Thanks for the reply.

1. What's the yum command to exclude a package? I only know how to update a specific package list.

2. As far as I know, yum is supposed to be managing my packages based on the configured repositories. What do you mean by "tidy-up"? I do what I stated. I run that one command to update.

3. The site you supplied is in German. Is there an English version of this page or a way to translate it with one click (I'm a little lazy )?

Thanks in advance for your help.

jc_cpu

1. man yum
... it's a big, closely worded, manual but well worth the effort.

2. yum clean all (same man page)

3. http://babelfish.altavista.com/

How do I exclude more than one package?

I'm entering the following command:

sudo yum update --exclude=velocity* --exclude=excalibur-avalon-logkit*

Yum is still trying to update the following package:

---> Package velocity.noarch 0:1.5-1jpp set to be updated

The end result is:

--> Processing Dependency: excalibur-avalon-logkit for package: velocity
--> Finished Dependency Resolution
Error: Missing Dependency: excalibur-avalon-logkit is needed by package velocity


Why is it doing this? My command is supposed to exclude those 2 packages. Right?

... or possibly a comma separated list. You can also set this in /etc/yum.conf (see man yum.conf).

http://fedoraproject.org/wiki/Tools/yum
http://fedoraproject.org/wiki/Docs/D...CustomizingYum
... you can also use the yum skip-broken plugin.

If you are tired of yum rebuilding the entire cache ...every ...single ...time ...you ...run ...it ... use yum -C <command>.

Thanks for all of your help, but none of those commands to update worked in this case. There was some sort of dependency conflict that not even the skip-broken plug-in could handle. I did manage to update the computer. To do so, I had to do the following:

1.

yum remove velocity

This ended up removing the following packages:

=============================================================================
Package Arch Version Repository Size
=============================================================================
Removing:
velocity i386 1.4-6jpp.1 installed 1.6 M
Removing for dependencies:
bsf noarch 2.4.0-1jpp installed 126 k
bsh noarch 1.3.0-11jpp installed 729 k
openoffice.org-calc i386 1:2.0.4-5.5.23 installed 19 M
openoffice.org-core i386 1:2.0.4-5.5.23 installed 221 M
openoffice.org-draw i386 1:2.0.4-5.5.23 installed 2.6 M
openoffice.org-graphicfilter i386 1:2.0.4-5.5.23 installed 427 k
openoffice.org-impress i386 1:2.0.4-5.5.23 installed 4.2 M
openoffice.org-math i386 1:2.0.4-5.5.23 installed 3.2 M
openoffice.org-writer i386 1:2.0.4-5.5.23 installed 6.7 M
openoffice.org-xsltfilter i386 1:2.0.4-5.5.23 installed 212 k

Transaction Summary
=============================================================================
Install 0 Package(s)
Update 0 Package(s)
Remove 11 Package(s)

-------------------------------------------------------------------------

2.

yum update

3.

yum install bsf bsh

4.

yum install <openoffice packages>

5.

yum install velocity

6.

reboot the computer because over 100 packages were updated.

7. yum clean all

This was non-intuitive, but it worked. Hopefully, I won't have this problem again in the future (keeping my fingers crossed).

IIRC: package dependencies are read from a header in the rpm. An update to a package may end up using a different description in the header, to use a slightly different package, which can lead to dependency conflicts and updates being refused.

The cleanest way to resolve this is to remove the offending package, then install it. The newer descriptions make sure that the proper dependencies get loaded.

The fact that OOo was removed with velocity, but didn't need velocity, seems to show the problem was with the velocity package description somewhere. Hopefully this has been picked up elsewhere.

Is it just me or does this sort of thing happen to rpm distros more?

Removing the offending package should not have removed OOo along with bsf and bsh.

I don't have any man pages for bsf and bsh, but this is what google gave me.

BSF appears to be some sort of Java thing.

http://www.alphaworks.ibm.com/tech/bsf

This site says that bsh is a Bourne shell.

http://publib.boulder.ibm.com/infoce...xcmds1/bsh.htm

The fact that yum removed all of these packages when I removed velocity tells me that the problem was with all of these packages. I could be wrong. Looks like they don't have the dependency anymore though.

Usually yum works well for me. Hopefully this problem won't happen again and I can just go back to the easy "yum update" command.