Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at
Bug 2225688 - Macaulay2: FTBFS in Fedora rawhide/f39
Summary: Macaulay2: FTBFS in Fedora rawhide/f39
Alias: None
Product: Fedora
Classification: Fedora
Component: Macaulay2
Version: 39
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Rex Dieter
QA Contact: Fedora Extras Quality Assurance
Whiteboard: AcceptedFreezeException
Depends On:
Blocks: F39FTBFS F40FTBFS F39FinalFreezeException
TreeView+ depends on / blocked
Reported: 2023-07-25 17:06 UTC by Fedora Release Engineering
Modified: 2023-11-10 01:44 UTC (History)
4 users (show)

Fixed In Version: Macaulay2-1.22-1.fc39
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2023-11-10 01:44:21 UTC
Type: ---

Attachments (Terms of Use)
build.log (deleted)
2023-07-25 17:07 UTC, Fedora Release Engineering
no flags Details
root.log (deleted)
2023-07-25 17:07 UTC, Fedora Release Engineering
no flags Details
state.log (deleted)
2023-07-25 17:07 UTC, Fedora Release Engineering
no flags Details

Description Fedora Release Engineering 2023-07-25 17:06:58 UTC
Macaulay2 failed to build from source in Fedora rawhide/f39

For details on the mass rebuild see:
Please fix Macaulay2 at your earliest convenience and set the bug's status to
ASSIGNED when you start fixing it. If the bug remains in NEW state for 8 weeks,
Macaulay2 will be orphaned. Before branching of Fedora 40,
Macaulay2 will be retired, if it still fails to build.

For more details on the FTBFS policy, please visit:

Comment 1 Fedora Release Engineering 2023-07-25 17:07:03 UTC
Created attachment 1977541 [details]

Comment 2 Fedora Release Engineering 2023-07-25 17:07:07 UTC
Created attachment 1977542 [details]

file root.log too big, will only attach last 32768 bytes

Comment 3 Fedora Release Engineering 2023-07-25 17:07:09 UTC
Created attachment 1977543 [details]

Comment 4 Fedora Release Engineering 2023-08-16 07:54:28 UTC
This bug appears to have been reported against 'rawhide' during the Fedora Linux 39 development cycle.
Changing version to 39.

Comment 5 Fedora Blocker Bugs Application 2023-10-27 17:40:39 UTC
Proposed as a Freeze Exception for 39-final by Fedora user music using the blocker tracking app because:

 A slightly-incompatible update of the Macaulay2 stack is required to fix FTBFS in F39 so that the package can be maintained over the F39 lifecycle. The necessary update was already completed in F40/Rawhide as, and an Updates Policy exception for F39 was requested from FESCo in In that issue, I was asked to request a freeze exception for the update—so here is that request!

Comment 6 Geoffrey Marr 2023-10-30 21:00:56 UTC
Discussed during the 2023-10-30 blocker review meeting: [0]

The decision to classify this bug as an "AcceptedFreezeException (Final)" was made on churchyard's justification: avoid the old interface provides being permanently available in the frozen release repo.


Comment 7 Adam Williamson 2023-10-30 23:52:06 UTC
unfortunately we aren't going to have time to include this. for future reference, it would be best to prepare the update *while* waiting for fesco/FE vote, so it's ready to go as soon as approved...

Comment 8 Fedora Update System 2023-11-01 11:28:02 UTC
FEDORA-2023-2aae5096fc has been submitted as an update to Fedora 39.

Comment 9 Fedora Update System 2023-11-02 01:47:55 UTC
FEDORA-2023-2aae5096fc has been pushed to the Fedora 39 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-2aae5096fc`
You can provide feedback for this update here:

See also for more information on how to test updates.

Comment 10 Fedora Update System 2023-11-10 01:44:21 UTC
FEDORA-2023-2aae5096fc has been pushed to the Fedora 39 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.