Bug 1488132
Summary: | cyrus-imapd-3.0.4 is available | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Upstream Release Monitoring <upstream-release-monitoring> |
Component: | cyrus-imapd | Assignee: | Pavel Zhukov <pzhukov> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | rawhide | CC: | code, j, pokorra.mailinglists, pzhukov, vanmeeuwen+fedora, zdohnal |
Target Milestone: | --- | Keywords: | FutureFeature, Reopened, Triaged |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | cyrus-imapd-3.0.4-1.fc26 cyrus-imapd-3.0.4-1.fc27 | Doc Type: | Enhancement |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2017-09-15 22:22:38 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
2017-09-04 12:11:04 UTC
I have pushed new version with patched cassandane. Ideally cassandane should be updated as well. Cool, thanks; I was doing flood cleanup yesterday. It's safe to update Cassandane but since it's developed against what's in the head of the Cyrus tree, there's a load of additional tests that are going to fail. Figuring out which are expected to fail and which are valid failures would most likely involve annoying upstream even more than I already have. So I think it's best to just leave it alone for now, but I'll look into it if upstream starts mumbling about making a 3.2 release or maybe we decide to use the new "arbitrary branching" functionality to package up the 3.1 releases Seems like we hit new issue [1] it happens from time to time but mostly on ppc. [1] https://github.com/cyrusimap/cyrus-imapd/issues/1862 (In reply to Jason Tibbitts from comment #2) > Cool, thanks; I was doing flood cleanup yesterday. > Thank you for disabling failing test. Closing as rawhide. We're in f27 beta freeze anyway. Yes, but the release announcement says "This release contains important security fixes, as well as bug fixes" even though the release notes don't mention anything security related.... So I will push back to F26 just to be safe. cyrus-imapd-3.0.4-1.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-e4609f71f6 cyrus-imapd-3.0.4-1.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2017-689e9b1af5 cyrus-imapd-3.0.4-1.fc27 has been pushed to the Fedora 27 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-2017-689e9b1af5 cyrus-imapd-3.0.4-1.fc26 has been pushed to the Fedora 26 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-2017-e4609f71f6 cyrus-imapd-3.0.4-1.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report. cyrus-imapd-3.0.4-1.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report. |