Welcome To openEuler Community

Hey @goumenghao , thanks for your contribution to the community.

Bot Usage Manual

I'm the Bot here serving you. You can find the instructions on how to interact with me at Here . That means you can comment below every pull request or issue to trigger Bot Commands.

Contact Guide

If you have any questions, please contact the SIG: sig-epol ,
and any of the maintainers: @shinwell_hu, @small_leek, @solarhu ,
and any of the committers: @cherry530, @lostway1, @lyn1001 .

以下的要求不是强制性的, 未按模板评论时对issue无任何影响
issue处理注意事项:
1. 当前issue受影响的分支提交pr时, 须在pr描述中填写当前issue编号进行关联, 否则无法关闭当前issue;
2. 模板内容需要填写完整, 无论是受影响或者不受影响都需要填写完整内容,未引入的分支不需要填写, 否则无法关闭当前issue;
3. 以下为模板中需要填写完整的内容, 请复制到评论区回复, 注: 内容的标题名称(影响性分析说明, 缺陷严重等级, 受影响版本排查(受影响/不受影响), 修复是否涉及abi变化(是/否))不能省略,省略后defect-manager将无法正常解析填写内容.
评论区可能使用到的指令说明:

影响性分析说明:

缺陷严重等级:(Critical/High/Moderate/Low)

缺陷根因说明:

受影响版本排查(受影响/不受影响):

1. openEuler-20.03-LTS-SP4:
2. openEuler-22.03-LTS-SP3:
3. openEuler-22.03-LTS-SP4:
4. openEuler-24.03-LTS:
5. openEuler-24.03-LTS-SP1:
6. openEuler-24.03-LTS-SP2:

abi变化(是/否):

1. openEuler-20.03-LTS-SP4:
2. openEuler-22.03-LTS-SP3:
3. openEuler-22.03-LTS-SP4:
4. openEuler-24.03-LTS:
5. openEuler-24.03-LTS-SP1:
6. openEuler-24.03-LTS-SP2:

缺陷issue处理具体操作请参考:
https://atomgit.com/openeuler/cve-manager/blob/master/cve-vulner-manager/doc/md/defect-manager-manual.md
pr关联issue具体操作请参考:
https://docs.atomgit.com/docs/help/home/org_project/pullrequests/pr-related-issue

该失败是由于 doxygen 升级导致 python-sphinxygen 解析出现问题，已有PR修复，待合入 26.09
https://atomgit.com/src-openeuler/python-sphinxygen/pull/4

@lyn1001 未对受影响版本排查/abi变化进行分析

个人工程验证

@goumenghao 修复位于 python-sphinxygen，请在对应工程中开启python-sphinxygen的指定增量构建，lilv 等包作为下游会构建成功。

错误日志：
2026-08-16 17:30:59 FAILED: [code=1] doc/api/lilv.rst
2026-08-16 17:30:59 /usr/bin/sphinxygen -f doc/xml/index.xml doc/api
2026-08-16 17:30:59 Traceback (most recent call last):
2026-08-16 17:30:59 File "/usr/bin/sphinxygen", line 8, in
2026-08-16 17:30:59 sys.exit(main())
2026-08-16 17:30:59 ^^^^^^
2026-08-16 17:30:59 File "/usr/lib/python3.11/site-packages/sphinxygen/sphinxygen.py", line 1005, in main
2026-08-16 17:30:59 run(**vars(parser.parse_args(sys.argv[1:])))
2026-08-16 17:30:59 File "/usr/lib/python3.11/site-packages/sphinxygen/sphinxygen.py", line 965, in run
2026-08-16 17:30:59 read_definition_doc(index, language, root)
2026-08-16 17:30:59 File "/usr/lib/python3.11/site-packages/sphinxygen/sphinxygen.py", line 765, in read_definition_doc
2026-08-16 17:30:59 read_member_doc(index, lang, member)
2026-08-16 17:30:59 File "/usr/lib/python3.11/site-packages/sphinxygen/sphinxygen.py", line 735, in read_member_doc
2026-08-16 17:30:59 handlerskind
2026-08-16 17:30:59 File "/usr/lib/python3.11/site-packages/sphinxygen/sphinxygen.py", line 711, in read_typedef
2026-08-16 17:30:59 assert target_text[-2:] == "(*" and args_text[0] == ")"
2026-08-16 17:30:59 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2026-08-16 17:30:59 AssertionError

原因分析：Doxygen 1.18 改变了函数指针 typedef 的 XML 输出格式: 现在包含完整的 void() 片段, 以 ( 开头而不是 )。sphinxygen 1.0.12 的 read_typedef() 中硬编码了旧格式断言(target_text[-2:] == "(" and args_text[0] == ")"),因此在新格式下直接 AssertionError。

解决办法：使 read_typedef() 同时兼容 doxygen 1.17 与 1.18,生成的 Sphinx 标记与旧版本完全一致。

pr：https://atomgit.com/src-openeuler/python-sphinxygen/pull/5