Bug 890526 - -devel multilib conflict: python gdb scripts #2
Summary: -devel multilib conflict: python gdb scripts #2
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: glib2
Version: 17
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact: Fedora Extras Quality Assurance
URL: http://lists.fedoraproject.org/piperm...
Whiteboard:
Depends On: 525213
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-12-27 14:37 UTC by Jan Kratochvil
Modified: 2013-08-01 04:38 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-08-01 04:38:02 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Jan Kratochvil 2012-12-27 14:37:06 UTC
Description of problem:
multilib conflict due to different build timestamps and Python embedding the *.py timestamp into the *.pyc/*.pyo files.

Version-Release number of selected component (if applicable):
glib2-devel-2.32.4-2.fc17

Steps to Reproduce:
yum install glib2-devel.{x86_64,i686}

Actual results:
  file /usr/share/glib-2.0/gdb/glib.pyc from install of
glib2-devel-2.32.4-2.fc17.i686 conflicts with file from package
glib2-devel-2.32.4-2.fc17.x86_64
  file /usr/share/glib-2.0/gdb/glib.pyo from install of
glib2-devel-2.32.4-2.fc17.i686 conflicts with file from package
glib2-devel-2.32.4-2.fc17.x86_64
  file /usr/share/glib-2.0/gdb/gobject.pyc from install of
glib2-devel-2.32.4-2.fc17.i686 conflicts with file from package
glib2-devel-2.32.4-2.fc17.x86_64
  file /usr/share/glib-2.0/gdb/gobject.pyo from install of
glib2-devel-2.32.4-2.fc17.i686 conflicts with file from package
glib2-devel-2.32.4-2.fc17.x86_64

Expected results:
Installed package.

Additional info:
"make install" of the upstream package "touches" the target installed *.py file.
So best upstream should restore the original *.py timestamp for the installed file.
Or at least restore it in the glib2.spec file.

Comment 1 Jan Kratochvil 2012-12-27 16:11:50 UTC
It is duplicate of Bug 718404 but that one was fixed only for f18+.

Comment 2 Fedora End Of Life 2013-07-04 00:41:08 UTC
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. 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 WONTFIX if it remains open with a Fedora 
'version' of '17'.

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 prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 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 to Fedora 17's end of life.

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 2013-08-01 04:38:05 UTC
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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.

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.