IRC logs for #cip for Thursday, 2021-10-28

« Wednesday, 2021-10-27 Index Friday, 2021-10-29 »
*** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has joined #cip06:20
*** toscalix <toscalix!~toscalix@90.167.158.238> has joined #cip06:59
*** toscalix <toscalix!~toscalix@90.167.158.238> has quit IRC07:15
*** toscalix <toscalix!~toscalix@90.167.158.238> has joined #cip07:15
*** brlogger <brlogger!~supybot@45.114.123.168> has joined #cip08:37
*** ChanServ sets mode: +o brlogger08:37
*** toscalix <toscalix!~toscalix@90.167.158.238> has quit IRC09:34
*** uli <uli!~uli@55d4ee7d.access.ecotel.net> has joined #cip11:45
*** toscalix <toscalix!~toscalix@84.78.243.38> has joined #cip12:02
*** masami <masami!~masami@FL1-122-133-108-128.tky.mesh.ad.jp> has joined #cip12:33
*** jki <jki!~jki@88.215.84.132> has joined #cip12:59
jki#startmeeting CIP IRC weekly meeting13:01
brloggerMeeting started Thu Oct 28 13:01:17 2021 UTC and is due to finish in 60 minutes.  The chair is jki. Information about MeetBot at http://wiki.debian.org/MeetBot.13:01
brloggerUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:01
brloggerThe meeting name has been set to 'cip_irc_weekly_meeting'13:01
*** brlogger changes topic to " (Meeting topic: CIP IRC weekly meeting)"13:01
jkihi all!13:01
iwamatsuhi13:01
ulihello13:01
alicefo/13:01
masamihi13:01
patersonc[m]\o/13:01
jkiIIRC, pavel will not join, right?13:02
iwamatsuI can not see Pavel.13:03
jki#topic AI review13:03
*** brlogger changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)"13:03
jki1. Combine root filesystem with kselftest binary - iwamatsu & alicef13:03
alicefI'm currently working isar-cip-core13:03
alicefas I think that KernelCI will be against make changes for use isar-cip-core. I'm working making isar-cip-core kernelci compatible13:05
alicefand added a new isar-cip-core image to the kernelci fileserver https://storage.staging.kernelci.org/images/rootfs/cip/13:05
alicefcurrently I could login with the default root/root and I found some KernelCI missing package that I will resolve later13:06
alicefabout the Gitlab CI kselftest binary is still paused for now13:07
jkiok13:08
jki2. Look into S3 artifact upload issues - patersonc13:09
alicefby the way, I wanted to ask about the root password in the isar-cip-core13:09
jkiyep - didn't we chat about that last time?13:10
patersonc[m]jki: no updates13:10
alicefjki: yes but I have some new question. isar-cip-core root password is needed for the IEC certification?13:10
jkirather likely - but only for the final "production" image13:11
alicefI was thinking if we can boot isar-cip-core password less and add the root password during IEC KernelCI testing13:11
jkiyou should clarify that with the security WG people13:12
jkiI think it should at least be fine to remove the password from the kernelCI targeting image13:12
alicefok13:12
alicefyes that is what I'm working on13:13
alicefI just wanted to know about the security certification perspective13:13
jkican't tell, I'm not directly involved -> mailing list13:14
alicefok, I will ask in the mailing list13:14
alicefthanks13:14
jkiok - next AI13:15
jki3. Update 5.10-cip branch - iwamatsu & pavel13:15
jki(picked this up from our past-week discussion)13:15
iwamatsuWhat is the purpose of this?13:17
jkimerging reviews 5.10-lts into 5.10-cip13:17
jkito expose that result to our tests13:17
jkis/reviews/reviewed/13:18
iwamatsuGot it, no update. but I can do it after this meeting.13:18
jkiperfect, TIA!13:18
jki4. Propose review coordination workflow with gitlab snippets - iwamatsu13:19
iwamatsuOkay. I invistigated about this.13:19
iwamatsuFirst , Snippets of gitlab can be created using the gitlab API.13:20
iwamatsusample code: https://gitlab.com/-/snippets/219700613:20
iwamatsuThis can be created as a sample. https://gitlab.com/cip-project/cip-kernel/linux-cip/-/snippets/2197003.13:21
iwamatsuAnd since this is a git repository, we can use it with git command. Of cource we can use it with Web UI.13:21
iwamatsugitrepo URL: https://gitlab.com/cip-project/cip-kernel/linux-cip/snippets/2197003.git13:22
iwamatsuMy impression are...13:22
iwamatsuPros: There is no need to create a new repository.13:22
iwamatsuCons: 1. The URL is different every time.13:22
iwamatsu2. repository is created for each kernel version.13:23
iwamatsu3. We don't know which version from URL and repository name.13:23
iwamatsuSo, I don't think this is easy to use.  I think it is better to create or reuse a dedicated repository.13:24
iwamatsuThat's all from me.13:25
patersonc[m]GitLab also supports a wiki right? Would that give a consistent URL?13:25
jkiyes, you can activate a wiki per project13:25
iwamatsues.13:25
iwamatsuYes13:25
jkithat would be a git repo as well13:26
jkiwith stable URL13:26
iwamatsuThere is no problem with Wiki for linux-cip repo.13:26
jkiright13:26
jkijust needs activation13:26
jkiand decision who should be allowed to edit it (anyone / project members)13:27
iwamatsuwe can control it via web ui13:28
jkiboth web ui and git push, yes13:28
iwamatsuI can enable wiki in linux-cip now, if we use wiki :-)13:29
jkigive it a try and discuss again need week?13:30
iwamatsuIf anyone wants to use it other than gitlab wiki.13:31
iwamatsuI think wiki is better for review coordination13:32
uli+113:33
iwamatsuor we can wait Pavel's comment.13:33
jkimaybe prepare a basic example, like you did for the snippets13:34
iwamatsuI see.13:34
iwamatsuOK, I will prepare it13:35
jkithanks!13:35
jkianything else under "AIs"?13:36
jki313:36
jki213:36
jki113:36
jki#topic Kernel maintenance updates13:36
*** brlogger changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)"13:36
ulireviewed 5.10.7513:37
iwamatsuI am reviewing 5.10.76.13:37
masamiThis week reported 3 new CVEs. These CVEs have been already fixed.13:37
jkianything else to discuss under this topic?13:40
jki313:40
jki213:40
jki113:40
jki#topic Kernel testing13:40
*** brlogger changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)"13:40
patersonc[m]I think Alice has already reported most of the news13:41
jkithen let's assume "most = all" ;)13:42
jki313:42
jki213:42
jki113:42
jki#topic AOB13:42
*** brlogger changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)"13:42
jkianyone anything else?13:44
jki313:45
patersonc[m]Not I13:45
jki213:45
jki113:45
jki#endmeeting13:45
brloggerMeeting ended Thu Oct 28 13:45:13 2021 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:45
brloggerMinutes:        https://irclogs.baserock.org/meetings/cip/2021/10/cip.2021-10-28-13.01.html13:45
brloggerMinutes (text): https://irclogs.baserock.org/meetings/cip/2021/10/cip.2021-10-28-13.01.txt13:45
brloggerLog:            https://irclogs.baserock.org/meetings/cip/2021/10/cip.2021-10-28-13.01.log.html13:45
*** brlogger changes topic to "Civil Infrastructure Platform Project. Find the logs at https://irclogs.baserock.org/cip/"13:45
jkithen thank you all!13:45
iwamatsuthank you!13:45
masamibye!13:45
jkibye13:45
patersonc[m]TTFN13:45
ulibye13:45
alicefbye13:46
*** masami <masami!~masami@FL1-122-133-108-128.tky.mesh.ad.jp> has quit IRC13:50
*** jki <jki!~jki@88.215.84.132> has quit IRC13:50
*** uli <uli!~uli@55d4ee7d.access.ecotel.net> has left #cip13:51
*** jki <jki!~jki@165.225.27.13> has joined #cip14:03
*** jki <jki!~jki@165.225.27.13> has quit IRC14:52
*** jki <jki!~jki@165.225.26.250> has joined #cip15:04
*** jki <jki!~jki@165.225.26.250> has quit IRC15:16
*** toscalix <toscalix!~toscalix@84.78.243.38> has quit IRC16:24
*** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has quit IRC21:58
« Wednesday, 2021-10-27 Index Friday, 2021-10-29 »

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!