Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1742336 - python-pikepdf-1.6.1 is available
Summary: python-pikepdf-1.6.1 is available
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: python-pikepdf
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Elliott Sales de Andrade
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 1706351
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-08-16 18:31 UTC by Upstream Release Monitoring
Modified: 2019-09-01 06:44 UTC (History)
3 users (show)

Fixed In Version: python-pikepdf-1.6.1-1.fc30
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-09-01 06:44:08 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Upstream Release Monitoring 2019-08-16 18:31:06 UTC 
Latest upstream release: 1.6.0
Current version/release in rawhide: 1.5.0-2.fc31
URL: https://github.com/pikepdf/pikepdf

Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/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 2019-08-16 18:31:09 UTC 
An unexpected error occurred while creating the scratch build and has been automatically reported. Sorry!
Comment 2 Upstream Release Monitoring 2019-08-16 19:50:20 UTC 
Latest upstream release: 1.6.1
Current version/release in rawhide: 1.5.0-2.fc31
URL: https://github.com/pikepdf/pikepdf

Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/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 3 Upstream Release Monitoring 2019-08-16 19:50:22 UTC 
An unexpected error occurred while creating the scratch build and has been automatically reported. Sorry!
Comment 4 Fedora Update System 2019-08-23 21:32:10 UTC 
FEDORA-2019-4c3b49e7a3 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-4c3b49e7a3
Comment 5 Elliott Sales de Andrade 2019-08-23 21:39:58 UTC 
pybind11 is broken on Rawhide.
Comment 6 Fedora Update System 2019-08-24 01:36:30 UTC 
python-pikepdf-1.6.1-1.fc30 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-4c3b49e7a3
Comment 7 Fedora Update System 2019-09-01 06:44:08 UTC 
python-pikepdf-1.6.1-1.fc30 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report.
Note You need to log in before you can comment on or make changes to this bug.