Bug 2340619
| Summary: | httpie: FTBFS in Fedora rawhide/f42 | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Fedora Release Engineering <releng> | ||||||||
| Component: | httpie | Assignee: | Miro Hrončok <mhroncok> | ||||||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | unspecified | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 42 | CC: | mhroncok, mikel, python-packagers-sig | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | Unspecified | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | httpie-3.2.4-3.fc41 httpie-3.2.4-3.fc40 httpie-3.2.4-3.fc42 | Doc Type: | --- | ||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2025-03-08 01:23:57 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: | 2300528 | ||||||||||
| Attachments: |
|
||||||||||
|
Description
Fedora Release Engineering
2025-01-22 20:29:57 UTC
Created attachment 2070397 [details]
build.log
file build.log too big, will only attach last 32768 bytes
Created attachment 2070398 [details]
root.log
file root.log too big, will only attach last 32768 bytes
Created attachment 2070399 [details]
state.log
This bug appears to have been reported against 'rawhide' during the Fedora Linux 42 development cycle. Changing version to 42. FEDORA-2025-8eef31cca3 (httpie-3.2.4-3.fc41) has been submitted as an update to Fedora 41. https://bodhi.fedoraproject.org/updates/FEDORA-2025-8eef31cca3 FEDORA-2025-fa9141f051 (httpie-3.2.4-3.fc40) has been submitted as an update to Fedora 40. https://bodhi.fedoraproject.org/updates/FEDORA-2025-fa9141f051 FEDORA-2025-0c92a48ab7 (httpie-3.2.4-3.fc42) has been submitted as an update to Fedora 42. https://bodhi.fedoraproject.org/updates/FEDORA-2025-0c92a48ab7 FEDORA-2025-0c92a48ab7 has been pushed to the Fedora 42 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-0c92a48ab7` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-0c92a48ab7 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2025-8eef31cca3 has been pushed to the Fedora 41 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-8eef31cca3` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-8eef31cca3 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2025-fa9141f051 has been pushed to the Fedora 40 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-fa9141f051` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-fa9141f051 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2025-8eef31cca3 (httpie-3.2.4-3.fc41) has been pushed to the Fedora 41 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2025-fa9141f051 (httpie-3.2.4-3.fc40) has been pushed to the Fedora 40 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2025-0c92a48ab7 (httpie-3.2.4-3.fc42) has been pushed to the Fedora 42 stable repository. If problem still persists, please make note of it in this bug report. |