Bug 1992426

Summary: Handle parsing errors
Product: [Fedora] Fedora Reporter: Orion Poplawski <orion>
Component: python-breatheAssignee: Dan Čermák <dan.cermak>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: dan.cermak
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: python-breathe-4.30.0-4.fc36 Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-08-11 21:14: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:

Description Orion Poplawski 2021-08-11 04:34:26 UTC
Description of problem:

gdal docs are failing to build with:

Exception occurred:
  File "/usr/lib/python3.10/site-packages/sphinx/util/cfamily.py", line 275, in fail
    raise self._make_multi_error(errors, '')
sphinx.util.cfamily.DefinitionError: Invalid C++ declaration: Expected identifier in nested name. [error at 8]
  typename...
  --------^

This appears to be due to breathe not handling parsing errors.  There is a PR upstream at https://github.com/michaeljones/breathe/pull/711 but it doesn't apply cleanly to the current release so I haven't been able to test it.

I'm in the middle of a hdf5/netcdf/octave update in F35 and so am in a bit of a time crunch unfortunately.  I'm not sure if this can be worked around easily in gdal or not.

Version-Release number of selected component (if applicable):
python3-breathe-4.30.0-2.fc35.noarch

Comment 1 Fedora Update System 2021-08-11 21:13:20 UTC
FEDORA-2021-ef9e5e465a has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2021-ef9e5e465a

Comment 2 Fedora Update System 2021-08-11 21:14:24 UTC
FEDORA-2021-ef9e5e465a has been pushed to the Fedora 36 stable repository.
If problem still persists, please make note of it in this bug report.