Bug 1297505

Summary: postgresql-9.4.5-1.fc23.i686 conflicts with file from package postgresql-9.4.5-1.fc23.x86_64
Product: [Fedora] Fedora Reporter: Yupeng Chang <changyp6>
Component: postgresqlAssignee: Pavel Raiskup <praiskup>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 23CC: devrim, hhorak, jmlich83, jstanek, pkajaba, praiskup, tgl
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-01-12 00:18:41 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:

Description Yupeng Chang 2016-01-11 17:17:51 UTC 
Description of problem:
postgresql-9.4.5-1.fc23.i686 conflicts with file from package postgresql-9.4.5-1.fc23.x86_64

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


How reproducible:
sudo dnf install postgresql-devel.i686 postgresql-devel.x86_64

Steps to Reproduce:
1.
2.
3.

Actual results:
dnf reports errors:
  file /usr/share/doc/postgresql/README.rpm-dist from install of postgresql-9.4.5-1.fc23.i686 conflicts with file from package postgresql-9.4.5-1.fc23.x86_64
  file /usr/include/pg_config_ext.h from install of postgresql-devel-9.4.5-1.fc23.i686 conflicts with file from package postgresql-devel-9.4.5-1.fc23.x86_64
  file /usr/include/pgsql/server/pg_config_ext.h from install of postgresql-devel-9.4.5-1.fc23.i686 conflicts with file from package postgresql-devel-9.4.5-1.fc23.x86_64

Expected results:

Both i686 and x86_64 devel packages can be installed.

Additional info:
Comment 1 Pavel Raiskup 2016-01-12 00:18:41 UTC 
This has been fixed in git [1] but not yet updated in F23, thanks for the
report.
[1] http://pkgs.fedoraproject.org/cgit/rpms/postgresql.git/commit/?h=f23&id=ca2f2daa2dde4650d1a0134d917c036337a00c25

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