Bug 2339005 - racket: drop ppc64le and s390x support for F43
Summary: racket: drop ppc64le and s390x support for F43
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: racket
Version: 42
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Jens Petersen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-01-20 15:03 UTC by Jens Petersen
Modified: 2025-07-13 02:57 UTC (History)
1 user (show)

Fixed In Version: racket-8.16-1.fc42 racket-8.16-1.el10_0 racket-8.16-1.fc41
Clone Of:
Environment:
Last Closed: 2025-03-15 00:41:51 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Jens Petersen 2025-01-20 15:03:39 UTC
Building Racket on ppc64le and s390x which use pseudo-bytecode VM
takes about 5 hours - which seems too high a maintenance burden.

So I am proposing to drop these lower tier arch's for Fedora 43.

You can comment in this issue if you concerned about this.

Reproducible: Always

Comment 1 Jens Petersen 2025-01-20 15:05:48 UTC
Well one alternative might be make the packages for these archs more minimal.
Maybe just providing the scheme compiler say.

Comment 2 Aoife Moloney 2025-02-26 13:25:01 UTC
This bug appears to have been reported against 'rawhide' during the Fedora Linux 42 development cycle.
Changing version to 42.

Comment 3 Fedora Update System 2025-03-06 02:22:04 UTC
FEDORA-2025-e4e1343d8b (racket-8.16-1.fc42) has been submitted as an update to Fedora 42.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-e4e1343d8b

Comment 4 Fedora Update System 2025-03-07 08:34:45 UTC
FEDORA-2025-e4e1343d8b 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-e4e1343d8b`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-e4e1343d8b

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

Comment 5 Fedora Update System 2025-03-15 00:41:51 UTC
FEDORA-2025-e4e1343d8b (racket-8.16-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 6 Fedora Update System 2025-07-04 12:15:13 UTC
FEDORA-2025-89618328d9 (racket-8.16-1.fc41) has been submitted as an update to Fedora 41.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-89618328d9

Comment 7 Fedora Update System 2025-07-04 14:46:07 UTC
FEDORA-EPEL-2025-98f30302f5 (racket-8.16-1.el10_0) has been submitted as an update to Fedora EPEL 10.0.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-98f30302f5

Comment 8 Fedora Update System 2025-07-05 01:07:04 UTC
FEDORA-2025-89618328d9 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-89618328d9`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-89618328d9

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

Comment 9 Fedora Update System 2025-07-05 01:52:02 UTC
FEDORA-EPEL-2025-98f30302f5 has been pushed to the Fedora EPEL 10.0 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-98f30302f5

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

Comment 10 Fedora Update System 2025-07-13 01:53:29 UTC
FEDORA-EPEL-2025-98f30302f5 (racket-8.16-1.el10_0) has been pushed to the Fedora EPEL 10.0 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 11 Fedora Update System 2025-07-13 02:57:24 UTC
FEDORA-2025-89618328d9 (racket-8.16-1.fc41) has been pushed to the Fedora 41 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.