Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1517569 - bcc-tools is conflicting with postfix
Summary: bcc-tools is conflicting with postfix
Keywords:
Status: CLOSED DUPLICATE of bug 1517408
Alias: None
Product: Fedora
Classification: Fedora
Component: bcc
Version: 27
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jiri Olsa
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-11-26 22:38 UTC by Jérôme Fenal
Modified: 2017-11-26 22:52 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-11-26 22:52:25 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Jérôme Fenal 2017-11-26 22:38:27 UTC
Description of problem:

Thee bcc-tools package has a conflicting file /usr/share/man/man8/trace.8.gz also present in postfix.

Version-Release number of selected component (if applicable):

bcc-tools-0.4.0-1.fc27.noarch

How reproducible:


Steps to Reproduce:
1. Install postfix (dnf install postfix)
2. Try to install bcc-tools (dnf install bcc-tools)

Actual results:

Error: Transaction check error:
  file /usr/share/man/man8/trace.8.gz from install of bcc-tools-0.4.0-1.fc27.noarch conflicts with file from package postfix-2:3.2.4-1.fc27.x86_64

Expected results:

Pasckage installed without conflicting with postfix

Additional info:

Comment 1 Rafael Fonseca 2017-11-26 22:52:25 UTC
Thank you for the report.

This has already been reported and the fix will be applied to all affected Fedora versions (26, 27 and rawhide). So closing this bug.

*** This bug has been marked as a duplicate of bug 1517408 ***


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