Thursday, 2024-12-05

« Wednesday, 2024-12-04 Index Friday, 2024-12-06 »
*** prabhakalad <prabhakalad!~prabhakar@165.225.197.26> has quit IRC (Ping timeout: 248 seconds)02:39
*** prabhakalad <prabhakalad!~prabhakar@165.225.197.26> has joined #cip02:40
*** sashal_ <sashal_!sid491190@id-491190.hampstead.irccloud.com> has joined #cip05:03
*** rynofinn____ <rynofinn____!sid362734@id-362734.lymington.irccloud.com> has quit IRC (Ping timeout: 272 seconds)05:03
*** sashal <sashal!sid491190@id-491190.hampstead.irccloud.com> has quit IRC (Ping timeout: 264 seconds)05:03
*** sashal_ is now known as sashal05:03
*** dl9pf <dl9pf!sid395223@user/dl9pf> has quit IRC (Ping timeout: 246 seconds)05:03
*** rynofinn____ <rynofinn____!sid362734@id-362734.lymington.irccloud.com> has joined #cip05:06
*** dl9pf <dl9pf!sid395223@user/dl9pf> has joined #cip05:06
*** monstr <monstr!~monstr@nat-35.starnet.cz> has joined #cip06:48
*** monstr <monstr!~monstr@nat-35.starnet.cz> has quit IRC (Read error: Connection reset by peer)07:10
*** monstr_ <monstr_!~monstr@nat-35.starnet.cz> has joined #cip07:10
*** masami <masami!~masami@FL1-118-111-145-206.tky.mesh.ad.jp> has joined #cip12:59
*** jki <jki!~jki@195.145.170.171> has joined #cip12:59
*** iwamatsu__ <iwamatsu__!~iwamatsu_@2405:6581:5360:1800:e544:cfcc:e9e9:cb0c> has joined #cip13:00
jkihi all13:00
iwamatsu__hi13:00
masamihi13:00
pave1hi!13:00
patersoncHey13:01
jkiok, let's go13:01
jki#startmeeting CIP IRC weekly meeting13:01
collab-meetbotMeeting started Thu Dec  5 13:01:59 2024 UTC and is due to finish in 60 minutes.  The chair is jki. Information about MeetBot at http://wiki.debian.org/MeetBot.13:01
collab-meetbotUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:01
collab-meetbotThe meeting name has been set to 'cip_irc_weekly_meeting'13:01
*** collab-meetbot changes topic to " (Meeting topic: CIP IRC weekly meeting)"13:02
jki#topic AI review13:02
*** collab-meetbot changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)"13:02
jki- prepare blog entry on SLTS kernel state and challenges [Jan]13:02
jkionce again, /me was very busy with other stuff :(13:02
jkihope to get it done before x-max :)13:02
jkiI'm not seeing other AIs from last week, so...13:03
jki513:03
jki413:03
jki313:03
jki213:03
jki113:03
jki#topic Kernel maintenance updates13:03
*** collab-meetbot changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)"13:03
masamiThis week reported 38 new CVEs and 0 updated CVEs.13:03
pave1New kernel release cycle began, so 6.1.120 is going to be huge. Reviewing that.13:03
pave1(And leftovers from the last cycle).13:04
uli_i pushed out 4.413:04
iwamatsu__I reviewed 6.1.118 and 119.13:04
jkianything else?13:06
patersoncI see that 6.12 is now listed on https://www.kernel.org/category/releases.html13:06
pave1There were questions about that on TSC.13:06
jkioh, missed that, thanks for the hint13:07
pave1Hmm. Fun, it is marked as longterm on that page, but not on main page.13:07
jkiwas there anything on some list?13:07
* patersonc shrugs13:08
jkierr, 6.12 is not listed on that page yet13:08
jkilatest version is still 6.613:08
patersoncCache?13:08
patersonchttps://usercontent.irccloud-cdn.com/file/cN4DiqPN/image.png13:08
pave1Aha, no;13:08
pave1https://www.kernel.org/category/releases.html is confusing13:09
jkiindeed, just open again in a private tab13:09
jkinow it's there, updated today13:09
pave1Says 'Longterm release kernels' but then lists two years ...13:09
jkilonger than 2 months ;)13:10
patersoncLTS support usually starts at 2 years, then is increased as time goes on if there's enough interest/support etc.13:10
pave1Yup, right. But 5.10 + 6.1 + 6.12 all ending on Dec 2026 looks really, really scary.13:11
jkiwell, but none of that is any news13:11
pave1And I thought 2025 would be bad :)13:12
jkigood news: it won't get worse after that ;)13:13
jkibut, yes, we will gain 3 new self-maintained kernels at once in 202713:13
patersoncMy current understanding is that most LTSs will end up being supported for 4 years13:14
jkiand drop one at that time (4.4)13:14
jkiwhere was that 4 years thing communicated?13:14
pave1My understanding was similar to patersonc's.13:15
jki?13:17
pave1No idea. Patersonc?13:18
patersoncGreg told me :)13:19
jkiwell, we will see13:20
jkianyway - still the question where we should place our announcement outside of cip-dev13:20
jkiif there is no email thread yet13:20
jkiif someone spots something, let me know13:21
pave1Ok.13:21
pave1Also, there'll be last 4.19.X release.13:21
pave1I guess that's good place to announce we'll be continuing to maintain this.13:21
jkiyes, that would be good for 4.1913:22
jkibut for 6.12, I will probably start an own thread somewhere next week, cip-dev/lkml/stable13:22
pave14.19 -- Should I do that?13:22
jkipavel: yes, sure13:23
pave1ok.13:23
jkimaybe we should just cooardinate so that we can cross-reference threads13:23
pave1ok, so you cc me and I cc you, so that the second post can cross-reference?13:24
jkido we have an idea when that final 4.19 will be?13:24
*** monstr_ <monstr_!~monstr@nat-35.starnet.cz> has quit IRC (Ping timeout: 252 seconds)13:24
pave1jki: I'd expect it in few days, no more than a week.13:25
jkithat sounds good13:25
jkiok - anything else?13:26
jki513:26
jki413:27
jki313:27
jki213:27
jki113:27
jki#topic Kernel release status13:27
*** collab-meetbot changes topic to "Kernel release status (Meeting topic: CIP IRC weekly meeting)"13:27
jki4.4 and 4.19 rt are late13:27
pave14.4-rt late, sorry about that.13:27
pave14.19-rt: I asked for an update, -rc1 is more than week old, so I expect we get that.13:27
jkiok, then there is hope :)13:28
*** iwamatsu__ <iwamatsu__!~iwamatsu_@2405:6581:5360:1800:e544:cfcc:e9e9:cb0c> has quit IRC (Quit: Client closed)13:28
pave16.1-rt: 6.1.119-rt is out. I gues I'll do matching -cip and then -cip-rt, unless someone objects.13:28
jkisounds good13:29
pave1(y)13:29
jkimoving on...13:30
jki513:30
jki413:30
jki313:30
jki213:30
jki113:30
jki#topic Kernel testing13:30
*** collab-meetbot changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)"13:30
patersoncHowdy. I've not been up to much this week I'm afraid13:30
pave1bbb is still acting up. I had to retry 6.11.X maybe 10 times.13:31
patersoncstill... Sorry Pavel13:31
*** iwamatsu__ <iwamatsu__!~iwamatsu_@2405:6581:5360:1800:e544:cfcc:e9e9:cb0c> has joined #cip13:33
jkimore testing topics?13:33
jkimaybe one from my side:13:34
jkithere are requests (one public) to add Raspberry Pi 4 to our target set, at least inofficially13:35
jkidoes anyone else see value or has concerns?13:35
pave1We should probably do that.13:35
pave1It is slightly unusual hardware, but it is cheap and common.13:36
jkiexactly13:36
jkishould work for 6.1, otherwise 6.12 for sure13:36
jkiupstream, obviously13:36
iwamatsu__+113:36
patersoncAny particular reason to use Pi4 over the other versions?13:36
jkiI will put that on the agenda for next TSC13:37
jkiRPi4 is legacy13:37
pave1RPi3 is too old, RPi5 is too new :-).13:37
jkiRPi5 is - to my knowledge - not yet sufficently upstream13:37
patersoncFair doos :)13:37
jkiperfect13:38
jkianything else?13:38
jki513:38
jki413:38
jki313:38
jki213:38
jki113:38
*** monstr <monstr!~monstr@nat-35.starnet.cz> has joined #cip13:38
jki#topic AOB13:38
*** collab-meetbot changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)"13:38
jkiother topics for today?13:39
jki513:39
jki413:39
jki313:39
jki213:39
jki113:39
jki#endmeeting13:39
collab-meetbotMeeting ended Thu Dec  5 13:39:58 2024 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:39
collab-meetbotMinutes:        http://ircbot.wl.linuxfoundation.org/meetings/cip/2024/12/cip.2024-12-05-13.01.html13:39
collab-meetbotMinutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2024/12/cip.2024-12-05-13.01.txt13:39
collab-meetbotLog:            http://ircbot.wl.linuxfoundation.org/meetings/cip/2024/12/cip.2024-12-05-13.01.log.html13:39
*** 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:39
jkithank you!13:40
pave1Thank you!13:40
uli_thanks13:40
masamithank you13:40
iwamatsu__thank you13:40
*** iwamatsu__ <iwamatsu__!~iwamatsu_@2405:6581:5360:1800:e544:cfcc:e9e9:cb0c> has quit IRC (Quit: Client closed)13:40
*** masami <masami!~masami@FL1-118-111-145-206.tky.mesh.ad.jp> has quit IRC (Quit: Leaving)13:40
*** jki <jki!~jki@195.145.170.171> has quit IRC (Ping timeout: 252 seconds)14:20
*** jki <jki!~jki@195.145.170.145> has joined #cip14:33
*** monstr <monstr!~monstr@nat-35.starnet.cz> has quit IRC (Remote host closed the connection)15:27
*** jki <jki!~jki@195.145.170.145> has quit IRC (Ping timeout: 252 seconds)16:27
*** prabhakalad <prabhakalad!~prabhakar@165.225.197.26> has quit IRC (Ping timeout: 246 seconds)16:38
*** prabhakalad <prabhakalad!~prabhakar@165.225.17.42> has joined #cip16:39
*** prabhakalad <prabhakalad!~prabhakar@165.225.17.42> has quit IRC (Ping timeout: 265 seconds)21:31
*** prabhakalad <prabhakalad!~prabhakar@165.225.17.40> has joined #cip21:31
*** prabhakalad <prabhakalad!~prabhakar@165.225.17.40> has quit IRC (Ping timeout: 248 seconds)21:39
« Wednesday, 2024-12-04 Index Friday, 2024-12-06 »

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