Bug 856330 - iprutils-2.3.11-1.fc18 conflicts with itself
iprutils-2.3.11-1.fc18 conflicts with itself
Status: CLOSED CURRENTRELEASE
Product: Fedora
Classification: Fedora
Component: iprutils (Show other bugs)
18
powerpc Linux
unspecified Severity unspecified
: ---
: ---
Assigned To: David Woodhouse
Fedora Extras Quality Assurance
:
Depends On:
Blocks: F18Alphappc
  Show dependency treegraph
 
Reported: 2012-09-11 15:26 EDT by David Aquilina
Modified: 2014-06-23 20:19 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-09-11 15:47:00 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
proposed patch (1.37 KB, patch)
2012-09-11 15:28 EDT, David Aquilina
no flags Details | Diff

  None (edit)
Description David Aquilina 2012-09-11 15:26:37 EDT
Description of problem:

iprutils-2.3.11-1.fc18 conflicts with itself: 

Transaction Check Error:
  file /usr/sbin/iprconfig conflicts between attempted installs of iprutils-2.3.11-1.fc18.ppc64 and iprutils-2.3.11-1.fc18.ppc64
  file /usr/sbin/iprdbg conflicts between attempted installs of iprutils-2.3.11-1.fc18.ppc64 and iprutils-2.3.11-1.fc18.ppc64
  file /usr/sbin/iprdump conflicts between attempted installs of iprutils-2.3.11-1.fc18.ppc64 and iprutils-2.3.11-1.fc18.ppc64
  file /usr/sbin/iprinit conflicts between attempted installs of iprutils-2.3.11-1.fc18.ppc64 and iprutils-2.3.11-1.fc18.ppc64
  file /usr/sbin/iprupdate conflicts between attempted installs of iprutils-2.3.11-1.fc18.ppc64 and iprutils-2.3.11-1.fc18.ppc64

I think there's some weirdness in the specfile, but was able to make some minor changes to fix the above errors.
Comment 1 David Aquilina 2012-09-11 15:28:19 EDT
Created attachment 611898 [details]
proposed patch
Comment 2 Karsten Hopp 2012-09-11 15:47:00 EDT
looks good, fixed in iprutils-2.3.11-2.fc18

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