- Dev - mailweb.openeuler.org

htop 和 entr 申请加入 src-openeuler
by clouds＠isrc.iscas.ac.cn 01 Jul '20

01 Jul '20

Hi, 系统监控工具 [htop](https://gitee.com/charlize/htop-openEuler) 和文件监控工具 [entr](https://gitee.com/charlize/openEuler-entr) 申请加入 openEuler 软件包仓库，谢谢。 clouds

2 6

【virt sig】虚拟化组件在openeuler仓库里边创建组件仓库
by Zhanghailiang 01 Jul '20

01 Jul '20

背景：由于虚拟化相关组件存在大量代码开发，采用src-openeuler以tar包+patch方式存在开发效率低的问题，现在Virt SIG决定讲其中的qemu，libvirt组件开发移动到openeuler以源码仓库方式进行开发，src-openeuler中的qemu和libvirt 保留用来进行obs编译出包使用，src-openeuler会自动从openeuler同步。问题：当前在操作时遇到问题，由于openeuler中的仓库自动创建相关组件的仓库，导致我们无法使用码云的自动导入功能，直接从组件的上游社区导入解决方法：先讲openeuler自动创建的qemu，libvirt仓库删除，然后通过码云的自动导入仓库功能创建。涉及组件： Qemu，libvirt

1 0

Re: [Virt-Test] Add some patches for openEuler virtualization base on tp-qemu
by Chenqun (kuhn) 30 Jun '20

30 Jun '20

Add attachment patches Thanks. Chen Qun >-----Original Message----- >From: Chenqun (kuhn) >Sent: Tuesday, June 30, 2020 6:21 PM >To: dev(a)openeuler.org; qa(a)openeuler.org >Cc: Chenzhendong (alex) <alex.chen(a)huawei.com>; Zhanghailiang ><zhang.zhanghailiang(a)huawei.com>; Pannengyuan ><pannengyuan(a)huawei.com>; Kezhiming <kezhiming(a)huawei.com>; >Wangshengfang <wangshengfang(a)huawei.com>; Zhangxiaofeng (F) ><victor.zhangxiaofeng(a)huawei.com>; tangjie (A) <tangjie18(a)huawei.com> >Subject: [Virt-Test] Add some patches for openEuler virtualization base on tp- >qemu > >Hi All, > > The tp-qemu is a set of very open source virtualization test cases for qemu and >OpenVSwitch. > Unfortunately, it do not support openEuler and very unfriendly to aarch64 >support. > This serials is to adapt to openEuler and aarch64. There are a total of 16 >patches here. > > We plan to put the tp-qemu in the openEuler community and maintain it for a >long time. > Of course, we will also try to push it to upstream, so that upstream supports >openEuler well. > > The upstream source repository： > https://github.com/autotest/tp-qemu > >Chen Qun (5): > watchdog: check watchdog device need machine for aarch64 > numa_opts: uses smp_override instead of vcpu_maxcpus for aarch64 > numa_maxnodes: set maxnode from 128 to 32. > provider/qemu_version: add qemu_version version_compare function > qmp_command: add qmp 'node-name' expect value for blockdev > >Jie Tang (9): > cpu_device_hotplug_maximum: The value of machine_type getted from > machines.cfg is incorrect on arm. > cpu_device_hotplug: aarch64 do not support vcpu hot-unplug by now. > cpu_hotplug: aarch64 use vm.hotplug_vcpu_device to hotplug vcpu. > cpu_hotplug: autotest module is no longer supported, remove it. > cpu_hotplug: if default irq(15) not exist, need verify another. > cpu_hotplug: can not offline all cpus. > cpu_device_hotplug: Add 'aarch64' to supported platform in > cpu_device_hotplug.cfg. > cpu_hotplug: add more tests for vcpu hot-plug in cpu-hotplug.cfg. > cpu_device_hotplug_maximum: verify max vcpus need hotplug. > >Wang Ziming (2): > hotplug_mem.cfg: edit threshold adapt to arm64-pci machine type. > hotplug_mem: Increase sub_test_wait_time > >Thanks. >Chen Qun >

1 0

[Virt-Test] Add some patches for openEuler virtualization base on tp-qemu
by Chenqun (kuhn) 30 Jun '20

30 Jun '20

Hi All, The tp-qemu is a set of very open source virtualization test cases for qemu and OpenVSwitch. Unfortunately, it do not support openEuler and very unfriendly to aarch64 support. This serials is to adapt to openEuler and aarch64. There are a total of 16 patches here. We plan to put the tp-qemu in the openEuler community and maintain it for a long time. Of course, we will also try to push it to upstream, so that upstream supports openEuler well. The upstream source repository： https://github.com/autotest/tp-qemu Chen Qun (5): watchdog: check watchdog device need machine for aarch64 numa_opts: uses smp_override instead of vcpu_maxcpus for aarch64 numa_maxnodes: set maxnode from 128 to 32. provider/qemu_version: add qemu_version version_compare function qmp_command: add qmp 'node-name' expect value for blockdev Jie Tang (9): cpu_device_hotplug_maximum: The value of machine_type getted from machines.cfg is incorrect on arm. cpu_device_hotplug: aarch64 do not support vcpu hot-unplug by now. cpu_hotplug: aarch64 use vm.hotplug_vcpu_device to hotplug vcpu. cpu_hotplug: autotest module is no longer supported, remove it. cpu_hotplug: if default irq(15) not exist, need verify another. cpu_hotplug: can not offline all cpus. cpu_device_hotplug: Add 'aarch64' to supported platform in cpu_device_hotplug.cfg. cpu_hotplug: add more tests for vcpu hot-plug in cpu-hotplug.cfg. cpu_device_hotplug_maximum: verify max vcpus need hotplug. Wang Ziming (2): hotplug_mem.cfg: edit threshold adapt to arm64-pci machine type. hotplug_mem: Increase sub_test_wait_time Thanks. Chen Qun

1 0

[Virt-Test] Add some patches for openEuler virtualization base on tp-libvirt
by Chenqun (kuhn) 30 Jun '20

30 Jun '20

Hi All, The tp-libvirt is a set of very open source virtualization test cases for libvirt and qemu. Unfortunately, it do not support openEuler and very unfriendly to aarch64 support. This serials is to adapt to openEuler and aarch64. There are a total of 77 patches here. We plan to put the tp-libvirt in the openEuler community and maintain it for a long time. Of course, we will also try to push it to upstream, so that upstream supports openEuler well. The upstream source repository： https://github.com/autotest/tp-libvirt Chen Qun (18): libvirt_hugepage: set static_hugepage nums 4096 vcpu_affinity: change err_msg for vcpu_affinity virsh_domxml_to_native: add arch_bin '/usr/libexec/qemu-kvm' virsh_define: the last char of vmname can't be '-' or '_' vcpu_affinity: set cpuset range from 0 to 7 libvirt_hugepage: recalculate the number of static hugepage emulator_capabilities: add qemu_user root for qemu_conf virsh_nodeinfo: recalculate the number of cores_per_socket_os virsh_change_media_matrix:ide controllers are unsupported for aarch64 virsh_cpu_compare: update expect keyword output for aarch64 max_vcpus: add update_vcpu_topology function for max_vcpu hotplug_serial: fix subprocess.Popen() use error hotplug_serial: don't need delete virtio-serial controller sometime hotplug_serial: fix inconsistency filename between create and attach virsh_domxml_to_native: increase ASAN environmental judgment conditions virsh_domtime: hwclock will be stop both of suspend and managedsave for aarch64 virsh_domtime: add different cpu_mode for aarch64 hotplug_serial: add err msg for the return of two_devid Jie Tang (2): arm_vcpu_hotplug_opts: hot-unplug vcpu action is not supported on aarch64. guestpin: aarch64 do not support vcpu hot-unplug. Ke Zhiming (8): libvirt_usb_hotplug_device: redirect warning to /dev/null virsh_event: wait for few seconds after attach disk virsh_start: declaration before local variable reference virsh_dommemstat: declaration before local variable reference virsh_domstats: internal snapshots not supported on aarch64 virsh memtune: Set acceptable_minus for arm hotplug_serial: delete the existing file before shutil.copy pcibridge: delete s_0 variants Pan Nengyuan (18): virsh_attach_detach_disk: update test case virsh-attach-detach-disk virsh_maxvcpus: fix unboundLocalError in virsh_maxvcpus test case pcibridge: fix incorrect pci bus address usb_hotplug: ignore set selinux status in usb_hotplug test case libvirt_usb_hotplug_device: fix incorrect address attr guestnuma: update test case guestnuma virsh_migrate: update virsh_migrate testcase with numa nodedev: add smmu support on aarch64 virsh_nodedev: add aarch64 support virsh_migrate: dump traceback to improve the testcase's usability pcibridge: Do not convert pci_br_index to decimal at_dt_interface: use 'virtio' model in q35 for interface virsh_migrate: fix attaching interface failed during migration virsh_migrate: do not check 'strict' mode when enable_HP virsh_migrate: remove duplicate reset hugepages virsh_migrate: remove status_error when cache enable virsh_migrate: fix a 'model name' keyerror virsh_migrate: add cpu_model in migration for kunpeng platform Wang Shengfang (2): iface_network: add support for UEFI pxe boot and local boot files virsh_boot: add edk cdrom boot test case Wang Ziming (29): virsh_save_image: fix error for new xml is too large max_vcpus: fix max vcpus num to 'pc-q35' machine type virsh_attach_detach_disk: make sure the multipathd.service is stopped when create VG with a block devices. virtual_disks_multidisks:stop multipathd.service before modprobe scsi_debug hotplug_serial:adapt to the return messages of dup_hotplug hotplug_serial:the object r_o should be a str. libvirt_usb_hotplug_device: the maximum of usb device is 39. virtual_disks_multidisks: increase wait time between detach_disk operations. virsh_domxml_from_native: replace '\s' in re.sub() in virsh_convxml function with ''. virsh_attach_device: remove control characters such as '^@' from the result of session.cmd_output virtual_disks_multidisks: increase wait time in add_sleep function for not only ppc64 platform. virsh_blockcopy: change disk_target_bus and disk_format for lun_t type disk_device virtual_disks_multidisks: Check disk bus device option need to adapt to different platform. virtual_disks_multidisks: change iteration_times as it cause test time out. virtual_disks_multidisks: change virt_disk_addr_options unit to differentiate system disk. virsh_detach_device: Increase sleep to make sure detach_device operation succeed especially for device_alias. virsh_attach_device.py:Add short sleep time after attach_device operation. virtual_disks_multidisks: attach disk to VM with the same index controller,exepct error. sriov: change loop_times as it cause test time out. virsh_save_image_edit: change expected state to make it suitable for no_option. virsh_attach_detach_disk: wait for few seconds after detach disk. virsh_attach_detach_disk: wait for few seconds after attach disk virtual_disks_multidisk: add loader and nvram to xml adapt to aarch64 platform virtual_disks_multidisk: Retain pcie-root-port and pcie-to-pci-bridge when modifying VM XML virsh_attach_detach_disk: Replace the bus type of CDROM adapt to arrch64 platform. virtual_disks_multidisk: Disk bus device option need to adapt to aarch64 platform. virtual_disks_multidisks: Change bus and slot in virt_disk_addr_options parameter libvirt_mem: edit cpu_model and hugepages page_size to adapt to aarch64 and x86_64 platform. sriov: Add new ethernet driver hinic to adapt to arrch64 platform. Thanks. Chen Qun

1 0

[Virt-Test] Add some patches for openEuler virtualization base on avocado and avocado-vt
by Chenqun (kuhn) 30 Jun '20

30 Jun '20

Hi All, Avocado/Avocado-vt is a very good set of automated testing framework and virtualization plugins. Unfortunately, they do not support openEuler and aarch64. This serials is to adapt to openEuler and aarch64. There are a total of 29 patches here, one of which is Avocado and the other 28 are Avocado-vt. We plan to put the avocado/avocado-vt in the openEuler community and maintain it for a long time. Of course, we will also try to push it to upstream, so that upstream supports openEuler well. The upstream source repository： https://github.com/avocado-framework/avocado https://github.com/avocado-framework/avocado-vt Chen Qun (12): virsh: add '--nvram' in undefine for aarch64 base.cfg: add kbd for vm in the base.cfg qemu_vm: openEuler version not support tcp '-redir' utils_misc: change key word for verify_dmesg machines.cfg: set aarch64 default vGIC version=3 qemu_vm: change rombar from 0 to 1 for multiple network cards base.cfg: Add boot index for disk_image base.cfg: add virtio_ports for qemu-guest-agent testcases qemu_vm: add add_numa_object_mem function for aarch64 virt_vm: continue to login when connect to vm failed qemu_vm: don't need add_numa_object_mem after qemu 4.1.0 version qcontainer: change EFI pflash path for different OS in aarch64 Jie Tang (7): get_cpu_model: verify command for aarch64 to get supported cpu models. qemu_vm: when only confirm vm max vcpu, create vm by default. env_process: verify command for aarch64 to check device category. qcontainer: Add qdevice.QCPUBus in bus for machine_arm64_pci. qemu_vm: Set dies=1 while dies=0. base: add download url for iozone utils_test: verify copy dst path and build command for iozone. Ke Zhiming (1): virsh: fix VirshPersistent err Pan Nengyuan (4): virt_vm: use a serial connection when remote login failed utils_misc: fix migrate error on x86 when vlu enable in lscpu cpu.py: fix migrate error on x86 when vlu enable in lscpu nfs: fix nfs mounts repeatedly Wang Shengfang (3): avocado.utils.ditro: support openEuler virt_vm: add kernel panic verification msg in verify kernel crash utils_test: Add new_xml_with_object() to avoid triggering the GC and deleting the xml file Wang Ziming (2): openEuler: add openEuler 20.03 support libvirt: create netfs pool in pre_pool function with correct command Thanks. Chen Qun

1 0

【Meeting Notice】sig-ai-bigdata regular meeting Time: 2020-07-02 11:00-12:00
by 403975152 29 Jun '20

29 Jun '20

发件人: "Meeting Book"<uMeeting(a)huawei.com>; 发送时间: 2020年6月29日(星期一) 下午2:09 收件人: "Hubble_Zhu"<403975152(a)qq.com>; 主题: 【Meeting Notice】sig-ai-bigdata regular meeting Time: 2020-07-02 11:00-12:00 Topic sig-ai-bigdata regular meeting Time 2020-07-02 11:00-12:00((UTC+08:00)Beijing)   Join Conference Join (External) >> Meeting ID 628 852 074   Convener 朱恒博   Agenda 1. sig成员前期工作进展审视 2. 下一步工作计划和分工   Tips: Dial the access number to join conference 注：仅支持部分国家和地区。( Only some countries and regions are supported.) 请点击会议链接按照提示下载Zoom客户端入会，并升级Zoom最新版本。 Please click the conference link and download the Zoom to join the conference, and upgrade to the latest version of Zoom.

1 0

【Meeting Notice】sig-ai-bigdata regular meeting Time: 2020-07-02 11:00-12:00
by 403975152 29 Jun '20

29 Jun '20

发件人: "Meeting Book"<uMeeting(a)huawei.com>; 发送时间: 2020年6月29日(星期一) 下午2:09 收件人: "Hubble_Zhu"<403975152(a)qq.com>; 主题: 【Meeting Notice】sig-ai-bigdata regular meeting Time: 2020-07-02 11:00-12:00 Topic sig-ai-bigdata regular meeting Time 2020-07-02 11:00-12:00((UTC+08:00)Beijing)   Join Conference Join (External) >> Meeting ID 628 852 074   Convener 朱恒博   Agenda 1. sig成员前期工作进展审视 2. 下一步工作计划和分工   Tips: Dial the access number to join conference 注：仅支持部分国家和地区。( Only some countries and regions are supported.) 请点击会议链接按照提示下载Zoom客户端入会，并升级Zoom最新版本。 Please click the conference link and download the Zoom to join the conference, and upgrade to the latest version of Zoom.

1 0

【Meeting Notice】sig-ai-bigdata regular meeting Time: 2020-07-02 11:00-12:00
by 403975152 29 Jun '20

29 Jun '20

发件人: "Meeting Book"<uMeeting(a)huawei.com>; 发送时间: 2020年6月29日(星期一) 下午2:09 收件人: "Hubble_Zhu"<403975152(a)qq.com>; 主题: 【Meeting Notice】sig-ai-bigdata regular meeting Time: 2020-07-02 11:00-12:00 Topic sig-ai-bigdata regular meeting Time 2020-07-02 11:00-12:00((UTC+08:00)Beijing)   Join Conference Join (External) >> Meeting ID 628 852 074   Convener 朱恒博   Agenda 1. sig成员前期工作进展审视 2. 下一步工作计划和分工   Tips: Dial the access number to join conference 注：仅支持部分国家和地区。( Only some countries and regions are supported.) 请点击会议链接按照提示下载Zoom客户端入会，并升级Zoom最新版本。 Please click the conference link and download the Zoom to join the conference, and upgrade to the latest version of Zoom.

1 0

注销OBS系统过渡性域名( openeuler-build.huawei.com )影响确认
by George 24 Jun '20

24 Jun '20

hi,allopenEuler社区提供的OBS构建系统，当前有两个域名在使用: openeuler-build.huawei.com build.openeuler.org 其中（openeuler-build.huawei.com）是前期提供的过渡性域名. 我们（sig-infra）希望提供唯一的域名管理，保留（build.openeuler.org），注销（openeuler-build.huawei.com）。该变更不会影响OBS系统业务功能，将保持和变更前完全一致。如果此变更对您有影响，希望及时反馈，谢谢。

1 0

答复: [Community] 【开发过程疑问】
by Zhuyanpeng 23 Jun '20

23 Jun '20

那说明他们的maillist就是 dev(a)openeuler.org<mailto:dev@openeuler.org> 您通过这个maillist 交流即可，可以在邮件标题前面写上sig名，比如【ovrit】xxxx 发件人: 田琦 [mailto:mrwwheat@gmail.com] 发送时间: 2020年6月23日 9:18 收件人: Zhuyanpeng <zhuyanpeng(a)huawei.com> 主题: Re: [Community] 【开发过程疑问】谢谢您的回复，请问您知道storage和ovirt组的邮件列表吗？网站上的邮件列表都是：dev(a)openeuler.org<mailto:dev@openeuler.org>。他们有自己的频道吗？谢谢！ Zhuyanpeng <zhuyanpeng(a)huawei.com<mailto:zhuyanpeng@huawei.com>> 于2020年6月10日周三下午7:54写道：欢迎参与openEuler 社区 Sig 列表在https://openeuler.org/zh/sig.html，如果对某个sig感兴趣，可以先通过sig的邮件列表进行讨论 Ceph、dpdk、storage等sig，与存储系统相关； Ha等sig，与分布式系统相关 Virt、ovirt等sig，与云计算、虚拟化相关 Sig的信息我们也在努力完善中。发件人: 田琦 [mailto:mrwwheat@gmail.com<mailto:mrwwheat@gmail.com>] 发送时间: 2020年6月11日 10:02 收件人: community(a)openeuler.org<mailto:community@openeuler.org> 主题: [Community] 【开发过程疑问】 Openeuler社区管理员您好，我是田琦，卡耐基梅隆大学（CMU）的计算机科学的研究生，毕业于2019年11月，目前在Google担任软件工程师的工作。我对openeular这个项目非常感兴趣，非常想参与其中做出一些贡献。我对算法开发，存储系统，分布式系统和云计算比较擅长和感兴趣，并且熟悉java/C/C++/Python开发。我注意到openeular的sig组很多都没有联系方式和具体项目内容，您能帮我选择并且沟通一下合适的项目组吗？谢谢！

1 0

openEuler 20.09版本计划已发布，请大家关注，7月28日是大颗粒特性冻结日，之后20.09版本不再接受大颗粒特性的合入。
by Jiangyumin (Jimmy) 20 Jun '20

20 Jun '20

openEuler 20.09 版本计划已发布，请大家关注，7月28日是大颗粒特性冻结日，之后20.09版本不再接受大颗粒特性的合入，大家如果有新的需求，请尽快在release-management中以issue提出讨论，多谢。 openEuler 20.09详细版本计划请参见以下链接： https://gitee.com/openeuler/release-management/blob/master/openEuler-20.09/…

1 0

Re: 开源供应链点亮计划任务咨询
by 方亚芬 20 Jun '20

20 Jun '20

岳泽龙同学，你好。非常感谢对这个任务感兴趣，欢迎报名参加。我是这个项目负责人之一，gitee ID：woqidaideshi，有问题欢迎联系。在你报名参加并最终获取到这个任务后，openEuler 社区会寄一块树莓派 4B 给你，不需要你自己准备。现在是项目申请阶段，可以根据要求报名参加，学生指南：https://isrc.iscas.ac.cn/summer2020/help/student.html。我们这几天在 B 站直播介绍相关任务，感兴趣的话可以去围观一下，直播日程详情见附件。其他资料见官网：https://isrc.iscas.ac.cn/summer2020/。谢谢。 -----原始邮件----- 发件人:"岳泽龙" <lukedyue(a)gmail.com> 发送时间:2020-06-07 08:00:00 (星期日) 收件人: yafen(a)iscas.ac.cn 抄送: 主题: 开源供应链点亮计划任务咨询方老师您好：我是来自华中科技大学数学与统计学院大四的岳泽龙同学，我对您发起的给 openEuler 移植 Xfce 桌面环境给树莓派使用这一任务十分感兴趣，希望能够参与该任务。我已经日常使用 Linux 两年，对把 Linux 作为一个日常使用的操作系统会遇到什么问题有较多了解。我曾经给 Arch Linux 的 AUR 提交过包，https://aur.archlinux.org/packages/?K=lukedyue&SeB=m 以及曾经维护过的 https://git.archlinux.org/svntogit/community.git/tree/trunk/PKGBUILD?h=pack… AOSC OS 打过一些软件包。尽管没有尝试过给使用 RPM 包管理器的 Linux 打包，但我相信我能够较快地学习相关知识并打出第一个包，然后找到依赖关系，逐渐将 Xfce 移植到 openEuler 上。不知道您觉得我能否胜任这一工作？另外我想要咨询一下您的是，如果我没有树莓派 4B 的话，对于相关任务是否需要自己提前进行购买？另：我的 GitHub 链接是 https://github.com/dragonJACson 我的博客链接是 https://blog.dreamof.net 谢谢！岳泽龙祝工作顺利，生活愉快。 ------------------------------------------ 方亚芬中国科学院软件研究所智能软件研究中心邮箱：yafen(a)iscas.ac.cn 地址：北京市海淀区中关村南四街4号5楼

3 5

关于 openEuler 社区官网 SA 和 CVE 的优化需求
by Yanxiaobing 20 Jun '20

20 Jun '20

【Sa部分】前期有客户反馈我们升级包下载没有归类，不方便找出哪些是需要下载的。 a) 建议按版本，源码、架构（X86_64 , aarch64）归类不同的升级包版本1： SRPM XXXX ARM XXXX X86 XXXX 版本2： SRPM XXXX ARM XXXX X86 XXXX b) 建议将安全公告分 Overview 和 Update packages 两个tab页面呈现【CVE部分】 a) 汇总页面将 CVSS 分数修改为严重等级 b) 将严重等级调整到 “概要”列之后 c) 对应CVSS V2 打分的CVE ，页面要显示 CVSS V2 向量列表 d) CVE详情里面增加建议增加关联issue的链接【第三方订阅接口】 OSV 厂商需要有个渠道获取openEuler 的CVE 和 SA 信息，建议以RSS订阅的方式推送数据，建议数据格式CVRF Best Regards 颜小兵 18667033283

