Bug 1771164

Summary: R-pdftools-2.3.1 is available
Product: [Fedora] Fedora Reporter: Upstream Release Monitoring <upstream-release-monitoring>
Component: R-pdftoolsAssignee: 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: quantum.analyst
Target Milestone: ---Keywords: FutureFeature, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: R-pdftools-2.3.1-1.fc32 R-pdftools-2.3.1-4.fc31 Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-07-15 01:11:34 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 2.3 (#1771164) none

Description Upstream Release Monitoring 2019-11-11 22:03:43 UTC
Latest upstream release: 2.3
Current version/release in rawhide: 2.2-3.fc31
URL: https://github.com/ropensci/pdftools

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/18100/

Comment 1 Upstream Release Monitoring 2019-11-11 22:03:52 UTC
Created attachment 1635090 [details]
[patch] Update to 2.3 (#1771164)

Comment 2 Upstream Release Monitoring 2020-05-22 14:48:48 UTC
Latest upstream release: 2.3.1
Current version/release in rawhide: 2.2-5.fc32
URL: https://github.com/ropensci/pdftools

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/18100/

Comment 3 Fedora Update System 2020-07-11 22:01:11 UTC
FEDORA-2020-4c0ce71810 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-4c0ce71810

Comment 4 Fedora Update System 2020-07-15 01:11:34 UTC
FEDORA-2020-4c0ce71810 has been pushed to the Fedora 32 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 5 Fedora Update System 2020-08-09 06:59:27 UTC
FEDORA-2020-3ba55ba092 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-3ba55ba092

Comment 6 Fedora Update System 2020-08-10 00:54:56 UTC
FEDORA-2020-3ba55ba092 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-3ba55ba092`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-3ba55ba092

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

Comment 7 Fedora Update System 2020-08-18 01:23:08 UTC
FEDORA-2020-3ba55ba092 has been pushed to the Fedora 31 stable repository.
If problem still persists, please make note of it in this bug report.