Bug 2150782
| Summary: | python-filelock-3.8.2 is available | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Upstream Release Monitoring <upstream-release-monitoring> | ||||
| Component: | python-filelock | Assignee: | Lumír Balhar <lbalhar> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | rawhide | CC: | lbalhar, logans, python-packagers-sig | ||||
| Target Milestone: | --- | Keywords: | FutureFeature, Triaged | ||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | python-filelock-3.8.2-1.fc38 | Doc Type: | If docs needed, set a value | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2022-12-08 12:11:27 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: | 1914413 | ||||||
| Attachments: |
|
||||||
|
Description
Upstream Release Monitoring
2022-12-05 09:40:49 UTC
Created attachment 1930030 [details]
Update to 3.8.1 (#2150782)
the-new-hotness/release-monitoring.org's scratch build of python-filelock-3.8.1-1.fc36.src.rpm for rawhide failed http://koji.fedoraproject.org/koji/taskinfo?taskID=94968611 Releases retrieved: 3.8.2 Upstream release that is considered latest: 3.8.2 Current version/release in rawhide: 3.7.1-1.fc38 URL: https://github.com/benediktschmitt/py-filelock 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/11739/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/python-filelock Scratch build failed. Details below:
GenericError: File upload failed: cli-build/1670265163.8316543.DZPGWwGr/python-filelock-3.8.2-1.fc36.src.rpm
Traceback:
File "/usr/local/lib/python3.10/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.10/site-packages/hotness/builders/koji.py", line 198, in build
output["build_id"] = self._scratch_build(session, package.name, srpm)
File "/usr/local/lib/python3.10/site-packages/hotness/builders/koji.py", line 451, in _scratch_build
session.uploadWrapper(source, serverdir)
File "/usr/lib/python3.10/site-packages/koji/__init__.py", line 3083, in uploadWrapper
self.fastUpload(localfile, path, name, callback, blocksize, overwrite, volume=volume)
File "/usr/lib/python3.10/site-packages/koji/__init__.py", line 3018, in fastUpload
raise GenericError("File upload failed: %s/%s" % (path, name))
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
Filelock actually does not need the latest setuptools. https://src.fedoraproject.org/rpms/python-filelock/pull-request/8 FEDORA-2022-e5b27dce75 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2022-e5b27dce75 FEDORA-2022-e5b27dce75 has been pushed to the Fedora 38 stable repository. If problem still persists, please make note of it in this bug report. |