Bug 2482693

Summary:	givaro-4.2.2 is available
Product:	[Fedora] Fedora	Reporter:	Upstream Release Monitoring <upstream-release-monitoring>
Component:	givaro	Assignee:	Ben Beasley <code>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	code, loganjerry, mycae
Target Milestone:	---	Keywords:	FutureFeature, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	givaro-4.2.2-1.fc45 givaro-4.2.2-1.el9 givaro-4.2.2-1.fc43 givaro-4.2.2-1.el10_3 givaro-4.2.2-1.fc44	Doc Type:	---
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2026-06-04 12:40:59 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 2026-05-28 14:29:38 UTC

Releases retrieved: 4.2.2
Upstream release that is considered latest: 4.2.2
Current version/release in rawhide: 4.2.1-7.fc45
URL: https://casys.gricad-pages.univ-grenoble-alpes.fr/givaro/

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


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

Comment 1 Fedora Update System 2026-06-04 12:37:09 UTC

FEDORA-2026-f898d5bddb (givaro-4.2.2-1.fc45) has been submitted as an update to Fedora 45.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-f898d5bddb

Comment 2 Fedora Update System 2026-06-04 12:40:59 UTC

FEDORA-2026-f898d5bddb (givaro-4.2.2-1.fc45) has been pushed to the Fedora 45 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 3 Fedora Update System 2026-06-04 12:55:01 UTC

FEDORA-2026-7f4bbbcb23 (givaro-4.2.2-1.fc44) has been submitted as an update to Fedora 44.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-7f4bbbcb23

Comment 4 Fedora Update System 2026-06-04 13:08:05 UTC

FEDORA-2026-c5d6f6721e (givaro-4.2.2-1.fc43) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-c5d6f6721e

Comment 5 Fedora Update System 2026-06-04 13:31:20 UTC

FEDORA-EPEL-2026-7b1f75c244 (givaro-4.2.2-1.el10_3) has been submitted as an update to Fedora EPEL 10.3.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-7b1f75c244

Comment 6 Fedora Update System 2026-06-04 21:03:01 UTC

FEDORA-EPEL-2026-b12acda3e1 (givaro-4.2.2-1.el9) has been submitted as an update to Fedora EPEL 9.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-b12acda3e1

Comment 7 Fedora Update System 2026-06-05 04:30:04 UTC

FEDORA-EPEL-2026-b12acda3e1 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-2026-b12acda3e1

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

Comment 8 Fedora Update System 2026-06-05 04:42:37 UTC

FEDORA-EPEL-2026-7b1f75c244 has been pushed to the Fedora EPEL 10.3 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-7b1f75c244

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

Comment 9 Fedora Update System 2026-06-05 04:51:47 UTC

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

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

Comment 10 Fedora Update System 2026-06-05 05:14:48 UTC

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

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

Comment 11 Fedora Update System 2026-06-13 00:41:38 UTC

FEDORA-EPEL-2026-b12acda3e1 (givaro-4.2.2-1.el9) 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 2026-06-13 00:55:14 UTC

FEDORA-2026-c5d6f6721e (givaro-4.2.2-1.fc43) has been pushed to the Fedora 43 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 13 Fedora Update System 2026-06-13 00:57:34 UTC

FEDORA-EPEL-2026-7b1f75c244 (givaro-4.2.2-1.el10_3) has been pushed to the Fedora EPEL 10.3 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 14 Fedora Update System 2026-06-13 01:10:47 UTC

FEDORA-2026-7f4bbbcb23 (givaro-4.2.2-1.fc44) has been pushed to the Fedora 44 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 15 Fedora Update System 2026-06-14 05:02:39 UTC

FEDORA-2026-c5d6f6721e (givaro-4.2.2-1.fc43) has been pushed to the Fedora 43 stable repository.
If problem still persists, please make note of it in this bug report.