Bug 1124040

Summary: drupal7-crumbs-2.0-beta19 is available
Product: [Fedora] Fedora Reporter: Upstream Release Monitoring <upstream-release-monitoring>
Component: drupal7-crumbsAssignee: Peter Borsa <hello>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: hello, shawn
Target Milestone: ---Keywords: FutureFeature, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: drupal7-crumbs-2.0-0.8.beta19.el5 Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-09-10 13:28:36 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:

Description Upstream Release Monitoring 2014-07-28 21:09:44 UTC
Latest upstream release: 2.0-beta18
Current version/release in Fedora Rawhide: 2.0-0.7.beta13.fc21
URL: http://drupal.org/project/crumbs

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 Upstream Release Monitoring 2014-08-04 19:13:51 UTC
Latest upstream release: 2.0-beta19
Current version/release in Fedora Rawhide: 2.0-0.7.beta13.fc21
URL: http://drupal.org/project/crumbs

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 2 Peter Borsa 2014-08-06 18:45:36 UTC
I'll update it tomorrow.

Comment 3 Fedora Update System 2014-08-31 21:52:31 UTC
drupal7-crumbs-2.0-0.8.beta19.el6 has been submitted as an update for Fedora EPEL 6.
https://admin.fedoraproject.org/updates/drupal7-crumbs-2.0-0.8.beta19.el6

Comment 4 Fedora Update System 2014-08-31 21:52:36 UTC
drupal7-crumbs-2.0-0.8.beta19.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/drupal7-crumbs-2.0-0.8.beta19.fc19

Comment 5 Fedora Update System 2014-08-31 21:52:42 UTC
drupal7-crumbs-2.0-0.8.beta19.el5 has been submitted as an update for Fedora EPEL 5.
https://admin.fedoraproject.org/updates/drupal7-crumbs-2.0-0.8.beta19.el5

Comment 6 Fedora Update System 2014-08-31 21:52:47 UTC
drupal7-crumbs-2.0-0.8.beta19.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/drupal7-crumbs-2.0-0.8.beta19.fc20

Comment 7 Fedora Update System 2014-09-02 03:53:34 UTC
Package drupal7-crumbs-2.0-0.8.beta19.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 drupal7-crumbs-2.0-0.8.beta19.el6'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-2357/drupal7-crumbs-2.0-0.8.beta19.el6
then log in and leave karma (feedback).

Comment 8 Fedora Update System 2014-09-10 13:28:36 UTC
drupal7-crumbs-2.0-0.8.beta19.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 9 Fedora Update System 2014-09-10 13:30:47 UTC
drupal7-crumbs-2.0-0.8.beta19.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 10 Fedora Update System 2014-09-24 03:47:36 UTC
drupal7-crumbs-2.0-0.8.beta19.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 11 Fedora Update System 2014-09-24 03:48:40 UTC
drupal7-crumbs-2.0-0.8.beta19.el5 has been pushed to the Fedora EPEL 5 stable repository.  If problems still persist, please make note of it in this bug report.