Description of problem:
# dnf install --allowerasing ./b/BEDTools-2.24.0-5.fc23.x86_64.rpm -y --exclude="BEDTools"
Last metadata expiration check performed 2:06:59 ago on Mon Sep 14 08:07:37 2015.
Package Arch Version Repository Size
BEDTools x86_64 2.24.0-5.fc23 @commandline 5.8 M
Install 1 Package
Total size: 5.8 M
Installed size: 11 M
Running transaction check
Transaction check succeeded.
Running transaction test
Error: Transaction check error:
file /usr/bin from install of BEDTools-2.24.0-5.fc23.x86_64 conflicts with file from package filesystem-3.2-34.fc23.x86_64
Related or possible duplicate of bug #1254005.
Just out of curiosity. What is the use case of such command?
OK, my intial command was a bit different, something like
# dnf install --allowerasing ./b/*.x86_64.rpm -y --exclude="BEDTools"
but BEDTools was still getting pulled in. So to figure out if something else is pulling it as a dependency or dnf is misbehaving I've devised the above command. My expectation was it will abort b/c no packages were specified as yum does.
This bug appears to have been reported against 'rawhide' during the Fedora 24 development cycle.
Changing version to '24'.
More information and reason for this action is here:
I have created a pull-request: https://github.com/rpm-software-management/dnf/pull/469
PR has been merged, so will be part of DNF 2.0