Bug 2301019 - opensubdiv: FTBFS in Fedora rawhide/f41
Summary: opensubdiv: FTBFS in Fedora rawhide/f41
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: opensubdiv
Version: 42
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Luya Tshimbalanga
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F41FTBFS
TreeView+ depends on / blocked
 
Reported: 2024-07-29 20:00 UTC by Fedora Release Engineering
Modified: 2025-05-08 03:29 UTC (History)
1 user (show)

Fixed In Version: opensubdiv-3.6.0-3.fc41
Clone Of:
Environment:
Last Closed: 2025-04-29 20:39:48 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
build.log (3.07 KB, text/plain)
2024-07-29 20:01 UTC, Fedora Release Engineering
no flags Details
root.log (32.00 KB, text/plain)
2024-07-29 20:01 UTC, Fedora Release Engineering
no flags Details
state.log (1.50 KB, text/plain)
2024-07-29 20:01 UTC, Fedora Release Engineering
no flags Details

Description Fedora Release Engineering 2024-07-29 20:00:56 UTC
opensubdiv failed to build from source in Fedora rawhide/f41

https://koji.fedoraproject.org/koji/taskinfo?taskID=120703559


For details on the mass rebuild see:

https://fedoraproject.org/wiki/Fedora_41_Mass_Rebuild
Please fix opensubdiv 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,
opensubdiv will be orphaned. Before branching of Fedora 42,
opensubdiv will be retired, if it still fails to build.

For more details on the FTBFS policy, please visit:
https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/

Comment 1 Fedora Release Engineering 2024-07-29 20:01:00 UTC
Created attachment 2042022 [details]
build.log

Comment 2 Fedora Release Engineering 2024-07-29 20:01:05 UTC
Created attachment 2042023 [details]
root.log

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

Comment 3 Fedora Release Engineering 2024-07-29 20:01:08 UTC
Created attachment 2042024 [details]
state.log

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

Comment 5 Fedora Update System 2025-04-22 15:51:16 UTC
FEDORA-EPEL-2025-cc577b01d6 (openxr-1.1.47-1.el10_1) has been submitted as an update to Fedora EPEL 10.1.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-cc577b01d6

Comment 6 Fedora Update System 2025-04-22 15:51:16 UTC
FEDORA-2025-e9ea6cdd41 (embree-4.4.0-1.fc42, openxr-1.1.47-1.fc42, and 1 more) has been submitted as an update to Fedora 42.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-e9ea6cdd41

Comment 7 Fedora Update System 2025-04-22 15:51:18 UTC
FEDORA-2025-4a41c56252 (embree-4.4.0-1.fc41, opensubdiv-3.6.0-3.fc41, and 2 more) has been submitted as an update to Fedora 41.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-4a41c56252

Comment 8 Fedora Update System 2025-04-22 15:51:19 UTC
FEDORA-2025-7611c1c141 (embree-4.4.0-1.fc40 and openxr-1.1.47-1.fc40) has been submitted as an update to Fedora 40.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-7611c1c141

Comment 9 Fedora Update System 2025-04-23 03:17:30 UTC
FEDORA-2025-e9ea6cdd41 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-e9ea6cdd41`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-e9ea6cdd41

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

Comment 10 Fedora Update System 2025-04-23 03:26:51 UTC
FEDORA-2025-4a41c56252 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-4a41c56252`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-4a41c56252

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

Comment 11 Fedora Update System 2025-04-23 03:44:09 UTC
FEDORA-EPEL-2025-cc577b01d6 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-2025-cc577b01d6

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

Comment 12 Fedora Update System 2025-04-23 03:55:30 UTC
FEDORA-2025-7611c1c141 has been pushed to the Fedora 40 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-7611c1c141`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-7611c1c141

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

Comment 13 Fedora Update System 2025-04-29 20:39:48 UTC
FEDORA-2025-e9ea6cdd41 (embree-4.4.0-1.fc42, openxr-1.1.47-1.fc42, and 1 more) has been pushed to the Fedora 42 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 14 Fedora Update System 2025-04-30 01:38:05 UTC
FEDORA-2025-4a41c56252 (embree-4.4.0-1.fc41, opensubdiv-3.6.0-3.fc41, and 2 more) has been pushed to the Fedora 41 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 15 Fedora Update System 2025-05-01 03:11:34 UTC
FEDORA-EPEL-2025-cc577b01d6 (openxr-1.1.47-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 2025-05-08 03:29:43 UTC
FEDORA-2025-7611c1c141 (embree-4.4.0-1.fc40 and openxr-1.1.47-1.fc40) has been pushed to the Fedora 40 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.