- Dev - mailweb.openeuler.org

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

2024

2023

2022

2021

2020

2019

Dev