Bug 1145735 - findbugs RPM conflicts with other RPMs
Summary: findbugs RPM conflicts with other RPMs
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: findbugs
Version: 20
Hardware: All
OS: All
unspecified
high
Target Milestone: ---
Assignee: Richard Fearn
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-09-23 15:20 UTC by Matthew Cline
Modified: 2014-10-02 10:59 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-10-01 18:35:18 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
"yum install findbugs" log (4.59 KB, text/plain)
2014-09-29 21:33 UTC, Matthew Cline
no flags Details

Description Matthew Cline 2014-09-23 15:20:01 UTC
Attempting to install the findbugs RPM via yum give the following transaction check errors:

  file /usr/share/findbugs/lib/jaxen.jar from install of findbugs-2.0.3-4.fc20.noarch conflicts with file from package jaxen-0:1.1.6-1.fc20.noarch
  file /usr/share/findbugs/lib/dom4j.jar from install of findbugs-2.0.3-4.fc20.noarch conflicts with file from package dom4j-0:1.6.1-18.fc20.noarch
  file /usr/share/findbugs/lib/jsr-305.jar from install of findbugs-2.0.3-4.fc20.noarch conflicts with file from package jsr-305-0-0.16.20130910svn.fc20.noarch
  file /usr/share/findbugs/lib/findbugs-bcel.jar from install of findbugs-2.0.3-4.fc20.noarch conflicts with file from package findbugs-bcel-5.3-0.2.20130910svn1521566.fc20.noarch
  file /usr/share/findbugs/lib/jFormatString.jar from install of findbugs-2.0.3-4.fc20.noarch conflicts with file from package jFormatString-0-0.14.20131227git.fc20.noarch
  file /usr/share/findbugs/lib/apache-commons-lang.jar from install of findbugs-2.0.3-4.fc20.noarch conflicts with file from package apache-commons-lang-2.6-13.fc20.noarch
  file /usr/share/java/findbugs.jar conflicts between attempted installs of findbugs-2.0.3-4.fc20.noarch and findbugs-2.0.3-4.fc20.noarch

Comment 1 Richard Fearn 2014-09-23 15:53:22 UTC
What command are you using to install findbugs?

I just tried this, for example, and got no error:

$ sudo yum install jaxen dom4j jsr-305 findbugs-bcel jFormatString apache-commons-lang
$ sudo yum install findbugs

Comment 2 Richard Fearn 2014-09-23 15:58:45 UTC
The first 6 errors look a bit odd because the files in /usr/share/findbugs/lib belong to the findbugs package. They shouldn't conflict with files in the jaxen, dom4j, etc. packages.

The last error also looks odd as it seems to be reporting a conflict between findbugs and findbugs...

Comment 3 Matthew Cline 2014-09-29 21:23:11 UTC
I already have findbugs version 2.0.3 release 3.fc20 installed, so I'm just using "yum update".

Comment 4 Matthew Cline 2014-09-29 21:32:30 UTC
I tried removing findbugs and then doing a fresh install, and still got the same problems.  Attached is a full log of the install attempt.

Comment 5 Matthew Cline 2014-09-29 21:33:34 UTC
Created attachment 942496 [details]
"yum install findbugs" log

Comment 6 Richard Fearn 2014-09-30 11:05:28 UTC
I think you might have symlinks even though the packages are not installed. Can you confirm by attaching the output from:

$ sudo yum remove findbugs apache-commons-lang findbugs-bcel jFormatString jcip-annotations jsr-305
$ ls -l /usr/share/findbugs/lib /usr/share/java/findbugs.jar

Comment 7 Matthew Cline 2014-10-01 18:35:18 UTC
[root@localhost findbugs]# ls -l /usr/share/findbugs /usr/share/java/findbugs.jar
/bin/ls: cannot access /usr/share/java/findbugs.jar: No such file or directory
/usr/share/findbugs:
total 4
drwxr-xr-x. 3 root root 4096 Sep 29 14:29 etc/
lrwxrwxrwx. 1 root root   15 Feb 15  2014 lib -> /usr/share/java/

So, I did have a symbolic link from /usr/share/findbugs/lib to /usr/share/java

After doing "rm -rf /usr/share/findbugs", yum could install findbugs just fine.

Sorry for the false alarm.

Comment 8 Richard Fearn 2014-10-02 10:59:48 UTC
(In reply to Matthew Cline from comment #7)
> After doing "rm -rf /usr/share/findbugs", yum could install findbugs just
> fine.
> 
> Sorry for the false alarm.

No problem. Thanks for responding, and glad you could get it sorted.


Note You need to log in before you can comment on or make changes to this bug.