合并受阻
Hi wilhelmleibniz, welcome to the openEuler Community.
I'm the Bot here serving you. You can find the instructions on how to interact with me at Here.
If you have any questions, please contact the SIG: Networking, and any of the maintainers: @sunsuwan , @xiangyu2020 , @zengwefeng , @MrRlu , @robertxw , any of the committers: @jiangheng12 , @zhongxuan2


当前仓库存在以下 保护分支 :
| Protected Branch | Version | Release |
|---|---|---|
| * master | 2.4.58 | 9 |
| openEuler-20.03-LTS-SP4 | 2.4.43 | 27 |
| openEuler-22.03-LTS-LoongArch | 2.4.51 | 10 |
| openEuler-22.03-LTS-SP3 | 2.4.51 | 24 |
| openEuler-22.03-LTS-SP4 | 2.4.51 | 24 |
| openEuler-24.03-LTS | 2.4.58 | 9 |
| openEuler-24.03-LTS-Next | 2.4.58 | 9 |
| openEuler-24.03-LTS-SP1 | 2.4.58 | 9 |
| openEuler-24.03-LTS-SP2 | 2.4.58 | 9 |
| openEuler-25.03 | 2.4.58 | 7 |
| openEuler-25.09 | 2.4.58 | 9 |
评论 /sync <branch1> <branch2> ... 可将当前 PR 修改同步到其它分支(创建同步 PR):
a) 如果当前 PR 是 Open 状态,同步操作将延迟到 PR 被合并时执行
b) 如果当前 PR 已经 Merged,将立即执行同步操作
注意:
- /sync 命令可以指定同步到多个分支,仅最后一个 /sync 命令生效
- 如果创建的同步 PR 不正确,可通过向同步 PR 的源分支提交轻量级 PR 完善,或使用 /close 命令关闭


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


x86_64架构构建及构建后检查:multiarch/src-openeuler/x86-64/httpd/361/console


aarch64架构构建及构建后检查:multiarch/src-openeuler/aarch64/httpd/361/console


| Check Name | Build Result | Build Details | |
|---|---|---|---|
| check_binary_file | :white_check_mark:SUCCESS | #357 | |
| check_package_yaml_file | :white_check_mark:SUCCESS | ||
| check_repo_in_maintain | :white_check_mark:SUCCESS | ||
| check_consistency | :bug:WARNING | ||
| check_spec_file | :white_check_mark:SUCCESS | ||
| aarch64 | check_build | :x:FAILED | #361 |
| x86_64 | check_build | :x:FAILED | #361 |


@wilhelmleibniz


门禁常见失败问题及解决方案, 可参考门禁问题排查手册
若门禁存在误报,您可以评论/ci_mistake 357进行误报标记,357表示本次构建号
也可带上误报的门禁检查项以及误报类型(ci、obs、infra),比如/ci_mistake 357 obs check_build check_install表示的是check_build和check_install存在误报,误报类型为obs
若想取消误报标记,可以评论/ci_unmistake 357取消
也可在评论后加上一段文字描述,但请另起一行


/retest


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


x86_64架构构建及构建后检查:multiarch/src-openeuler/x86-64/httpd/362/console


aarch64架构构建及构建后检查:multiarch/src-openeuler/aarch64/httpd/362/console


| Check Name | Build Result | Build Details | |
|---|---|---|---|
| check_binary_file | :white_check_mark:SUCCESS | #358 | |
| check_package_yaml_file | :white_check_mark:SUCCESS | ||
| check_repo_in_maintain | :white_check_mark:SUCCESS | ||
| check_consistency | :bug:WARNING | ||
| check_spec_file | :white_check_mark:SUCCESS | ||
| aarch64 | check_build | :x:FAILED | #362 |
| x86_64 | check_build | :x:FAILED | #362 |


@wilhelmleibniz


门禁常见失败问题及解决方案, 可参考门禁问题排查手册
若门禁存在误报,您可以评论/ci_mistake 358进行误报标记,358表示本次构建号
也可带上误报的门禁检查项以及误报类型(ci、obs、infra),比如/ci_mistake 358 obs check_build check_install表示的是check_build和check_install存在误报,误报类型为obs
若想取消误报标记,可以评论/ci_unmistake 358取消
也可在评论后加上一段文字描述,但请另起一行


/retest


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


x86_64架构构建及构建后检查:multiarch/src-openeuler/x86-64/httpd/363/console


aarch64架构构建及构建后检查:multiarch/src-openeuler/aarch64/httpd/363/console


| Check Name | Build Result | Build Details | |
|---|---|---|---|
| check_binary_file | :white_check_mark:SUCCESS | #359 | |
| check_package_yaml_file | :white_check_mark:SUCCESS | ||
| check_repo_in_maintain | :white_check_mark:SUCCESS | ||
| check_consistency | :bug:WARNING | ||
| check_spec_file | :white_check_mark:SUCCESS | ||
| aarch64 | check_build | :x:FAILED | #363 |
| x86_64 | check_build | :x:FAILED | #363 |


@wilhelmleibniz


门禁常见失败问题及解决方案, 可参考门禁问题排查手册
若门禁存在误报,您可以评论/ci_mistake 359进行误报标记,359表示本次构建号
也可带上误报的门禁检查项以及误报类型(ci、obs、infra),比如/ci_mistake 359 obs check_build check_install表示的是check_build和check_install存在误报,误报类型为obs
若想取消误报标记,可以评论/ci_unmistake 359取消
也可在评论后加上一段文字描述,但请另起一行


/check-cla


backport some patches from upstream
issue link:
https://gitee.com/src-openeuler/httpd/issues/ICPIOS?from=project-issue
patches link:
https://github.com/apache/httpd/commit/6764774d51f3dcb07e79779c64a463d3c112b53f
https://github.com/apache/httpd/commit/c4218c88fe078570e7439c652a21f4773a432a76
https://github.com/apache/httpd/commit/3dec975c92ed1e2d5e60c88bbc331edd37ab49d7
https://github.com/apache/httpd/commit/f82a9e886f42db063fb87c2973b33a88320ae65b