Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1240307 - please update for EPEL6
Summary: please update for EPEL6
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: scorep
Version: el6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Dave Love
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 1240306
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-07-06 14:10 UTC by Dave Love
Modified: 2015-12-15 18:49 UTC (History)
1 user (show)

Fixed In Version: scorep-1.4.2-2.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-12-15 18:49:02 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Dave Love 2015-07-06 14:10:21 UTC 
Description of problem:

This would be necessary in conjunction with #1240306.
The f23 srpm builds <http://copr.fedoraproject.org/coprs/loveshack/livhpc/build/101708/>.
Comment 1 Orion Poplawski 2015-07-06 16:57:41 UTC 
I think this is new enough that it seems reasonable.  At some point though we really should stop breaking ABI.  Shall I add you to the scorep (and cube) packages so you can take care of this?
Comment 2 Dave Love 2015-07-12 21:33:06 UTC 
(In reply to Orion Poplawski from comment #1)
> I think this is new enough that it seems reasonable.  At some point though
> we really should stop breaking ABI.  

I thought there was already an update in testing, but I realize it's only
in testing for EPEL6.

> Shall I add you to the scorep (and
> cube) packages so you can take care of this?

OK.
Comment 3 Orion Poplawski 2015-07-12 23:32:36 UTC 
I've pushed it (1.3) to stable.  Once that is complete you can update to 1.4.2 if you want.
Note You need to log in before you can comment on or make changes to this bug.