Bug 869928
| Summary: | hop-2.3.1 is available | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Upstream Release Monitoring <upstream-release-monitoring> |
| Component: | hop | Assignee: | Michel Lind <michel> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rawhide | CC: | michel |
| 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: | 2012-11-20 03:18:22 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
2012-10-25 07:16:10 UTC
bigloo-3.9a-1.fc18,hop-2.4.0-0.1.rc2.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/bigloo-3.9a-1.fc18,hop-2.4.0-0.1.rc2.fc18 Package bigloo-3.9a-1.fc18, hop-2.4.0-0.2.rc3.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing bigloo-3.9a-1.fc18 hop-2.4.0-0.2.rc3.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-16940/bigloo-3.9a-1.fc18,hop-2.4.0-0.2.rc3.fc18 then log in and leave karma (feedback). hop-2.4.0-0.2.rc3.fc17,bigloo-3.9a-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/hop-2.4.0-0.2.rc3.fc17,bigloo-3.9a-1.fc17 hop-2.4.0-0.2.rc3.fc17, bigloo-3.9a-1.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report. |