Bug 1297505 - postgresql-9.4.5-1.fc23.i686 conflicts with file from package postgresql-9.4.5-1.fc23.x86_64
Summary: postgresql-9.4.5-1.fc23.i686 conflicts with file from package postgresql-9.4....
Keywords:
Status: CLOSED DUPLICATE of bug 1190346
Alias: None
Product: Fedora
Classification: Fedora
Component: postgresql
Version: 23
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Pavel Raiskup
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-11 17:17 UTC by Yupeng Chang
Modified: 2016-01-12 00:18 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-01-12 00:18:41 UTC
Type: Bug


Attachments (Terms of Use)

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


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