Bug 2013807
| Summary: | containerd-1.5.8 is available | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Upstream Release Monitoring <upstream-release-monitoring> |
| Component: | containerd | Assignee: | Olivier Lemasle <o.lemasle> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rawhide | CC: | go-sig, maxwell, o.lemasle |
| Target Milestone: | --- | Keywords: | FutureFeature, Triaged |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | containerd-1.5.8-1.fc36 containerd-1.5.8-1.fc34 containerd-1.5.8-1.fc35 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-11-22 22:15:08 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: | 2024384 | ||
|
Description
Upstream Release Monitoring
2021-10-13 19:50:40 UTC
Hi Olivier, The new release is out. Github is rate limiting Antiya, so it hasn't updated this bug yet. I marked this bug as blocking the new `moby-engine` release-monitoring bug, because the new version of Moby depends on the new version of Containerd. When you update these packages together, how do you normally handle it? Is it necessary to create a side tag? It probably makes sense to make me a co-maintainer of this package, as well. Thanks, Maxwell > The new release is out. Github is rate limiting Antiya, so it hasn't updated this bug yet.
Actually, Antiya has already picked up on the new update, but because this pre-release has a greater number then the actual release, it got confused. I misread the version number when I made my last post. I have seen this happen with a couple other packages; I will file a bug against Anyiya when I have a chance.
FEDORA-2021-a9338f491d has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2021-a9338f491d FEDORA-2021-a9338f491d has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2021-79ba5abef6 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2021-79ba5abef6 FEDORA-2021-eb2742b148 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-eb2742b148 FEDORA-2021-eb2742b148 has been pushed to the Fedora 34 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-eb2742b148` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-eb2742b148 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2021-79ba5abef6 has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-79ba5abef6` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-79ba5abef6 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2021-eb2742b148 has been pushed to the Fedora 34 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2021-79ba5abef6 has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report. |