- Dev - mailweb.openeuler.org

云原生sig例会
by openEuler conference 31 Oct '24

31 Oct '24

您好！ sig-CloudNative 邀请您参加 2024-11-05 16:00 召开的Zoom会议会议主题：云原生sig例会会议内容：云原生sig例会会议链接：https://us06web.zoom.us/j/88922108716?pwd=bHgqdgbp2bcAAQoMGBOuCrTFzNb4Jc.1 会议纪要：https://etherpad.openeuler.org/p/sig-CloudNative-meetings 更多资讯尽在：https://www.openeuler.org/zh/ Hello! sig-CloudNative invites you to attend the Zoom conference will be held at 2024-11-05 16:00, The subject of the conference is 云原生sig例会, Summary: 云原生sig例会 You can join the meeting at https://us06web.zoom.us/j/88922108716?pwd=bHgqdgbp2bcAAQoMGBOuCrTFzNb4Jc.1. Add topics at https://etherpad.openeuler.org/p/sig-CloudNative-meetings. More information: https://www.openeuler.org/en/

1 0

RM sig双周会议
by openEuler conference 31 Oct '24

31 Oct '24

您好！ sig-release-management 邀请您参加 2024-11-01 10:00 召开的WeLink会议(自动录制) 会议主题：RM sig双周会议会议链接：https://meeting.huaweicloud.com:36443/#/j/982291579 会议纪要：https://etherpad.openeuler.org/p/sig-release-management-meetings 更多资讯尽在：https://www.openeuler.org/zh/ Hello! sig-release-management invites you to attend the WeLink conference(auto recording) will be held at 2024-11-01 10:00, The subject of the conference is RM sig双周会议, You can join the meeting at https://meeting.huaweicloud.com:36443/#/j/982291579. Add topics at https://etherpad.openeuler.org/p/sig-release-management-meetings. More information: https://www.openeuler.org/en/

1 0

【开发过程疑问】
by 3128856842 31 Oct '24

31 Oct '24

您好，请问加入G11N组的方式是什么？只要提交了翻译的相关内容就可以吗？ 3128856842 3128856842(a)qq.com  

2 1

RISC-V SIG 双周会
by openEuler conference 30 Oct '24

30 Oct '24

您好！ sig-RISC-V 邀请您参加 2024-10-31 10:00 召开的WeLink会议(自动录制) 会议主题：RISC-V SIG 双周会会议链接：https://meeting.huaweicloud.com:36443/#/j/962137543 会议纪要：https://etherpad.openeuler.org/p/sig-RISC-V-meetings 更多资讯尽在：https://www.openeuler.org/zh/ Hello! sig-RISC-V invites you to attend the WeLink conference(auto recording) will be held at 2024-10-31 10:00, The subject of the conference is RISC-V SIG 双周会, You can join the meeting at https://meeting.huaweicloud.com:36443/#/j/962137543. Add topics at https://etherpad.openeuler.org/p/sig-RISC-V-meetings. More information: https://www.openeuler.org/en/

1 0

sig-intelligence 例会
by openEuler conference 30 Oct '24

30 Oct '24

您好！ sig-intelligence 邀请您参加 2024-11-01 10:30 召开的Zoom会议(自动录制) 会议主题：sig-intelligence 例会会议内容： 1. issue处理议题征集中～会议链接：https://us06web.zoom.us/j/84797630168?pwd=ayo03V9SEuB3QCZXdsBuBYnaMaVor2.1 会议纪要：https://etherpad.openeuler.org/p/sig-intelligence-meetings 更多资讯尽在：https://www.openeuler.org/zh/ Hello! sig-intelligence invites you to attend the Zoom conference(auto recording) will be held at 2024-11-01 10:30, The subject of the conference is sig-intelligence 例会, Summary: 1. issue处理议题征集中～ You can join the meeting at https://us06web.zoom.us/j/84797630168?pwd=ayo03V9SEuB3QCZXdsBuBYnaMaVor2.1. Add topics at https://etherpad.openeuler.org/p/sig-intelligence-meetings. More information: https://www.openeuler.org/en/

1 0

bigdata SIG例会
by openEuler conference 30 Oct '24

30 Oct '24

您好！ bigdata 邀请您参加 2024-10-31 16:00 召开的WeLink会议会议主题：bigdata SIG例会会议链接：https://meeting.huaweicloud.com:36443/#/j/966890626 会议纪要：https://etherpad.openeuler.org/p/bigdata-meetings 更多资讯尽在：https://www.openeuler.org/zh/ Hello! bigdata invites you to attend the WeLink conference will be held at 2024-10-31 16:00, The subject of the conference is bigdata SIG例会, You can join the meeting at https://meeting.huaweicloud.com:36443/#/j/966890626. Add topics at https://etherpad.openeuler.org/p/bigdata-meetings. More information: https://www.openeuler.org/en/

