Bug 907094

Summary: erlang-ebloom-1.1.2 is available
Product: [Fedora] Fedora Reporter: Upstream Release Monitoring <upstream-release-monitoring>
Component: erlang-ebloomAssignee: Peter Lemenkov <lemenkov>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: lemenkov
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: 2013-03-10 12:13:53 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:
Bug Depends On:    
Bug Blocks: 913029    

Description Upstream Release Monitoring 2013-02-03 09:53:45 UTC
Latest upstream release: 1.1.2
Current version in Fedora Rawhide: 1.1.1
URL: https://github.com/basho/ebloom/tags

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

Comment 1 Fedora Update System 2013-03-10 12:11:33 UTC
erlang-js-1.2.2-1.fc18, erlang-bitcask-1.6.0-1.fc18, erlang-lager-1.2.2-1.fc18, erlang-ebloom-1.1.2-1.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/erlang-ebloom-1.1.2-1.fc18,erlang-lager-1.2.2-1.fc18,erlang-bitcask-1.6.0-1.fc18,erlang-js-1.2.2-1.fc18

Comment 2 Fedora Update System 2013-03-10 12:13:00 UTC
erlang-ebloom-1.1.2-1.el6 has been submitted as an update for Fedora EPEL 6.
https://admin.fedoraproject.org/updates/erlang-ebloom-1.1.2-1.el6

Comment 3 Fedora Update System 2013-03-26 16:39:52 UTC
erlang-ebloom-1.1.2-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.