Bug 747593 - Please, create EL6 branch in EPEL
Summary: Please, create EL6 branch in EPEL
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: extremetuxracer
Version: el6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matěj Cepl
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-20 12:50 UTC by Matěj Cepl
Modified: 2018-04-11 12:38 UTC (History)
3 users (show)

Fixed In Version: extremetuxracer-0.4-8.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-02-19 19:00:54 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Matěj Cepl 2011-10-20 12:50:21 UTC 
Just beacuse it is very important enterprise package, isn't it?
Comment 1 Nils Philippsen 2011-10-20 15:19:54 UTC 
Do you volunteer as EPEL maintainer ;-)?
Comment 2 Matěj Cepl 2011-12-13 12:04:01 UTC 
Yes, of course.
Comment 3 Nils Philippsen 2011-12-13 15:42:20 UTC 
Added package change request to bug #436126.
Comment 4 Nils Philippsen 2011-12-13 17:41:03 UTC 
Branch created.
Comment 5 Fedora Update System 2012-02-02 23:21:06 UTC 
extremetuxracer-0.4-8.el6 has been submitted as an update for Fedora EPEL 6.
https://admin.fedoraproject.org/updates/extremetuxracer-0.4-8.el6
Comment 6 Fedora Update System 2012-02-04 01:05:20 UTC 
Package extremetuxracer-0.4-8.el6:
* should fix your issue,
* was pushed to the Fedora EPEL 6 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=epel-testing extremetuxracer-0.4-8.el6'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-EPEL-2012-0320/extremetuxracer-0.4-8.el6
then log in and leave karma (feedback).
Comment 7 Fedora Update System 2012-02-19 19:00:54 UTC 
extremetuxracer-0.4-8.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.