Bug 2270095

Summary: pinentry-1.3.0 is available
Product: [Fedora] Fedora Reporter: Upstream Release Monitoring <upstream-release-monitoring>
Component: pinentryAssignee: Boris Ranto <branto>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: branto, jjelen, rdieter, yselkowi
Target Milestone: ---Keywords: FutureFeature, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: pinentry-1.3.0-2.fc40 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-03-29 04:10:43 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
Update to 1.3.0 (#2270095) none

Description Upstream Release Monitoring 2024-03-18 13:20:04 UTC 
Releases retrieved: 1.3.0
Upstream release that is considered latest: 1.3.0
Current version/release in rawhide: 1.2.1-7.fc41
URL: https://gnupg.org/index.html

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://docs.fedoraproject.org/en-US/package-maintainers/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/3643/


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/pinentry
Comment 1 Upstream Release Monitoring 2024-03-18 13:20:30 UTC 
Created attachment 2022335 [details]
Update to 1.3.0 (#2270095)
Comment 2 Upstream Release Monitoring 2024-03-18 13:26:11 UTC 
the-new-hotness/release-monitoring.org's scratch build of pinentry-1.3.0-1.fc38.src.rpm for rawhide failed http://koji.fedoraproject.org/koji/taskinfo?taskID=115113424
Comment 3 Jakub Jelen 2024-03-19 08:54:09 UTC 
Updated the package in rawhide, but I was not able to test it works ok in CentOS 10 stream. I see Yaakov did some changes recently for the package to work well with c10s, can you check the current version works ok there? If so, I would like to pull the rebase to the c10s when it will be possible.

https://koji.fedoraproject.org/koji/taskinfo?taskID=115151309
Comment 4 Yaakov Selkowitz 2024-03-27 21:25:24 UTC 
Please also merge this into F40, since KDE has moved to Qt6 in that release.
Comment 5 Jakub Jelen 2024-03-28 10:25:44 UTC 
(In reply to Yaakov Selkowitz from comment #4)
> Please also merge this into F40, since KDE has moved to Qt6 in that release.

Done. The package is building now:

https://koji.fedoraproject.org/koji/taskinfo?taskID=115555792
Comment 6 Fedora Update System 2024-03-28 11:05:52 UTC 
FEDORA-2024-8c577b7f4c (pinentry-1.3.0-1.fc40) has been submitted as an update to Fedora 40.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-8c577b7f4c
Comment 7 Fedora Update System 2024-03-29 02:55:38 UTC 
FEDORA-2024-16e0f28639 has been pushed to the Fedora 40 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-16e0f28639`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-16e0f28639

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 8 Fedora Update System 2024-03-29 04:10:43 UTC 
FEDORA-2024-16e0f28639 (pinentry-1.3.0-2.fc40) has been pushed to the Fedora 40 stable repository.
If problem still persists, please make note of it in this bug report.