Bug 2040907
| Summary: | rust-gtk4-sys-0.4.5 is available | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Upstream Release Monitoring <upstream-release-monitoring> |
| Component: | rust-gtk4-sys | Assignee: | Rémi Lauzier <remilauzier> |
| Status: | CLOSED ERRATA | QA Contact: | |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rawhide | CC: | remilauzier, rust-sig |
| Target Milestone: | --- | Keywords: | FutureFeature, Triaged |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | rust-gtk4-sys-0.4.5-1.fc37 | Doc Type: | --- |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-02-19 23:24:37 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-01-14 20:57:41 UTC
Scratch build failed. Details bellow:
BuilderException: Build started, but failure happened during post build operations:
Command '['git', 'commit', '-a', '-m', 'Update to 0.4.0 (#2040907)']' returned non-zero exit status 1.
StdOut:
On branch rawhide
Your branch is up to date with 'origin/rawhide'.
Untracked files:
(use "git add <file>..." to include in what will be committed)
SRPMS/
nothing added to commit but untracked files present (use "git add" to track)
Traceback:
File "/usr/local/lib/python3.9/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.9/site-packages/hotness/builders/koji.py", line 226, in build
raise BuilderException(
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
the-new-hotness/release-monitoring.org's scratch build of rust-gtk4-sys-0.3.1-1.fc34.src.rpm for rawhide completed http://koji.fedoraproject.org/koji/taskinfo?taskID=81250871 Latest upstream release: 0.4.1 Current version/release in rawhide: 0.3.1-2.fc36 URL: https://crates.io/crates/gtk4-sys 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://fedoraproject.org/wiki/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/230171/ Scratch build failed. Details bellow:
BuilderException: Build started, but failure happened during post build operations:
Command '['git', 'commit', '-a', '-m', 'Update to 0.4.1 (#2040907)']' returned non-zero exit status 1.
StdOut:
On branch rawhide
Your branch is up to date with 'origin/rawhide'.
Untracked files:
(use "git add <file>..." to include in what will be committed)
SRPMS/
nothing added to commit but untracked files present (use "git add" to track)
Traceback:
File "/usr/local/lib/python3.9/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.9/site-packages/hotness/builders/koji.py", line 226, in build
raise BuilderException(
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
the-new-hotness/release-monitoring.org's scratch build of rust-gtk4-sys-0.3.1-1.fc34.src.rpm for rawhide completed http://koji.fedoraproject.org/koji/taskinfo?taskID=81277611 Latest upstream release: 0.4.2 Current version/release in rawhide: 0.3.1-2.fc36 URL: https://crates.io/crates/gtk4-sys 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://fedoraproject.org/wiki/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/230171/ Scratch build failed. Details bellow:
BuilderException: Build started, but failure happened during post build operations:
Command '['git', 'commit', '-a', '-m', 'Update to 0.4.2 (#2040907)']' returned non-zero exit status 1.
StdOut:
On branch rawhide
Your branch is up to date with 'origin/rawhide'.
Untracked files:
(use "git add <file>..." to include in what will be committed)
SRPMS/
nothing added to commit but untracked files present (use "git add" to track)
Traceback:
File "/usr/local/lib/python3.9/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.9/site-packages/hotness/builders/koji.py", line 226, in build
raise BuilderException(
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
the-new-hotness/release-monitoring.org's scratch build of rust-gtk4-sys-0.3.1-1.fc34.src.rpm for rawhide completed http://koji.fedoraproject.org/koji/taskinfo?taskID=81368735 Latest upstream release: 0.4.5 Current version/release in rawhide: 0.3.1-2.fc36 URL: https://crates.io/crates/gtk4-sys 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://fedoraproject.org/wiki/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/230171/ Scratch build failed. Details bellow:
BuilderException: Build started, but failure happened during post build operations:
Command '['git', 'commit', '-a', '-m', 'Update to 0.4.5 (#2040907)']' returned non-zero exit status 1.
StdOut:
On branch rawhide
Your branch is up to date with 'origin/rawhide'.
Untracked files:
(use "git add <file>..." to include in what will be committed)
SRPMS/
nothing added to commit but untracked files present (use "git add" to track)
Traceback:
File "/usr/local/lib/python3.9/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.9/site-packages/hotness/builders/koji.py", line 226, in build
raise BuilderException(
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
the-new-hotness/release-monitoring.org's scratch build of rust-gtk4-sys-0.3.1-1.fc34.src.rpm for rawhide completed http://koji.fedoraproject.org/koji/taskinfo?taskID=81754631 FEDORA-2022-76268fe619 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-76268fe619 FEDORA-2022-76268fe619 has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report. |