Bug 1366892 - Upgrade path broken with pocl-0.13-4.fc24 build
Summary: Upgrade path broken with pocl-0.13-4.fc24 build
Keywords:
Status: CLOSED DUPLICATE of bug 1325666
Alias: None
Product: Fedora
Classification: Fedora
Component: pocl
Version: 24
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Fabian Deutsch
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-14 09:36 UTC by Egor Zakharov
Modified: 2016-08-14 09:42 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-08-14 09:42:13 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Egor Zakharov 2016-08-14 09:36:07 UTC
Description of problem:
DNF detects file conflicts when installing both .x86_64 and .i686 version of this package:

Error: Transaction check error:
  file /etc/OpenCL/vendors/pocl.icd conflicts between attempted installs of pocl-0.13-4.fc24.i686 and pocl-0.13-4.fc24.x86_64
  file /usr/bin/pocl-standalone conflicts between attempted installs of pocl-0.13-4.fc24.i686 and pocl-0.13-4.fc24.x86_64

Error Summary
-------------



With this problem, I can't update my system from updates-testing.

Version-Release number of selected component (if applicable):
pocl-0.13-4.fc24

How reproducible:
Always

Steps to Reproduce:
1. Enable updates-testing
2. Try to update from previous version
3. ???
4. PROFIT!!

Actual results:
DNF denies to continue transaction, detecting file conflicts.

Expected results:
Update should go without any problems.

Additional info:
I think, if this package contains binaries and shared libraries, for proper upgrade path they should be separated to two subpackages: libs and main package. There libs package contains only shared libraries.

I think the problem occurred only because of this. Nothing stops packages from depending on the .i686 library from pocl package.

Comment 1 Igor Gnatenko 2016-08-14 09:42:13 UTC

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


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