Bug 2466603

Summary:	algol68g-3.12.0 is available
Product:	[Fedora] Fedora	Reporter:	Upstream Release Monitoring <upstream-release-monitoring>
Component:	algol68g	Assignee:	Oleg Girko <ol+redhat>
Status:	CLOSED ERRATA	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	ol+redhat
Target Milestone:	---	Keywords:	FutureFeature, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	algol68g-3.12.0-1.el10_1 algol68g-3.12.0-1.el10_2 algol68g-3.12.0-1.el10_3 algol68g-3.12.0-1.fc44 algol68g-3.12.0-1.fc42 algol68g-3.12.0-1.el9 algol68g-3.12.0-1.fc43	Doc Type:	---
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2026-05-13 00:25: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 2026-05-04 20:43:09 UTC

Releases retrieved: 3.12.0
Upstream release that is considered latest: 3.12.0
Current version/release in rawhide: 3.11.3-1.fc45
URL: https://algol68genie.nl/en/algol-68-genie/

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


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

Comment 1 Fedora Update System 2026-05-04 20:47:06 UTC

FEDORA-2026-c91776d009 (algol68g-3.12.0-1.fc44) has been submitted as an update to Fedora 44.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-c91776d009

Comment 2 Fedora Update System 2026-05-04 20:48:20 UTC

FEDORA-2026-3d225232f9 (algol68g-3.12.0-1.fc43) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-3d225232f9

Comment 3 Fedora Update System 2026-05-04 20:49:07 UTC

FEDORA-2026-bd1ec0074b (algol68g-3.12.0-1.fc42) has been submitted as an update to Fedora 42.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-bd1ec0074b

Comment 4 Fedora Update System 2026-05-04 20:51:13 UTC

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

Comment 5 Fedora Update System 2026-05-04 20:51:26 UTC

FEDORA-EPEL-2026-51671e265a (algol68g-3.12.0-1.el10_3) has been submitted as an update to Fedora EPEL 10.3.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-51671e265a

Comment 6 Fedora Update System 2026-05-04 20:51:41 UTC

FEDORA-EPEL-2026-7b76126abc (algol68g-3.12.0-1.el10_1) has been submitted as an update to Fedora EPEL 10.1.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-7b76126abc

Comment 7 Fedora Update System 2026-05-04 20:52:01 UTC

FEDORA-EPEL-2026-62c0ae06ec (algol68g-3.12.0-1.el10_2) has been submitted as an update to Fedora EPEL 10.2.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-62c0ae06ec

Comment 8 Fedora Update System 2026-05-05 01:39:44 UTC

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

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

Comment 9 Fedora Update System 2026-05-05 01:55:28 UTC

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

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

Comment 10 Fedora Update System 2026-05-05 02:01:45 UTC

FEDORA-EPEL-2026-62c0ae06ec has been pushed to the Fedora EPEL 10.2 testing repository.

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

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

Comment 11 Fedora Update System 2026-05-05 02:11:11 UTC

FEDORA-EPEL-2026-51671e265a 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-51671e265a

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

Comment 12 Fedora Update System 2026-05-05 02:16:46 UTC

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

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

Comment 13 Fedora Update System 2026-05-05 02:17:19 UTC

FEDORA-EPEL-2026-7b76126abc has been pushed to the Fedora EPEL 10.1 testing repository.

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

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

Comment 14 Fedora Update System 2026-05-05 02:22:37 UTC

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

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

Comment 15 Fedora Update System 2026-05-13 00:25:04 UTC

FEDORA-EPEL-2026-7b76126abc (algol68g-3.12.0-1.el10_1) has been pushed to the Fedora EPEL 10.1 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 16 Fedora Update System 2026-05-13 20:41:13 UTC

FEDORA-EPEL-2026-62c0ae06ec (algol68g-3.12.0-1.el10_2) has been pushed to the Fedora EPEL 10.2 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 17 Fedora Update System 2026-05-13 20:55:05 UTC

FEDORA-EPEL-2026-51671e265a (algol68g-3.12.0-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 18 Fedora Update System 2026-05-13 21:14:01 UTC

FEDORA-2026-c91776d009 (algol68g-3.12.0-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 19 Fedora Update System 2026-05-13 21:27:05 UTC

FEDORA-2026-bd1ec0074b (algol68g-3.12.0-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 20 Fedora Update System 2026-05-13 23:03:48 UTC

FEDORA-EPEL-2026-edf552f0b9 (algol68g-3.12.0-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 21 Fedora Update System 2026-05-13 23:40:56 UTC

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