Bug 1266181 - There is no 32-bit apitrace in x86_64 repositories
Summary: There is no 32-bit apitrace in x86_64 repositories
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: apitrace
Version: 22
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Sandro Mani
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-09-24 17:13 UTC by Tomi Leppänen
Modified: 2016-07-19 18:01 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-19 18:01:06 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Tomi Leppänen 2015-09-24 17:13:23 UTC 
There is no i686 version of apitrace in x86_64 repositories. It is needed to trace 32-bit programs.

dnf info apitrace lists only x86_64 version on Fedora 22:
$ dnf info apitrace
Last metadata expiration check performed 1 day, 7:22:54 ago on Wed Sep 23 12:49:05 2015.
Available Packages
Name        : apitrace
Arch        : x86_64
Epoch       : 0
Version     : 6.1
Release     : 3.fc22
Size        : 1.3 M
Repo        : fedora
Summary     : Tools for tracing OpenGL
URL         : http://apitrace.github.io/
License     : MIT
Description : apitrace consists of a set of tools to:
...
$
Comment 1 Sandro Mani 2015-09-25 21:47:28 UTC 
See https://pagure.io/mash/issue/4
Comment 2 Fedora End Of Life 2016-07-19 18:01:06 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.
Note You need to log in before you can comment on or make changes to this bug.