IRC logs for #cip for Thursday, 2020-03-26

« Wednesday, 2020-03-25 Index Friday, 2020-03-27 »
*** rajm has joined #cip07:16
*** pave1 has joined #cip08:57
*** masashi910 has joined #cip08:57
*** suzuki83 has joined #cip08:59
masashi910#startmeeting CIP IRC weekly meeting09:00
brlogger`Meeting started Thu Mar 26 09:00:01 2020 UTC and is due to finish in 60 minutes.  The chair is masashi910. Information about MeetBot at http://wiki.debian.org/MeetBot.09:00
brlogger`Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.09:00
brlogger`The meeting name has been set to 'cip_irc_weekly_meeting'09:00
*** brlogger` changes topic to " (Meeting topic: CIP IRC weekly meeting)"09:00
masashi910#topic rollcall09:00
*** brlogger` changes topic to "rollcall (Meeting topic: CIP IRC weekly meeting)"09:00
masashi910please say hi if you're around09:00
iwamatsuhi09:00
suzuki83hi09:00
bwh_hi09:00
szlinhi09:00
*** bwh_ is now known as bwh09:00
patersonchi09:00
masashi910#topic AI review09:00
*** brlogger` changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)"09:00
punithi09:00
masashi9101. Combine root filesystem with kselftest binary - Iwamatsu-san09:00
pave1hi09:00
wenshi09:00
masashi910Iwamatsu-san, do you have update?09:01
iwamatsumasashi910: no update ahout this.09:01
masashi910iwamatsu: Noted. Thanks.09:01
masashi9102. Assign the owner of "CIP kernel config" - masashi91009:01
masashi910Iwamatsu-san kindly picked up this task. Iwamatsu-san, thank you!09:01
masashi910I will close this item.09:02
masashi9103. Strengthen sustainable process to backport patches from Mainline/LTS - Kernel Team09:02
masashi910This is under discussion among the Kernel team.09:02
*** tpollard has joined #cip09:02
masashi910The current consensus among the Kernel Team is described in the following document.09:02
masashi910https://docs.google.com/document/d/1U4-txCx_uofNH7YXc9LgKILdY-BPgb-nYm3DFrs-9Ns/edit?usp=sharing09:02
masashi910If you have any comments, please add as "comment"s to the document.09:02
masashi9104. Upload a guideline for reference hardware platform addition - masashi91009:02
masashi910Updates can be reported around June timeframe.09:02
masashi910any other topics?09:02
masashi910309:03
*** fujita3 has joined #cip09:03
masashi910209:03
masashi910109:03
masashi910#topic Kernel testing09:03
*** brlogger` changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)"09:03
masashi910patersonc: the floor is yours09:03
patersoncNo Kernel updates?09:04
masashi910patersonc: Sorry. You are right... let me back to the kernel update.09:04
masashi910#topic Kernel Updates09:05
*** brlogger` changes topic to "Kernel Updates (Meeting topic: CIP IRC weekly meeting)"09:05
iwamatsumasashi910: I reviewed v4.4.217.09:05
wensnew CVE which is an out-of-bounds write in vhost_net; requires backport to 4.4; all newer stable branches fixed09:06
pave1Solved realtime problems, so I could release v4.19.106-cip21-rt8.09:06
pave1Reviews on 4.19.112 and 4.19.113.09:06
wens"vhost: Check docket sk_family instead of call getname" is the fix09:06
pave1wens: Ok, let me take a look.09:06
wensshould be straightforward; I believe it was just an API change in between09:07
pave1wens: Or you can have it if you want practice :-).09:07
pave1wens: Fortunately it is easy most of the time.09:07
patersoncWell done pavel09:08
masashi910iwamatsu, wens, pave1: Thanks for your updates.09:09
patersonc0/09:09
masashi910Any other topics?09:09
patersoncFYI I emailed Greg last night about whether 4.19 LTS will be extended, he said "I have not decided yet, normally I do so sometime in the middle of the year"09:10
patersoncHe also asked why I'm interested, why 2 years isn't enough and can I ensure users would take the updates. I'll reply to him later, let me know if you have anything you want me to include.09:10
patersoncI guess if 4.19 LTS isn't extended, it may drive more users to CIP's SLTS?09:11
masashi910patersonc: Great to raise this topic! Thanks!09:11
punitI think it would be worth mentioning that it is used by "buster"09:11
pave1patersonc: If lts isn't extended, we may want to call ourselves "lts" :-).09:11
pave1punit: I assume Greg is aware of Debian status.09:12
patersoncHow long will Buster use it?09:12
bwhUntil 202409:12
punitTo call ourselves LTS we'd need to widen the scope of our coveraage, no?09:12
patersoncDoes Debian take LTS straight, or add some stuff on top? What would they do if LTS support ended?09:13
pave1punit: Well, we'd need to apply more patches, and we'd get testing from community.09:13
punitMaybe bwh has some insight?09:14
pave1punit: Applying patches to areas we don't care about is quite easy, so...09:14
bwhpatersonc: We sometimes add driver backports, e.g. we have some newer HiSilicon bits09:14
patersoncOkay, thanks09:15
bwhWe could probably work with the CIP branch if necessary09:15
patersoncThat might be good for CIP09:15
punitpavel: I think it makes sense to apply patches to wider areas. We attract more developers / users and can get wider testing coverage09:16
pave1punit: I think so, too.09:16
pave1Is 4.4-stable or 4.19-stable likely to become unmaintained, first?09:17
masashi910all: Great discussions! Thanks. This is an important topic. So we will come back in the future IRC as well.09:17
patersonchttps://www.kernel.org/category/releases.html09:17
masashi910Can we move on?09:18
masashi910309:18
masashi910209:18
masashi910109:18
masashi910#topic Kernel testing09:18
*** brlogger` changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)"09:18
patersoncThe CI setup now builds/tests with the CIP qemu config (thank you Iwamatsu-san).09:19
patersoncBoth CIP and stable Kernels09:19
patersoncSome boards in lab-cip-renesas are offline due to USB issues. Office is shut due to CV so there's not a lot I can do to fix atm.09:19
patersonclab-cip-cybertrust currently has some network issues and is offline, sorry. They are investigating.09:19
patersonclab-cip-denx setup is in progress.09:19
patersoncA new 'staging' instance of our LAVA master is being set up so updates/improvements don't affect production.09:19
patersoncThen we can move to a much newer version of LAVA09:19
patersoncAny questions?09:20
punit+1 to moving to a newer version!09:20
masashi910patersonc: Thanks for your works.09:21
masashi910Any other comments or queries?09:21
masashi910309:21
masashi910209:21
masashi910109:21
masashi910#topic CIP Core09:22
*** brlogger` changes topic to "CIP Core (Meeting topic: CIP IRC weekly meeting)"09:22
punitI guess that's me this week!09:22
masashi910punit: Yes, please!09:22
punitThere isn't a lot to report other than the moving of security WG test image to isar-cip-core repo from Hayashi-san's private one09:23
punitThat's it from me. Let me know if there are any questions09:23
masashi910punit: Thanks for your report!09:23
masashi910punit: I have a question. So, by moving Hayashi-san's private one to the public, it will be maintained by who?09:24
punitIt was maintained by members of Core. But with the relocation, it'll get wider visibility. It'll still be maintained by core09:25
masashi910punit: I see. Thanks.09:26
masashi910Any other comments or queries?09:26
masashi910309:26
punitThe image is currently being used for development of test cases and evaluation against IEC standard09:26
masashi910punit: I understood. Thanks for your explanation.09:27
masashi910309:27
masashi910209:27
masashi910109:27
masashi910#topic Software update09:27
*** brlogger` changes topic to "Software update (Meeting topic: CIP IRC weekly meeting)"09:27
suzuki83Hello09:27
suzuki83I tested deby + meta-swupdate integrated by Hieu-san and it could run correctly.09:28
suzuki83But it doesn't support A/B update at the moment, so I suggested integrating it by using meta-swupdate-boards.09:28
suzuki83See this link for more details: https://gitlab.com/cip-project/cip-core/deby/-/issues/809:28
suzuki83That's all from me.09:28
masashi910suzuki83: Thanks for your report.09:28
masashi910Any comments or queries?09:28
masashi910309:29
masashi910209:29
masashi910109:29
masashi910#topic CIP Security09:29
*** brlogger` changes topic to "CIP Security (Meeting topic: CIP IRC weekly meeting)"09:29
masashi910Yoshida-san, are you around?09:29
yoshidak[m]hi09:29
yoshidak[m]1. The progress of the certification09:29
yoshidak[m]Same as the last report, we are waiting for approval from GB to pay for gap assessment.09:29
yoshidak[m]2. Creating and testing our security packages09:29
yoshidak[m]We confirmed that we can share test cases for the security packages from the copylight point of view.09:30
yoshidak[m]But, it will be revised at the certification phases, so we will not share it at this time.09:30
yoshidak[m]Once we complete security packages certification, we will be sharing revised security packages proposal and test cases.09:30
yoshidak[m]Although, we can share it as just reference and it will be helpful to understand what is required in the specs.09:30
yoshidak[m]So, please let me know if you want to check it.09:30
yoshidak[m]Any question?09:31
pave1yoshidak: We are trying to be open project.09:31
pave1yoshidak: From my side it makes sense to make changes public as soon as we make them,09:31
pave1yoshidak: even if they may change in future.09:32
yoshidak[m]<pave1 "yoshidak: even if they may chang"> I see. Of cause we can share it. Thank you this comment.09:32
pave1yoshidak: Thank you.09:33
masashi910yoshidak[m]: Thanks for your report.09:33
masashi910Any other comments or queries?09:33
masashi910309:33
masashi910209:33
masashi910109:33
masashi910#topic AOB09:33
*** brlogger` changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)"09:33
masashi9101. Summer Time09:33
masashi910The summer saving time is starting. But please note that this IRC meeting starts at UTC (GMT) 09:00.09:33
masashi910This is just reminder.09:33
masashi910Are there any business matters to discuss?09:34
masashi910309:34
masashi910209:34
masashi910109:34
masashi910#endmeeting09:34
brlogger`Meeting ended Thu Mar 26 09:34:26 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)09:34
brlogger`Minutes:        https://irclogs.baserock.org/meetings/cip/2020/03/cip.2020-03-26-09.00.html09:34
brlogger`Minutes (text): https://irclogs.baserock.org/meetings/cip/2020/03/cip.2020-03-26-09.00.txt09:34
brlogger`Log:            https://irclogs.baserock.org/meetings/cip/2020/03/cip.2020-03-26-09.00.log.html09:34
*** brlogger` changes topic to "Civil Infrastructure Platform Project. Find the logs at https://irclogs.baserock.org/cip/"09:34
masashi910Thanks very much!09:34
pave1Thank you!09:34
punitThanks!09:34
suzuki83Thank you!09:34
iwamatsuthank you!09:34
bwhThanks09:35
szlinthank you09:35
wensthank you09:35
yoshidak[m]Thank you!09:35
fujita3Thank you!09:35
*** suzuki83 has quit IRC09:35
*** fujita3 has quit IRC09:35
*** pave1 has quit IRC10:20
*** brlogger has joined #cip14:28
*** brlogger` has quit IRC14:28
*** bwh has quit IRC14:29
*** bwh has joined #cip14:30
*** toscalix has joined #cip17:50
*** tpollard has quit IRC18:14
*** toscalix has quit IRC18:55
*** toscalix has joined #cip18:56
*** toscalix has quit IRC20:45
*** rajm has quit IRC23:08
*** pave1 has joined #cip23:41
*** pave1 has quit IRC23:58
« Wednesday, 2020-03-25 Index Friday, 2020-03-27 »

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!