Releases retrieved: 2.0.2 Upstream release that is considered latest: 2.0.2 Current version/release in rawhide: 2.0.1^20230725giteeb51ad-2.fc39 URL: https://github.com/Toblerity/Shapely 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/4023/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/python-shapely
Scratch build failed. Details below: BuilderException: Build failed: There is a syntax error in updated specfile. See attached diff for the changes. Traceback: File "/usr/local/lib/python3.11/site-packages/hotness/use_cases/package_scratch_build_use_case.py", line 56, in build result = self.builder.build(request.package, request.opts) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/site-packages/hotness/builders/koji.py", line 205, in build raise BuilderException(str(exc), value=output) If you think this issue is caused by some bug in the-new-hotness, please report it on the-new-hotness issue tracker: https://github.com/fedora-infra/the-new-hotness/issues
Created attachment 1993874 [details] Update to 2.0.2 (#2244165)
(In reply to Upstream Release Monitoring from comment #2) > Created attachment 1993874 [details] > Update to 2.0.2 (#2244165) This is interesting. It seems Anitya tries to be smart about where to put the new version. I never looked at it closely before. But here it fails to handle the previous version (a post release) correctly. Did I mention forge macros and the way it is able to handle commits and even puts a dat in the release?
(In reply to Sandro from comment #3) > Did I mention forge macros and the way it is able to handle commits and even > puts a dat in the release? Apart from not being able to type faultlessly before my first coffee, I was not entirely correct about the date. But see my comment in the PR commit (https://src.fedoraproject.org/fork/gui1ty/rpms/python-shapely/c/e406ebcfba3493dc1ec51f4f1fe274c0ea2a611e?branch=rawhide).
FEDORA-2023-be06f68d98 has been submitted as an update to Fedora 40. https://bodhi.fedoraproject.org/updates/FEDORA-2023-be06f68d98
FEDORA-2023-be06f68d98 has been pushed to the Fedora 40 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2023-4e85e98a63 has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2023-4e85e98a63
FEDORA-2023-4e85e98a63 has been pushed to the Fedora 39 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-4e85e98a63` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-4e85e98a63 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-4e85e98a63 has been pushed to the Fedora 39 stable repository. If problem still persists, please make note of it in this bug report.