Bug 1335982 - [RFE] EPEL6 branch of vtable-dumper
Summary: [RFE] EPEL6 branch of vtable-dumper
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: vtable-dumper
Version: rawhide
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Orion Poplawski
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-05-13 17:42 UTC by Pat Riehecky
Modified: 2016-06-07 04:46 UTC (History)
2 users (show)

Fixed In Version: vtable-dumper-1.1-1.el6
Clone Of:
Environment:
Last Closed: 2016-06-07 04:46:39 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Pat Riehecky 2016-05-13 17:42:26 UTC
Description of problem:
Can vtable-dumper be branched for EPEL6?

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Richard Shaw 2016-05-13 18:29:32 UTC
Orion, would you like this one as well? It's required by abi-dumper and abi-tracker.

Comment 2 Orion Poplawski 2016-05-13 18:32:54 UTC
Sure.  Can you approve my branch requests in pkgdb?

Comment 3 Fedora Update System 2016-05-18 16:19:17 UTC
vtable-dumper-1.1-1.el6 has been submitted as an update to Fedora EPEL 6. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-010d891253

Comment 4 Fedora Update System 2016-05-21 05:49:42 UTC
vtable-dumper-1.1-1.el6 has been pushed to the Fedora EPEL 6 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-010d891253

Comment 5 Fedora Update System 2016-06-07 04:46:37 UTC
vtable-dumper-1.1-1.el6 has been pushed to the Fedora EPEL 6 stable repository. If problems still persist, please make note of it in this bug report.


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