3 2

openeuler TC会议议题申请2020/6/19
by liqingqing (C) 19 Jun '20

19 Jun '20

评审openeuler中添加一个f-stack包，该包可以用来支持用户态协议栈功能、或是作为http/https服务器的测试服务器。 f-stack简介：腾讯公司商用的一个用户态协议栈。 https://github.com/F-Stack/f-stack 介绍随着网络接口卡的飞速发展，使用Linux内核处理数据包的不良性能已成为现代网络系统的瓶颈。但是，随着Internet增长的需求不断增长，需要一种性能更高的网络处理解决方案。内核旁路技术已经引起越来越多的关注。有各种类似的技术，例如：DPDK，NETMAP和PF_RING。内核绕过的主要思想是Linux仅用于处理控制流。所有数据流都在用户空间中处理。因此，内核旁路可以避免由于内核数据包复制，线程调度，系统调用和中断引起的性能瓶颈。此外，内核旁路可以通过多重优化方法获得更高的性能。在各种技术中，DPDK已被广泛使用，因为它 F-Stack<http://www.f-stack.org/?from=github>是基于DPDK的开源高性能网络框架，具有以下特征： 1. 网卡在满负载下可以实现的超高网络性能：1000万个并发连接，500万RPS，100万CPS。 2. 移植FreeBSD 11.01用户空间堆栈，它提供了完整的堆栈功能，并削减了大量不相关的功能。这样可以大大提高网络性能。 3. 支持Nginx，Redis和其他成熟的应用程序。服务可以轻松使用F-Stack。 4. 易于通过多进程体系结构进行扩展。 5. 提供微线程接口。具有状态应用程序的各种应用程序可以轻松使用F-Stack获得高性能，而无需处理复杂的异步逻辑。 6. 提供一个Epoll / Kqueue接口，该接口允许多种应用程序轻松使用F-Stack。历史为了应对日益严重的DDoS攻击，2012年底，腾讯云DNSPod的授权DNS服务器从千兆以太网切换到10千兆比特。我们面临几种选择：一种是继续使用Linux内核中的原始网络堆栈，另一个是使用内核旁路技术。经过几轮调查；我们最终选择开发基于DPDK的下一代DNS服务器。原因是DPDK提供超高性能，并且将来可以无缝扩展到40G甚至100G NIC。经过几个月的开发和测试，基于DPDK的高性能DNS服务器DKDNS于2013年10月正式发布。它能够通过单个10GE端口实现多达1100万个QPS，而通过两个10GE端口则能够实现1820万个QPS。然后，我们开发了一个称为F-Stack的用户空间TCP / IP堆栈，该堆栈可通过单个10GE端口处理60万个RPS。随着腾讯云的快速发展，我们越来越多的服务需要更高的网络访问性能。同时，在我们业务增长的推动下，F-Stack不断改进，并最终发展成为通用的网络访问框架。但是我们最初的TCP / IP堆栈无法满足这些服务的需求。继续开发和维护完整的高性能网络堆栈可能太昂贵了。经过评估几个计划；我们最终决定将FreeBSD的（11.0稳定的）TCP / IP堆栈移植到F-Stack中。这不仅使我们能够停止重新发明轮子，我们还可以利用FreeBSD社区将来将带来的改进。多亏了libplebnet<https://gitorious.org/freebsd/kmm-sandbox/commit/fa8a11970bc0ed092692736f17…>和libuinet，<https://github.com/pkelsey/libuinet>这项工作变得容易了很多。随着各种应用程序的快速发展，为了帮助不同的应用程序快速轻松地使用F-Stack，F-Stack集成了Nginx，Redis和其他常用的APP，以及微线程框架，并提供了标准的Epoll / Kqueue界面。目前，除了DNSPod的授权DNS服务器外，腾讯云中还有多种产品使用了F-Stack，例如HttpDNS（D +），COS访问模块，CDN访问模块等。

1 0

Re: 123
by zhouang 18 Jun '20

18 Jun '20

From: zhouang via Test [mailto:test@openeuler.org] Sent: Thursday, June 18, 2020 8:16 PM To: test(a)openeuler.org Subject: [Test] 123 ateast

1 0