1 0

openeuler 24.03-LTS-SP1 分支初始化公示通知
by yangchaohao 30 Oct '24

30 Oct '24

各位openeuler社区的maintainer、 committer和contributor们好： openEuler-24.03-LTS-SP1版本分支初始化创建pr已提交，链接为init openEuler-24.03-LTS-SP1 branch ・ Pull Request !5967 ・ openEuler/community - Gitee.com<https://gitee.com/openeuler/community/pulls/5967> 请涉及各sig的maintainer检视，如无问题请评论/lgtm 。公示三天，若无反对意见，将于11月1日12点合入。 ________________________________ 杨超豪 Yang Chaohao Email：yangchaohao(a)huawei.com<mailto:yangchaohao@huawei.com>

1 0

SBOM SIG例会
by openEuler conference 29 Oct '24

29 Oct '24

您好！ sig-sbom 邀请您参加 2024-10-30 16:00 召开的WeLink会议(自动录制) 会议主题：SBOM SIG例会会议链接：https://meeting.huaweicloud.com:36443/#/j/986957489 会议纪要：https://etherpad.openeuler.org/p/sig-sbom 更多资讯尽在：https://www.openeuler.org/zh/ Hello! sig-sbom invites you to attend the WeLink conference(auto recording) will be held at 2024-10-30 16:00, The subject of the conference is SBOM SIG例会, You can join the meeting at https://meeting.huaweicloud.com:36443/#/j/986957489. Add topics at https://etherpad.openeuler.org/p/sig-sbom. More information: https://www.openeuler.org/en/

1 0

openEuler tc 补充会议
by openEuler conference 29 Oct '24

29 Oct '24

您好！ TC 邀请您参加 2024-10-30 10:00 召开的WeLink会议(自动录制) 会议主题：openEuler tc 补充会议会议链接：https://meeting.huaweicloud.com:36443/#/j/963310592 会议纪要：https://etherpad.openeuler.org/p/TC-meetings 更多资讯尽在：https://www.openeuler.org/zh/ Hello! TC invites you to attend the WeLink conference(auto recording) will be held at 2024-10-30 10:00, The subject of the conference is openEuler tc 补充会议, You can join the meeting at https://meeting.huaweicloud.com:36443/#/j/963310592. Add topics at https://etherpad.openeuler.org/p/TC-meetings. More information: https://www.openeuler.org/en/

1 0

Re: [Tc] Re: Re: %cmake引用统计
by wufengguang 29 Oct '24

29 Oct '24

