Thursday, 2024-05-16

« Wednesday, 2024-05-15 Index Friday, 2024-05-17 »
*** rajm <rajm!~robert@macc-04-b2-v4wan-169608-cust697.vm21.cable.virginm.net> has joined #cip01:46
*** monstr <monstr!~monstr@213.0.35.99> has joined #cip06:05
*** monstr <monstr!~monstr@213.0.35.99> has quit IRC (Ping timeout: 252 seconds)06:16
*** frieder <frieder!~frieder@255-179-142-46.pool.kielnet.net> has joined #cip06:29
*** monstr <monstr!~monstr@149.14.240.163> has joined #cip07:10
*** monstr <monstr!~monstr@149.14.240.163> has quit IRC (Remote host closed the connection)07:19
*** monstr <monstr!~monstr@149.14.240.163> has joined #cip09:35
*** monstr <monstr!~monstr@149.14.240.163> has quit IRC (Remote host closed the connection)09:43
*** monstr <monstr!~monstr@149.14.240.163> has joined #cip11:40
*** monstr <monstr!~monstr@149.14.240.163> has quit IRC (Ping timeout: 252 seconds)11:45
*** masami <masami!~masami@FL1-219-107-72-235.tky.mesh.ad.jp> has joined #cip12:51
*** jki <jki!~jki@62.156.206.32> has joined #cip12:58
jkihi all13:00
masamihello13:00
patersoncHello13:00
pave1Hi!13:01
jkiok, our rounds seems smaller today13:02
jkilet's start (I'm in a parallel meeting in fact913:02
pave1Summer slowly coming :-)13:03
jki#startmeeting CIP IRC weekly meeting13:03
collab-meetbot`Meeting started Thu May 16 13:03:04 2024 UTC and is due to finish in 60 minutes.  The chair is jki. Information about MeetBot at http://wiki.debian.org/MeetBot.13:03
collab-meetbot`Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:03
collab-meetbot`The meeting name has been set to 'cip_irc_weekly_meeting'13:03
*** collab-meetbot` changes topic to " (Meeting topic: CIP IRC weekly meeting)"13:03
jki#topic AI review13:03
*** collab-meetbot` changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)"13:03
jki- prepare blog entry on SLTS kernel state and challenges [Jan]13:03
jkisorry, not much news here, distractions again13:03
jkianything from last weeks?13:03
jki513:04
pave1No.13:04
jki413:04
jki313:04
jki213:04
jki113:04
jki#topic Kernel maintenance updates13:04
*** collab-meetbot` changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)"13:04
masamiThis week reported 6 new CVEs and 5 updated CVEs.13:04
pave1I did reviews: 6.1.91.13:04
jkionly 6? not 600? :)13:05
masamiyes! it was quiet week :)13:05
pave1I'd not make jokes about this, or we end up with 6000 next week.13:05
masamiit might be that the existing bugs are finally decreasing?13:07
pave1masami: I'm afraid it has more to do with position in release cycle or maybe maintainer workload.13:07
jkiI suspect that as well13:07
jkiok - anything else?13:08
masamipavel: it can be true..13:08
jki513:08
jki413:08
jki313:08
jki213:08
jki113:08
jki#topic Kernel release status13:09
*** collab-meetbot` changes topic to "Kernel release status (Meeting topic: CIP IRC weekly meeting)"13:09
pave14.19-rt is late.13:09
jkionly 4.19-rt is late right now13:09
jkiany hope on that?13:09
pave1I asked for v4.19.312-rt134, and it is up-to -rc3, but no release last time I checked.13:09
jkiok13:09
jkiany apparent bugs in it, or just busy maintainer?13:10
pave1I guess it is not going as smoothly as usual. Normally we see zero or single -rc.13:10
jkiwhere are those potential glitches tracked?13:11
jkianything in public?13:11
pave1I don't know about anything. I guess we may get some info in release announcement.13:11
jkican we do anything to help them - and get more information about issues at the same time?13:12
pave1Not really sure. I can try to ask, but I'm not sure if I know enough about rt to be able to help.13:13
jkijust thinking out load and feel like we should get more involved here, also thinking ahead when we have more self-maintained RT kernels...13:15
jkiok13:15
jkimoving on...13:15
jki513:15
jki413:15
jki313:15
jki213:15
jki113:15
jki#topic Kernel testing13:15
*** collab-meetbot` changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)"13:15
jkianything?13:16
patersoncAh sorry13:16
patersoncI looked into the stable-rc issue Pavel reported13:17
patersoncThanks for that13:17
patersoncWorking again now13:17
pave1Thank you. Tests are working again.13:17
patersoncI've also drafted the MRs to add v6.9 stable testing support13:17
pave16.9.1-rc1 is out now, so we could start that.13:18
patersoncI need the kernel-configs to be merged first. Then I can do the rest13:18
patersoncjki: Any updates on the Siemens LAVA lab?13:19
jkishould be back next week13:20
patersoncGreat13:20
patersoncI've no further updates this week13:23
jkiok13:25
jkimoving on...13:25
jki513:27
jki413:27
jki313:27
jki213:27
jki113:27
jki#topic AOB13:27
*** collab-meetbot` changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)"13:27
jkianything?13:29
jki513:29
pave1Not really, quiet week, as -rc1 was not released, yet.13:29
jki413:30
jki313:30
jki213:30
jki113:30
jki#endmeeting13:30
collab-meetbot`Meeting ended Thu May 16 13:30:16 2024 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:30
collab-meetbot`Minutes:        http://ircbot.wl.linuxfoundation.org/meetings/cip/2024/05/cip.2024-05-16-13.03.html13:30
collab-meetbot`Minutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2024/05/cip.2024-05-16-13.03.txt13:30
collab-meetbot`Log:            http://ircbot.wl.linuxfoundation.org/meetings/cip/2024/05/cip.2024-05-16-13.03.log.html13:30
*** 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 13: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/"13:30
pave1Thank you!13:30
jkithen thank you all!13:30
masamithanks13:30
*** masami <masami!~masami@FL1-219-107-72-235.tky.mesh.ad.jp> has quit IRC (Quit: Leaving)13:30
*** jki <jki!~jki@62.156.206.32> has quit IRC (Ping timeout: 264 seconds)13:35
*** masami <masami!~masami@FL1-219-107-72-235.tky.mesh.ad.jp> has joined #cip14:01
*** masami <masami!~masami@FL1-219-107-72-235.tky.mesh.ad.jp> has quit IRC (Client Quit)14:01
*** frieder <frieder!~frieder@255-179-142-46.pool.kielnet.net> has quit IRC (Remote host closed the connection)18:50
*** dl9pf_ <dl9pf_!sid395223@user/dl9pf> has joined #cip19:16
*** patersonc_ <patersonc_!sid614485@id-614485.hampstead.irccloud.com> has joined #cip19:16
*** dl9pf <dl9pf!sid395223@user/dl9pf> has quit IRC (Ping timeout: 256 seconds)19:17
*** patersonc <patersonc!sid614485@id-614485.hampstead.irccloud.com> has quit IRC (Read error: Connection reset by peer)19:17
*** dl9pf_ is now known as dl9pf19:17
*** patersonc_ is now known as patersonc19:17
*** shoragan_ <shoragan_!~shoragan@user/shoragan> has joined #cip19:17
*** shoragan <shoragan!~shoragan@user/shoragan> has quit IRC (Ping timeout: 256 seconds)19:17
*** arnd <arnd!sid21101@id-21101.hampstead.irccloud.com> has quit IRC (Ping timeout: 246 seconds)19:17
*** arnd <arnd!sid21101@id-21101.hampstead.irccloud.com> has joined #cip19:17
*** monstr <monstr!~monstr@213.0.35.99> has joined #cip21:08
*** monstr <monstr!~monstr@213.0.35.99> has quit IRC (Remote host closed the connection)21:22
*** rajm <rajm!~robert@macc-04-b2-v4wan-169608-cust697.vm21.cable.virginm.net> has quit IRC (Ping timeout: 240 seconds)22:10
« Wednesday, 2024-05-15 Index Friday, 2024-05-17 »

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