Bug 2154625
Summary: | pytz-2022.7 is available | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Upstream Release Monitoring <upstream-release-monitoring> |
Component: | pytz | Assignee: | Gwyn Ciesla <gwync> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | rawhide | CC: | gwync |
Target Milestone: | --- | Keywords: | FutureFeature, Triaged |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | pytz-2022.7-1.fc37 pytz-2022.7-1.fc36 | Doc Type: | --- |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2022-12-28 01:34:20 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: |
Description
Upstream Release Monitoring
2022-12-18 02:19:52 UTC
Scratch build failed. Details below: GenericError: File upload failed: cli-build/1671329995.954998.VOxDyWSJ/pytz-2022.7-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 FEDORA-2022-bb7e5d3baa has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-bb7e5d3baa FEDORA-2022-c6a9188adf has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-c6a9188adf FEDORA-2022-c6a9188adf has been pushed to the Fedora 37 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-c6a9188adf` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-c6a9188adf See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2022-bb7e5d3baa has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-bb7e5d3baa` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-bb7e5d3baa See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2022-c6a9188adf has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2022-bb7e5d3baa has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report. |