Bug 2305241

Summary:	c4core-0.2.2 is available
Product:	[Fedora] Fedora	Reporter:	Upstream Release Monitoring <upstream-release-monitoring>
Component:	c4core	Assignee:	Ben Beasley <code>
Status:	CLOSED ERRATA	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	code
Target Milestone:	---	Keywords:	FutureFeature, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	c4core-0.2.2-2.fc41	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-09-13 20:50:29 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 2024-08-15 22:08:21 UTC

Releases retrieved: 0.2.2
Upstream release that is considered latest: 0.2.2
Current version/release in rawhide: 0.2.0-2.fc41
URL: https://github.com/biojppm/c4core

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


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

Comment 1 Ben Beasley 2024-08-17 14:27:27 UTC

For now, this is still waiting on ppc64le test failures in rapidyaml 0.7.1: https://github.com/biojppm/rapidyaml/issues/440#issuecomment-2294036666

Comment 2 Fedora Update System 2024-09-06 11:23:28 UTC

FEDORA-2024-020f68c67e (c4core-0.2.2-2.fc42, c4fs-0.0.1^20240622git59cfbae-2.fc42, and 3 more) has been submitted as an update to Fedora 42.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-020f68c67e

Comment 3 Fedora Update System 2024-09-06 11:25:13 UTC

FEDORA-2024-7c8fab650a (c4core-0.2.2-2.fc41, c4fs-0.0.1^20240622git59cfbae-2.fc41, and 4 more) has been submitted as an update to Fedora 41.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-7c8fab650a

Comment 4 Fedora Update System 2024-09-06 11:26:49 UTC

FEDORA-2024-020f68c67e (c4core-0.2.2-2.fc42, c4fs-0.0.1^20240622git59cfbae-2.fc42, and 3 more) has been pushed to the Fedora 42 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 5 Fedora Update System 2024-09-07 01:35:43 UTC

FEDORA-2024-7c8fab650a has been pushed to the Fedora 41 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-7c8fab650a`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-7c8fab650a

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

Comment 6 Fedora Update System 2024-09-13 20:50:29 UTC

FEDORA-2024-7c8fab650a (c4core-0.2.2-2.fc41, c4fs-0.0.1^20240622git59cfbae-2.fc41, and 4 more) has been pushed to the Fedora 41 stable repository.
If problem still persists, please make note of it in this bug report.