Merge blocked
Welcome To openEuler Community
Hey @hello-leichen , 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. You can self-configure the PR merge rules for this repository. For more details, please refer to Here.
Contact Guide
If you have any questions, please contact the SIG: Programming-language ,
and any of the maintainers: @Charlie_li1, @lostway1 ,
and any of the committers: @lyn1001, @randy1568, @wk333 .


当前仓库存在以下 保护分支 :
评论 /sync <branch1> <branch2> ... 可将当前 PR 修改同步到其它分支(创建同步 PR):
a) 如果当前 PR 是 Open 状态,同步操作将延迟到 PR 被合并时执行
b) 如果当前 PR 已经 Merged,将立即执行同步操作
注意:
- /sync 命令可以指定同步到多个分支,仅最后一个 /sync 命令生效
- 如果创建的同步 PR 不正确,可通过向同步 PR 的源分支提交轻量级 PR 完善,或使用 /close 命令关闭


门禁正在运行, 您可以通过以下链接查看实时门禁检查结果.
若您对门禁结果含义不清晰或者遇到问题不知如何解决,可参考门禁指导手册
门禁入口及编码规范检查: multiarch/src-openeuler/trigger/python-virtualenv/68


x86_64架构构建及构建后检查:multiarch/src-openeuler/x86-64/python-virtualenv/68


aarch64架构构建及构建后检查:multiarch/src-openeuler/aarch64/python-virtualenv/68


| Check Name | Build Result | 详情 | Build Details | |
|---|---|---|---|---|
| check_binary_file | ✅SUCCESS | #68 | ||
| check_lfsconfig | ☑EXCLUDE | |||
| check_package_yaml_file | ✅SUCCESS | |||
| check_repo_in_maintain | ✅SUCCESS | |||
| check_consistency | ✅SUCCESS | |||
| check_spec_file | ✅SUCCESS | |||
| x86_64 | check_build | ✅SUCCESS | #68 | |
| check_install | ✅SUCCESS | |||
| check_license | ✅SUCCESS | |||
| aarch64 | check_build | ✅SUCCESS | #68 | |
| check_install | ✅SUCCESS | |||
| check_license | ✅SUCCESS | |||


如下为接口变更检查结果,目标分支为openEuler-24.03-LTS-SP3,请PR提交者check差异信息
| Arch Name | Check Items | Rpm Name | Check Result | Build Details |
|---|---|---|---|---|
| compare_package(x86_64) | add_rpms | ✅SUCCESS | #68 | |
| delete_rpms | ✅SUCCESS | |||
| rpm_cmd | ✅SUCCESS | |||
| rpm_files | ✅SUCCESS | |||
| rpm_provides | ✅SUCCESS | |||
| rpm_requires | ✅SUCCESS | |||
| compare_package(aarch64) | add_rpms | ✅SUCCESS | #68 | |
| delete_rpms | ✅SUCCESS | |||
| rpm_cmd | ✅SUCCESS | |||
| rpm_files | ✅SUCCESS | |||
| rpm_provides | ✅SUCCESS | |||
| rpm_requires | ✅SUCCESS |


当前PR是否有AI参与:
[] 否
[x] 是
__1. Agent平台信息: opencode v2.2.2
__2. 模型信息: DeepSeek-V4.1-Flash
__3. Prompt摘要: 按 issue 回合上游 CVE-2026-113719 修复,更新 spec 并验证清理路径
fixes #33
CVE-2026-113719:复用已有 app-data 目录时,pip_install 的清理逻辑直接拼接 top_level.txt / RECORD 条目,未校验是否落在环境内;恶意或残留元数据可用 ../ 或绝对路径删除环境外文件,造成数据破坏。
回合上游 PR #3428(合并提交 e3cea6fa):清理前对每个条目做 resolve,只允许删除环境内、且不是元数据父目录的路径;环境外条目告警并跳过。
验证:按 spec %prep(%autosetup + 现有 Patch0-2)应用 Patch3,fuzz=0 干净通过。用 20.26.6 源码构造带 ../../../../outside 条目和正常条目的 dist-info:基线删除两个环境外文件,修复版保留并告警,环境内条目仍正常删除。未做完整环境创建 PoC:该路径需真实 seed 流程,已用等价的 _uninstall_dist 单元场景覆盖。
CVE 单补丁提交,便于单独跟踪。