Bug 2219682

Summary: sshguard-2.4.3 is available
Product: [Fedora] Fedora Reporter: Upstream Release Monitoring <upstream-release-monitoring>
Component: sshguardAssignee: Felix Wang <topazus>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: ce, redhat-developer
Target Milestone: ---Keywords: FutureFeature, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: sshguard-2.4.3-4.fc40 Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-04-19 21:32:47 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 2.4.3 (#2219682) none

Description Upstream Release Monitoring 2023-07-04 18:51:37 UTC 
Releases retrieved: 2.4.3
Upstream release that is considered latest: 2.4.3
Current version/release in rawhide: 2.4.2-6.fc38
URL: https://www.sshguard.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://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/13819/


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/sshguard
Comment 1 Upstream Release Monitoring 2023-07-04 18:51:42 UTC 
Created attachment 1974034 [details]
Update to 2.4.3 (#2219682)
Comment 2 Upstream Release Monitoring 2023-07-04 18:57:13 UTC 
the-new-hotness/release-monitoring.org's scratch build of sshguard-2.4.3-1.fc38.src.rpm for rawhide completed http://koji.fedoraproject.org/koji/taskinfo?taskID=102926170
Comment 3 Fedora Admin user for bugzilla script actions 2024-03-26 00:16:24 UTC 
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.
Comment 4 Fedora Admin user for bugzilla script actions 2024-03-28 01:07:37 UTC 
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.
Comment 5 Fedora Update System 2024-03-28 05:32:48 UTC 
FEDORA-2024-8fe9cb8c69 (sshguard-2.4.3-1.fc40) has been submitted as an update to Fedora 40.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-8fe9cb8c69
Comment 6 Fedora Update System 2024-03-29 02:54:52 UTC 
FEDORA-2024-8fe9cb8c69 has been pushed to the Fedora 40 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf install --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-8fe9cb8c69 \*`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-8fe9cb8c69

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 7 Fedora Update System 2024-03-29 16:27:13 UTC 
FEDORA-2024-7d6fecf9a4 has been pushed to the Fedora 40 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf install --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-7d6fecf9a4 \*`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-7d6fecf9a4

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 8 Fedora Update System 2024-04-19 21:32:47 UTC 
FEDORA-2024-5d3b816579 (sshguard-2.4.3-4.fc40) has been pushed to the Fedora 40 stable repository.
If problem still persists, please make note of it in this bug report.