Bug 2121905
| Summary: | python-pikepdf-6.0.2 is available | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Upstream Release Monitoring <upstream-release-monitoring> |
| Component: | python-pikepdf | Assignee: | Elliott Sales de Andrade <quantum.analyst> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rawhide | CC: | epel-packagers-sig, python-sig, quantum.analyst, zdohnal |
| Target Milestone: | --- | Keywords: | FutureFeature, Triaged |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | python-pikepdf-5.6.1-1.fc37 python-pikepdf-5.6.1-1.fc36 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-10-03 00:17:13 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: | |||
| Bug Depends On: | 2118215 | ||
| Bug Blocks: | |||
|
Description
Upstream Release Monitoring
2022-08-27 08:15:31 UTC
Releases retrieved: 5.6.1 Upstream release that is considered latest: 5.6.1 Current version/release in rawhide: 5.3.0-1.fc37 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/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/python-pikepdf Releases retrieved: 6.0.0.post1 Upstream release that is considered latest: 6.0.0.post1 Current version/release in rawhide: 5.3.0-1.fc37 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/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/python-pikepdf Releases retrieved: 6.0.0.post2 Upstream release that is considered latest: 6.0.0.post2 Current version/release in rawhide: 5.3.0-1.fc37 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/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/python-pikepdf Releases retrieved: 6.0.1 Upstream release that is considered latest: 6.0.1 Current version/release in rawhide: 5.3.0-1.fc37 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/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/python-pikepdf Releases retrieved: 6.0.2 Upstream release that is considered latest: 6.0.2 Current version/release in rawhide: 5.3.0-1.fc37 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/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/python-pikepdf Hi Elliot, are you planning on rebasing the package? I'm planning to rebase qpdf in rawhide and the current python-pikepdf fails to build with new qpdf in copr. I cannot update this until Python 3.11 is fixed. Elliot, the bug you've attached seems to be fixed in the current Python version in rawhide - python3.11-3.11.0~rc2-1.fc38 - check Misc/NEWS in Python source tarball for changelog update from https://github.com/python/cpython/commit/3ea0beb3599f734bb9387a526dccd5768ad6b1a9 . Is there another bug blocking the rebase? Ah, I missed that there was another rc; weird that GitHub doesn't show that commit as part of it. FEDORA-2022-533db534b3 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-533db534b3 FEDORA-2022-ab306a2854 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-ab306a2854 FEDORA-2022-533db534b3 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 --refresh --advisory=FEDORA-2022-533db534b3` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-533db534b3 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2022-ab306a2854 has been pushed to the Fedora 37 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-ab306a2854` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-ab306a2854 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2022-ab306a2854 has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2022-533db534b3 has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report. |