Bug 2105958

Summary: gscan2pdf-2.12.8 is available
Product: [Fedora] Fedora Reporter: Upstream Release Monitoring <upstream-release-monitoring>
Component: gscan2pdfAssignee: Petr Pisar <ppisar>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: ppisar, rakesh.pandit, sven
Target Milestone: ---Keywords: FutureFeature, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: gscan2pdf-2.12.8-1.fc37 gscan2pdf-2.12.8-1.fc36 gscan2pdf-2.12.8-1.fc35 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-07-20 01:31:08 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:

Description Upstream Release Monitoring 2022-07-11 10:51:23 UTC
Releases retrieved: 2.12.8
Upstream release that is considered latest: 2.12.8
Current version/release in rawhide: 2.12.7-2.fc37
URL: http://gscan2pdf.sourceforge.net/

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


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/gscan2pdf

Comment 1 Petr Pisar 2022-07-11 13:31:09 UTC
A bug-fix release suitable for all Fedoras.

Comment 2 Fedora Update System 2022-07-11 13:44:10 UTC
FEDORA-2022-6277c056bd has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-6277c056bd

Comment 3 Fedora Update System 2022-07-11 13:44:18 UTC
FEDORA-2022-432b45b8de has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-432b45b8de

Comment 4 Fedora Update System 2022-07-12 02:30:59 UTC
FEDORA-2022-6277c056bd 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-6277c056bd`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-6277c056bd

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

Comment 5 Fedora Update System 2022-07-12 02:37:52 UTC
FEDORA-2022-432b45b8de has been pushed to the Fedora 35 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-432b45b8de`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-432b45b8de

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

Comment 6 Fedora Update System 2022-07-20 01:31:08 UTC
FEDORA-2022-6277c056bd has been pushed to the Fedora 36 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 7 Fedora Update System 2022-07-20 01:38:26 UTC
FEDORA-2022-432b45b8de has been pushed to the Fedora 35 stable repository.
If problem still persists, please make note of it in this bug report.