Latest upstream release: 4.04 Current version/release in rawhide: 4.03-3.fc36 URL: https://www.xpdfreader.com 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/5264/
Scratch build failed. Details below: BuilderException: Build started, but failure happened during post build operations: Command '['rpmbuild', '-D', '_sourcedir .', '-D', '_topdir .', '-bs', '/var/tmp/thn-s1hmzwsi/xpdf.spec']' returned non-zero exit status 1. StdOut: warning: line 83: It's not recommended to have unversioned Obsoletes: Obsoletes: xpdf-chinese-simplified warning: line 85: It's not recommended to have unversioned Obsoletes: Obsoletes: xpdf-chinese-traditional warning: line 87: It's not recommended to have unversioned Obsoletes: Obsoletes: xpdf-korean warning: line 89: It's not recommended to have unversioned Obsoletes: Obsoletes: xpdf-japanese error: Bad source: ./xpdf-4.04.tar.gz: No such file or directory 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 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-297317210f has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-297317210f
FEDORA-2022-444e84551f has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2022-444e84551f
FEDORA-2022-4ad6325e9b has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-4ad6325e9b
FEDORA-2022-297317210f 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 --advisory=FEDORA-2022-297317210f` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-297317210f See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-444e84551f has been pushed to the Fedora 34 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-444e84551f` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-444e84551f See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-4ad6325e9b has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-4ad6325e9b` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-4ad6325e9b See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-444e84551f has been pushed to the Fedora 34 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2022-4ad6325e9b has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2022-297317210f has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report.