[What's the desktop develop plan?]
by buque 18 Jun '20

18 Jun '20

Hi, I just know desktop feature will be published on 9/30. How many software in it. I want to pack some software and work ahead. Thks~

1 0

glibc version update notification
by liqingqing 18 Jun '20

18 Jun '20

hi, dear developers, current glibc version what we used is 2.28 and it was launched at year 2018, it's too old for our system and there are little bugs which are not fixed. and lately gcc version was updated to 9.3, the glibc upstream community has already do a lot of works to adapt this change in the latest version. so in the next week, we will update glibc to the latest version 2.31. notice that this change will cause other package's build result which depend on the glibc. so I need all of your help to resolve this situlation by update your own package or use other ways. thx.

3 4

【dev】【Release Management SIG】openEure 20.03 LTS 7月份补丁版本合入范围统计
by Jiangzhenhua (Ronnie, Kunpeng Computing) 18 Jun '20

18 Jun '20

openEuler 20.03 LTS 7月份补丁版本计划于7月31日发布，现启动补丁合入需求收集，各项目如有补丁合入计划，请通过dev邮件列表通知Release Management SIG组，截止时间6月18日，其他时间提交的补丁合入需求不再接纳在7月份补丁版本中。谢谢！ Best Regards Ronnie Jiang 姜振华 [智能计算email签名图档] 姜振华 Ronnie Jiang 华为智能计算产品部 Mobile: 17052280688 E-mail: zhenhua.jiang(a)huawei.com<mailto:zhenhua.jiang@huawei.com> 深圳龙岗坂田华为基地F4-6-B071S HUAWEI Area F4-6-B071S, Bantian, Longgang District,Shenzhen 518129, P.R.China www.huawei.com<../../../../../z00124665/Desktop/enterprise.huawei.com>

2 1

Re:
by 方亚芬 16 Jun '20

16 Jun '20

同学，你好。如果最终确定由你完成这个项目，我们会寄一个树莓派 4B 给你。欢迎报名参加这个任务。我是这个项目负责人之一，gitee ID：woqidaideshi，邮箱：yafen(a)iscas.ac.xn--cn,-8y9fz4pj74an5eu49afsl4og. 参与任务需要在官方网站报名，报名链接：https://isrc.iscas.ac.cn/summer2020/help/student.html#%E5%AD%A6%E7%94%9F%E5%A6%82%E4%BD%95%E6%8A%A5%E5%90%8D 。谢谢。 -----原始邮件----- 发件人:"淡" <2087698086(a)qq.com> 发送时间:2020-06-15 20:40:49 (星期一) 收件人: "方亚芬" <yafen(a)iscas.ac.cn> 抄送: 主题: Re: Re: 老师你好，这个项目需要树莓派4b，但我只有树莓派3b，请问参加这个项目会配备树莓派4b吗？谢谢老师的解答！ ---Original--- From: "方亚芬"<yafen(a)iscas.ac.cn> Date: 2020/6/14 14:12:12 To: "淡"<2087698086(a)qq.com>; Cc: "dev(a)openeuler.org"<dev(a)openeuler.org>;"Hexiaowen (Hex, EulerOS)"<hexiaowen(a)huawei.com>; Subject: Re: 同学，你好。总结来说，这个项目的目的是：为运行在树莓派 4B 的 openEuler 操作系统添加 Xfce 桌面环境。添加的桌面环境类似我们使用到的其他 Linux 系统桌面，例如需要一些基本的图形界面功能。项目详情见：https://gitee.com/openeuler/marketing/issues/I1H8G3。 -----原始邮件----- 发件人:"淡" <2087698086(a)qq.com> 发送时间:2020-06-12 13:53:55 (星期五) 收件人: yafen <yafen(a)iscas.ac.cn> 抄送: 主题: 老师您好！我像请问一下“项目ID: 2021100 为 openEuler 添加 Xfce 桌面环境并能够运行在树莓派 4B 上”的项目详细信息和内容，谢谢！！祝工作顺利，生活愉快。 ------------------------------------------ 方亚芬中国科学院软件研究所智能软件研究中心邮箱：yafen(a)iscas.ac.cn 地址：北京市海淀区中关村南四街4号5楼祝工作顺利，生活愉快。 ------------------------------------------ 方亚芬中国科学院软件研究所智能软件研究中心邮箱：yafen(a)iscas.ac.cn 地址：北京市海淀区中关村南四街4号5楼

1 0

[Infra] Discussion on bugzila
by Fred Li 16 Jun '20

16 Jun '20

Hi all, I noticed that there is an issue to ask where to find openEuler bugzilla. Firstly, there is not bugzilla for openEuler. If you have requirements on it, please leave your comments in the issue, or reply this email. [1] https://gitee.com/openeuler/community/issues/I1K12D -- Regards Fred Li (李永乐)

2 1

issue about ceph upgrade
by linfeilong 15 Jun '20

15 Jun '20

Hello zinze, There is an issue about ceph upgrade: https://gitee.com/open_euler/dashboard?issue_id=I1C3HC details of this issue: openEuler支持最新的ceph14.2.8 1、openEuler是否能直接通过ceph-deploy工具直接部署ceph 2、openEuler下能否通过部署工具ceph-ansible工具集群部署 3、openEuler能否直接编译最新的ceph源码包 Please take a look, and we should talk about it, thanks

2 1

Re: openeuler 20.3 lts dnf update后重启出错
by Liyongle (Fred) 15 Jun '20

15 Jun '20

Could anyone check this issue? Fred 李永乐 From: yls [mailto:yls_4@163.com] Sent: Monday, June 15, 2020 09:54 To: contact(a)openeuler.org Subject: openeuler 20.3 lts dnf update后重启出错就是正常的命令，dnf update -y,完成后重启，ssh 服务就启动不了，提示openssh 7.8和openssh 8.1冲突

2 1

Re:
by 方亚芬 14 Jun '20

14 Jun '20

同学，你好。总结来说，这个项目的目的是：为运行在树莓派 4B 的 openEuler 操作系统添加 Xfce 桌面环境。添加的桌面环境类似我们使用到的其他 Linux 系统桌面，例如需要一些基本的图形界面功能。项目详情见：https://gitee.com/openeuler/marketing/issues/I1H8G3。 -----原始邮件----- 发件人:"淡" <2087698086(a)qq.com> 发送时间:2020-06-12 13:53:55 (星期五) 收件人: yafen <yafen(a)iscas.ac.cn> 抄送: 主题: 老师您好！我像请问一下“项目ID: 2021100 为 openEuler 添加 Xfce 桌面环境并能够运行在树莓派 4B 上”的项目详细信息和内容，谢谢！！祝工作顺利，生活愉快。 ------------------------------------------ 方亚芬中国科学院软件研究所智能软件研究中心邮箱：yafen(a)iscas.ac.cn 地址：北京市海淀区中关村南四街4号5楼

1 0

关于open euler支持基于NVMe预留命令的HA软件
by Lengchao 13 Jun '20

13 Jun '20

NVMe over fabric是存储前端协议的未来发展趋势，业界主流的存储厂商均已推出支持NVMe over fabric的产品，而HA软件是系统可靠应用解决方案的关键。由于SCSI和NVMe协议体系不同，NVMe定义的专门的预留命令，HA软件配套NVMe over fabric的存储产品，需要配套支持NVMe的预留命令。请问open euler的HA软件预计支持NVMe的预留命令的合入时间和发布时间？

2 3

【Meeting Notice】sig-ai-bigdata regular meeting Time: 2020-06-08 20:00-20:30
by 403975152 10 Jun '20

10 Jun '20

Topic sig-ai-bigdata regular meeting Time 2020-06-08 20:00-20:30((UTC+08:00)Beijing)   Join Conference Join (External) >> Meeting ID 556 377 019   Convener 朱恒博   Agenda 1. sig成员前期工作进展审视 2. 下一步工作计划和分工   Tips: Dial the access number to join conference 注：仅支持部分国家和地区。( Only some countries and regions are supported.) 请点击会议链接按照提示下载Zoom客户端入会，并升级Zoom最新版本。 Please click the conference link and download the Zoom to join the conference, and upgrade to the latest version of Zoom.

3 3

【讨论】是否需要在多个分支间自动同步PR以减少分支间合入遗漏
by Zhuyanpeng 09 Jun '20

09 Jun '20

https://gitee.com/openeuler/infrastructure/issues/I1K340?from=project-issue 发生结果: openEuler当前有2个分支， lts分支、master分支，大部分cve、bug需要在2个分支都要合入。根据openEuler生命周期规划，后续openEuler会同时存在3个分支，比如20.09版本发布后就会有20.03 lts分支、20.09 维护分支、21.03 master分支，那么就存在部分cve、bug需要在3个分支都要合入可能存在只合入了1个分支、其他分支没合入的情况期望结果: 分支间没有漏合，考虑通过基础设施提供自动向其他分支同步issue、pr的能力

1 0

upgrade python3 from 3.7.4 to 3.8.3
by hanxinke 09 Jun '20

09 Jun '20

背景：当前python社区的各个分支状态如下，3.7和3.8分支均为稳定版本，其中3.9还未发布正式版本，3.8分支基于3.7合入了较多的新特性和bugfix。 [cid:image001.png@01D63E49.148DF270] 目标：升级openeuler python3开源软件，准备从3.7.4版本更新到3.8.3稳定版本，两个版本间存在较多差异，需要适配的变更点罗列如下，具体详见附件，后期若有疑问请在该邮件中回复讨论。差异描述差异类型差异引入原因差异引入版本影响分析是否需要适配适配方案在函数调用中允许使用的关键字名称语法受到进一步的限制。特别地，f((keyword)=arg) 不再被允许。关键字参数赋值形式的左侧绝不允许一般标识符以外的其他内容修改 bugfix 3.8 f((keyword)=arg) 不再被允许 Y 使用者适配该变更当类似 [(10, 20) (30, 40)] 这样在代码中少了一个逗号时，编译器将显示 SyntaxWarning 并附带更有帮助的提示。这相比原来用 TypeError 来提示第一个元组是不可调用的更容易被理解修改 DFX增强 3.8 当类似 [(10, 20) (30, 40)] 这样在代码中少了一个逗号时，编译器将从原来的TypeError变为显示 SyntaxWarning Y 使用者适配该变更 datetime.date 或 datetime.datetime 和 datetime.timedelta 对象之间的算术运算现在将返回相应子类的实例而不是基类的实例修改 bugfix 3.8 datetime.date 或 datetime.datetime 和 datetime.timedelta 对象之间的算术运算现在将返回相应子类的实例而不是基类的实例 Y 使用者适配该变更字典推导式已与字典字面值实现同步，会先计算键再计算值 >>> cast = {input('role? '): input('actor? ') for i in range(2)} role? King Arthur actor? Chapman role? Black Knight actor? Cleese 修改 bugfix 3.8 字典推导式已与字典字面值实现同步，会先计算键再计算值 Y 使用者适配该变更异常 asyncio.CancelledError 现在继承自 BaseException 而不是 Exception 修改 DFX增强 3.8 异常 asyncio.CancelledError 现在继承自 BaseException 而不是 Exception Y 使用者适配该变更 collections.namedtuple() 的 _asdict() 方法现在将返回 dict 而不是 collections.OrderedDict。修改 bugfix 3.8 collections.namedtuple() 的 _asdict() 方法现在将返回 dict 而不是 collections.OrderedDict。 Y 使用者适配该变更 csv.DictReader 现在将返回 dict 而不是 collections.OrderedDict 修改 bugfix 3.8 csv.DictReader 现在将返回 dict 而不是 collections.OrderedDict Y 使用者适配该变更对于特定类型的无效或已损坏 gzip 文件现在将引发 BadGzipFile 而不是 OSError 修改 DFX增强 3.8 对于特定类型的无效或已损坏 gzip 文件现在将引发 BadGzipFile 而不是 OSError Y 使用者适配该变更函数 math.factorial() 不再接受非整数类参数修改 bugfix 3.8 函数 math.factorial() 不再接受非整数类参数 Y 使用者适配该变更返回布尔值结果的 os.path 函数例如 exists(), lexists(), isdir(), isfile(), islink(), 以及 ismount() 现在对于包含在 OS 层级无法表示的字符或字节的路径将会返回 False 而不是引发 ValueError 或其子类 UnicodeEncodeError 和 UnicodeDecodeError。修改 DFX增强 3.8 返回布尔值结果的 os.path 函数在对于包含在 OS 层级无法表示的字符或字节的路径将会返回 False 而不是引发 ValueError 或其子类 UnicodeEncodeError 和 UnicodeDecodeError。 Y 使用者适配该变更返回布尔值结果的 pathlib.Path 方法例如 exists(), is_dir(), is_file(), is_mount(), is_symlink(), is_block_device(), is_char_device(), is_fifo(), is_socket() 现在对于包含在 OS 层级无法表示的字符或字节的路径将会返回 False 而不是引发 ValueError 或其子类 UnicodeEncodeError 修改 DFX增强 3.8 返回布尔值结果的 pathlib.Path 方法在对于包含在 OS 层级无法表示的字符或字节的路径将会返回 False 而不是引发 ValueError 或其子类 UnicodeEncodeError Y 使用者适配该变更 shutil.make_archive() 现在对于通过 format="tar" 创建的归档文件将使用新式的 pax (POSIX.1-2001) 格式而非旧式的 GNU 格式修改 bugfix 3.8 shutil.make_archive() 现在对于通过 format="tar" 创建的归档文件将使用新式的 pax (POSIX.1-2001) 格式而非旧式的 GNU 格式 Y 使用者适配该变更 tarfile 模块现在对新的归档默认使用 modern pax (POSIX.1-2001) 格式而不再是之前的 GNU 专属格式修改 bugfix 3.8 tarfile 模块现在对新的归档默认使用 modern pax (POSIX.1-2001) 格式而不再是之前的 GNU 专属格式 Y 使用者适配该变更作为对 DTD 和外部实体检索的缓解，在默认情况下 xml.dom.minidom 和 xml.sax 模块不再处理外部实体修改 bugfix 3.8 作为对 DTD 和外部实体检索的缓解，在默认情况下 xml.dom.minidom 和 xml.sax 模块不再处理外部实体 Y 使用者适配该变更只会安装 python3.8 程序，不再有 python3.8m 程序只会安装 python3.8-config 脚本，不再有 python3.8m-config 脚本 m 已经从动态库文件名后缀中移除：包括标准库中的扩展模块以及第三方包所产生和安装的模块例如从 PyPI 下载的模块。以 Linux 为例，Python 3.7 的后缀 .cpython-37m-x86_64-linux-gnu.so ，在 Python 3.8 中改为 .cpython-38-x86_64-linux-gnu.so。修改 bugfix 3.8 m 已经从动态库文件名后缀中移除：包括标准库中的扩展模块以及第三方包所产生和安装的模块 Y spec文件中需要修改重新组织了所有头文件以更好地区分不同种类的 API： Include/*.h 应为可移植的公有稳定版 C API。 Include/cpython/*.h 应为 CPython 专属的不稳定版 C API；公有 API，部分私有 API 附加 _Py or _PY 前缀。 Include/internal/*.h 应为 CPython 特别专属的私有内部 C API。此 API 不具备向下兼容保证并且不应在 CPython 以外被使用。它们的公开仅适用于特别限定的需求例如调试器和性能分析等必须直接访问 CPython 内部数据而不通过调用函数的应用修改 bugfix 3.8 Include/internal/*.h 应为 CPython 特别专属的私有内部 C API。此 API 不具备向下兼容保证并且不应在 CPython 以外被使用 Y 使用者适配该变更 distutils 的 bdist_wininst 命令现在已弃用，请改用 bdist_wheel (wheel 包) 修改 bugfix 3.8 distutils 的 bdist_wininst 命令现在已弃用，请改用 bdist_wheel (wheel 包) Y 使用者适配该变更 ElementTree 模块中的已弃用方法 getchildren() 和 getiterator() 现在会引发 DeprecationWarning 而不是 PendingDeprecationWarning 修改 DFX增强 3.8 ElementTree 模块中的已弃用方法 getchildren() 和 getiterator() 现在会引发 DeprecationWarning 而不是 PendingDeprecationWarning Y 使用者适配该变更将不是 concurrent.futures.ThreadPoolExecutor 的实例的对象传给 loop.set_default_executor() 已被弃用修改 bugfix 3.8 将不是 concurrent.futures.ThreadPoolExecutor 的实例的对象传给 loop.set_default_executor() 已被弃用 Y 使用者适配该变更 xml.dom.pulldom.DOMEventStream, wsgiref.util.FileWrapper 和 fileinput.FileInput 的 __getitem__() 方法已被弃用修改 bugfix 3.8 xml.dom.pulldom.DOMEventStream, wsgiref.util.FileWrapper 和 fileinput.FileInput 的 __getitem__() 方法已被弃用 Y 使用者适配该变更 typing.NamedTuple 类已弃用了 _field_types 属性而改用具有同样信息的 __annotations__ 属性修改 bugfix 3.8 typing.NamedTuple 类已弃用了 _field_types 属性而改用具有同样信息的 __annotations__ 属性 Y 使用者适配该变更 ast 类 Num, Str, Bytes, NameConstant 和 Ellipsis 被视为已弃用，应当改用 Constant 修改 bugfix 3.8 ast 类 Num, Str, Bytes, NameConstant 和 Ellipsis 被视为已弃用，应当改用 Constant Y 使用者适配该变更 ast.NodeVisitor 的方法 visit_Num(), visit_Str(), visit_Bytes(), visit_NameConstant() 和 visit_Ellipsis() 现在已被弃用，添加 visit_Constant() 方法来处理所有常量节点修改 bugfix 3.8 ast.NodeVisitor 的方法 visit_Num(), visit_Str(), visit_Bytes(), visit_NameConstant() 和 visit_Ellipsis() 现在已被弃用，添加 visit_Constant() 方法来处理所有常量节点 Y 使用者适配该变更 asyncio.coroutine() decorator 已弃用，原有的 @asyncio.coroutine 请改用 async def 来替代修改 bugfix 3.8 asyncio.coroutine() decorator 已弃用，原有的 @asyncio.coroutine 请改用 async def 来替代 Y 使用者适配该变更在 asyncio 中，loop 参数的显式传递已被弃用修改 bugfix 3.8 在 asyncio 中，loop 参数的显式传递已被弃用 Y 使用者适配该变更将协程对象显式传递给 asyncio.wait() 的做法已被弃用修改 bugfix 3.8 将协程对象显式传递给 asyncio.wait() 的做法已被弃用 Y 使用者适配该变更 gettext 模块中的下列函数和方法已被弃用: lgettext(), ldgettext(), lngettext() 和 ldngettext() 修改 bugfix 3.8 gettext 模块中的下列函数和方法已被弃用: lgettext(), ldgettext(), lngettext() 和 ldngettext() Y 使用者适配该变更函数 bind_textdomain_codeset()，方法 output_charset() 和 set_output_charset()，以及函数 translation() 和 install() 的 codeset 形参也被弃用修改 bugfix 3.8 函数 bind_textdomain_codeset()，方法 output_charset() 和 set_output_charset()，以及函数 translation() 和 install() 的 codeset 形参也被弃用 Y 使用者适配该变更 threading.Thread 的 isAlive() 方法已弃用修改 bugfix 3.8 threading.Thread 的 isAlive() 方法已弃用 Y 使用者适配该变更 macpath 模块，在 Python 3.7 中弃用，现已被移除修改 bugfix 3.8 macpath 模块，在 Python 3.7 中弃用，现已被移除 Y 使用者适配该变更函数 platform.popen() 已被移除，它自 Python 3.3 起就已被弃用：请改用 os.popen() 修改 bugfix 3.8 函数 platform.popen() 已被移除，它自 Python 3.3 起就已被弃用：请改用 os.popen() Y 使用者适配该变更函数 time.clock() 已被移除，它自 Python 3.3 起就已被弃用：请根据具体需求改用 time.perf_counter() 或 time.process_time() 以获得具有良好定义的行为修改 bugfix 3.8 函数 time.clock() 已被移除，它自 Python 3.3 起就已被弃用：请根据具体需求改用 time.perf_counter() 或 time.process_time() 以获得具有良好定义的行为 Y 使用者适配该变更 pyvenv 脚本已被移除，推荐改用 python3.8 -m venv 来帮助消除容易混淆 pyvenv 脚本所关联的 Python 解释器这一问题修改 bugfix 3.8 pyvenv 脚本已被移除，推荐改用 python3.8 -m venv 来帮助消除容易混淆 pyvenv 脚本所关联的 Python 解释器这一问题 Y spec文件中需要修改使用者需要适配 parse_qs, parse_qsl 和 escape 已从 cgi 模块中被移除。这些函数自 Python 3.2 或更早就已被弃用。它们应改为从 urllib.parse 和 html 模块导入修改 bugfix 3.8 parse_qs, parse_qsl 和 escape 已从 cgi 模块中被移除。这些函数自 Python 3.2 或更早就已被弃用。它们应改为从 urllib.parse 和 html 模块导入 Y 使用者适配该变更 filemode 函数已从 tarfile 模块中被移除修改 bugfix 3.8 filemode 函数已从 tarfile 模块中被移除 Y 使用者适配该变更 XMLParser 构造器不再接受 html 参数修改 bugfix 3.8 XMLParser 构造器不再接受 html 参数 Y 使用者适配该变更 XMLParser 的 doctype() 方法已被移除修改 bugfix 3.8 XMLParser 的 doctype() 方法已被移除 Y 使用者适配该变更 "unicode_internal" 编解码器已被移除修改 bugfix 3.8 "unicode_internal" 编解码器已被移除 Y 使用者适配该变更 sqlite3 模块的 Cache 和 Statement 对象已不再公开给用户修改 bugfix 3.8 sqlite3 模块的 Cache 和 Statement 对象已不再公开给用户 Y 使用者适配该变更 fileinput.input() 和 fileinput.FileInput() 中自 Python 3.6 起就已被忽略并弃用的 bufsize 关键字参数已被移除修改 bugfix 3.8 fileinput.input() 和 fileinput.FileInput() 中自 Python 3.6 起就已被忽略并弃用的 bufsize 关键字参数已被移除 Y 使用者适配该变更在 Python 3.7 中弃用的函数 sys.set_coroutine_wrapper() 和 sys.get_coroutine_wrapper() 已被移除修改 bugfix 3.8 在 Python 3.7 中弃用的函数 sys.set_coroutine_wrapper() 和 sys.get_coroutine_wrapper() 已被移除 Y 使用者适配该变更 yield 表达式（包括 yield 和 yield from 子句）现在不允许在推导式和生成器表达式中使用（但 for 子句最左边的可迭代对象表达式除外）修改 bugfix 3.8 yield 表达式（包括 yield 和 yield from 子句）现在不允许在推导式和生成器表达式中使用（但 for 子句最左边的可迭代对象表达式除外） Y 使用者适配该变更当标识号检测 (is 和 is not) 与特定类型的字面值 (例如字符串和数字) 一同使用时编译器现在会产生 SyntaxWarning。该警告会建议用户改用相等性检测 (== and !=) 修改 bugfix 3.8 当标识号检测 (is 和 is not) 与特定类型的字面值 (例如字符串和数字) 一同使用时编译器现在会产生 SyntaxWarning。该警告会建议用户改用相等性检测 (== and !=) Y 使用者适配该变更从内置类型 bool, int, float, complex 和标准库的一些类中移除了 __str__ 实现。它们现在会从 object 继承 __str__()。作为结果，在这些类的子类中定义 __repr__() 方法将会影响它们的字符串表示修改 bugfix 3.8 从内置类型 bool, int, float, complex 和标准库的一些类中移除了 __str__ 实现。它们现在会从 object 继承 __str__()。作为结果，在这些类的子类中定义 __repr__() 方法将会影响它们的字符串表示 Y 使用者适配该变更 subprocess.Popen的preexec_fn参数不再与子解释器兼容。在子解释器中使用该参数会引起RuntimeError 修改 bugfix 3.8 subprocess.Popen的preexec_fn参数不再与子解释器兼容。在子解释器中使用该参数会引起RuntimeError Y 使用者适配该变更当传入多模数据时 statistics.mode() 函数不会再引发异常修改 bugfix 3.8 当传入多模数据时 statistics.mode() 函数不会再引发异常 Y 使用者适配该变更 tkinter.ttk.Treeview 类的 selection() 方法不再接受参数。带参数调用该方法来改变选择在 Python 3.6 中已弃用。请使用专门方法例如 selection_set() 来改变选择修改 bugfix 3.8 tkinter.ttk.Treeview 类的 selection() 方法不再接受参数。带参数调用该方法来改变选择在 Python 3.6 中已弃用。请使用专门方法例如 selection_set() 来改变选择 Y 使用者适配该变更附带 'r' 旗标打开的 dbm.dumb 数据库现在将是只读的。如果数据库不存在，附带 'r' 和 'w' 旗标的 dbm.dumb.open() 不会再创建数据库修改 bugfix 3.8 附带 'r' 旗标打开的 dbm.dumb 数据库现在将是只读的。如果数据库不存在，附带 'r' 和 'w' 旗标的 dbm.dumb.open() 不会再创建数据库 Y 使用者适配该变更现在当自定义元类未在传给 type.__new__ 的命名空间中提供 __classcell__ 入口时将引发 RuntimeError。在 Python 3.6--3.7 中是则是引发 DeprecationWarning 修改 DFX增强 3.8 现在当自定义元类未在传给 type.__new__ 的命名空间中提供 __classcell__ 入口时将引发 RuntimeError。在 Python 3.6--3.7 中是则是引发 DeprecationWarning Y 使用者适配该变更现在所有平台下的 mmap.flush() 方法都会在成功时返回 None 并在错误时引发异常。之前 Unix 下会在成功时返回零；在失败时引发错误。修改 bugfix 3.8 现在所有平台下的 mmap.flush() 方法都会在成功时返回 None 并在错误时引发异常。之前 Unix 下会在成功时返回零；在失败时引发错误。 Y 使用者适配该变更从只读的 dbm 数据库 (dbm.dumb, dbm.gnu 或 dbm.ndbm) 删除键将会引发 error (dbm.dumb.error, dbm.gnu.error 或 dbm.ndbm.error) 而不是 KeyError 修改 DFX增强 3.8 从只读的 dbm 数据库 (dbm.dumb, dbm.gnu 或 dbm.ndbm) 删除键将会引发 error (dbm.dumb.error, dbm.gnu.error 或 dbm.ndbm.error) 而不是 KeyError Y 使用者适配该变更当将 'socket' 作为 name 形参传入时，函数 asyncio.BaseTransport.get_extra_info() 现在会返回一个可安全使用的套接字对象修改 bugfix 3.8 当将 'socket' 作为 name 形参传入时，函数 asyncio.BaseTransport.get_extra_info() 现在会返回一个可安全使用的套接字对象 Y 使用者适配该变更 PyEval_ReInitThreads() 函数已从 C API 中移除。它不应当被显式地调用；请改用 PyOS_AfterFork_Child() 修改 bugfix 3.8 PyEval_ReInitThreads() 函数已从 C API 中移除。它不应当被显式地调用；请改用 PyOS_AfterFork_Child() Y 使用者适配该变更在 Unix 上，C 扩展不会再被链接到 libpython, 当 Python 被嵌入时，libpython 不可使用 RTLD_LOCAL 加载，而要改用 RTLD_GLOBAL。修改 bugfix 3.8 在 Unix 上，C 扩展不会再被链接到 libpython, 当 Python 被嵌入时，libpython 不可使用 RTLD_LOCAL 加载，而要改用 RTLD_GLOBAL。 Y 使用者适配该变更移除了操作码 BREAK_LOOP, CONTINUE_LOOP, SETUP_LOOP 和 SETUP_EXCEPT。添加了新的操作码 ROT_FOUR, BEGIN_FINALLY, CALL_FINALLY 和 POP_FINALLY。修改了 END_FINALLY 和 WITH_CLEANUP_START 的行为修改 bugfix 3.8 移除了操作码 BREAK_LOOP, CONTINUE_LOOP, SETUP_LOOP 和 SETUP_EXCEPT。添加了新的操作码 ROT_FOUR, BEGIN_FINALLY, CALL_FINALLY 和 POP_FINALLY。修改了 END_FINALLY 和 WITH_CLEANUP_START 的行为 Y 使用者适配该变更 platform.dist()和linux_distribution()已经被删除修改 bugfix 3.8 platform.dist()和linux_distribution()已经被删除 Y 使用者适配该变更

2 2

答复: TC review提醒 2020/06/01 软件包管理规范检视
by Hexiaowen (Hex, EulerOS) 06 Jun '20

06 Jun '20

Hi all：这个PR 是关于软件管理、选型相关的内容。https://gitee.com/openeuler/community/pulls/495 大家讨论比较激烈，已经根据大家意见做了刷新。烦请大家挑毛病，提建议。何晓文（@overweight） Tel : +86 18042018786 Email : hexiaowen(a)huawei.com This e-mail and its attachments contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it! 发件人: Hexiaowen (Hex, EulerOS) 发送时间: 2020年6月2日 9:39 收件人: 'tc(a)openeuler.org' <tc(a)openeuler.org>; 'dev(a)openeuler.org' <dev(a)openeuler.org> 抄送: Xiongwei (William, Euler) <xiongwei888(a)huawei.com>; Xiehong (Cynthia) <xiehong(a)huawei.com>; Zhanghailiang <zhang.zhanghailiang(a)huawei.com>; Guohanjun (Hanjun Guo) <guohanjun(a)huawei.com>; Xiexiuqi <xiexiuqi(a)huawei.com>; Wangxun (Dream) <dream.wangxun(a)huawei.com> 主题: TC review提醒 2020/06/01 软件包管理规范检视 Hi TC & dev members：关于软件包管理，这个提交整理了一个初稿，涉及引入、退出、选型升级。 https://gitee.com/openeuler/community/pulls/495 请各位TC成员、及社区开发者检视，并充分讨论。 Thanks

1 0

【Meeting Notice】sig-ai-bigdata regular meeting Time: 2020-06-08 20:00-20:30
by 403975152 05 Jun '20

05 Jun '20

Topic sig-ai-bigdata regular meeting Time 2020-06-08 20:00-20:30((UTC+08:00)Beijing)   Join Conference Join (External) >> Meeting ID 556 377 019   Convener 朱恒博   Agenda 1. sig成员前期工作进展审视 2. 下一步工作计划和分工   Tips: Dial the access number to join conference 注：仅支持部分国家和地区。( Only some countries and regions are supported.) 请点击会议链接按照提示下载Zoom客户端入会，并升级Zoom最新版本。 Please click the conference link and download the Zoom to join the conference, and upgrade to the latest version of Zoom.

1 0

release management 目录
by Jiangzhenhua (Ronnie, Kunpeng Computing) 04 Jun '20

04 Jun '20

建议maintainer 先定义清楚repo下面的目录，repo源下有个readme，说明每个目录的用途，后面大家创建目录，或者文件，就可以有参照了。大家觉得呢？ Best Regards Ronnie Jiang 姜振华 [智能计算email签名图档] 姜振华 Ronnie Jiang 华为智能计算产品部 Mobile: 17052280688 E-mail: zhenhua.jiang(a)huawei.com<mailto:zhenhua.jiang@huawei.com> 深圳龙岗坂田华为基地F4-6-B071S HUAWEI Area F4-6-B071S, Bantian, Longgang District,Shenzhen 518129, P.R.China www.huawei.com<../../../../../z00124665/Desktop/enterprise.huawei.com>

2 1

Re: 移植 openEuler 至 RK3399 平台
by 方亚芬 03 Jun '20

03 Jun '20

吴超超同学，你好，欢迎报名参加这个任务。我是这个项目负责人之一，gitee ID：woqidaideshi，有问题欢迎联系。参与任务需要在官方网站报名，报名链接：https://isrc.iscas.ac.cn/summer2020/help/student.html#%E5%AD%A6%E7%94%9F%E5%A6%82%E4%BD%95%E6%8A%A5%E5%90%8D 。谢谢。 -----原始邮件----- 发件人:"super jxwcsuper" <jxwcsuper(a)gmail.com> 发送时间:2020-06-03 09:04:01 (星期三) 收件人: hexiaowen(a)huawei.com, yafen(a)iscas.ac.cn 抄送: 主题: 移植 openEuler 至 RK3399 平台导师：您好我是吴超超，是东莞理工大学的在读研究生，我的研究方向是物联网，同时我对机器视觉也有着浓厚的兴趣，想向嵌入式机器视觉发展，我对您的这个移植openEuler至RK3399平台的项目很感兴趣，希望能够有机会在您的指导下完成这个开源项目，下面是我的简历，希望您能够考虑一下，谢谢。祝工作顺利，生活愉快。 ------------------------------------------ 方亚芬中国科学院软件研究所智能软件研究中心邮箱：yafen(a)iscas.ac.cn 地址：北京市海淀区中关村南四街4号5楼

1 0

请问文件监控工具 entr 应加入哪个SIG？
by clouds 02 Jun '20

02 Jun '20

大家好，文件监控工具 [entr](http://eradman.com/entrproject/) 的RPM包已在 OpenEuler 系统中通过安装验证，请问应该加入哪个 SIG，另外是否有关于向社区提交包的流程文档链接？谢谢。

2 1

TC review提醒 2020/06/01 软件包管理规范检视
by Hexiaowen (Hex, EulerOS) 02 Jun '20

02 Jun '20

Hi TC & dev members：关于软件包管理，这个提交整理了一个初稿，涉及引入、退出、选型升级。 https://gitee.com/openeuler/community/pulls/495 请各位TC成员、及社区开发者检视，并充分讨论。 Thanks

1 0

答复: “移植 openEuler 至 RK3399 平台”项目申请
by Hexiaowen (Hex, EulerOS) 01 Jun '20

01 Jun '20

后续交流的邮件，可以发到dev(a)openeuler.org<mailto:可以发到dev@openeuler.org> 首先非常欢迎你参与openEuler的社区项目，为openEuler社区贡献自己的力量。 Woqidaideshi(玉芬) yafen(a)iscas.ac.cn<mailto:yafen@iscas.ac.cn> 是这个项目的具体负责人。xiaowen_he这是我的微信号，我们也可以微信群组交流。当前处于项目发布阶段，我们在制定项目相关的具体实施计划和运作流程。我们建议你提前熟悉openEuler社区相关的开发流程，试用openEuler。何晓文（Hex EulerOS）庞加莱实验室 [2012实验室] Tel : +86 18042018786 Email : hexiaowen(a)huawei.com [cid:image002.png@01D63802.7498F680] This e-mail and its attachments contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it! 发件人: 王力猛 [mailto:407860076@qq.com] 发送时间: 2020年5月30日 20:29 收件人: Hexiaowen (Hex, EulerOS) <hexiaowen(a)huawei.com> 主题: “移植 openEuler 至 RK3399 平台”项目申请尊敬的导师：您好！我是中国地质大学（北京）控制工程专业研一学生王力猛，研究方向为嵌入式系统。学生对linux系统操作及linux内核有所学习，基本掌握C++和Python编程语言。与同实验室同学一同参与竞赛项目，具有良好的团队合作能力，同时对于新知识有着浓厚的学习兴趣。学生对openEuler社区任务列表中的“No.88-移植openEuler至RK3399平台”（https://gitee.com/openeule… 最后祝老师身体健康、事业有成！

1 0

你好，请问ShellCheck和shfmt仓新上线https://gitee.com/src-openeuler，需要加入哪个SIG？
by Wangyushui 01 Jun '20

01 Jun '20

l ShellCheck<https://github.com/koalaman/shellcheck> 是一款实用的 shell脚本静态检查工具。 l shfmt<https://github.com/mvdan/sh>是一款对shell脚本进行格式化工具，可以让代码格式更加美观，易于阅读 ________________________________

4 3

会议纪要：【Meeting Notice】sig-ai-bigdata regular meeting Time: 2020-05-28 18:30-19:00
by 403975152 28 May '20

28 May '20

与会人：sinever，Hubble_Zhu, traffic_millions, njlzk, Anonymous_Z, Liusheng, zhaobo, zhengzhenyu, Hexiujun, wangxiyuan, Wangli, zhangmiao 整体计划：规划在openEuler 20.03LTS和openEuler20.09版本上线AI和大数据重点软件包，聚焦如下几个软件包发力 AI: tensorflow, pytorch BigData: spark, mapreduce, yarn, hdfs, flink, hbase, hive 会上问题：问题1: 验证各个软件包功能的策略？结论: 仅测试基本功能。测试全部功能工作量大，一些扩展特性也不支持所有平台。问题2：软件包的依赖包有问题如何处理？   举例：flink当前主线版本编译没问题，基本功能没问题。但在使用一些扩展功能的时候。发现依赖的netty有问题   当前解决方案：本地重新构建netty替换原有so。结论：依据功能特点和修复难度来决策   如果是扩展功能，不解决   如果是基本功能，并且通过简单制作私有patch的方法可以解决，那就用私有patch解决   如果是基本功能，但是修复难度较大不好解决，那就先放一放。下一步计划： Hubble_Zhu: 1. 建议尽快验证大数据关键包在openEuler arm环境上的执行，编译 2. 负责MapReduce，hdfs，flink，hive，hbase上线 traffic_millions: 1. 建议尽快推动dlib代码上openEuler，尽快闭环 2. 建议自己使用一下dlib api 3. 负责spark上线 njlzk: 1. 负责pytorch上线 Anonymous_Z 1. 建议尽快验证jupyter基本功能在openEuler arm上运行，前期工作尽快闭环 2. 负责yarn上线 sinever: 1. 规划软件包版本的选型策略 2. 规划软件包的更新策略 3. 负责TensorFlow上线 Hubble Zhu QQ:      403975152 TEL:     18565630552 E-mail: 403975152(a)qq.com   ------------------ 原始邮件 ------------------ 发件人: "朱恒博"<403975152(a)qq.com>; 发送时间: 2020年5月28日(星期四) 上午9:43 收件人: "dev"<dev(a)openeuler.org>;"tc"<tc(a)openeuler.org>;"sig-ai-bigdata"<sig-ai-bigdata(a)openeuler.org>; 主题: 【Meeting Notice】sig-ai-bigdata regular meeting Time: 2020-05-28 18:30-19:00 Topic sig-ai-bigdata regular meeting Time 2020-05-28 18:30-19:00((UTC+08:00)Beijing)   Join Conference Join (External) >> Meeting ID 424 821 546   Convener Hubble_Zhu   Agenda 1. sig成员前期工作审视； 2. TC例会思想传达 3. 下一步工作计划和分工   Tips: Dial the access number to join conference 注：仅支持部分国家和地区。( Only some countries and regions are supported.) 请点击会议链接按照提示下载Zoom客户端入会，并升级Zoom最新版本。 Please click the conference link and download the Zoom to join the conference, and upgrade to the latest version of Zoom.

1 0

OpenJFX is launching!
by hedongbo 28 May '20

28 May '20

JavaFX/OpenJFX is a set of graphics and media APIs that enables Java developers to design, create, test, debug, and deploy rich client applications that operate consistently across diverse platforms. We have set up a repo request[1] in openEuler, Bytedance may need JavaFX, too. [1] https://gitee.com/openeuler/community/pulls/492

1 0

希望参与 Python 和函数式语言相关的工作
by clouds 28 May '20

28 May '20

大家好，我是一名数据分析工程师，工作中使用 Python 和 R 比较多，对函数式语言也比较感兴趣，比如 Ocaml，Clojure, Racket, Julia 等，有多年使用 Linux （以 Debian 系发行版为主，也使用过 CentOS）经验，希望能够参与 SIG Programming-language 方面的工作，谢谢。 clouds

2 1

【Meeting Notice】sig-ai-bigdata regular meeting Time: 2020-05-28 18:30-19:00
by 403975152 28 May '20

28 May '20

Topic sig-ai-bigdata regular meeting Time 2020-05-28 18:30-19:00((UTC+08:00)Beijing)   Join Conference Join (External) >> Meeting ID 424 821 546   Convener Hubble_Zhu   Agenda 1. sig成员前期工作审视； 2. TC例会思想传达 3. 下一步工作计划和分工   Tips: Dial the access number to join conference 注：仅支持部分国家和地区。( Only some countries and regions are supported.) 请点击会议链接按照提示下载Zoom客户端入会，并升级Zoom最新版本。 Please click the conference link and download the Zoom to join the conference, and upgrade to the latest version of Zoom.

1 0

TC meeting 议题刷新
by myeuler 27 May '20

27 May '20

本次的TC meeting定于周三上午10点，请大家申报议题，目前有如下的几个议题： * SIG申请申请成立sig-python-modules SIG组，收集Python的各种module，通过自动化工具进行软件包的生成申请成立sig-perl-modules SIG组，收集perl的各种module，通过自动化工具进行软件包的生成。申请成立sig-release-management SIG组，协同厂商做release的roadmap，特性对齐等。申请成立sig-gnome SIG组，负责补齐openEuler的gnome应用生态申请成立open-CV SIG组。 https://gitee.com/openeuler/community/pulls/480讨论。是否批准auto_py2to3成立一个SIG https://gitee.com/openeuler/community/pulls/460，成立sig-REDF决策。 * openEuler-Advisor进展介绍。 * openEuler/pyporter工具介绍和后续开发计划介绍。 * sig-ai-bigdata工作进展，下一步计划和roadmap汇报 * RISC-V SIG roadmap ，进展介绍，以及部分RISC-V 软件包版本决策。

3 3

【Meeting Notice】sig-ai-bigdata regular meeting Time: 2020-05-28 18:30-19:00
by Meeting Book 27 May '20

27 May '20

1 0

RISC-V SIG 会议纪要答复: [Tc] TC meeting 议题刷新
by zhangxuzhou 27 May '20

27 May '20

* RISC-V SIG roadmap ，进展介绍，以及部分RISC-V 软件包版本决策。遗留问题： 1．对openEuler源码包有修改的尽快推到主线；需要和负责人同步社区支持RISC-V 的软件包版本信息，必要的推动升级； 2．源码包名称中不应带有arch 标识，需要确定原因并重新构建 3．与Release SIG 对齐gcc、glibc、gdb在 20.09 版本上的策略，确定最终使用的版本； 4．与Release SIG 对齐 RISC-V 版本使用的kernel 版本计划 5．在openEuler/ autobuild-openeuler4riscv -增加文档介绍如何得到最小系统的软件包列表发件人: myeuler [mailto:myeuler@163.com] 发送时间: 2020年5月26日 11:29 收件人: openEuler技术委员会 <tc(a)openeuler.org>; openEuler-dev <dev(a)openeuler.org> 主题: [Tc] TC meeting 议题刷新本次的TC meeting定于周三上午10点，请大家申报议题，目前有如下的几个议题： * SIG申请申请成立sig-python-modules SIG组，收集Python的各种module，通过自动化工具进行软件包的生成申请成立sig-perl-modules SIG组，收集perl的各种module，通过自动化工具进行软件包的生成。申请成立sig-release-management SIG组，协同厂商做release的roadmap，特性对齐等。申请成立sig-gnome SIG组，负责补齐openEuler的gnome应用生态申请成立open-CV SIG组。 https://gitee.com/openeuler/community/pulls/480讨论。是否批准auto_py2to3成立一个SIG https://gitee.com/openeuler/community/pulls/460，成立sig-REDF决策。 * openEuler-Advisor进展介绍。 * openEuler/pyporter工具介绍和后续开发计划介绍。 * sig-ai-bigdata工作进展，下一步计划和roadmap汇报 * RISC-V SIG roadmap ，进展介绍，以及部分RISC-V 软件包版本决策。

1 0

[RM] Release Manager Team Meeting Minutes 20200526
by Jiangyumin (Jimmy) 26 May '20

26 May '20

Release Manager Team Meeting Minutes 20200526 Time: 9:10 �C 10:30 on Tuesday, May 26, 2020 Attendee: Release Manager Team Summary: Jiang Yumin Conclusion:�� һ�� Sig��&Maintainner��ؼ��ơ��Ͳ��Խ��ȡ��ؼ��Խ��£� Related SIG team and maintainer aligns the progress of key feature Design, Coding, and Testing. The progress of key features is as follows�� n OS��ȷ��1069��һ��601��303��ģ��173��,��79%�� OS Dependency Package: 1069 software packages to be supplemented have been sorted out, the development of the first batch of 601 software packages has been started, and completed 303 rectifications and compiled 173. The overall progress is 79%. n ��ƽ̨��裺��Ͳ��ƺ�ԭ��֤��60%�� Package Management: Completed software package dependency management and patch tracing, completed design and prototype verification, and started development. The overall progress is 60%. n ��ƽ̨��𡢵��ּ��ɣ��뿪��׶�, ��չ30%��ݴ��Դ�빹��70%��lkp-test/��Դ��40%�� Community Testing Platform: The deployment and scheduling tasks are completed by level, and the development progress 30%. Data processing and source code building: 70%; klp-test/open-source use case design: 40%. n OS��---��ȿ�ܼ��2P MySQL��ݿ�mix��4P MariaDB��ݿ��Ŀ��Ѵ�ɡ�MySQL��ŵĲ�Ʒ��Ҫ��ʼ�� Domain-based scheduling framework technology: The 2P MySQL database mix scenario and Kunpeng 4P MariaDB database optimization objectives have been achieved. The product implementation of MySQL tuning will start. n OS��---A-Ops��(�ں��滻)��չ55%��Ӧ�ó��ڴ�PIN/�ָ��Լ��ҳ��Ϣ��ɴ��뿪��֤��ɿ��Լӹ̽׶Ρ�CNOS��ܼ��տ�Դ��ʽ��ɿ�� A-Ops technology (hot kernel replacement): The overall requirement progress is 55%. The code development for application memory PIN/recovery and restart page information storage has been completed, and the test verification and reliability hardening phases have started. CNOS framework continues to complete development in the community in open source manner. n ��Ὺ��ͳһͨ��ӻ��巽ʽ��֣��ݹ�һ��⻯��Ҳ�� Subsequent meeting development progress is uniformly presented through visual board, and the content is unified presentation (the virtual feature is also included). �� ⡣ 1��ȷ��Դ��1->N��У��SIG��(��ؿ��ϴ��)�ֱ��Ƿ��Ҫ��ѭ��˾�µĿ�Դ��Ҫ�� During the 1-> N incubation process in open source community, clarify whether the new SIG and features (local development, upload community) need to follow the company��s new open source rule. Mingpei

1 0

【Meeting Notice】TC meeting Time: 2020-05-27 10:00-12:30
by Meeting Book 26 May '20

26 May '20

1 0

TC meeting 议题
by myeuler 25 May '20

25 May '20

本次的TC meeting定于周三上午10点，请大家申报议题，目前有如下的几个议题： 1. 申请成立sig-python-modules SIG组，收集Python的各种module，通过自动化工具进行软件包的生成 2. 申请成立sig-perl-modules SIG组，收集perl的各种module，通过自动化工具进行软件包的生成。 3. 申请成立open-CV SIG组。 4. https://gitee.com/openeuler/community/pulls/480讨论。是否批准auto_py2to3成立一个SIG 5. https://gitee.com/openeuler/community/pulls/460，成立sig-REDF决策。 6. openEuler-Advisor进展介绍。 7. openEuler/pyporter工具介绍和后续开发计划介绍。 8. sig-ai-bigdata工作进展，下一步计划和roadmap汇报 9. RISC-V SIG roadmap ，进展介绍，以及部分RISC-V 软件包版本决策。如果有其它议题，请大家申请，议题排序依然是SIG组申请优先讨论。谢谢

2 1

TC meeting 议题列表
by myeuler 25 May '20

25 May '20

本次的TC meeting定于周三上午10点，请大家申报议题，目前有如下的几个议题： 1. 申请成立sig-python-modules SIG组，收集Python的各种module，通过自动化工具进行软件包的生成 2. 申请成立sig-perl-modules SIG组，收集perl的各种module，通过自动化工具进行软件包的生成。 3. 申请成立open-CV SIG组。 4. https://gitee.com/openeuler/community/pulls/480讨论。是否批准auto_py2to3成立一个SIG 5. openEuler-Advisor进展介绍。 6. openEuler/pyporter工具介绍和后续开发计划介绍。 7. sig-ai-bigdata工作进展，下一步计划和roadmap汇报如果有其它议题，请大家申请，议题排序依然是SIG组申请优先讨论。谢谢

1 0

TC meeting topic collection
by myeuler 25 May '20

25 May '20

本次的TC meeting定于周三上午10点，请大家申报议题，目前有如下的几个议题： 1. 申请成立sig-python-modules SIG组，收集Python的各种module，通过自动化工具进行软件包的生成 2. 申请成立sig-perl-modules SIG组，收集perl的各种module，通过自动化工具进行软件包的生成。 3. 申请成立open-CV SIG组。 4. https://gitee.com/openeuler/community/pulls/480讨论。是否批准auto_py2to3成立一个SIG 5. openEuler-Advisor进展介绍。 6. openEuler/pyporter工具介绍和后续开发计划介绍。如果有其它议题，请大家申请，议题排序依然是SIG组申请优先讨论。谢谢

1 0

【Meeting Notice】sig-ai-bigdata regular meeting Time: 2020-05-23 10:30-12:00
by 正心 24 May '20

24 May '20

1 1

[RM] Release Manager Team Conference notification 0526
by Jiangyumin (Jimmy) 22 May '20

22 May '20

Release Manager Team Meeting 0526 会议时间 2020年5月26日（周二）9:00 -11:00 会议地点 Web 会议主题 Release Manager Team Meeting 召集人 MarlonMa 与会人 Release Manager Team 会议议题 Fixed topics： ? Key Features Design and Development Progress ? Discussion on risks and key issues Arrange other topics as needed. 会议ID Join Conference Join (Internal) >><http://imeeting.huawei.com/meeting/joinzoom?id=382945312&app=welink> Join (External) >><https://welink-meeting.zoom.us/j/382945312> Meeting ID 382 945 312 注意事项 1、请勿迟到、早退； 2、会议期间，请将手机设为振动或会议状态； 3、请控制会议时间，及时输出会议纪要，让我们开一个高效的会！

1 0

【Meeting Notice】Release Manager Team Meeting 0526 Time: 2020-05-26 09:00-11:00
by Meeting Book 22 May '20

22 May '20

1 0

[CMake ] CMake从v3.12之后增加了不少新特性，为了使能新特性，SIG组准备近期在openEuler 开发分支将CMake升级到 v3.17.2版本，验证通过后合入20.3 LTS 分支。邮件后面是CMake 版本差异分析，诸位如果使用CMake 并且分析升级后可能存在影响，请尽快告知我们，多谢
by Licihua 21 May '20

21 May '20

CMake�� 1 CMake�� CMake��v3.12֮��˲��ԣ�Ϊ��ʹ��ԣ�׼��openEuler ��֧��CMake�� v3.17.2�汾��֤ͨ��20.3 LTS ��֧��ʼ��CMake �汾��λ��ʹ��CMake ��ҷ��ܴ��Ӱ�죬�뾡��֪��ǡ� 2 CMake�� ͨ��ɾ��ͱ��Linux��Ӱ��ģ��Ӱ��1��߰汾��CMake��export(PACKAGE) ��ֻ��ͨ��CMAKE_EXPORT_PACKAGE_REGISTRY��Ż��Ч��Ȼ��ִ��κβ��(�漰��ܲ��Ч��ڸ߰汾��ʹ��ǰ��CMAKE_EXPORT_PACKAGE_REGISTRY��) 3 �� 3.1 �� (1) CMake��Visual Studio��XCode��Green Hills MULTI��޸ĺ�� (2) CMake��˶�Object C��Object C++��CUDA��Ե�֧�֡� (3) CMake��˶��ɱ��֧�֡� (4) CMake��֧�� ʹ�ü򵥵Ĺ��ļ��iOS��tvOS��watchOS<https://cmake.org/cmake/help/v3.15/manual/cmake-toolchains.7.html#cross-com…>��н��<https://cmake.org/cmake/help/v3.15/manual/cmake-toolchains.7.html#cross-com…>�� ͻ��x86_64��aarch64�ܹ��Linux�ں˵�EulerOS��ϵͳû�й�ϵ�� 3.2 ��޸� (1) CMake��v3.14��Ժ��һ��ļ��API��ṩ��ḻ��﷨��ּ��ȡ��cmake-server<https://cmake.org/cmake/help/v3.15/manual/cmake-server.7.html#manual:cmake-…>��IDEģʽ��(��v3.15��ǿ��δ��Ὣcmake-server�Ƴ��ʹ��cmake-file-api��v3.17��cmake-server��Ȼ��ڣ��ܹ��¼��)�� 3.3 ��޸� (1) cmake��ѡ��-S <source_dir>��ָ��ԴĿ¼λ�ã��ѡ��-B��ʹ�á�(��¼��) (2) cmake��ѡ��-B<build_dir>��ָ��buildĿ¼��ѡ��-S��ʹ�á�(��¼��) (3) cmake �CE <create_sysmlink>��Windows��ʹ�á�(��¼��) (4) cmake ��ģʽ(cmake --build)��ˡ�verbose��-vѡ��ָ��ϸ�Ĺ��ĳЩ��Xcode��֧�ִ�ѡ�(��¼��) (5) cmake -E compare_files��һ�� --ignore-eolѡ���ָ��ڱȽ��ļ�ʱӦ��β��죨��LF��CRLF��(��¼��) (6) cmake-gui<https://cmake.org/cmake/help/v3.15/manual/cmake-gui.1.html#manual:cmake-gui…>�Ի��µ�-S��-B��ȷָ��Դ�ļ��Ŀ¼��(��¼��) (7) ��CMAKE_CENERATOR��ʹ��cmakeû��-Gѡ��ʱ��ָ��һ��Ĭ��(��¼��) (8) cmake �Cbuild�� Ctarget��˶Զ��Ŀ��֧�֡�(��¼��) (9) cmake��һ��installѡ���ܹ��ڹ��һ��Ŀ��а�װ��ʹ��ʹ��ɵĹ��ϵͳ�򱾻��ߡ�(��¼��) (10) cmake��һ��µ�CLIѡ�loglevel��(��¼��) (11) cmake �CE remove_directory��й��֧��ɾ��Ŀ¼��(��¼��) (12) cmake �CE tar��ɹ��ܡ�(��¼��) (13) cmake -E��֧��true��false����Ƿֱ𷵻�0��1��˳��ʱ��ִ��κβ��(��¼��) (14) cmake��һ��trace-redirect=<file>��ѡ���ڽ�--trace��ض��ļ��stderr��(��¼��) (15) cmake --loglevel��ѡ��Ϊ--log-level��ʹ��ѡ��һ�¡�(��--loglevel��¼��) (16) cmake��ˡ�debug-find��ѡ���find_*��ʱ�õ��ɶ��(��¼��) (17) cmake��ˡ�trace-fromatѡ��á�trace��ʽ��ǰ��֧�־ɵ��ɶ��ʽ��µ�JSON��ʽ��µ�JSON��ʽ��и�ʽ��Զ��(��¼��) (18) cmake��-E rm��ɾ��Ŀ¼��ļ��ȡ��е�-E remove��-E remove_directory��и��õ��Ч��(�ɵ��ѡ��ɱ��¼��) 3.4 ��޸� ��ڱ�дCmakeLists.txt�ļ�ʱ�õ��ִ��ĳ��ʹ�ø�ʽ��:Command(operation)��eg. add_subdirectory(src bin)�� (1) add_custom_command()he add_custom_target()��WORKING_DIRECTORYѡ��֧��ʽ��(��¼��) (2) add_link_options()��ڵ�ǰĿ¼��ѡ�(��¼��) (3) ��install(Ŀ¼)��װ�ڵ�ǰĿ¼֮�ⴴ��Ŀ�ꡣ(��¼��) (4) link_directories��˿��Ʋ��λ�õ�ѡ�(��¼��) (5) list��ڿ��ƶ��Ŀ��н��ıȽϲ��ѡ�(��¼��) (6) math��˻�ȡ16��Ƶ�ѡ�(��¼��) (7) target_link_directories��ΪĿ�꼰��ָ��Ŀ¼��(��¼��) (8) target_link_options()��ΪĿ��ָ��ѡ�(��¼��) (9) target_link_libraries()��ڿ��Ե��޸��ڵ�ǰĿ¼֮�ⴴ��Ŀ�ꡣ(��¼��) (10) file()<https://cmake.org/cmake/help/v3.15/command/file.html#command:file>��һ��µ��CREATE_LINK��ڴ��Ӳ��ӻ��ӡ�(��¼��) (11) file()��һ��µ��READ_SYMLINK��ȷ��ָ��·��(��¼��) (12) file()��һ��SIZEģʽ��ȡ��һ��ļ��Ĵ�С��(��¼��) (13) find_package()��ѡ��Ľ��ļ�·��еķ��ӡ�(��¼��) (14) if()<https://cmake.org/cmake/help/v3.15/command/if.html#command:if>��֧�ּ��﷨�Ƿ��˻��Ĺ�� (��¼��) (15) try_compile()<https://cmake.org/cmake/help/v3.15/command/try_compile.html#command:try_com…> �� try_run()<https://cmake.org/cmake/help/v3.15/command/try_run.html#command:try_run>��LINK_OPTIONSѡ�(��¼��) (16) add_library()��ALIASѡ��֧��UNKNOWN��͵ĵ��⡣(��¼��) (17) cmake_parse_arguments()��<prefix>_KEYWORDS_MISSING_VALUES��Ը�֪��߸��ֵ�Ĺؼ��ֲ��(��¼��) (18) execute_process()��COMMAND_ECHOѡ�֧��CMAKE_EXECUTE_PROCESS_COMMAND_ECHO��ִ��֮ǰ��ַ��ԡ�(��¼��) (19) file��һ��µĲ��FOLLOW_SYMLINK_CHAIN��ò�� ڵݹ��Ͱ�װ��ӡ�(��¼��) (20) list()��µ��PREPENDF��POP_FRONT��POP_BACK��(��¼��) (21) string()��µ��REPEAT��(��¼��) (22) add_test()��COMMAND_EXPAND_LISTSѡ�ʵ��COMMAND��е��б��չ��ʽ��б��(��¼��) (23) file��GET_RUNTIME_DEPENDENCIES��Եݹ��ȡ�ɿ�ִ��ļ��ӵĿ��б��ּ��GetPrerequisites<https://cmake.org/cmake/help/v3.16/module/GetPrerequisites.html#module:GetP…>��(��¼��) (24) ��target_precompile_headers()��ָ��ҪԤ��ı�ͷ�б��Լӿ��ٶȡ�(��¼��) (25) ��add_custom_command()<https://cmake.org/cmake/help/v3.17/command/add_custom_command.html#command:…>��ָ��ڵ�ǰ��Ŀ¼�н��DEPENDS��·��(��¼��) (26) foreach()��ZIP_LISTSѡ���ͬʱ��б��(��¼��) (27) load_cache��ģʽ��ڿ��ʹ��cmake �CP��нű��(��¼��) (28) message()<https://cmake.org/cmake/help/v3.17/command/message.html#command:message>��µĹؼ��CHECK_START�� CHECK_PASS��CHECK_FAIL��(��¼��) 3.5 ��޸� (1) FindQt<https://cmake.org/cmake/help/v3.15/module/FindQt.html#module:FindQt> ģ�鲻�ٱ� find_package()<https://cmake.org/cmake/help/v3.15/command/find_package.html#command:find_p…> ��Ϊ��ģ�顣��Qt Project��ξͿ��ѡ��ṩ��Լ��QtConfig.cmake��ļ��Ӧ�ó��ͨ��find_package(Qt)�� find_package(Qt CONFIG)��Ӧ��(��漰����¼��) (2) ��export(PACKAGE)<https://cmake.org/cmake/help/v3.15/command/export.html#command:export> ��ֻ��ͨ��CMAKE_EXPORT_PACKAGE_REGISTRY<https://cmake.org/cmake/help/v3.15/variable/CMAKE_EXPORT_PACKAGE_REGISTRY.h…>��Ȼ��ִ��κβ��(�漰��ܲ��Ч��ʹ��ǰ��CMAKE_EXPORT_PACKAGE_REGISTRY<https://cmake.org/cmake/help/v3.15/variable/CMAKE_EXPORT_PACKAGE_REGISTRY.h…>��) (3) ��ɱ��ģ��Ȳ��ʹ�ã��δ��汾�н��Ƴ��v3.17�о�� 4 �� ݴ󲿷ֲο�CMake Release Note��CMake User Manual��CMakeʵ��ʹ�þ��鲻�㣬��©��λר�Ҷ�� λ� ŷ��-2012 ʵ�� Ϊ��޹�˾ Tel : +86 15158056404 Email : licihua(a)huawei.com [cid:image001.png@01D62FAC.E7B3F7E0] This e-mail and its attachments contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it!

1 0

最近发现软件包归属领域和sig描述不符合，建议各位maintainer审视并作出调整
by solar.hu＠foxmail.com 21 May '20

21 May '20

hi all：最近发现软件包归属领域和sig描述不符合，提了如下issue https://gitee.com/openeuler/community/issues/I1HWHK?from=project-issue 建议各个sig maintainer审视软件包领域是否正确，并与对应sig达成一致并发起变更。如果无法达成一致，请填写如下文件，会有专人跟踪，并提交tc审核。 https://etherpad.openeuler.org/p/pkg_discussion_list solar.hu(a)foxmail.com

1 0

【Meeting Notice】sig-ai-bigdata regular meeting Time: 2020-05-21 18:30-20:00
by Meeting Book 21 May '20

21 May '20

2 1

【Meeting Notice】sig-ai-bigdata regular meeting Time: 2020-05-21 18:30-20:00
by 正心 17 May '20

17 May '20

1 0

【Meeting Notice】sig-ai-bigdata regular meeting Time: 2020-05-21 18:30-20:00
by Meeting Book 17 May '20

17 May '20

1 0

Upgrade GCC to 9.3.0
by guoge (A) 15 May '20

15 May '20

Hi, dev-team GCC 9.3 has been released on 2020-03-12, and we are ready to upgrade the master branch now. The kernel repo can be compiled through gcc 9.3, no changes needed. Below are the repos that may need to change a little bit, since gcc 9.3 provides libgfortran.so.5, no libgfortran.so.4 provides anymore. atlas future gegl04 gutenprint liberation-fonts liberation-sans-fonts nototools Numpy pcp pygtk2 python-fonttools python-pandas python-pillow python-scikit-learn scipy sil-padauk-fonts suitesparse xsane gimp libvma perl-Archive-Zip perl-MIME-Types the upgrade would be done on May 14th [1], the maintainer of the repos above should look at the daily build report. [1] https://gitee.com/src-openeuler/gcc/pulls/5

3 2

openEuler 能否默认配置 repos 官方源
by mfl 15 May '20

15 May '20

测试在华为云 ECS 通过自定义镜像的方式安装了 openEuler(4.19.90-2003.4.0.0036.oe1.aarch64) ,安装成功后发现 yum ,dnf 默认都没有源配置，建议 openEuler 能在ISO 安装配置默认源。

2 1

回复：答复: sig 组中 Base-service 的 nodejs rmp 包维护者咨询
by xiaoshen＠isrc.iscas.ac.cn 15 May '20

15 May '20

1 0

答复: sig 组中 Base-service 的 nodejs rmp 包维护者咨询
by Hexiaowen (Hex, EulerOS) 14 May '20

14 May '20

胡峰，nodejs找个人接口下xiaoshen 何晓文（Hex EulerOS）庞加莱实验室 [2012实验室] Tel : +86 18042018786 Email : hexiaowen(a)huawei.com [cid:image002.png@01D62A23.A1175090] This e-mail and its attachments contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it! 发件人: Zhuyanpeng 发送时间: 2020年5月13日 19:30 收件人: xiaoshen(a)isrc.iscas.ac.cn 抄送: Xiongwei (William, Euler) <xiongwei888(a)huawei.com>; Hexiaowen (Hex, EulerOS) <hexiaowen(a)huawei.com> 主题: 答复: [Dev] sig 组中 Base-service 的 nodejs rmp 包维护者咨询 https://gitee.com/openeuler/community/blob/master/sig/Base-service/OWNERS 发件人: xiaoshen--- via Dev [mailto:dev@openeuler.org] 发送时间: 2020年5月12日 12:23 收件人: dev(a)openeuler.org<mailto:dev@openeuler.org> 主题: [Dev] sig 组中 Base-service 的 nodejs rmp 包维护者咨询您好，我是 sig-cms 组的维护者，我维护的开源项目涉及到 Base-service 的 nodejs，有些问题想咨询一下，您这边能提供一个对接人吗？谢谢！

1 0

Re: sig-ai-bigdata
by 正心 13 May '20

13 May '20

既然这样，那太好了，可以从你最熟悉的地方入手，比如你使用的big data是什么软件栈，可以尝试把你现在用的软件栈(可以具体看)迁移到openeuler上(x86_64和aarch64)，看openeuler上能否满足功能、性能要求，然后我们去弥补差距，这就是很大的贡献。如果你对其他的有兴趣，也可以提出来。 1. 我们的软件库是基于centos还是需要下载源码自己编译? 你说的这些软件库是什么软件库。 2. 我在一个issue里看到您已经跑过spark和TensorFlow。那么最终提供给用户是类似于cloudera这样的集成环境还是原生包让用户选择? 咱们是操作系统，我们要从操作系统的角度思考问题：操作系统不提供这些成熟的商业软件，而是提供基础能力，即当cloudera这样的厂商或使用cloudera的人要在openeuler上使用时，能够很方面的构建、运行起来，功能、性能无损失，甚至有提高。 3. 我是否可以参加下次周会? 是周一还是周五呢？欢迎参加，后面的例会会议通知会提前发到@dev @tc 和sig-ai-bigdata@openeuler.org(筹建中，最近会OK)，所有订阅这三个邮件列表的人都可以收到，并可以接入。祝好。在 2020-05-13 20:48:56，"hao zhang" <unioah(a)gmail.com> 写道：谢谢很详细的讲解。我之前做过一些软件打包，主要是对ubuntu和 archlinux的。我本人一直从事big data方面的开发应用，也算对这一块有些了解。我想我可以先从搭建环境开始， 1. 我们的软件库是基于centos还是需要下载源码自己编译? 2. 我在一个issue里看到您已经跑过spark和TensorFlow。那么最终提供给用户是类似于cloudera这样的集成环境还是原生包让用户选择? 3. 我是否可以参加下次周会? 是周一还是周五呢？谢谢，浩 On Wed, May 13, 2020, 3:44 AM 正心 <sinever(a)126.com> wrote: 浩，你好，非常感谢你的关注，也非常欢迎你的加入。 sig-ai-bigdata的使命如同你在sig的介绍中看到的： 1. 提供openeuler上ai和bigdata的基础运行能力； 2. 提供openeuler上ai和bigdata的竞争力构建； 3. 提供openeuler上ai和bigdata的创新性预研； 4. 提供openeuler上ai和bigdata的新硬件的支持、加速； Openeuler是华为基于上游社区完全从零构建的操作系统，很多软件栈都在构建中，在因此在ai和bigdata上的支持也方兴未艾，当前的首要任务是提供openeuler上ai和bigdata的基础运行能力，包括对各种硬件、各种主流软件包、软件框架的支持，可以做的工作还是很多，如验证典型ai和bigdata软件在openeuler的支持情况，分析他们的依赖，架构梳理，并提供在openeuler的支持(基于openeuler进行构建，提供安装包)，你个人有相关经验吗，如OS打包、ai框架开发使用、bigdata框架的开发使用等或者你个人有什么想法，我们可以讨论或者根据你现有的能力和爱好安排。另外，也欢迎你介绍更多的小伙伴加入进来，一起构建ai和bigdata在openeuler上的未来，期待你的精彩表现。祝 0 error 0 warning sinever | | 正心 | | 邮箱：sinever(a)126.com | 签名由网易邮箱大师定制 On 05/13/2020 00:36, hao zhang wrote: Hi Sinever, 您好，我是新加入到openeuler sig-ai-bigdata 方向的兼职开发人员。根据这次会议的记录，我想在bigdata上面提供帮助。请问具体我可以做些什么？谢谢，浩

1 0

openeuler sig-ai-bigdata第三次例会会议纪要
by 正心 13 May '20

13 May '20

会议时间：2020.05.12 17:30 - 19:00 会议人员：Fred_Li 、cynthia_xh、chxssg、sinever、hubble_zhu、njlzk、zhangrui、xiaoweiwei 会议结论：按照议题：议题一：sig-ai-bigdata前期工作审视与总结 1.完成ai应用视角和系统视角软件栈整理初稿； 2.完成ai领域典型框架tensorflow/caffe在openeuler依赖梳理； 3.完成cml领域典型库libsvm依赖梳理； 4.完成bigdata领域典型应用jupyter依赖梳理； 5.完成引入openeuler支持ai、bigdata技术栈依赖包；议题二：sig-ai-bigdata后期工作内容和方法讨论 1.后续需要继续整理bigdata、ai领域系统视角软件栈，形成全景图； 2.后续从使用角度提供常用软件的常规基本运行能力，如tensorflow/caffe/jupyter/pytorch/hadoop/spark等，提供通常安装方法，如pip、jvm等； 3.对于高性能模式从底层开始逐渐向上支持，如tensorflow支持onednn/cuda/opencl/opencv等； 4.后面引入软件包时先整理使用方法、编译方法、软件架构、依赖关系形成readme，再引入到openeuler；议题三：sig-ai-bigdata后期工作任务分配 1.ai领域软件栈整理，责任人sinever 2.bigdata领域软件栈整理，责任人hubble_zhu、sinever 3.caffe使用方法、软件架构、编译方法、依赖关系整理，责任人njlzk 4.jupyter使用方法、软件架构、编译方法、依赖关系整理，责任人zhangrui 5.hadoop/spark/libsvm使用方法、软件架构、编译方法、依赖关系整理，hubble_zhu 6.其他人任务后续线下视情况再安排；其他： 1.openeuler后续会支持图形界面，因此一些有图形界面的软件也是很需要的； 2.后续例会尽量公开，方面感兴趣的人自行加入，sig-ai-bigdata邮件组建立前可以先使用dev(a)openeuler.com; 3.确认nvidia的相关库是否开源，责任人sinever； 4.后面从x86_64的应用迁移到aarch64可以考虑使用迁移工具； 5.需要整理出sig的roadmap，责任人sinever；

1 0

Roadmap of GCC & OpenJDK in openEuler
by guoge (A) 12 May '20

12 May '20

Hi, tc-team Please review this roadmap of GCC & OpenJDK, two of most important compilers in OS, any questions are welcomed. GCC: The currently supported gcc version is 7.3, it will be upgraded soon, and there will only be ONE existing repo of GCC, the Compiler SIG has prepared well for the next coming gcc 9.3, and it will the candidate(depends on the compatibility & performance between gcc 9.3 and 10.x) default C/C++ compiler in 20.09 LTS. The Compiler SIG has also started the work of gcc 10.1, GNU has released gcc 10.1 on May 7th. OpenJDK: We will support 3 versions of JDK in openEuler，8/LTS/latest，they are all essential components of a commercial OS. 8: Still the most popular adoption of JDK, about over 50% of applications still run on JDK 8[1]. LTS(11): newest version of LTS but incompatible with JDK 8, supporting modularity/AOT/ZGC/stream enhancement/more efficient G1GC/…, we hope developers migrate their code to Java 11 ASAP. Latest(14): OpenJDK is bootstrap but only supports version n-1, which means you can only compile JDK 14 with JDK 13, JDK 15 with JDK 14, and so on, so the latest release of JDK is needed if we want to support the next LTS(17). We have supported OpenJDK 8 & 11 now, they will be updated quarterly to get critical patch update. The next step is to support the latest version of OpenJDK(14), which is under development. [1] https://www.infoq.cn/article/2HFbAm4fDoK6meJfbKW8

1 0

[RM] Release Manager Team Meeting Minutes 20200512
by Maliang (Marlon, IT) 12 May '20

12 May '20

Release Manager Team Meeting Minutes 20200512 Time: 9:15�C10:30 on Tuesday, May 12, 2020 Attendee: Release Manager Team Summary: Marlon Ma Conclusion:�� һ��Sig��&Maintainner��ؼ��ơ��Ͳ��Խ��ȡ��ؼ��Խ��£� Related SIG team and maintainer aligns the progress of key feature Design, Coding, and Testing. The progress of key features is as follows�� n OS��ȷ��1069��һ��601��50%�� OS Dependency Package: 1069 software packages to be supplemented have been sorted out, and the development of the first batch of 601 software packages has been started. The overall progress is 50%. n ��ƽ̨��裺��Ͳ��ƺ�ԭ��֤��25%�� Package Management: Completed software package dependency management and patch tracing, completed design and prototype verification, and started development. The overall progress is 25%. n ��ƽ̨��𡢵��ּ��ɣ��뿪��׶Σ��ݴ��Դ�빹��20%��lkp-test/��Դ��30%�� Community Testing Platform: The deployment and scheduling tasks are completed by level, and the development phase starts. Data processing and source code building: 20%; klp-test/open-source use case design: 30%. n OS��---��ȿ�ܼ��2P MySQL��ݿ�mix��4P MariaDB��ݿ��Ŀ��Ѵ�ɡ��û�̬aware��֪��Ⱥ��ں˹ؼ��ݽṹ�Ż��У��70%�� Domain-based scheduling framework technology: The 2P MySQL database mix scenario and Kunpeng 4P MariaDB database optimization objectives have been achieved. The user-mode aware awareness scheduling and kernel key data structure optimization are in progress. The overall progress is 70%. n OS��---A-Ops��(�ں��滻)��չ40%��Ӧ�ó��ڴ�PIN/�ָ��Լ��ҳ��Ϣ��ɴ��뿪��֤��ɿ��Լӹ̽׶Ρ� A-Ops technology (hot kernel replacement): The overall requirement progress is 40%. The code development for application memory PIN/recovery and restart page information storage has been completed, and the test verification and reliability hardening phases have started. �� ⡣ 1��openEuler��Դ��SPEC�淶�� Review the SPEC specifications of the open-source software package in the openEuler community. Wu Fengguang 2��ˮƽ��Ӧ��Maintainner��Ҫ��ȷ�� The application software maintainer needs to be specified. Ma Liang 3��5.30ǰ��Maintainner��QA Team��ɹؼ��Դ�� ALL Before May 30, the related maintainers and QA team complete the lecture on key features. ALL 4��Ԥ��5�µ�Ready��ҪЭ��һ��Ϲ��Ա�� The Lab required for community development is expected to be ready by the end of May. A material administrator needs to be coordinated. Ma Liang 5��ƽ̨��Ŷ�Crystal��Ի��ϱ��з��ա� �ſ�� The testing platform development team has a weak foundation in the Crystal language, which may cause risks in the short term. Du Kaitian B/R Thanks �� MarlonMa

1 0

sig 组中 Base-service 的 nodejs rmp 包维护者咨询
by xiaoshen＠isrc.iscas.ac.cn 12 May '20

12 May '20

您好，我是 sig-cms 组的维护者，我维护的开源项目涉及到 Base-service 的 nodejs，有些问题想咨询一下，您这边能提供一个对接人吗？谢谢！

1 0

答复: 关于 Base-service 下的src-openeuler/mongodb 维护者咨询
by Hexiaowen (Hex, EulerOS) 11 May '20

11 May '20

多谢你的反馈，已经知会胡峰给你协调一个对应的接口人。请关注邮件。后续问题讨论，可以直接发到邮件列表。dev(a)openeuler.org 何晓文（Hex EulerOS）发件人: xiaoshen(a)isrc.iscas.ac.cn [mailto:xiaoshen@isrc.iscas.ac.cn] 发送时间: 2020年5月10日 10:19 收件人: Hexiaowen (Hex, EulerOS) <hexiaowen(a)huawei.com> 主题: 关于 Base-service 下的src-openeuler/mongodb 维护者咨询您好，我是 sig-cms 组的维护者，我维护的开源项目涉及到 Base-service 的mongodb，有些问题想咨询一下，您这边能提供一个对接人吗？谢谢！

2 1

(no subject)
by 梦天 11 May '20

11 May '20

ok

1 0

Re: Welcome to the "Dev" mailing list
by smileb_j 11 May '20

11 May '20

At 2020-05-11 10:09:13, dev-request(a)openeuler.org wrote: >Welcome to the "Dev" mailing list! > >To post to this list, send your email to: > > dev(a)openeuler.org > >You can unsubscribe or make adjustments to your options via email by >sending a message to: > > dev-request(a)openeuler.org > >with the word 'help' in the subject or body (don't include the >quotes), and you will get back a message with instructions. You will >need your password to change your options, but for security purposes, >this password is not included here. If you have forgotten your >password you will need to reset it via the web UI.

1 0

openEuler-Advisor upstream-info automation plan
by Wu Fengguang 11 May '20

11 May '20

大家好， openEuler-Advisor/upstream-info是不是可以合作开发？ crystal-ci项目正好也需要类似的upstream-info，因为我们的目标是测试大量上游软件，必需拿到他们的git URL先。附件是我刚写的计划。请大家帮忙review，并看看怎么分工合作。 archlinux core repo 和 community repo 的初步统计结果： core community has git url 778 3904 <<<<< 这些是我们可以利用的信息 total pkgs 2461 6817 Regards, Fengguang

1 0

Re: Cheap Facebook Traffic
by Ethelyn Eversole � 10 May '20

10 May '20

hi dev here it is, social website traffic: http://www.mgdots.co/detail.php?id=113 Full details attached Regards Ethelyn Eversole � Unsubscribe option is available on the footer of our website

1 0

创建 crystal-ci 邮件列表
by wufengguang 09 May '20

09 May '20

您好，我们sig-CICD需要一个带archive功能的邮件列表，名字为 crystal-ci 用于crystal-ci的项目研发。谢谢！ Thanks, Fengguang

3 3

[dev]Incorrect mail list address for some SIGs
by Fred Li 08 May '20

08 May '20

Hi all, As Edward mentioned in [1], the following SIGs' mail address are incorrect. Please visit [1] to check or reply this email. Thank you. sig-CICD: @Fengguang @wubodong sig-RISC-V: @zhoupeng01 sig-ai-bigdata: @sinever @njlzk sig-bounds_checking_function: @shiguangliang01 @zhaozhijian sig-golang: @haomintsai @jing-rui sig-security-facility: @zhujianwei001 @mailofzxf [1] https://gitee.com/openeuler/community/issues/I1FYIL -- Regards Fred Li (李永乐)

1 0

[RM] Release Manager Team Conference notification 0512
by Maliang (Marlon, IT) 07 May '20

07 May '20

Release Manager Team Meeting 0512 会议时间 2020年5月12日（周二）9:15-10:00 会议地点 Web 会议主题 Release Manager Team Meeting 召集人 MarlonMa 与会人 Release Manager Team 会议议题 Fixed topics： ? Key Features Design and Development Progress ? Discussion on risks and key issues Arrange other topics as needed. 会议ID Topic [WeLink Meeting] Release Manager Team Meeting 0512 Time 2020-05-12 09:00-10:45 ((UTC+08:00)Beijing) Join Conference Join (Internal) >><http://imeeting.huawei.com/meeting/joinzoom?id=907899847&app=welink> Join (External) >><https://welink-meeting.zoom.us/j/907899847> Meeting ID 907 899 847 注意事项 1、请勿迟到、早退； 2、会议期间，请将手机设为振动或会议状态； 3、请控制会议时间，及时输出会议纪要，让我们开一个高效的会！

1 0

请问哪里有ukui装到openeuler的详细指导
by Hufeng (Solar, Euler) 29 Apr '20

29 Apr '20

胡峰（Hu Feng）华为技术有限公司 Tel : +86 18616502896 Email : solar.hu(a)huawei.com [cid:image003.png@01D61BEB.DF31DDA0] This e-mail and its attachments contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it!

2 1

[desktop]请问哪里有ukui装到openeuler的详细指导
by Hufeng (Solar, Euler) 26 Apr '20

26 Apr '20

胡峰（Hu Feng）华为技术有限公司 Tel : +86 18616502896 Email : solar.hu(a)huawei.com [cid:image001.png@01D61BEC.31C9D130] This e-mail and its attachments contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it!

1 0

[RM] Release Manager Team Meeting Minutes 20200421
by Maliang (Marlon, IT) 22 Apr '20

22 Apr '20

Release Manager Team Meeting Minutes 20200421 Time: 9:15�C10:00 on Tuesday, April 21, 2020 Attendee: Release Manager Team Summary: Marlon Ma Conclusion:�� һ��ȷRM-Meeting��ʱ��Ϊÿ˫�ܶ��9:15--10:00,�ڼ��ݽ׶��Խ��趨ר�⡣��£� Specify that the subsequent RM-Meeting meeting will be held from 9:15 to 10:00 every Tuesday morning. During the meeting, topics will be set based on the progress of each phase. The arrangements are as follows: [��˿�ѡ��: Start RM-Meetlng 4 һ 6 �� RM-Meetlng M �� һ 12 RM-Meetlng Sep 1 RM-Meetlng RM-Meetlng Jun- RM-Meetlng �� Sep Al-lg 2 RM-Meetlng 0 [ llty �� 0 0 RM-Meetlng poll-it һ 2 �� 2 5 Jun 0 Jun RM-Meetlng RM-Meetlng �� Ill 2 A [ �� һ 11 RM-Meetlng pIan ` �� Jul �� RM-Meetlng �� 14 R M May 25 Meetlng Sep Mar �� AP 21 G O/N 0 GO RM-Meetlng Rel ease Sep �� Sep 2 Sep 2] ��ȷRM-Meeting��ɫ�͹ؼ��Owner/Sig��ˣ��ɶ�Ӧ��Owner/Sig��л㱨��ơ��ȡ� The RM-Meeting participants and Key Feature/Sig owners are determined at the meeting. The Feature /Sig owners will report the feature design and development progress at the regular meeting. �� RM-Meeting��ɫ�� The RM-Meeting participants are as follows�� [��˿�ѡ��: S �� & Ma rs (Key Features) RM- Meeting madcet11KJ �� 0 �� ] �� ؼ��Owner/Sig�� Key Feature/Sig owner�� ؼ�� Owner/Sig�� Ӧ��Ż� ��ݿ��Ż� ��ǿ�� ҵ��Ż� Web server ��Ż� �ֲ�ʽ�洢��Ż� A-Tune �Զ��ģ��Ԥ�� ǿ ��ARMƽ̨�� Ż�GCC �� ⻯ ��ԭ��VMM �� ΪARMƽ̨��Ӹ߼��⻯�� ARM��⻯IO��Ż� �� repo��, Ԥ��м��İ�װ�� openEuler repo�У� Ԥ�ó��õļ��ٿ� ��Ч��ά ��ϵͳ�ں�� ǿ�� Լ۱� �༶�ڴ� ��ǿ Ч�� ƽ̨ �ſ���� ƽ̨�� B/R Thanks �� MarlonMa

1 0

OpenJDK 11 is ready to release
by guoge (A) 22 Apr '20

22 Apr '20

When is the course of openEuler events, it becomes necessary for some of Java developers to migrate their applications to Java 11, which our Compiler SIG have been prepared for a long while. We bring you openEuler Community builds of OpenJDK 11 with : - ZGC support for AArch64(low latency experimental GC) - TLS 1.3 - JFR support - experimental AOT/JIT compiler(based on Graal) the OpenJDK 11 will be available on April 30. Best regards, Guo Ge

2 1

How to get the patches openEuler 20.03 LTS Kernel has
by Fred Li 22 Apr '20

22 Apr '20

Hi all, We are frequently asked what patches kernel has comparing with Kernel 4.19. [1] shows how to find them and hope it helps. If more information is needed, please leave messages in the issue [1]. [1] https://gitee.com/openeuler/kernel/issues/I1F430 -- Regards Fred Li (李永乐)

1 0

[Infra][RaspberryPi]How to set default branch for RaspberryPi
by Fred Li 20 Apr '20

20 Apr '20

Hi Infra team, [1] is one issue from RaspberryPi team. The maintainer is set the role as "developer" in Gitee, but it seems that he has some issue to set the default branch. Could you help on this, or clarify how to manage default branch? Thanks [1] https://gitee.com/openeuler/raspberrypi-kernel/issues/I1ESH0 -- Regards Fred Li (李永乐)

3 6

Updated invitation: openEuler Raspberry Pi SIG Weekly Meeting @ Weekly from 3pm to 4pm on Tuesday (CST) (dev@openeuler.org)
by eli＠patch.sh 17 Apr '20

17 Apr '20

This event has been changed. Title: openEuler Raspberry Pi SIG Weekly Meeting Welcome, please join the openEuler Raspberry Pi SIG weekly meeting to discuss how to build an openEuler running in the Raspberry Pi devices.Zoom Meeting ID: 881 4204 8958Agenda[1] https://docs.google.com/document/d/1HuN7sWLiPuvGLqd-1tH1WAbzk51tgXpFBodp3dz… https://gitee.com/openeuler/raspberrypi[2] https://gitee.com/openeuler/raspberrypi-kernel Slack https://openeuler-raspberrypi.slack.com IRC Channel #openeuler-raspberrypi (changed) When: Weekly from 3pm to 4pm on Tuesday China Standard Time - Shanghai Calendar: dev(a)openeuler.org Who: * eli(a)patch.sh - organizer * dev(a)openeuler.org Event details: https://www.google.com/calendar/event?action=VIEW&eid=Nzc5ZnJjbXRrbWhwdnU5b… Invitation from Google Calendar: https://www.google.com/calendar/ You are receiving this courtesy email at the account dev(a)openeuler.org because you are an attendee of this event. To stop receiving future updates for this event, decline this event. Alternatively you can sign up for a Google account at https://www.google.com/calendar/ and control your notification settings for your entire calendar. Forwarding this invitation could allow any recipient to send a response to the organizer and be added to the guest list, or invite others regardless of their own invitation status, or to modify your RSVP. Learn more at https://support.google.com/calendar/answer/37135#forwarding

1 0

Updated invitation: openEuler Raspberry Pi SIG Weekly Meeting @ Weekly from 3pm to 4pm on Tuesday (CST) (dev@openeuler.org)
by eli＠patch.sh 17 Apr '20

17 Apr '20

This event has been changed. Title: openEuler Raspberry Pi SIG Weekly Meeting Welcome, please join the openEuler Raspberry Pi SIG weekly meeting to discuss how to build an openEuler running in the Raspberry Pi devices.Zoom Meeting ID: 881 4204 8958Repositories[1] https://gitee.com/openeuler/raspberrypi[2] https://gitee.com/openeuler/raspberrypi-kernel Slack https://openeuler-raspberrypi.slack.com IRC Channel #openeuler-raspberrypi (changed) When: Weekly from 3pm to 4pm on Tuesday China Standard Time - Shanghai Calendar: dev(a)openeuler.org Who: * eli(a)patch.sh - organizer * dev(a)openeuler.org Event details: https://www.google.com/calendar/event?action=VIEW&eid=Nzc5ZnJjbXRrbWhwdnU5b… Invitation from Google Calendar: https://www.google.com/calendar/ You are receiving this courtesy email at the account dev(a)openeuler.org because you are an attendee of this event. To stop receiving future updates for this event, decline this event. Alternatively you can sign up for a Google account at https://www.google.com/calendar/ and control your notification settings for your entire calendar. Forwarding this invitation could allow any recipient to send a response to the organizer and be added to the guest list, or invite others regardless of their own invitation status, or to modify your RSVP. Learn more at https://support.google.com/calendar/answer/37135#forwarding

1 0

Invitation: openEuler Raspberry Pi SIG Weekly Meeting @ Weekly from 3pm to 4pm on Tuesday (CST) (dev@openeuler.org)
by eli＠patch.sh 17 Apr '20

17 Apr '20

You have been invited to the following event. Title: openEuler Raspberry Pi SIG Weekly Meeting Welcome, please join the openEuler Raspberry Pi SIG weekly meeting to discuss how to build an openEuler running in the Raspberry Pi devices.Zoom Meeting ID: 881 4204 8958Repositories[1] https://gitee.com/openeuler/raspberrypi[2] https://gitee.com/openeuler/raspberrypi-kernel Slack https://openeuler-raspberrypi.slack.com IRC Channel #openeuler-raspberrypi When: Weekly from 3pm to 4pm on Tuesday China Standard Time - Shanghai Calendar: dev(a)openeuler.org Who: * eli(a)patch.sh - organizer * dev(a)openeuler.org Event details: https://www.google.com/calendar/event?action=VIEW&eid=Nzc5ZnJjbXRrbWhwdnU5b… Invitation from Google Calendar: https://www.google.com/calendar/ You are receiving this courtesy email at the account dev(a)openeuler.org because you are an attendee of this event. To stop receiving future updates for this event, decline this event. Alternatively you can sign up for a Google account at https://www.google.com/calendar/ and control your notification settings for your entire calendar. Forwarding this invitation could allow any recipient to send a response to the organizer and be added to the guest list, or invite others regardless of their own invitation status, or to modify your RSVP. Learn more at https://support.google.com/calendar/answer/37135#forwarding

1 0

[design summit][governance]Requirements collection for community governance team
by Fred Li 14 Apr '20

14 Apr '20

Hi all, 大家好！openEuler Virtual Summit[1]将于4月17日召开，其中openEuler Community Governance小组将在4月18日（北京时间）9点到10点开会讨论下个阶段的工作任务及优先级。我们这个团队主要为社区提供如下服务： - 组织运作流程设计，比如技术委员会、SIG、打包小组、安全委员会等之间如何协调好。 - 版本开发流程 - 社区价值观（code of conduct) - 其他所有没有团队负责的问题如果您有任何需求或者疑问，请在etherpad[2] 或者 issues[3] 写下来，或者直接回复该邮件。 The team community governance will have the design summit meeting at 9:00 on April 18th [1]. I am glad to collect your requirements to us and please put it in etherpad[2], issues[3], or just reply this email. [1] https://openeuler.org/zh/summit/2020-virtual-summit.html [2] http://etherpad.openeuler.org/p/openeuler-virtual-summit-2020-community-gov… [3] https://gitee.com/openeuler/community/issues -- Regards Fred Li (李永乐)

1 0

[summit]openEuler Virtual Summit 2020 will be held on Apr. 17th and 18th
by Fred Li 13 Apr '20

13 Apr '20

Hi all, I am exited to announce that openEuler Virtual Summit is coming! Due to COVID-19, we have to hold the first summit virtually, and I believe this is good to all the members' health. Please stay healthy and strong. Please visit https://openeuler.org/zh/summit/2020-virtual-summit.html (Chinese) or https://openeuler.org/en/summit/2020-virtual-summit.html (English) for details. As you can find on the page, there are several pases: 1. From now on to April 9th, it is call for speakers. To emphasize, this is only for Design summit, and please developers to start planning your design summit. 2. From Apr. 10th to 15th, it is open for registration. 3. The summit will be on Apr. 17th and 18th. There will be 2 parts. The first one is summit, and the second one is design summit. On Design summit, the contributors will have a virtual face to face meeting to discuss what we will develop for next release, which is openEuler 20.09 here. openEuler SIGs maintainers, please start to plan the design summit for your SIG with your team. Please note that you will have 2 hours for the meeting. Once confirmed, please send the following information to marketing(a)openeuler.org. Make sure you have subscribed [1]. - group name (SIG name): - chair: - BIO of the chair: - Brief introduction to the meeting: [1] https://mailweb.openeuler.org/postorius/lists/marketing@openeuler.org/ -- Regards Fred Li (李永乐)

7 10

[infra][docs]Quality improvement for joint docs and infrastructure
by Fred Li 12 Apr '20

12 Apr '20

Hi infra and docs team, Please visit [1] to get the details. The issue was that one link in docs was wrong, which is understandable, but the impact is that the build of website failed but nobody knew until checking the final result. We need improve the integration and test. Any thoughts? [1] https://gitee.com/openeuler/docs/issues/I1E9ZD -- Regards Fred Li (李永乐)

2 1

openEuler峰会议题-RaspberryPi
by 方亚芬 11 Apr '20

11 Apr '20

老师，您好。以下是 RaspberryPi SIG 组参与的议题。烦请查收，谢谢。- 组名：树莓派 - 主持人：方亚芬 - 主持人简介：树莓派 SIG 组负责人 - 会议议程简介：本次会议主要介绍如下内容： 1、RaspberryPi SIG 组的背景介绍 2、RaspberryPi SIG 组的当前工作进展包括 openEuler 移植到树莓派的方法、当前存在问题及解决方案 3、后续发展规划 - group name (SIG name): RaspberryPi - chair: YaFen Fang - BIO of the chair: RaspberryPI SIG maintainer. - Brief introduction to the meeting: 1. Background of RaspberryPi SIG group. 2. Current progress of RaspberryPi SIG Include how to migrate openEuler to Raspberry Pi, and how to tackle current problems. 3. Future plan 祝工作顺利，生活愉快。 ------------------------------------------ 方亚芬中国科学院软件研究所智能软件研究中心邮箱：yafen(a)iscas.ac.cn 地址：北京市海淀区中关村南四街4号5楼

2 1

关于优化社区文档的阅读体验，欢迎您的反馈/Optimized the reading experience of document in the community document.Your feedback is welcome
by Junqi?Xie 10 Apr '20

10 Apr '20

关于优化社区文档的阅读体验，欢迎您的反馈： https://gitee.com/openeuler/website/issues/I1E208?from=project-issue issue内容如下：关于文档阅读体验，有如下issue反馈： 1、https://gitee.com/openeuler/docs/issues/I1CTZ8?from=project-issue 2、https://gitee.com/openeuler/docs/issues/I1CPWY?from=project-issue 3、https://gitee.com/openeuler/docs/issues/I1CPXV?from=project-issue 主要问题点在于： 1、目录结构不易展开 2、文档内容不连续，层级太多且无法顺畅翻页阅读。每次都需要在左侧导航切换希望提供pdf、single page、multi page不同阅读体验 sigle page：一个页面显示一个章节的所有内容，且能够提供页内的索引、目录或者浮动目录 multi page：一个页面内显示一个手册的所有内容。针对这些问题，请大家体验下mindspore资料阅读方式，如果大家认可该方式，openEuler社区文档就按照该框架优化资料阅读内容： https://www.mindspore.cn/tutorial/zh-CN/master/index.html 您是否认可mindspore的阅读体验？或者有更好的建议参考? 【English】 The following issues have been reported regarding document reading experience: 1.https://gitee.com/openeuler/docs/issues/I1CTZ8?from=project-issue 2.https://gitee.com/openeuler/docs/issues/I1CPWY?from=project-issue 3.https://gitee.com/openeuler/docs/issues/I1CPXV?from=project-issue The main problems are as follows: 1.The directory structure is difficult to expand. 2.The document content is not continuous. There are too many layers and pages cannot be turned smoothly. You need to switch between the navigation tree on the left each time. Different reading experience for PDF, single page, and multi page. sigle page: All contents of a chapter are displayed on a page. In addition, indexes, directories, or floating directories can be provided on the page. multi page: displays all contents of a manual on a page. To solve these problems, please experience the MindSpore documentation reading mode. If you agree with this mode or have made improvements based on this mode, the documentation of the OpenEuler community will be optimized based on this mode. **https://www.mindspore.cn/tutorial/zh-CN/master/index.html ** Do you recognize mindspore's reading experience? Or do you have any better suggestions?

1 0

openeuler kmod drivers compile support
by Xin.Yan＠microchip.com 08 Apr '20

08 Apr '20

Loop more, if any one can help, thanks. From: Xin Yan - A50803 Sent: 2020年4月8日 11:49 To: contact(a)openeuler.org Subject: openeuler kmod drivers compile support Hi openeuler team, I am having problems finding macros necessary to build kmod driver rpm packages. For instance, our spec file calls kernel_module_package that is missing form openEuler. It will be hard to support drivers well on openEuler without kmod packing support. I can see below macro in centos: [root@rhel7u7e-s1 rpm]# grep -ri kernel_module_package /usr/lib/rpm /usr/lib/rpm/redhat/kmodtool:# generally called only by the %kernel_module_package RPM macro /usr/lib/rpm/redhat/macros:%global redhat_kernel_module_package 1 /usr/lib/rpm/redhat/macros:%global kernel_module_package_release 1 /usr/lib/rpm/redhat/macros:#kernel_module_package [ -n name ] [ -v version ] [ -r release ] [ -s script ] /usr/lib/rpm/redhat/macros:%kernel_module_package_buildreqs %global kmodtool_generate_buildreqs 1 \ /usr/lib/rpm/redhat/macros:%kernel_module_package(n:v:r:s:f:xp:) %{expand:%( \ /usr/lib/rpm/redhat/macros: echo "%%global kernel_module_package_moddir() extra" \ [root@rhel7u7e-s1 rpm]# But I can not find anything in openeuler: [root@openeuler2003test]# grep -ri kernel_module_package /usr/lib/rpm [root@openeuler2003test]# Best regards, Bob

1 0

Re: Chinese Fedora packager is here
by handsome_feng 07 Apr '20

07 Apr '20

Hi, Robin, I'm one of the UKUI maintainers, we are very happy to learned that you are instersted in porting UKUI to Fedora, and that's exactly what we want to do. :) So, what can we do and how to coporate? We don’t have much experience in this. Thanks, handsome_feng

3 2

订阅
by Sober 05 Apr '20

05 Apr '20

1 0

Chinese Fedora packager is here
by Robin Lee 03 Apr '20

03 Apr '20

Hi, all I learned about openeuler is packaging Ukui from news. Any chance we can also submit the packages to Fedora? Or any openeuler packager also want to be Fedora packager? I can help if anyone is interested. -robin

4 6

Re: [A-tune] Glad to join a-tune group and need more information
by Fred Li 03 Apr '20

03 Apr '20

+ dev(a)openeuler.org and community(a)openeuler.org. Hi Zhangmiao, Glad to hear that your are interested in A-Tune project. You are right, there is not so much information on website(I mean openeuler.org) The design idea is that the project content will be stored in gitee only. If you haven't visited [1], please visit it. And you can also leave issues in [1] or email here. Thanks [1] https://gitee.com/openeuler/A-Tune On Thu, Apr 2, 2020 at 4:21 PM zhangmiao via A-tune <a-tune(a)openeuler.org> wrote: > > Hello all, > > I am from iscas(Institute of Software Chinese Academy of Science, > 中科院软件所) > > we are very interested in a-tune project. and would like to join it with > our effort. > > but information from home website is very limited, and not in time. > > would you please share your recent progress? > _______________________________________________ > A-tune mailing list -- a-tune(a)openeuler.org > To unsubscribe send an email to a-tune-leave(a)openeuler.org -- Regards Fred Li (李永乐)

1 0

[Docs]Please check the 2 PRs for the same(perhaps) purpose
by Fred Li 03 Apr '20

03 Apr '20

Hi Docs team, community, To add one committer to Docs team, @amyMaYun submitted [1], and I put -1 comment with reason, but I haven't got any reply so far. @Rudy_Tan submitted another one [2], and it got approved immediately. I am not against the nominated committer himself/herself, but I am against the process. I propos to revert [2] if there is not a reasonalbe explanation. [1] https://gitee.com/openeuler/community/pulls/321 [2] https://gitee.com/openeuler/community/pulls/300 -- Regards Fred Li (李永乐)

3 4

Re: Welcome to the "Dev" mailing list
by axj 29 Mar '20

29 Mar '20

At 2020-03-29 16:42:01, dev-request(a)openeuler.org wrote: >Welcome to the "Dev" mailing list! > >To post to this list, send your email to: > > dev(a)openeuler.org > >You can unsubscribe or make adjustments to your options via email by >sending a message to: > > dev-request(a)openeuler.org > >with the word 'help' in the subject or body (don't include the >quotes), and you will get back a message with instructions. You will >need your password to change your options, but for security purposes, >this password is not included here. If you have forgotten your >password you will need to reset it via the web UI.

1 0

add to the list
by hxp 29 Mar '20

29 Mar '20

1 0

Introduction to the new commentable and rename_from features supported in ci-bot
by joey 20 Mar '20

20 Mar '20

Hi all: I’m Joey and from infrastructure team of openEuler. So glad to see you guys and hope everybody is doing well. I’m writing here to have a brief introduction to the new features provided by ci-bot. We believe they would be helpful for your repository management. As it’s known to us, ci-bot is an automation system to handle lots of infrastructure stuff, such as gitee web hook events, repository management, owner management and etc. For more details about our lovely ci-bot, please refer to https://gitee.com/openeuler/ci-bot <https://gitee.com/openeuler/ci-bot>. For now, please let me elaborate how you can make use of the two features to ease the repository management. 1. Add commentable property for repository definition in openeuler.yaml or src-openeuler.yaml under openeuler/community. PR is: https://gitee.com/openeuler/ci-bot/pulls/26 <https://gitee.com/openeuler/ci-bot/pulls/26> . > Previously users could leave a comment at the index page of the project, which is a great feature provided by Gitee. While as we all know, the more conventional way is posting an issue request for questions/bugs/features. So after discussion, we finally consider to disable the comment-to-repository feature for all repositories. So here comes to this functionality, which adds an extra commentable property. If it’s not specified, the default value is false of boolean type. > Actually, you DO NOT need to pay any attention to this new property since non-commentable repository is strongly recommended. Just think it never exists. The example is shown as below, ```yaml community: openeuler repositories: - name: A-Tune description: "" type: public commentable: false # User CAN NOT see or leave comment to repository - name: ci-bot description: "" type: public commentable: true # Users CAN see and leave comment to repository - name: community description: "" type: public # User CAN NOT see or leave comment to repository ``` 2. Add rename_from property for repository definition in openeuler.yaml or src-openeuler.yaml under openeuler/community. PR is: https://gitee.com/openeuler/ci-bot/pulls/27 <https://gitee.com/openeuler/ci-bot/pulls/27> . > Please let me take a real case for example. In PR https://gitee.com/openeuler/community/pulls/128 <https://gitee.com/openeuler/community/pulls/128>, iSulad team wants to change the names of three repositories: iSulad-kit ===> iSulad-img iSulad-lxcfs-toolkit ===> lxcfs-tools iSulad-tools ===> syscontainer-tools > As the PR is shown to us, the code diff is as below, which leaded ci-bot to completely remove the old repository and create a new empty one with the new name, causing loss of all the existing issues and PRs. ```diff - - name: iSulad-kit + - name: iSulad-img description: "" - - name: iSulad-lxcfs-toolkit + - name: lxcfs-toolkit description: "" - - name: iSulad-tools + - name: syscontainer-tools description: "" ``` > While after the PR has been merged, the diff would be like the following. This could make use of the newly supported renaming-repository Gitee OpenAPI to keep all the issues and PRs unchanged. ```diff - - name: iSulad-kit + - name: iSulad-img description: "" + rename_from: iSulad-kit - - name: iSulad-lxcfs-toolkit + - name: lxcfs-toolkit description: "" + rename_from: iSulad-lxcfs-toolkit - - name: iSulad-tools + - name: syscontainer-tools description: "" + rename_from: iSulad-tools ``` > While it should noted that rename_from is not declarative but imperative cause it will take effect only for once and not stored in DB. So if we remove it from repository definition after renaming operation has been finished, nothing will happen. Hopefully I have explained clear enough. Currently the new functionalities are not in production yet and your feedback is rather important to us. So please reply this email for further discussion as soon as you have any doubt. Looking forward to your feedback. Take care! Best regards, Joey

3 2

The Guide of Contributor V2.0, thank you for your review~~~
by Yang Li 17 Mar '20

17 Mar '20

2 1

Re: [Discusion] How can I become a member of Technical Committee in openEuler
by Liyongle (Fred) 12 Mar '20

12 Mar '20

Hi all, First I apologize that the email title should not include [isulad]. Some friends have left their comments here and hope you have to read or comment. https://gitee.com/openeuler/community/issues/I1B0B4 Your opinion matters. Fred 李永乐 -----Original Message----- From: Fred Li [mailto:yongle.li@gmail.com] Sent: Saturday, March 7, 2020 13:03 To: community <community(a)openeuler.org>; tc <tc(a)openeuler.org>; infra <infra(a)openeuler.org>; dev(a)openeuler.org; isulad(a)openeuler.org; a-tune(a)openeuler.org Subject: [Isulad] [Discusion] How can I become a member of Technical Committee in openEuler Hi openEuler community members, First of all, I will write Chinese in this email as all the information below are written in English in [1]. The purpose of this email is to ask you to leave your opinions in [1]. 各位openEuler社区的朋友们，我陆续会收到一些关于成为openEuler技术委员会成员的请求。比如如下： 1）我们公司做OS的，很大很有经验，公司可以派几名员工成为TC成员 2）某某是我们的架构师，很有经验，能否安排他成为TC成员 3）如果我给openEuler社区捐款，能否安排我成为TC成员？听到这类说法，一方面我很开心，因为说明有人关心openEuler社区并且有意进行技术贡献；一方面也有些困惑，因为可能因为我们没有解释清楚某些席位（比如TC成员、Committer）在开源社区的权利责任和义务是什么。于是我想请大家（无论是否有开源社区工作经验，还是没有）在[1]发表您的观点和看法。 1. 请在[1]的Issue区留言 2. 中文和英语都行 3. 记得遵守开源社区文化，简单一句话就是“be nice to others，对人友善” 将来，大家的观点可以汇总成一篇博客；其中一些大多数人支持的观点也可以作为社区治理的一部分。谢谢 [1] https://gitee.com/openeuler/community/issues/I1B0B4 -- Regards Fred Li (李永乐) _______________________________________________ Isulad mailing list -- isulad(a)openeuler.org To unsubscribe send an email to isulad-leave(a)openeuler.org

2 1

[Discusion] How can I become a member of Technical Committee in openEuler
by Fred Li 07 Mar '20

07 Mar '20

Hi openEuler community members, First of all, I will write Chinese in this email as all the information below are written in English in [1]. The purpose of this email is to ask you to leave your opinions in [1]. 各位openEuler社区的朋友们，我陆续会收到一些关于成为openEuler技术委员会成员的请求。比如如下： 1）我们公司做OS的，很大很有经验，公司可以派几名员工成为TC成员 2）某某是我们的架构师，很有经验，能否安排他成为TC成员 3）如果我给openEuler社区捐款，能否安排我成为TC成员？听到这类说法，一方面我很开心，因为说明有人关心openEuler社区并且有意进行技术贡献；一方面也有些困惑，因为可能因为我们没有解释清楚某些席位（比如TC成员、Committer）在开源社区的权利责任和义务是什么。于是我想请大家（无论是否有开源社区工作经验，还是没有）在[1]发表您的观点和看法。 1. 请在[1]的Issue区留言 2. 中文和英语都行 3. 记得遵守开源社区文化，简单一句话就是“be nice to others，对人友善” 将来，大家的观点可以汇总成一篇博客；其中一些大多数人支持的观点也可以作为社区治理的一部分。谢谢 [1] https://gitee.com/openeuler/community/issues/I1B0B4 -- Regards Fred Li (李永乐)

1 0

Fw:Welcome to the "Dev" mailing list
by 丁丽丽 26 Feb '20

26 Feb '20

-------- Forwarding messages -------- From: dev-request(a)openeuler.org Date: 2020-02-03 15:15:51 To: None <dingll1992(a)163.com> Subject: Welcome to the "Dev" mailing list Welcome to the "Dev" mailing list! To post to this list, send your email to: dev(a)openeuler.org You can unsubscribe or make adjustments to your options via email by sending a message to: dev-request(a)openeuler.org with the word 'help' in the subject or body (don't include the quotes), and you will get back a message with instructions. You will need your password to change your options, but for security purposes, this password is not included here. If you have forgotten your password you will need to reset it via the web UI.

1 0