PDA

View Full Version : Local File Conflict. Update



erich_18
20th September 2008, 04:00 AM
Hello,

Running FC9 64Bits.

The system starts updating automatically, then I get an error message that says: "Local File Conflict" with the following:

"Test Transaction Errors: file /usr/share/java/avalon-logkit.jar from install of excalibur-avalon-logkit-2.2.1-0.r508111.3jpp.noarch conflicts with file from package avalon-logkit-1.2-5jpp.5.fc9.x86_64 "

Anyway around this?

Thanks

Eric

Hlingler
20th September 2008, 04:48 AM
Lots of different ways around it.

Simplest would be to remove existing avalon-logkit-1.2-5jpp.5.fc9.x86_64 first - but I bet it would drag lots of important stuff out with it. You can try, but beware, and cancel the order if YUM wants to erase lots of important stuff. Open a terminal, log in as root user, and command:
yum remove avalon-logkit

If that fails (as expected), you'll have to work around the road-block. Next easiest thing is to do a manual update, and exclude excalibur-avalon-logkit-2.2.1-0.r508111.3jpp.noarch from the update list:
yum update --exclude=excalibur-avalon-logkit

If that fails too, there are still more ways around this, but try those first.

V

erich_18
22nd September 2008, 04:18 AM
Thanks for your response and time to help me.

I tried the latter and get the following:

[root@localhost Eric]# yum update --exclude=excalibur-avalon-logkit
Loaded plugins: presto, refresh-packagekit
Setting up and reading Presto delta metadata
No Presto metadata available for jpackage17-f9
No Presto metadata available for livna
No Presto metadata available for google
No Presto metadata available for fedora
No Presto metadata available for adobe-linux-i386
No Presto metadata available for updates-newkey
No Presto metadata available for jpackage-generic-nonfree
No Presto metadata available for jpackage-generic
No Presto metadata available for jpackage50-f9
No Presto metadata available for updates
Excluding Packages in global exclude list
Finished
Setting up Update Process
Resolving Dependencies
--> Running transaction check
---> Package jakarta-commons-logging.noarch 0:1.1-4jpp set to be updated
---> Package xorg-x11-server-Xorg.x86_64 0:1.5.0-1.fc9 set to be updated
---> Package freeciv.x86_64 0:2.1.6-1.fc9 set to be updated
---> Package nss_compat_ossl.x86_64 0:0.9.3-1.fc9 set to be updated
---> Package xorg-x11-server-common.x86_64 0:1.5.0-1.fc9 set to be updated
---> Package sqlite.i386 0:3.5.9-1.fc9 set to be updated
---> Package alsa-utils.x86_64 0:1.0.17-2.fc9 set to be updated
---> Package libdhcp4client.x86_64 12:4.0.0-17.fc9 set to be updated
---> Package log4j.x86_64 0:1.2.14-4jpp.1.fc9 set to be updated
---> Package xorg-x11-drv-evdev.x86_64 0:2.0.4-1.fc9 set to be updated
---> Package dhclient.x86_64 12:4.0.0-17.fc9 set to be updated
---> Package velocity.noarch 0:1.5-2jpp set to be updated
--> Processing Dependency: jakarta-commons-lang for package: velocity
--> Processing Dependency: servletapi4 for package: velocity
--> Processing Dependency: excalibur-avalon-logkit for package: velocity
---> Package sqlite.x86_64 0:3.5.9-1.fc9 set to be updated
--> Running transaction check
---> Package servletapi4.noarch 0:4.0.4-4jpp set to be updated
---> Package jakarta-commons-lang.noarch 0:2.3-1jpp set to be updated
---> Package velocity.noarch 0:1.5-2jpp set to be updated
--> Processing Dependency: excalibur-avalon-logkit for package: velocity
--> Finished Dependency Resolution
velocity-1.5-2jpp.noarch from jpackage-generic has depsolving problems
--> Missing Dependency: excalibur-avalon-logkit is needed by package velocity-1.5-2jpp.noarch (jpackage-generic)
Error: Missing Dependency: excalibur-avalon-logkit is needed by package velocity-1.5-2jpp.noarch (jpackage-generic)
[root@localhost Eric]#

JohnVV
22nd September 2008, 05:05 AM
have you updated the yum key see:
http://forums.fedoraforum.org/showthread.php?t=199573
also give removing the presto plugin a try .

erich_18
22nd September 2008, 05:16 AM
thanks. yes already have the update key you mentioned. tried that and it told me I already had it. actually as stated above when I selected to remove the avalon kit it was dragging openoffice with if scared I might loose more than that along with it, and also maybe open "pandoras box" and have hell load of errors afterwards,,:


================================================== ==============================
Package Arch Version Repository Size
================================================== ==============================
Removing:
avalon-logkit x86_64 1.2-5jpp.5.fc9 installed 460 k
Removing for dependencies:
bsf noarch 2.4.0-1jpp installed 126 k
bsh x86_64 1.3.0-12jpp.3.fc9 installed 2.0 M
openoffice.org-calc x86_64 1:2.4.1-17.6.fc9 installed 22 M
openoffice.org-core x86_64 1:2.4.1-17.6.fc9 installed 219 M
openoffice.org-draw x86_64 1:2.4.1-17.6.fc9 installed 2.9 M
openoffice.org-graphicfilter x86_64 1:2.4.1-17.6.fc9 installed 432 k
openoffice.org-impress x86_64 1:2.4.1-17.6.fc9 installed 4.9 M
openoffice.org-math x86_64 1:2.4.1-17.6.fc9 installed 3.6 M
openoffice.org-writer x86_64 1:2.4.1-17.6.fc9 installed 7.3 M
openoffice.org-writer2latex x86_64 0.5-2.fc9 installed 390 k
openoffice.org-xsltfilter x86_64 1:2.4.1-17.6.fc9 installed 296 k
velocity x86_64 1.4-7jpp.1 installed 1.9 M

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

so I selected no and tried the second recommendation.

Im still googling around for answers, hopefully I can find someting soon, or if you have any more ides that would be great, I have more updates pending because of this...seems nothing else will update unless I get this one fixed...

/Eric

Hlingler
24th September 2008, 12:22 AM
Everything listed there looks to me like stuff that can be safely removed, then re-installed later. Your settings/configs will be retained for later use even if the packages are removed....

Or: have you tried the 'skip-broken' switch:
yum --skip-broken update

V