Bug 2383798

Summary:	xgamma-1.0.8 is available
Product:	[Fedora] Fedora	Reporter:	Upstream Release Monitoring <upstream-release-monitoring>
Component:	xgamma	Assignee:	Petr Pisar <ppisar>
Status:	CLOSED ERRATA	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	ajax, ofourdan, ppisar
Target Milestone:	---	Keywords:	FutureFeature, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	xgamma-1.0.8-1.fc43 xgamma-1.0.8-1.fc42 xgamma-1.0.8-1.fc41	Doc Type:	---
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2025-08-12 00:56:04 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 2025-07-28 00:41:18 UTC

Releases retrieved: 1.0.8
Upstream release that is considered latest: 1.0.8
Current version/release in rawhide: 1.0.7-6.fc43
URL: https://gitlab.freedesktop.org/xorg/app/xgamma

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


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

Comment 1 Petr Pisar 2025-07-28 08:17:35 UTC

The release is signed with a new key which isn't signed with the old one. I asked the signer for a cross signature.

Comment 2 Petr Pisar 2025-07-28 08:33:00 UTC

A bug-fix release suitable for all Fedoras.

Comment 3 Petr Pisar 2025-07-30 08:57:48 UTC

Signature of the new key verified.

Comment 4 Fedora Update System 2025-07-30 09:10:53 UTC

FEDORA-2025-5319fe4569 (xgamma-1.0.8-1.fc42) has been submitted as an update to Fedora 42.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-5319fe4569

Comment 5 Fedora Update System 2025-07-30 09:10:57 UTC

FEDORA-2025-7911668770 (xgamma-1.0.8-1.fc41) has been submitted as an update to Fedora 41.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-7911668770

Comment 6 Fedora Update System 2025-07-31 01:26:35 UTC

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

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

Comment 7 Fedora Update System 2025-07-31 01:32:12 UTC

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

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

Comment 8 Fedora Update System 2025-08-12 00:56:04 UTC

FEDORA-2025-5319fe4569 (xgamma-1.0.8-1.fc42) has been pushed to the Fedora 42 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 9 Fedora Update System 2025-08-12 01:11:01 UTC

FEDORA-2025-7911668770 (xgamma-1.0.8-1.fc41) has been pushed to the Fedora 41 stable repository.
If problem still persists, please make note of it in this bug report.