Releases retrieved: 12.0.0 Upstream release that is considered latest: 12.0.0 Current version/release in rawhide: 11.10.1-1.fc43 URL: https://qpdf.sf.net 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/5542/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/qpdf
Created attachment 2079434 [details] Update to 12.0.0 (#2350975)
the-new-hotness/release-monitoring.org's scratch build of qpdf-12.0.0-1.fc40.src.rpm for rawhide failed http://koji.fedoraproject.org/koji/taskinfo?taskID=130051133
Releases retrieved: 12.1.0 Upstream release that is considered latest: 12.1.0 Current version/release in rawhide: 11.10.1-1.fc43 URL: https://qpdf.sf.net 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/5542/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/qpdf
Created attachment 2083621 [details] Update to 12.1.0 (#2350975)
the-new-hotness/release-monitoring.org's scratch build of qpdf-12.1.0-1.fc40.src.rpm for rawhide failed http://koji.fedoraproject.org/koji/taskinfo?taskID=131205365
Releases retrieved: 12.2.0 Upstream release that is considered latest: 12.2.0 Current version/release in rawhide: 11.10.1-1.fc43 URL: https://qpdf.sf.net 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/5542/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/qpdf
Created attachment 2088373 [details] Update to 12.2.0 (#2350975)
the-new-hotness/release-monitoring.org's scratch build of qpdf-12.2.0-1.fc40.src.rpm for rawhide failed http://koji.fedoraproject.org/koji/taskinfo?taskID=132330980
Rebase pushed via https://src.fedoraproject.org/rpms/qpdf/pull-request/7 , coordinating update via side-tag with dependent packages due soname change.
FEDORA-2025-bd6e345995 (libcupsfilters-2.1.1-2.fc43, pdfmixtool-1.1.1-13.fc43, and 3 more) has been submitted as an update to Fedora 43. https://bodhi.fedoraproject.org/updates/FEDORA-2025-bd6e345995
FEDORA-2025-bd6e345995 (libcupsfilters-2.1.1-2.fc43, pdfmixtool-1.1.1-13.fc43, and 3 more) has been pushed to the Fedora 43 stable repository. If problem still persists, please make note of it in this bug report.