Bug 1190155 - RFE Build rubygem-jgrep for EPEL6
Summary: RFE Build rubygem-jgrep for EPEL6
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: rubygem-jgrep
Version: el6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Lubomir Rintel
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-02-06 13:53 UTC by Steve Traylen
Modified: 2016-10-09 15:39 UTC (History)
3 users (show)

Fixed In Version: rubygem-jgrep-1.4.1-1.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-10-09 14:48:16 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Steve Traylen 2015-02-06 13:53:41 UTC 
Hi,

Could you please build an EPEL6 verison rubygem-jgrep.

I checked and the .el7 src.rpm appears to build without modification.

Many Thanks

Steve.
Comment 1 Lubomir Rintel 2016-09-22 08:46:48 UTC 
Not really, sorry -- I no longer wish to maintain the package and intend to orphan it soon.

Leaving it open, perhaps the new maintainer would be willing to do the el6 build.

If you'd like to request the branch yourself then you're more than welcome.
Comment 2 Fedora Update System 2016-09-23 10:48:20 UTC 
rubygem-jgrep-1.4.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-496142bcae
Comment 3 Tuomo Soini 2016-09-24 19:51:45 UTC 
Doesn't quite work:

package: rubygem-jgrep-1.4.1-1.el6.noarch
  unresolved deps: 
     ruby(release) >= 0:1.8


There is nothing providing ruby(release) on rhel6 or epel6.
Comment 4 Fedora Update System 2016-10-09 14:48:16 UTC 
rubygem-jgrep-1.4.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.
Comment 5 Tuomo Soini 2016-10-09 15:39:48 UTC 
Read comment number 3 and try again.
Note You need to log in before you can comment on or make changes to this bug.