Bug 1711229

Summary: python-swiftclient FTBFS with sphinx2
Product: [Fedora] Fedora Reporter: Patrik Kopkan <pkopkan>
Component: python-swiftclientAssignee: Miro Hrončok <mhroncok>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: rawhideCC: amoralej, apevec, mhroncok
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: python-swiftclient-3.7.0-2.fc31 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-05-17 11:42:56 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: 1685211, 1686977    
Attachments:
Description Flags
Copr build log, built with python3.8 none

Description Patrik Kopkan 2019-05-17 09:42:53 UTC 
Created attachment 1569989 [details]
Copr build log, built with python3.8

python-swiftclient-3.5.0-4 fails to build because of removing depracated API. 
upstream should use this instead https://www.sphinx-doc.org/en/2.0/extdev/logging.html

File "/usr/lib/python3.8/site-packages/oslosphinx/__init__.py", line 76, in builder_inited
    app.info('Using openstack theme from %s' % theme_dir)
AttributeError: 'Sphinx' object has no attribute 'info'
Comment 1 Miro Hrončok 2019-05-17 09:52:24 UTC 
Note that the package was recently updated and we need to retest the new version.
Yet from the spec it seems that is still uses oslosphinx.
Comment 2 Alfredo Moralejo 2019-05-17 10:55:50 UTC 
swiftclient has been updated to 3.7.0 in rawhide https://koji.fedoraproject.org/koji/buildinfo?buildID=1266215 which worked fine with sphinx 2.0.1 and does not depend on oslo-sphinx.

You should try to use spec from master to rebuild with 3.8.
Comment 3 Miro Hrončok 2019-05-17 11:30:56 UTC 
Will do.
Comment 4 Miro Hrončok 2019-05-17 11:42:56 UTC 
This is already fixed. Sorry for the noise, we have a very large backlog of failures to process, so we do not always have recent enough builds.