Bug 990230 - xmedcon-devel: conflict between 32 and 64 bit files
Summary: xmedcon-devel: conflict between 32 and 64 bit files
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: xmedcon
Version: 26
Hardware: Unspecified
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Ankur Sinha (FranciscoD)
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-07-30 15:43 UTC by Edgar Hoch
Modified: 2018-05-29 11:57 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-05-29 11:57:49 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Edgar Hoch 2013-07-30 15:43:58 UTC
Description of problem:
xmedcon-devel 32 and 64 bit version cannot be installed at the same time because of conflicting files.

Version-Release number of selected component (if applicable):
xmedcon-devel-0.10.7-10.fc19.x86_64
xmedcon-devel-0.10.7-10.fc19.i686

How reproducible:
Always.

Steps to Reproduce:
1. Choose a F19 system without installed xmedcon-devel packages.
2. Run "yum -y install xmedcon-devel.x86_64 xmedcon-devel.i686"

Actual results:

Transaction check error:
  file /usr/bin/xmedcon-config conflicts between attempted installs of xmedcon-devel-0.10.7-10.fc19.i686 and xmedcon-devel-0.10.7-10.fc19.x86_64
  file /usr/include/xmedcon/m-config.h conflicts between attempted installs of xmedcon-devel-0.10.7-10.fc19.i686 and xmedcon-devel-0.10.7-10.fc19.x86_64
  file /usr/include/xmedcon/m-depend.h conflicts between attempted installs of xmedcon-devel-0.10.7-10.fc19.i686 and xmedcon-devel-0.10.7-10.fc19.x86_64


Expected results:
yum installes both packages without error.

Comment 1 Ankur Sinha (FranciscoD) 2014-01-05 15:21:18 UTC
Hi,

Hrm. Will have to look into this one. Thanks for your bug report. 

Thanks
Warm regards,
Ankur

Comment 2 Fedora End Of Life 2015-01-09 22:14:12 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 3 Fedora End Of Life 2015-02-18 14:03:06 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 4 Jaroslav Reznik 2015-03-03 16:54:20 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22

Comment 5 Fedora End Of Life 2016-07-19 20:02:41 UTC
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 6 Edgar Hoch 2016-07-19 20:52:44 UTC
The problem still exists on Fedora 24:

# LANG=C dnf install xmedcon-devel.x86_64 xmedcon-devel.i686
[...]
Error: Transaction check error:
  file /usr/bin/xmedcon-config conflicts between attempted installs of xmedcon-devel-0.10.7-17.fc24.i686 and xmedcon-devel-0.10.7-17.fc24.x86_64
  file /usr/include/xmedcon/m-config.h conflicts between attempted installs of xmedcon-devel-0.10.7-17.fc24.i686 and xmedcon-devel-0.10.7-17.fc24.x86_64
  file /usr/include/xmedcon/m-depend.h conflicts between attempted installs of xmedcon-devel-0.10.7-17.fc24.i686 and xmedcon-devel-0.10.7-17.fc24.x86_64

Comment 7 Fedora End Of Life 2017-07-25 18:33:44 UTC
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '24'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 8 Edgar Hoch 2017-07-25 20:35:59 UTC
The problem still exists on Fedora 26:

# LANG=C dnf install xmedcon-devel.x86_64 xmedcon-devel.i686
[...]
Running transaction check
Transaction check succeeded.
Running transaction test
The downloaded packages were saved in cache until the next successful transaction.
You can remove cached packages by executing 'dnf clean packages'.
Error: Transaction check error:
  file /usr/bin/xmedcon-config conflicts between attempted installs of xmedcon-devel-0.10.7-18.fc26.x86_64 and xmedcon-devel-0.10.7-18.fc26.i686
  file /usr/include/xmedcon/m-config.h conflicts between attempted installs of xmedcon-devel-0.10.7-18.fc26.x86_64 and xmedcon-devel-0.10.7-18.fc26.i686
  file /usr/include/xmedcon/m-depend.h conflicts between attempted installs of xmedcon-devel-0.10.7-18.fc26.x86_64 and xmedcon-devel-0.10.7-18.fc26.i686

Comment 9 Ankur Sinha (FranciscoD) 2018-01-01 16:36:04 UTC
I'm going to take this up with upstream. It's not good practice to generate arch specific headers, and the config script should ideally be arch independent too.

Comment 10 Ankur Sinha (FranciscoD) 2018-01-07 17:41:04 UTC
Upstream has fixed this and will make a new 0.15 release soon. I'll update the Fedora bits when that happens.

Comment 11 Fedora End Of Life 2018-05-03 08:15:35 UTC
This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '26'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 26 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 12 Fedora End Of Life 2018-05-29 11:57:49 UTC
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26
is no longer maintained, which means that it will not receive any
further security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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