Bug 1285582

Summary: rubygem-jgrep-1.4.1 is available
Product: [Fedora] Fedora Reporter: Upstream Release Monitoring <upstream-release-monitoring>
Component: rubygem-jgrepAssignee: Lubomir Rintel <lkundrak>
Status: CLOSED NEXTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: dcleal, lkundrak, lrintel
Target Milestone: ---Keywords: FutureFeature, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-09-21 15:24:10 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
dist-git patch for 1.4.0 update
none
Rebase-helper rebase-helper-debug.log log file. See for details and report the eventual error to rebase-helper https://github.com/phracek/rebase-helper/issues. none

Description Upstream Release Monitoring 2015-11-26 00:25:46 UTC
Latest upstream release: 1.4.0
Current version/release in rawhide: 1.3.3-6.fc23
URL: http://rubygems.org/gems/jgrep

Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy

More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring

Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.

Comment 1 Upstream Release Monitoring 2015-11-26 00:25:53 UTC
Failed to kick off scratch build.

spectool was unable to grab new sources

old source: JSON-Grep-6a96698f42475975375b027b4d3bf5d8511b4a8f.tar.gz
old sha256: 0f7c357d979dc1c7f22ad40df1adf549179a57bd583483ebe945ceb1a1fc975e

new source: ./JSON-Grep-6a96698f42475975375b027b4d3bf5d8511b4a8f.tar.gz
new sha256: 0f7c357d979dc1c7f22ad40df1adf549179a57bd583483ebe945ceb1a1fc975e

Comment 2 Dominic Cleal 2015-11-26 10:58:37 UTC
Created attachment 1099214 [details]
dist-git patch for 1.4.0 update

Attached is a suggested patch for the 1.4.0 update.  It also changes the source to rubygems.org to match other gems.

I'm maintaining the gem upstream now so if you'd like any help with the package, I can request ACLs.

Comment 3 Upstream Release Monitoring 2016-03-01 10:15:47 UTC
lkundrak's rubygem-jgrep-1.4.0-1.fc25 completed http://koji.fedoraproject.org/koji/buildinfo?buildID=740293

Comment 4 Upstream Release Monitoring 2016-05-18 00:19:41 UTC
Latest upstream release: 1.4.1
Current version/release in rawhide: 1.4.0-1.fc25
URL: http://rubygems.org/gems/jgrep

Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy

More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring

Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.

Based on the information from anitya:  https://release-monitoring.org/project/4657/

Comment 5 Upstream Release Monitoring 2016-05-18 00:19:52 UTC
Patching or scratch build for rubygem-jgrep-1.4.0 failed.

Comment 6 Upstream Release Monitoring 2016-05-18 00:19:53 UTC
Created attachment 1158571 [details]
Rebase-helper rebase-helper-debug.log log file.
See for details and report the eventual error to rebase-helper https://github.com/phracek/rebase-helper/issues.

Comment 7 Upstream Release Monitoring 2016-05-18 00:19:55 UTC
Patches were not touched. All were applied properly