Latest upstream release: 2.8.0 Current version/release in rawhide: 2.7.0-1.fc35 URL: https://github.com/pikepdf/pikepdf 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/17724/
FEDORA-2021-6aa3a93f98 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-6aa3a93f98
Hey, if I may just ask out of curiosity, are there plans to bring this update to Fedora 32 and 33? (2.7.0 fixes an incompatibility with the latest libqpdf versions but I'm not even sure those will land in f32/33. But if they do, we'd need pikepdf >= 2.7)
I just realized that qpdf 10.2 is already in updates-testing for f32/33 and pdfarranger does not work with this combination of qpdf and pikepdf versions. I'd appreciate a pikepdf >= 2.7.0 update first and any qpdf updates afterwards. Thanks and let me know if I can do anything to help!
FEDORA-2021-6aa3a93f98 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-2021-6aa3a93f98` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-6aa3a93f98 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Any chance to get this update in F32 an F33? Thanks!
v2 has breaking changes and thus cannot be brought to stable releases https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/ If something is broken, then it will require backporting fixes. But if qpdf breaks things, it really should not be updated in Fedora <34.
Thanks for the clarification, I wasn't sure whether that would or wouldn't be a problem. From my limited point of view, I wonder if this would be a suitable case for an exception from the update policy. Yes, this qpdf update should not break stuff, I agree and I already gave negative karma to disable auto-push of this qpdf update. I wonder, however, if updating pikepdf from v1 to v2 would really break any dependent packages. If that is not the case, the update to v2 would be the much simpler fix, wouldn't it? I just wanted to share this idea real quick. Maybe you can easily comment on it from your knowledge as pikepdf maintainer. I'll try to find some time for more research tonight. Is there anything else I can do to improve this situation?
We ended up applying a workaround to pdfarranger and I just pushed updates to testing. Sorry for hijacking this issue and thanks for the help!
OK sure, I was going to look into if we could do backports, but if you have a workaround, I won't continue then.
FEDORA-2021-2bbd832710 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-2021-2bbd832710` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-2bbd832710 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2021-2bbd832710 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-2bbd832710
FEDORA-2021-2bbd832710 has been pushed to the Fedora 34 stable repository. If problem still persists, please make note of it in this bug report.