Bug 2162858

Summary:	openssh-ldap-authkeys-0.2.0 is available
Product:	[Fedora] Fedora	Reporter:	Upstream Release Monitoring <upstream-release-monitoring>
Component:	openssh-ldap-authkeys	Assignee:	Neal Gompa <ngompa13>
Status:	CLOSED ERRATA	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	ngompa13
Target Milestone:	---	Keywords:	FutureFeature, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openssh-ldap-authkeys-0.2.0-1.el9 openssh-ldap-authkeys-0.2.0-1.el8 openssh-ldap-authkeys-0.2.0-1.fc37 openssh-ldap-authkeys-0.2.0-1.fc36 openssh-ldap-authkeys-0.2.0-1.el7	Doc Type:	---
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-01-30 00:35:15 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 2023-01-21 14:22:25 UTC

Releases retrieved: 0.2.0
Upstream release that is considered latest: 0.2.0
Current version/release in rawhide: 0.1.0~git20200205.aee4c46-7.fc37
URL: https://github.com/fuhry/openssh-ldap-authkeys

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


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/openssh-ldap-authkeys

Comment 1 Fedora Update System 2023-01-21 14:26:26 UTC

FEDORA-EPEL-2023-2b21523f30 has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-2b21523f30

Comment 2 Fedora Update System 2023-01-21 14:26:27 UTC

FEDORA-2023-eac3496790 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2023-eac3496790

Comment 3 Fedora Update System 2023-01-21 14:26:28 UTC

FEDORA-EPEL-2023-5e24cefd4a has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-5e24cefd4a

Comment 4 Fedora Update System 2023-01-21 14:26:30 UTC

FEDORA-2023-610125f888 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2023-610125f888

Comment 5 Fedora Update System 2023-01-21 14:26:30 UTC

FEDORA-EPEL-2023-8cd63938fa has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-8cd63938fa

Comment 6 Fedora Update System 2023-01-22 01:37:40 UTC

FEDORA-2023-eac3496790 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-2023-eac3496790`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-eac3496790

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

Comment 7 Fedora Update System 2023-01-22 02:02:01 UTC

FEDORA-EPEL-2023-8cd63938fa has been pushed to the Fedora EPEL 8 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-8cd63938fa

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

Comment 8 Fedora Update System 2023-01-22 02:04:17 UTC

FEDORA-EPEL-2023-2b21523f30 has been pushed to the Fedora EPEL 9 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-2b21523f30

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

Comment 9 Fedora Update System 2023-01-22 02:41:40 UTC

FEDORA-2023-610125f888 has been pushed to the Fedora 37 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-610125f888`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-610125f888

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

Comment 10 Fedora Update System 2023-01-22 02:53:34 UTC

FEDORA-EPEL-2023-5e24cefd4a has been pushed to the Fedora EPEL 7 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-5e24cefd4a

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

Comment 11 Fedora Update System 2023-01-30 00:35:15 UTC

FEDORA-EPEL-2023-2b21523f30 has been pushed to the Fedora EPEL 9 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 12 Fedora Update System 2023-01-30 01:03:05 UTC

FEDORA-EPEL-2023-8cd63938fa has been pushed to the Fedora EPEL 8 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 13 Fedora Update System 2023-01-30 01:24:51 UTC

FEDORA-2023-610125f888 has been pushed to the Fedora 37 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 14 Fedora Update System 2023-01-30 01:31:11 UTC

FEDORA-2023-eac3496790 has been pushed to the Fedora 36 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 15 Fedora Update System 2023-01-30 01:43:23 UTC

FEDORA-EPEL-2023-5e24cefd4a has been pushed to the Fedora EPEL 7 stable repository.
If problem still persists, please make note of it in this bug report.