Bug 2437452
| Summary: | python-setuptools-82.0.1 is available | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Upstream Release Monitoring <upstream-release-monitoring> |
| Component: | python-setuptools | Assignee: | Tomáš Hrnčiar <thrnciar> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rawhide | CC: | cstratak, mhroncok, python-maint, python-packagers-sig, thrnciar |
| Target Milestone: | --- | Keywords: | FutureFeature, Triaged |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | python-setuptools-82.0.1-1.fc45 | Doc Type: | --- |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2026-05-12 14:20:15 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: | 2468411 | ||
|
Description
Upstream Release Monitoring
2026-02-06 22:38:03 UTC
https://setuptools.pypa.io/en/stable/history.html#v81-0-0 does not mention setup.py install removal yet. Releases retrieved: 82.0.0 Upstream release that is considered latest: 82.0.0 Current version/release in rawhide: 80.10.2-1.fc44 URL: https://pypi.python.org/pypi/setuptools Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/ More information about the service that created this bug can be found at: https://docs.fedoraproject.org/en-US/package-maintainers/Upstream_Release_Monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from Anitya: https://release-monitoring.org/project/4021/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/python-setuptools https://setuptools.pypa.io/en/stable/history.html#v82-0-0 removed pkg_resources. I expect that will hurt. We could impact check 81 and update to 81 first, possibly even in Fedora 44. But I don't see much benefit in that. 82 will definitely be a Fedora 45+ material, most likely with a system wide chnage proposal. Releases retrieved: 82.0.1 Upstream release that is considered latest: 82.0.1 Current version/release in rawhide: 80.10.2-1.fc44 URL: https://pypi.python.org/pypi/setuptools Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/ More information about the service that created this bug can be found at: https://docs.fedoraproject.org/en-US/package-maintainers/Upstream_Release_Monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from Anitya: https://release-monitoring.org/project/4021/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/python-setuptools FEDORA-2026-812f148ac7 (python-pyramid-2.0.2-12.fc45, python-setuptools80-80.10.2-3.fc45, and 1 more) has been submitted as an update to Fedora 45. https://bodhi.fedoraproject.org/updates/FEDORA-2026-812f148ac7 FEDORA-2026-812f148ac7 (python-pyramid-2.0.2-12.fc45, python-setuptools80-80.10.2-3.fc45, and 1 more) has been pushed to the Fedora 45 stable repository. If problem still persists, please make note of it in this bug report. |