Issue都在cmake下，容易看到全貌。需要配合写一个close issue的脚本，当构建工程通过后，批量close issue。 Issue需要关联到负责人。目前找到350+ 包含%cmake宏的src-openeuler仓，且在sig-info.yaml里有登记。那下一步就以这350+仓做个构建工程，批量触发问题，批量在cmake下建issue，关联到对应的维护者，推进fix。 From: Xinwei Hu <micromotive(a)qq.com> Sent: Monday, October 28, 2024 7:04 PM To: wufengguang <wufengguang(a)huawei.com> Cc: Funda Wang <fundawang(a)yeah.net>; dev(a)openeuler.org; tc <tc(a)openeuler.org>; wfg(a)mail.ustc.edu.cn; duanpengjie <duanpengjie(a)huawei.com>; yangchaohao <yangchaohao(a)huawei.com> Subject: Re: [Tc] Re: [Dev] Re: %cmake引用统计 issue可以批量建。meta issue没法做实质性关联。我建议直接在cmake下建issue，所有issue都关联到cmake和对应的oeep就好。在 2024年10月28日，15:32，wufengguang <wufengguang(a)huawei.com<mailto:wufengguang@huawei.com>> 写道：普通issue就可以了，EulerMaker团队不会去跟踪这些issue，仅仅是把它当做提醒开发者的一个途径（还有一个途径是email）。 EulerMaker团队会定期重新构建该工程。还继续有问题的包，继续发email提醒。已经fix的包，就不再做任何事。 From: Funda Wang <fundawang(a)yeah.net<mailto:fundawang@yeah.net>> Sent: Monday, October 28, 2024 3:27 PM To: wufengguang <wufengguang(a)huawei.com<mailto:wufengguang@huawei.com>> Cc: dev(a)openeuler.org<mailto:dev@openeuler.org>; tc <tc(a)openeuler.org<mailto:tc@openeuler.org>>; wfg(a)mail.ustc.edu.cn<mailto:wfg@mail.ustc.edu.cn>; duanpengjie <duanpengjie(a)huawei.com<mailto:duanpengjie@huawei.com>>; yangchaohao <yangchaohao(a)huawei.com<mailto:yangchaohao@huawei.com>> Subject: Re:[Dev] Re: %cmake引用统计创建 meta issue 我是同意的。然而gitee的接口是否允许创建子 issue，这个可能要咨询一下。就是将子issue发配给各仓库之后，把这些子issue设置为 meta issue 的子项，便于跟踪进度。在 2024-10-26 12:19:39，"wufengguang" <wufengguang(a)huawei.com<mailto:wufengguang@huawei.com>> 写道：我草拟了一个cmake macros切换计划，大家看是否OK。我仍然建议定义全局%__cmake_in_source_build为1，以保证master分支平滑切换，下游包的fix流程也最简单。同时，通过步骤3-8推动问题暴露和下游包fix。 1. FundaWang/cmake包：在master上合入cmake macros（兼容版本，即PR 80 + 定义全局%__cmake_in_source_build为1) 2. Fengguang/下游包: 提供600+包含%cmake的包清单 3. EulerMaker团队：创建1个工程，总计600+包url，src-openeuler/$pkg/，定义全局%__cmake_in_source_build为0,触发错误 4. FundaWang: fix几个典型情况，提交PR作为demo url；写cmake宏切换文档url 5. EulerMaker团队：写脚本，批量给600+仓提issue，提供cmake宏切换文档url及log url 6. 600+维护者：fork个人仓，fix，提PR到src-openeuler/$pkg/，合入master分支 7. EulerMaker团队：再次批量构建，对未fix的，写脚本，通过sig-info.yaml查发email催促fix 8. 重复以上2步 Regards, Fengguang From: Funda Wang <fundawang(a)yeah.net<mailto:fundawang@yeah.net>> Sent: Friday, October 25, 2024 7:12 PM To: wufengguang <wufengguang(a)huawei.com<mailto:wufengguang@huawei.com>> Cc: dev(a)openeuler.org<mailto:dev@openeuler.org>; tc <tc(a)openeuler.org<mailto:tc@openeuler.org>>; wfg(a)mail.ustc.edu.cn<mailto:wfg@mail.ustc.edu.cn>; duanpengjie <duanpengjie(a)huawei.com<mailto:duanpengjie@huawei.com>> Subject: Re:%cmake引用统计当前进度：根据TC决议，oEEP 已创建： https://gitee.com/openeuler/TC/pulls/110 请大家提出修改意见。目前已有下游工程师反馈，希望用同一个SPEC在前置版本中构建，如： https://gitee.com/src-openeuler/openvino/pulls/1 在 2024-10-23 17:02:32，"wufengguang" <wufengguang(a)huawei.com<mailto:wufengguang@huawei.com>> 写道：受影响的600+ spec清单见附件。受影响的SIG统计： bigdata/sig-info.yaml:1 Private/sig-info.yaml:1 sig-AccLib/sig-info.yaml:1 sig-HPC/sig-info.yaml:1 sig-python-modules/sig-info.yaml:1 sig-recycle/sig-info.yaml:1 sig-RISC-V/sig-info.yaml:1 sig-ROS/sig-info.yaml:1 sig-SDS/sig-info.yaml:1 System-tool/sig-info.yaml:1 xfce/sig-info.yaml:1 sig-bio/sig-info.yaml:2 sig-CloudNative/sig-info.yaml:2 sig-ebpf/sig-info.yaml:2 sig-high-performance-network/sig-info.yaml:2 Networking/sig-info.yaml:3 Runtime/sig-info.yaml:3 sig-embedded/sig-info.yaml:3 DB/sig-info.yaml:4 iSulad/sig-info.yaml:4 sig-compat-winapp/sig-info.yaml:4 sig-Java/sig-info.yaml:4 sig-security-facility/sig-info.yaml:4 Computing/sig-info.yaml:5 GNOME/sig-info.yaml:5 sig-desktop-apps/sig-info.yaml:5 ai/sig-info.yaml:7 sig-OS-Builder/sig-info.yaml:7 Others/sig-info.yaml:9 Programming-language/sig-info.yaml:13 sig-UKUI/sig-info.yaml:16 sig-epol/sig-info.yaml:17 dev-utils/sig-info.yaml:18 Application/sig-info.yaml:21 sig-DDE/sig-info.yaml:27 sig-KIRAN-DESKTOP/sig-info.yaml:28 Desktop/sig-info.yaml:31 Base-service/sig-info.yaml:32 Compiler/sig-info.yaml:36 sig-QT/sig-info.yaml:41 sig-KDE/sig-info.yaml:140 wfg /c/openeuler/community/sig% grep -c -f cmake-pkgs */sig-info.yaml | sort -n -k2 -t: From: wufengguang <wufengguang(a)huawei.com<mailto:wufengguang@huawei.com>> Sent: Wednesday, October 23, 2024 12:35 PM To: dev(a)openeuler.org<mailto:dev@openeuler.org> Cc: liyang (AG) <liyang342(a)huawei.com<mailto:liyang342@huawei.com>> Subject: [Dev] TC议题：cmake macros改进总结 # cmake macros改进，及其600+包升级 ## issues https://gitee.com/src-openeuler/cmake/issues/I5OATI ## 使用cmake编译安装需要单独定义DESTDIR cmake install ./ ## 打包时会导致安装路径不明确，打包文件不完整，所以建议改为： DESTDIR="%{buildroot}" cmake --install ./ https://gitee.com/src-openeuler/cmake/pulls/31 **%cmake_build, %cmake_install 等相关宏的缺失, 使得从 rpm 生态的其他发行版移植软件包不便。** 部分Fedora中包，如asdcplib，SPEC文件中会使用%cmake3_build, %cmake3_install宏定义。但是在openEuler中没有这几个定义，导致用户自行rpmbuild asdcplib.spec报错。 https://gitee.com/src-openeuler/cmake/pulls/53 由于相关宏的缺失，很多的确需要 out-of-source building 的包都会在 spec 中通过各种方式手动指定编译目录参数 Closed: 不完全兼容已有%cmake，会导致软件包批量构建失败aom等软件包批量失败。 https://gitee.com/src-openeuler/cmake/issues/IAND9Y ## cmake新增支持%cmake_build和%cmake_install的实施方案经过多方讨论，提供如下兼容方案1 ## PRs ### 方案1 <https://gitee.com/src-openeuler/cmake/pulls/81> **Support cmake_build and cmake_install** 【8月合入】 | | cmake包 | 各下游包 | | --- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------- | | 修改 | 定义全新 %**cmake_conf** %cmake_build %cmake_install | 逐步修改 %cmake 为 %cmake_conf %cmake_build %cmake_install | | 注解 | %cmake_conf 是在 %cmake 的基础上增加如下两行： + %{!?\_\_cmake_in_source_build:-S "%{\_vpath_srcdir}"} + %{!?\_\_cmake_in_source_build:-B "%{\_\_cmake_builddir}"} | 一旦定义builddir， 需同步修改conf/build/install三阶段 | 【归一化方法】后续版本在条件允许的时候，将 %cmake 和 %cmake_conf 合并成一个宏 ### 方案2 <https://gitee.com/src-openeuler/cmake/pulls/80> **Update cmake macro** 【讨论中】 | | cmake包 | 各下游包 | | ------------------------- | --------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------- | | 修改 | 重定义%cmake， 同时定义全局%__cmake_in_source_build为1 定义全新 %cmake_build %cmake_install | 逐步修改 %cmake 为 %cmake %cmake_build %cmake_install 同时定义%__cmake_in_source_build=0 | | 后期建议（半年后, 等所有下游包完成改造） | 去掉全局%__cmake_in_source_build=1定义 | 移除%__cmake_in_source_build=0 | ## 决策点 1. 技术方向：方案1 or 方案2 ？直接合入PR80 2. 落地版本：面向未来 25.03 ? 是 3. 回合版本：存量版本 22.03, 24.03 收益 ? 建议：仅回合对cmake包的修改，新增宏，以方便用户rpmbuild三方包。暂不考虑。 4. 兼容性：同一个spec, 可以拿到所有版本上去构建？暂不考虑。 5. 分离目录：是最佳实践，是未来方向。但存量软件包迁移是否迫切，收益是否大，优先级是否高？ 6. 在master上改, 批量暴露问题，推动下游包fix，缩短切换期，25.03分叉点前结束切换 7. release sig确认, 出倒排方案 8. oEEP：fundawang，fengguang ## 组织修改600+下游包 TODOs： 1. 确定上述技术路线（二选一） 2. 确定修改清单：在src-openeuler git上总共grep到634个包含%cmake的spec文件, 按SIG分类，发email出来 3. 提供文档与demo，目前发现有以下三类包，需要各自提供修改示例 1. %make_build、%make_install 2. %ninja_build、%ninja_install 3. %\_\_cmake --build、%\_\_cmake --install 4. 组织修改600+下游包spec，迁移到新的cmake宏，落地25.03版本 **决策点**：如何组织？专人批量修改固定套路的多数包，余下的push各个SIG组去修改？ _______________________________________________ Tc mailing list -- tc(a)openeuler.org<mailto:tc@openeuler.org> To unsubscribe send an email to tc-leave(a)openeuler.org<mailto:tc-leave@openeuler.org>

1 0

2024

2023

2022

2021

2020

2019

Dev