Bug 1801768 - cannot install both i686 and x86_64 version of atk-devel
Summary: cannot install both i686 and x86_64 version of atk-devel
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: atk
Version: 30
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-02-11 15:39 UTC by insaner
Modified: 2020-05-26 18:18 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: ---
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-05-26 18:18:04 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description insaner 2020-02-11 15:39:04 UTC
Description of problem:


file /usr/share/gir-1.0/Atk-1.0.gir from install of atk-devel.x86_64 conflicts with file from package atk-devel.i686


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

atk-devel-2.32.0-1.fc30.x86_64.rpm 

How reproducible:

install atk-devel.i686, then, try to install atk-devel.x86_64


Actual results:


# yum install atk-devel.x86_64
Last metadata expiration check: 2:18:30 ago on Tue 11 Feb 2020 08:11:12 AM EST.
Dependencies resolved.
======================================================================================================================================================================================================================================================
 Package                                                     Architecture                                             Version                                                          Repository                                                Size
======================================================================================================================================================================================================================================================
Installing:
 atk-devel                                                   x86_64                                                   2.32.0-1.fc30                                                    fedora                                                   189 k

Transaction Summary
======================================================================================================================================================================================================================================================
Install  1 Package

Total download size: 189 k
Installed size: 2.3 M
Is this ok [y/N]: y
Downloading Packages:
atk-devel-2.32.0-1.fc30.x86_64.rpm                                                                                                                                                                                    224 kB/s | 189 kB     00:00    
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Total                                                                                                                                                                                                                 185 kB/s | 189 kB     00:01     
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 'yum clean packages'.
Error: Transaction test error:
  file /usr/share/gir-1.0/Atk-1.0.gir from install of atk-devel-2.32.0-1.fc30.x86_64 conflicts with file from package atk-devel-2.32.0-1.fc30.i686
  file /usr/share/gtk-doc/html/atk/api-index-full.html from install of atk-devel-2.32.0-1.fc30.x86_64 conflicts with file from package atk-devel-2.32.0-1.fc30.i686



Expected results:

Should install atk-devel.x86_64 without problem (atk.i686 and atk.x86_64 installed without issue).


Additional info:

Same thing happens with gcc and glibc-common:

# rpmu gcc-9.2.1-1.fc30.x86_64.rpm glibc-common-2.29-9.fc30.x86_64.rpm 
Verifying...                          ################################# [100%]
Preparing...                          ################################# [100%]
        file /usr/bin/ldd from install of glibc-common-2.29-9.fc30.x86_64 conflicts with file from package glibc-common-2.29-9.fc30.i686
        file /usr/libexec/getconf/default from install of gcc-9.2.1-1.fc30.x86_64 conflicts with file from package gcc-9.2.1-1.fc30.i686

Comment 1 Ben Cotton 2020-04-30 20:27:40 UTC
This message is a reminder that Fedora 30 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-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 '30'.

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 30 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 2 Ben Cotton 2020-05-26 18:18:04 UTC
Fedora 30 changed to end-of-life (EOL) status on 2020-05-26. Fedora 30 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.