Releases retrieved: 0.6.3 Upstream release that is considered latest: 0.6.3 Current version/release in rawhide: 0.6.2-15.fc38 URL: https://musicbrainz.org/doc/libdiscid 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/1592/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/libdiscid
Scratch build failed. Details below: GenericError: File upload failed: cli-build/1677608462.704909.wqdlYNYs/libdiscid-0.6.3-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 3110, in uploadWrapper self.fastUpload(localfile, path, name, callback, blocksize, overwrite, volume=volume) File "/usr/lib/python3.10/site-packages/koji/__init__.py", line 3034, 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-2023-fb878516ad has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-fb878516ad
FEDORA-2023-50e11e9d5e has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2023-50e11e9d5e
FEDORA-2023-fb878516ad has been pushed to the Fedora 38 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-fb878516ad See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-50e11e9d5e 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-2023-50e11e9d5e` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-50e11e9d5e See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-15faa53b53 has been pushed to the Fedora 38 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-15faa53b53 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-922753f023 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-2023-922753f023` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-922753f023 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-15faa53b53 has been pushed to the Fedora 38 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2023-922753f023 has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report.