Bug 2335653
| Summary: | poetry-2.1.1 is available | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Upstream Release Monitoring <upstream-release-monitoring> |
| Component: | poetry | Assignee: | Tomáš Hrnčiar <thrnciar> |
| Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rawhide | CC: | gbcox, mhroncok, python-packagers-sig, thrnciar |
| Target Milestone: | --- | Keywords: | FutureFeature, Triaged |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2025-03-18 13:45:50 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: | 2351574 | ||
| Attachments: | |||
|
Description
Upstream Release Monitoring
2025-01-05 14:29:51 UTC
Created attachment 2064733 [details]
Update to 2.0.0 (#2335653)
the-new-hotness/release-monitoring.org's scratch build of poetry-2.0.0-1.fc40.src.rpm for rawhide failed http://koji.fedoraproject.org/koji/taskinfo?taskID=127576470 Releases retrieved: 2.0.1 Upstream release that is considered latest: 2.0.1 Current version/release in rawhide: 1.8.5-1.fc42 URL: https://github.com/python-poetry/poetry 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/17793/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/poetry Created attachment 2065646 [details]
Update to 2.0.1 (#2335653)
the-new-hotness/release-monitoring.org's scratch build of poetry-2.0.1-1.fc40.src.rpm for rawhide failed http://koji.fedoraproject.org/koji/taskinfo?taskID=127794425 Releases retrieved: 2.1.0 Upstream release that is considered latest: 2.1.0 Current version/release in rawhide: 1.8.5-2.fc42 URL: https://github.com/python-poetry/poetry 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/17793/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/poetry Created attachment 2076630 [details]
Update to 2.1.0 (#2335653)
the-new-hotness/release-monitoring.org's scratch build of poetry-2.1.0-1.fc40.src.rpm for rawhide failed http://koji.fedoraproject.org/koji/taskinfo?taskID=129264821 Releases retrieved: 2.1.1 Upstream release that is considered latest: 2.1.1 Current version/release in rawhide: 1.8.5-2.fc42 URL: https://github.com/python-poetry/poetry 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/17793/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/poetry Created attachment 2076789 [details]
Update to 2.1.1 (#2335653)
the-new-hotness/release-monitoring.org's scratch build of poetry-2.1.1-1.fc40.src.rpm for rawhide failed http://koji.fedoraproject.org/koji/taskinfo?taskID=129320241 This is blocking a yubikey-manager upgrade. Yubikey is used for hardware tokens, so it's important that the software be kept as up-to-date as possible. I noticed that you only have put it in rawhide (43). Could you please consider F42 and ideally also F41. Thank you very much! Created attachment 2080019 [details]
yubikey-manager - revert changes in pyproject.toml to make it buildable with poetry-core on F42
Hi,
poetry-core>=2 contains breaking changes which I'd rather not bring into F42 nor F41. I've managed to build it on F42 when I reverted the changes in pyproject.toml file. See the attached patch.
(In reply to Tomáš Hrnčiar from comment #14) > Created attachment 2080019 [details] > yubikey-manager - revert changes in pyproject.toml to make it buildable with > poetry-core on F42 > > Hi, > > poetry-core>=2 contains breaking changes which I'd rather not bring into F42 > nor F41. I've managed to build it on F42 when I reverted the changes in > pyproject.toml file. See the attached patch. Thanks for the patch. Much appreciated. I'll try it and if it doesn't work I'll contact upstream for suggestions. |