Welcome To openEuler Community

Hey @yue-yuankun , 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-golang ,
and any of the maintainers: @jing-rui ,
and any of the committers: @wd-gitcode .

@fuowang , @wangding16
以下的要求不是强制性的, 未按模板评论时对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://gitcode.com/Coopermassaki/cve-manager/blob/master/cve-vulner-manager/doc/md/defect-manager-manual.md
pr关联issue具体操作请参考:
https://docs.gitcode.com/docs/help/home/org_project/pullrequests/pr-related-issue

Welcome To openEuler Community

Hey @yue-yuankun , 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-golang ,
and any of the maintainers: @jing-rui ,
and any of the committers: @wd-gitcode .

同样的问题存在于很多软件包，是不是该提给release-management，给各审核者和开发者制定统一规范？

这个问题，sw代码能不能同源呢，全架构应用sw代码会对其他架构造成影响吗？
@little-huaduo

同样的问题存在于很多软件包，是不是该提给release-management，给各审核者和开发者制定统一规范？

@yue-yuankun

这里有规范，但是社区应该还没意识到打包成srpm时会遇到漏洞丢失的问题。

https://atomgit.com/openeuler/TC/blob/master/oEEP/oEEP-0012 openEuler软件包非upstream支持多架构代码提交规则.md