Bug 2152106

Summary: povray: FTBS in rawhide, f36, f37
Product: [Fedora] Fedora Reporter: Ralf Corsepius <rc040203>
Component: povrayAssignee: Ralf Corsepius <rc040203>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: rc040203
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: povray-3.7.0.10-8.fc38 Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-12-09 14:08:38 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Ralf Corsepius 2022-12-09 09:31:35 UTC
Description of problem:

povray fails to build from source in rawhide and fc35, fc36, fc37.

* When building povray in a local mock, building waits for keyboard input
* When building povray in koji, building hangs and doesn't seem to be wanting to finish.

Version-Release number of selected component (if applicable):
povray-3.7.0.10-7

How reproducible:
Always

Steps to Reproduce:
Rebuild povray-3.7.0.10-7 in mock or in a koji-scratch-build

Actual results:
c.f. above

Expected results:
The package to build.

Additional info:
- povray-3.7.0.10-7 did build flawlessly for f37 and is part of released fc37.
- Analogously for older fedoras. They all carry versions of povray, which do not differ significantly from povray-3.7.0.10-7.

=> Either a dependency underneath of povray has changed its functionality or something in Fedora's buildsystem (mock/koji/rpm/... is broken.

Comment 1 Fedora Update System 2022-12-09 14:05:36 UTC
FEDORA-2022-6606877069 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2022-6606877069

Comment 2 Fedora Update System 2022-12-09 14:08:38 UTC
FEDORA-2022-6606877069 has been pushed to the Fedora 38 stable repository.
If problem still persists, please make note of it in this bug report.