Bug 1823734

Summary: bout++ fails to build with Sphinx 3.0.0
Product: [Fedora] Fedora Reporter: Charalampos Stratakis <cstratak>
Component: bout++Assignee: david08741
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: cstratak, david08741, mhroncok
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-04-15 00:06:24 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:
Bug Depends On:    
Bug Blocks: 1783776    

Description Charalampos Stratakis 2020-04-14 11:23:33 UTC 
bout++ fails to build with Sphinx 3.0.0.

This report is automated and not very verbose, but we'll try to get back here with details.

For the build logs, see:
https://copr-be.cloud.fedoraproject.org/results/cstratak/sphinx_3.0.0/fedora-rawhide-x86_64/01335436-bout++/

For all our attempts to build bout++ with Sphinx 3.0.0, see:
https://copr.fedorainfracloud.org/coprs/cstratak/sphinx_3.0.0/package/bout++/

Testing and mass rebuild of packages is happening in copr. You can follow these instructions to test locally in mock if your package builds with Sphinx 3:
https://copr.fedorainfracloud.org/coprs/cstratak/sphinx_3.0.0/

Let us know here if you have any questions.

Sphinx 3 will be included in Fedora 33. To make that update smoother, we're building the dependent packages in Copr.
We'd appreciate help from the people who know this package best, but if you don't want to work on this now, let us know so we can try to work around it on our side.
Comment 1 david08741 2020-04-14 11:27:50 UTC 
The error seems to be related to mock failing on gethostbyname.
This is required by MPI to run. A workaround is enabling network access.

I didn't see any sphinx related errors, can you try again with network enabled?
Comment 2 Charalampos Stratakis 2020-04-15 00:06:24 UTC 
You are correct, indeed the issue was not related with sphinx. Closing this and sorry for the noise.