Bug 2071398

Summary:	libisds-0.11.2 is available
Product:	[Fedora] Fedora	Reporter:	Upstream Release Monitoring <upstream-release-monitoring>
Component:	libisds	Assignee:	Petr Pisar <ppisar>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	ppisar
Target Milestone:	---	Keywords:	FutureFeature, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	libisds-0.11.2-1.fc37 libisds-0.11.2-1.fc35 libisds-0.11.2-1.fc34 libisds-0.11.2-1.el8 libisds-0.11.2-1.el7 libisds-0.11.2-1.fc36	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-04-13 15:42:27 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-04-03 16:21:53 UTC

Latest upstream release: 0.11.2
Current version/release in rawhide: 0.11.1-6.fc37
URL: http://xpisar.wz.cz/libisds/dist/

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

Comment 1 Petr Pisar 2022-04-04 15:01:30 UTC

A bug-fix release suitable for all Fedoras and EPELs.

Comment 2 Fedora Update System 2022-04-04 15:17:47 UTC

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

Comment 3 Fedora Update System 2022-04-04 15:23:41 UTC

FEDORA-2022-f9fe91fe54 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-f9fe91fe54

Comment 4 Fedora Update System 2022-04-04 15:38:34 UTC

FEDORA-2022-cf5e31ed31 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2022-cf5e31ed31

Comment 5 Fedora Update System 2022-04-04 15:54:07 UTC

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

Comment 6 Fedora Update System 2022-04-04 16:06:05 UTC

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

Comment 7 Fedora Update System 2022-04-05 12:18:55 UTC

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

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

Comment 8 Fedora Update System 2022-04-05 12:41:03 UTC

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

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

Comment 9 Fedora Update System 2022-04-05 13:02:33 UTC

FEDORA-EPEL-2022-df57c5690f 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-2022-df57c5690f

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

Comment 10 Fedora Update System 2022-04-05 13:03:52 UTC

FEDORA-EPEL-2022-d26d4a3152 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-2022-d26d4a3152

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

Comment 11 Fedora Update System 2022-04-05 13:26:12 UTC

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

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

Comment 12 Fedora Update System 2022-04-13 15:42:27 UTC

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

Comment 13 Fedora Update System 2022-04-13 15:49:02 UTC

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

Comment 14 Fedora Update System 2022-04-13 16:34:52 UTC

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

Comment 15 Fedora Update System 2022-04-13 16:35:01 UTC

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

Comment 16 Fedora Update System 2022-05-07 04:16:41 UTC

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