Thursday, 2023-10-12

*** monstr <monstr!~monstr@nat-35.starnet.cz> has joined #cip05:49
*** monstr <monstr!~monstr@nat-35.starnet.cz> has quit IRC (Ping timeout: 240 seconds)05:54
*** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has joined #cip06:01
*** frieder <frieder!~frieder@i577B91E6.versanet.de> has joined #cip07:12
*** uli <uli!~uli@2001:4091:a247:80c0:34c2:e69f:e88f:90ef> has joined #cip09:55
*** monstr <monstr!~monstr@nat-35.starnet.cz> has joined #cip11:43
*** masami <masami!~masami@FL1-125-195-134-41.tky.mesh.ad.jp> has joined #cip11:50
*** sietze <sietze!~sietze_va@msw-v.fe.bosch.de> has joined #cip11:55
*** jki <jki!~jki@195.145.170.166> has joined #cip11:56
jkihi all!12:00
masamihello12:00
ulihello12:01
patersoncMornin12:01
sietzeHi!12:01
pave1Hi!12:01
jkithen let's go12:02
jki#startmeeting CIP IRC weekly meeting12:02
collab-meetbotMeeting started Thu Oct 12 12:02:17 2023 UTC and is due to finish in 60 minutes.  The chair is jki. Information about MeetBot at http://wiki.debian.org/MeetBot.12:02
collab-meetbotUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.12:02
collab-meetbotThe meeting name has been set to 'cip_irc_weekly_meeting'12:02
*** collab-meetbot changes topic to " (Meeting topic: CIP IRC weekly meeting)"12:02
jki#topic AI review12:02
*** collab-meetbot changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)"12:02
jkistill empty - we need to define new ones ;)12:02
pave1I believe we should be happy like this :-).12:02
jkialso correct12:02
jki#topic Kernel maintenance updates12:02
*** collab-meetbot changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)"12:02
iwamatsuhi all12:03
pave1I did reviews, 6.1.56, .57.12:03
ulii reviewed 6.1.55 and released 4.412:03
masamiThis week reported 6 new CVEs and 8 updated CVEs.12:03
iwamatsuI reviewd 6.1.56, and reviewing 6.1.57.12:03
pave15.10.198 is broken on Renesas boards. Avoid it.12:04
pave1Stable team is aware so I expect 5.10.199 to be ok.12:04
jkidid we test .198 too late?12:04
pave1Not really. We reported problems within 6 hours.12:06
jkiGreg was too fast again :)12:06
jkiok, anything else?12:07
pave1Greg says he waits 48 hours for feedback, but he released it earlier than that.12:07
patersoncpave1 even pointed to the broken commit12:07
jkiyeah, good that we do extra work12:09
jkiok, then move on in...12:09
jki512:09
jki412:09
jki312:09
jki212:09
jki112:09
jki#topic Kernel release status12:09
*** collab-meetbot changes topic to "Kernel release status (Meeting topic: CIP IRC weekly meeting)"12:09
jki4.412:09
uli-st45/-cip80 are out, including tarballs12:10
pave1I should do rt there.12:10
jkiperfect12:10
jki4.1912:10
iwamatsuon track.12:11
jkirt as well?12:11
pave1rt is due soon.12:11
jkiok12:11
jki5.1012:11
iwamatsuon track.  I will release with 5.10.197.12:11
pave1I'm confused with 5.10-rt.12:11
pave1I asked for 5.10.197-cip.12:12
pave1but I should go through logs again.12:12
pave1Last one was on Sep 19, and we are on two month schedule.12:13
jkithat's true12:13
pave1So... sorry for confusion, we don't need to do 5.10.197-cip for sake of -rt.12:13
pave1I confused it with 4.19.12:13
jkiok12:14
jkiand 6.112:14
pave1iwamatsu: Sorry about that.12:14
pave1-rt is due, soon.12:14
iwamatsuNo problem12:14
jkiso, 6.1?12:15
iwamatsuon track.12:15
jkirt-wise as well?12:15
pave1Yes. It is due in 9 days.12:16
jkigood12:16
jki#topic Kernel testing12:16
*** collab-meetbot changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)"12:16
patersoncHello12:16
patersoncI've been working on upgrading our LAVA version (at last)12:16
patersoncHopefully we'll do the upgrade early next week, but I'm still waiting to hear back from all of the lab owners12:17
jkiwho's is missing?12:17
patersoncI think only 1 lab replied12:17
patersonccybertrust12:17
jkiok12:17
pave1patersonc: From my point of view, testing offline is as bad on Monday as on any other day. We don't really know ahead when we'll need testing.12:18
masamipatersonc: I'll ask toyooka-san12:18
pave1patesrsonc: So I guess just go ahead :-).12:18
jkitalked to Claudius yesterday, and he told me he is aware and expect no problems12:18
patersoncGood to know, thanks Pavel12:18
patersoncmasami: Toyooka-san is the only one who replied :) No need to chase him, thank you12:18
pave1(and this may be actually good time as it is calm part of release cycle).12:19
jkido not wait for the mentor lab12:19
patersoncThanks jki12:19
masamipatersonc: ok :)12:19
patersoncI think the upgrade on the lab side is easy enough12:19
patersoncAlthough they will need to upgrade OS if they are still on Stretch12:19
patersoncThat's about it from me. Other than to say thank you to Pavel for reporting the LTS testing back to the ML - I've been a bit lack on that of late12:21
jkianything else on testing by anyone?12:22
jki512:23
jki412:23
jki312:23
jki212:23
jki112:23
jki#topic AOB12:23
*** collab-meetbot changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)"12:23
jkiany remaining topic for today?12:24
jki512:24
jki412:24
jki312:24
jki212:24
jki112:24
jki#endmeeting12:24
collab-meetbotMeeting ended Thu Oct 12 12:24:51 2023 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)12:24
collab-meetbotMinutes:        http://ircbot.wl.linuxfoundation.org/meetings/cip/2023/10/cip.2023-10-12-12.02.html12:24
collab-meetbotMinutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2023/10/cip.2023-10-12-12.02.txt12:24
collab-meetbotLog:            http://ircbot.wl.linuxfoundation.org/meetings/cip/2023/10/cip.2023-10-12-12.02.log.html12:24
*** collab-meetbot changes topic to "Civil Infrastructure Platform Project. CIP mailing list at https://lists.cip-project.org/g/cip-dev | CIP kernel meeting every Thursday at 12:00 UTC | Find the meeting logs at https://ircbot.wl.linuxfoundation.org/meetings/cip/ and chat logs at https://ircbot.wl.linuxfoundation.org/logs/%23cip/"12:24
pave1Thank you!12:24
sietzeThanks!12:24
jkithen thank you all12:24
ulithanks12:24
iwamatsuthank you12:25
masamithank you12:25
*** masami <masami!~masami@FL1-125-195-134-41.tky.mesh.ad.jp> has quit IRC (Quit: Leaving)12:25
patersoncCheers12:26
*** jki <jki!~jki@195.145.170.166> has quit IRC (Remote host closed the connection)12:44
*** sietze <sietze!~sietze_va@msw-v.fe.bosch.de> has quit IRC (Quit: Leaving)12:44
*** monstr <monstr!~monstr@nat-35.starnet.cz> has quit IRC (Remote host closed the connection)14:53
*** uli <uli!~uli@2001:4091:a247:80c0:34c2:e69f:e88f:90ef> has left #cip (Leaving)15:42
*** monstr <monstr!~monstr@nat-35.starnet.cz> has joined #cip17:28
*** frieder <frieder!~frieder@i577B91E6.versanet.de> has quit IRC (Remote host closed the connection)18:16
*** monstr <monstr!~monstr@nat-35.starnet.cz> has quit IRC (Remote host closed the connection)18:37
*** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has quit IRC (Ping timeout: 260 seconds)21:47
*** collab-meetbot` <collab-meetbot`!~supybot@ec2-35-167-58-160.us-west-2.compute.amazonaws.com> has joined #cip22:39
*** ChanServ sets mode: +o collab-meetbot`22:39
*** collab-meetbot <collab-meetbot!~supybot@ec2-34-211-103-193.us-west-2.compute.amazonaws.com> has quit IRC (Remote host closed the connection)22:46

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