Bug 2171458
Summary: | capnproto: FTBFS in Fedora rawhide/f38 | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Fedora Release Engineering <releng> |
Component: | capnproto | Assignee: | Neal Gompa <ngompa13> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | rawhide | CC: | fzatlouk, ngompa13 |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | RejectedFreezeException | ||
Fixed In Version: | capnproto-0.10.3-3.fc38 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2023-03-17 13:07:33 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: | 2117176, 2172252 |
Description
Fedora Release Engineering
2023-02-20 11:45:42 UTC
FEDORA-2023-0a2f5eea88 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-0a2f5eea88 Proposed as a Freeze Exception for 38-beta by Fedora user ngompa using the blocker tracking app because: Fix FTBFS/GCC13 issues with capnproto FEDORA-2023-0a2f5eea88 has been pushed to the Fedora 38 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-0a2f5eea88 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. Discussed in ticket: https://pagure.io/fedora-qa/blocker-review/issue/1055 The decision to classify this bug as an RejectedFreezeException was made: "There is no point in getting FTBFS fixes through the FE process." FEDORA-2023-0a2f5eea88 has been pushed to the Fedora 38 stable repository. If problem still persists, please make note of it in this bug report. Fixed. |