Hi 各位仓库的维护者开发者:
SUSE目前正在OpenEuler的21.09上进行开发工作,从2021年10月起陆续在gitee上提交了部分PR用于修复一些构建测试以及一致性的问题,其中一部分PR已经获得审阅并顺利合入,目前还有PR未得到审阅的机会,故在此占用一些资源将没有审核的PR列出:
1. 简化构建配置(project config)文件相关PR: https://gitee.com/src-openeuler/esc/pulls/12 https://gitee.com/src-openeuler/dwz/pulls/6 https://gitee.com/src-openeuler/freeradius/pulls/49 https://gitee.com/src-openeuler/eog/pulls/13 2. X86/ARM64 SRPM包补丁一致性修复 https://gitee.com/src-openeuler/qpdf/pulls/4 https://gitee.com/src-openeuler/nodejs/pulls/75 3. 编译/单元测测相关错误修复 https://gitee.com/src-openeuler/fcoe-utils/pulls/12 https://gitee.com/src-openeuler/libkae/pulls/18 https://gitee.com/src-openeuler/python-docopt/pulls/5 https://gitee.com/src-openeuler/satyr/pulls/11
烦请各位维护者可以在方便的时候可以审核一下相关PR,给出审核意见。
B.R
Chenxi [https://gitee.com/static/images/logo_themecolor.png]https://gitee.com/src-openeuler/satyr/pulls/11 修复satyr编译过程中so文件拷贝错误 ・ Pull Request !11 ・ src-openEuler/satyr - Gitee.comhttps://gitee.com/src-openeuler/satyr/pulls/11 在编译satyr发现在check之后,拷贝文件发生错误。删除文件拷贝操作请评审补丁,申请合入分支 gitee.com
[https://gitee.com/static/images/logo_themecolor.png]https://gitee.com/src-openeuler/python-docopt/pulls/5 提取master分支上的补丁修复21.09分支编译错误 ・ Pull Request !5 ・ src-openEuler/python-docopt - Gitee.comhttps://gitee.com/src-openeuler/python-docopt/pulls/5 21.09遇到了编译错误,发现master分支已经解决。故cherrypick到21.09分支用于修复测试错误。这个补丁是直接cherrypick,没有对补丁做任何修改请审核并合入分支 gitee.com
[https://gitee.com/static/images/logo_themecolor.png]https://gitee.com/src-openeuler/libkae/pulls/18 libkae: 修复KAE在aarch64上的编译警告(错误) ・ Pull Request !18 ・ src-openEuler/libkae - Gitee.comhttps://gitee.com/src-openeuler/libkae/pulls/18 在aarch64编译中,所有遇到的警告都会被视做错误,也就导致在aarch64平台编译失败。 34s ./utils/engine_log.h:73:13: error: ignoring ... gitee.com
[https://gitee.com/static/images/logo_themecolor.png]https://gitee.com/src-openeuler/fcoe-utils/pulls/12 fcoe-utils: 提取上游补丁修复非X86的编译问题 ・ Pull Request !12 ・ src-openEuler/fcoe-utils - Gitee.comhttps://gitee.com/src-openeuler/fcoe-utils/pulls/12 由于X86的char型定义与ARM定义不同,因此在编译非X86平台会遇到类型错误。在OpenEuler中的gcc_secure包中强制指定了fsignedchar参数用来workaround。如... gitee.com
[https://gitee.com/static/images/logo_themecolor.png]https://gitee.com/src-openeuler/nodejs/pulls/75 nodejs:修复 x86_64 和 aarch64 平台source rpm 不一致的问题 ・ Pull Request !75 ・ src-openEuler/nodejs - Gitee.comhttps://gitee.com/src-openeuler/nodejs/pulls/75 为了方便和一致,在各个平台上的 Source rpm 应该都包含所有patch。在spec文件中的source字段使用ifarch判断,会导致不同平台最终生成的source rpm不一致。所以在... gitee.com
[https://gitee.com/static/images/logo_themecolor.png]https://gitee.com/src-openeuler/qpdf/pulls/4 qpdf: 修复 x86_64 和 aarch64 平台source rpm 不一致的问题 ・ Pull Request !4 ・ src-openEuler/qpdf - Gitee.comhttps://gitee.com/src-openeuler/qpdf/pulls/4 为了方便和一致,在各个平台上的 Source rpm 应该都包含所有patch。在spec文件中的source字段使用ifarch判断,会导致不同平台最终生成的source rpm不一致。所以在... gitee.com
[https://gitee.com/static/images/logo_themecolor.png]https://gitee.com/src-openeuler/eog/pulls/13 eog.spec: 增加 chrpath 编译依赖 ・ Pull Request !13 ・ src-openEuler/eog - Gitee.comhttps://gitee.com/src-openeuler/eog/pulls/13 2109上的提交6acaedb增加了chrpath命令的使用,导致编译失败。为了保证编译通过,无论是否使用OBS系统, 增加chrpath 编译依赖申请审核,并合入2109分支 gitee.com
[https://gitee.com/static/images/logo_themecolor.png]https://gitee.com/src-openeuler/freeradius/pulls/49 freeradius.spec: Add chrpath to BuildRequires ・ Pull Request !49 ・ src-openEuler/freeradius - Gitee.comhttps://gitee.com/src-openeuler/freeradius/pulls/49 Previous commit 1131387 add chrpath command in install section.To avoid build issue which means s... gitee.com
[https://gitee.com/static/images/logo_themecolor.png]https://gitee.com/src-openeuler/dwz/pulls/6 dwz.spec: Add gdb to BuildRequires ・ Pull Request !6 ・ src-openEuler/dwz - Gitee.comhttps://gitee.com/src-openeuler/dwz/pulls/6 Add gdb BuildRequires to make build happy. gitee.com
[https://gitee.com/static/images/logo_themecolor.png]https://gitee.com/src-openeuler/esc/pulls/12 esc.spec: Add chrpath to BuildRequires ・ Pull Request !12 ・ src-openEuler/esc - Gitee.comhttps://gitee.com/src-openeuler/esc/pulls/12 Previous commit 09feeab add chrpath command in install section.To avoid build issue which means s... gitee.com