Bug 1822896

Summary: python-pikepdf-1.11.0 is available
Product: [Fedora] Fedora Reporter: Upstream Release Monitoring <upstream-release-monitoring>
Component: python-pikepdfAssignee: Elliott Sales de Andrade <quantum.analyst>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: python-sig, quantum.analyst, zdohnal
Target Milestone: ---Keywords: FutureFeature, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: python-pikepdf-1.11.0-1.fc30 python-pikepdf-1.11.0-1.fc31 python-pikepdf-1.11.1-1.fc32 Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-04-22 22:55:53 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:
Attachments:
Description Flags
[patch] Update to 1.11.0 (#1822896) none

Description Upstream Release Monitoring 2020-04-10 11:26:52 UTC
Latest upstream release: 1.11.0
Current version/release in rawhide: 1.10.4-1.fc33
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/

Comment 1 Upstream Release Monitoring 2020-04-10 11:26:57 UTC
Created attachment 1677782 [details]
[patch] Update to 1.11.0 (#1822896)

Comment 2 Upstream Release Monitoring 2020-04-10 11:30:06 UTC
the-new-hotness/release-monitoring.org's scratch build of python-pikepdf-1.11.0-1.fc30.src.rpm for rawhide failed http://koji.fedoraproject.org/koji/taskinfo?taskID=43190536

Comment 3 Fedora Update System 2020-04-13 10:27:35 UTC
FEDORA-2020-8972cb05f4 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-8972cb05f4

Comment 4 Fedora Update System 2020-04-13 10:28:17 UTC
FEDORA-2020-f7e8be44c3 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-f7e8be44c3

Comment 5 Fedora Update System 2020-04-13 10:28:42 UTC
FEDORA-2020-af6f698163 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2020-af6f698163

Comment 6 Fedora Update System 2020-04-13 18:32:41 UTC
FEDORA-2020-f7e8be44c3 has been pushed to the Fedora 31 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-f7e8be44c3`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-f7e8be44c3

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 7 Fedora Update System 2020-04-13 19:16:42 UTC
FEDORA-2020-af6f698163 has been pushed to the Fedora 30 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-af6f698163`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-af6f698163

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 8 Fedora Update System 2020-04-13 21:17:35 UTC
FEDORA-2020-8972cb05f4 has been pushed to the Fedora 32 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-8972cb05f4`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-8972cb05f4

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 9 Fedora Update System 2020-04-16 19:28:09 UTC
FEDORA-2020-daf8a4b019 has been pushed to the Fedora 32 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-daf8a4b019`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-daf8a4b019

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 10 Fedora Update System 2020-04-17 06:49:59 UTC
FEDORA-2020-daf8a4b019 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-daf8a4b019

Comment 11 Fedora Update System 2020-04-17 22:06:31 UTC
FEDORA-2020-daf8a4b019 has been pushed to the Fedora 32 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-daf8a4b019`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-daf8a4b019

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 12 Fedora Update System 2020-04-22 22:55:53 UTC
FEDORA-2020-af6f698163 has been pushed to the Fedora 30 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 13 Fedora Update System 2020-04-22 23:24:02 UTC
FEDORA-2020-f7e8be44c3 has been pushed to the Fedora 31 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 14 Fedora Update System 2020-04-25 02:23:02 UTC
FEDORA-2020-daf8a4b019 has been pushed to the Fedora 32 stable repository.
If problem still persists, please make note of it in this bug report.