Bug 2154501
| Summary: | spamassassin-4.0.0 is available | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Upstream Release Monitoring <upstream-release-monitoring> |
| Component: | spamassassin | Assignee: | Kevin Fenzi <kevin> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rawhide | CC: | jskarvad, kevin, nb, olysonek-foss, pavel, pbrobinson |
| Target Milestone: | --- | Keywords: | FutureFeature, Triaged |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | spamassassin-4.0.0-2.fc38 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-12-21 21:35:15 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-17 09:51:27 UTC
Scratch build failed. Details below:
BuilderException: Build failed:
Command '['rpmbuild', '-D', '_sourcedir .', '-D', '_topdir .', '-bs', '/var/tmp/thn-ew6avxyt/spamassassin.spec']' returned non-zero exit status 1.
StdOut:
setting SOURCE_DATE_EPOCH=1671235200
error: Bad file: ./Mail-SpamAssassin-rules-4.0.0.r1888502.tgz: No such file or directory
RPM build errors:
Bad file: ./Mail-SpamAssassin-rules-4.0.0.r1888502.tgz: No such file or directory
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 188, 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
FEDORA-2022-e341ba52a1 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2022-e341ba52a1 FEDORA-2022-20516ccc28 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2022-20516ccc28 FEDORA-2022-20516ccc28 has been pushed to the Fedora 38 stable repository. If problem still persists, please make note of it in this bug report. |