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

Summary:	bcc-tools is conflicting with postfix
Product:	[Fedora] Fedora	Reporter:	Jérôme Fenal <jfenal>
Component:	bcc	Assignee:	Jiri Olsa <jolsa>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	27	CC:	jolsa, rdossant, skozina
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-11-26 22:52:25 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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 ***