Thursday, 2025-02-27

« Wednesday, 2025-02-26 Index Friday, 2025-02-28 »
*** hiromotai <hiromotai!~Thunderbi@220x151x27x42.ap220.ftth.ucom.ne.jp> has joined #cip02:36
*** hiromotai <hiromotai!~Thunderbi@220x151x27x42.ap220.ftth.ucom.ne.jp> has quit IRC (Ping timeout: 265 seconds)03:26
*** hiromotai <hiromotai!~Thunderbi@220x151x27x42.ap220.ftth.ucom.ne.jp> has joined #cip04:27
*** monstr <monstr!~monstr@nat-35.starnet.cz> has joined #cip06:46
*** monstr <monstr!~monstr@nat-35.starnet.cz> has quit IRC (Ping timeout: 252 seconds)06:57
*** hiromotai <hiromotai!~Thunderbi@220x151x27x42.ap220.ftth.ucom.ne.jp> has quit IRC (Ping timeout: 260 seconds)07:47
*** prabhakalad <prabhakalad!~prabhakar@165.225.17.42> has quit IRC (Quit: Konversation terminated!)08:42
*** prabhakalad <prabhakalad!~prabhakar@165.225.17.42> has joined #cip08:42
*** monstr <monstr!~monstr@nat-35.starnet.cz> has joined #cip12:09
*** arisut <arisut!~none@gentoo/developer/alicef> has quit IRC (Quit: install gentoo)12:35
*** arisut <arisut!~none@gentoo/developer/alicef> has joined #cip12:35
*** ChanServ sets mode: +o arisut12:35
*** arisut <arisut!~none@gentoo/developer/alicef> has quit IRC (Client Quit)12:37
*** arisut <arisut!~none@gentoo/developer/alicef> has joined #cip12:38
*** ChanServ sets mode: +o arisut12:38
*** arisut <arisut!~none@gentoo/developer/alicef> has quit IRC (Remote host closed the connection)12:38
*** arisut <arisut!~none@gentoo/developer/alicef> has joined #cip12:43
*** ChanServ sets mode: +o arisut12:43
*** masami <masami!~masami@FL1-118-111-145-206.tky.mesh.ad.jp> has joined #cip12:54
*** jki <jki!~jki@195.145.170.177> has joined #cip12:56
arisuthello12:59
pave1Hi!12:59
uli_hello13:00
masamihello13:00
jkihi!13:00
*** iwamatsu__ <iwamatsu__!~iwamatsu_@2405:6581:5360:1800:458e:c5f7:a06f:8fa4> has joined #cip13:00
jkiok, let's fly13:00
jki#startmeeting CIP IRC weekly meeting13:00
collab-meetbotMeeting started Thu Feb 27 13:00:59 2025 UTC and is due to finish in 60 minutes.  The chair is jki. Information about MeetBot at http://wiki.debian.org/MeetBot.13:00
collab-meetbotUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:00
collab-meetbotThe meeting name has been set to 'cip_irc_weekly_meeting'13:00
*** collab-meetbot changes topic to " (Meeting topic: CIP IRC weekly meeting)"13:00
jki#topic AI review13:01
*** collab-meetbot changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)"13:01
iwamatsu__hello13:01
jkinone recorded13:01
jki513:01
jki413:01
jki313:01
jki213:01
jki113:01
jki#topic Kernel maintenance updates13:01
*** collab-meetbot changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)"13:01
pave1I'm doing reviews, 6.1.129, .130.13:01
uli_i'm working on the next 4.19 release13:01
masamiThis week reported 866 new CVEs and 14 updated CVEs.13:01
jki866 - a serious amount again :)13:02
pave16.1.129 was huge release. And basically stable patch is copy-pasted into CVE.13:02
iwamatsu__I reviewed 6.1.129, and I am reviewing  6.1.13013:02
masamimore than 800 CVEs were published in a one day13:03
pave1(.129 is huge, because it corresponds to -rc1 from mainline).13:03
jkithere is a new 5.10-rc in the make that should contain at least of the RT fixes we identified13:06
jkiwill likely be 4.19 and older relevant, but still haven't checked13:07
Asmadeus(Most of the CVEs that were published are for 2022, so likely not relevant)13:07
pave1Next -cip-rt is scheduled to Mar 20th.13:07
pave1Do you want earlier one if time permits?13:07
jkilet's wait for the regular stable-rt first13:08
pave1Yes, I'm not doing anything -stable-rt is not doing.13:08
pave1But I can do one "soon" after -stable-rt is released...13:08
pave1...or I can keep normal schedule.13:08
jkiit's not a critical security fix, so no hurry from that perspective13:10
pave1Ok.13:11
jkiconcrete deployment with the exact some issue are also not known to me13:11
jkiwe likely only saw it on 6.1 in the wild, even if 5.10 is equally affected13:11
jkiok - other maintenance topics?13:12
jki513:12
jki413:12
pave1(You can also have earlier 6.113:12
pave1if it helps and I have corresponding -stable-rt :-) )13:12
arisutI wanted to ask about annotated tags, on release. I see jki mail acking the issue but I didn't see any plan for the future13:12
jkiuli_: did you address the issue already?13:13
jki...for the next releases?13:13
uli_no, not yet13:13
jkiat all: please align your release toolings!13:13
jkiwe also have slightly different release announcement emails13:14
jkinot critical but also not really nice13:14
jkiand different workflows will only generate different mistakes on rainy days ;)13:14
arisutwe are diverting from upstream release tags without annotated tags13:15
arisuttags style13:15
pave1and slightly lower chance of one bug affecting everyone :-). This is manual process, announcement mails are hand-crafted :-)13:15
jkiand both is bad13:15
jkiuse a script that generate both, just using personal data/keys as parameters13:16
jkiand share that for review/improvements13:16
pave1Trouble is ... this is all over the place.13:17
arisuteach release commit should be signed for verify the origin13:17
pave1So you have buch of git commands, ok.13:17
pave1But then you submit for testing, and have to check with web browser how that went.13:17
jkicheck isar-cip-core/scripts/make_release for a starter - obviously, the kernel will need more13:17
arisutsuch release scripts should be on gitlab if they are not there yet13:17
jki+113:18
pave1And then you push changes, and again, the result is in web browser after random delay.13:18
iwamatsu__I can share my script too.13:18
pave1I send announcement emails using mutt. I don't know how to script that, really, either.13:18
pave1Plus scripts are significantly differnt for -cip, -cip-rt, and self-maintained -cip-rt.13:19
pave1So it is like 3 commands, then manual action, then other 3 commands.13:20
arisutpave1, you can use sendmail13:20
pave1arisut: Not in todays environment.13:20
arisutI'm using sendmail on Gentoo kernel announcement13:21
pave1arisut: Would not work here, would not work in most of the places.13:21
arisutpave1, https://stackoverflow.com/questions/57410259/how-to-send-an-email-using-sendmail-command-in-linux#5741183813:22
arisutthere is also example with mutt13:23
arisutand mail13:23
pave1arisut: I know how email worked in 1995, thank you. It does not work like that today.13:23
jkiok, one step after the other: maybe those for who scripting seem to work already can share that13:24
arisutyou could use mailcow for managing your own mail service13:25
jkiand then look at those workflows together, and if there remains one or two offs, it would still be progress13:25
pave1arisut: I'd have to deal with SPF and various such stuff. Plus that's not what my company wants me to use.13:26
arisutjki, +113:26
iwamatsu__+113:27
uli_i would appreciate a script that just writes something to stdout13:28
uli_then i can copy-and-paste it in any way i want :)13:28
jkiperfect :)13:30
uli_(and i will keep in mind to use annotated tags for the next release)13:30
jkithen let's sync again next week13:30
jkianything else?13:30
jki513:30
jki413:30
jki313:31
jki213:31
jki113:31
jki#topic Kernel release status13:31
*** collab-meetbot changes topic to "Kernel release status (Meeting topic: CIP IRC weekly meeting)"13:31
jkiall LEDs are green today13:31
jkianything to add?13:31
jki513:32
jki413:32
jki313:32
jki213:32
jki113:32
jki#topic Kernel testing13:32
*** collab-meetbot changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)"13:32
patersoncNo exciting updates from me this week13:32
arisutI'm sent a PR for adding CIP stable kernel to kernelci13:32
arisuthttps://github.com/kernelci/kernelci-pipeline/pull/105313:33
arisutneed your approval patersonc13:33
patersoncThanks13:33
arisutthan I started writing what we are missing https://gist.github.com/aliceinwire/e3c180d0ef8e442c530bfd8e4ddead5313:33
patersoncGreat13:34
arisutpatersonc, if you have something to add just fork the gist and update it13:34
patersoncWill do13:35
arisutthanks13:35
arisutthe next step I think would be to make the pipeline use the CIP gitlab configurations13:36
patersoncYes13:36
jkiwhat about https://lore.kernel.org/cip-dev/OSCPR01MB1483816E3365201CB54911E2FC2C22@OSCPR01MB14838.jpnprd01.prod.outlook.com/T/#u BTW?13:38
iwamatsu__We need to update these images, I think.13:39
patersoncYes I saw that. Iwamatsu-san was going to look into updating the LTP rootfs we're using - however if we move to KernelCI setup then it's something KernelCI already does.13:40
patersoncAlthough if we want to use CIP core images then I guess we'll have to bake it into the CIP core image creation13:40
jkiI think the LSP in isar-cip-core is fairly recent13:40
patersoncOkay13:41
jkiltp13:41
jkiltp-full_20240930.bb13:41
jkinot even half a year old ;)13:41
patersonc:)13:41
jkibut, yet, maintenance on that thing is needed as well from time to time13:41
iwamatsu__OK, I take a look that.13:42
jkiTIA!13:42
jkisee also https://lore.kernel.org/cip-dev/20250203115321.3589084-1-Sai.Sathujoda@toshiba-tsip.com/T/#t for more background on LTP packaging and updating13:43
jkigood13:44
jkiother testing topics?13:44
jki513:44
jki413:44
jki313:44
jki213:44
jki113:45
jki#topic AOB13:45
*** collab-meetbot changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)"13:45
jkianything else for today?13:46
*** iwamatsu__ <iwamatsu__!~iwamatsu_@2405:6581:5360:1800:458e:c5f7:a06f:8fa4> has quit IRC (Quit: Client closed)13:46
jki513:46
jki413:46
jki313:46
jki213:46
jki113:46
jki#endmeeting13:46
collab-meetbotMeeting ended Thu Feb 27 13:46:33 2025 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:46
collab-meetbotMinutes:        http://ircbot.wl.linuxfoundation.org/meetings/cip/2025/02/cip.2025-02-27-13.00.html13:46
collab-meetbotMinutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2025/02/cip.2025-02-27-13.00.txt13:46
collab-meetbotLog:            http://ircbot.wl.linuxfoundation.org/meetings/cip/2025/02/cip.2025-02-27-13.00.log.html13:46
*** 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:46
jkithanks all!13:46
pave1Thank you!13:46
arisutthanks13:46
masamithank you13:46
*** masami <masami!~masami@FL1-118-111-145-206.tky.mesh.ad.jp> has quit IRC (Quit: Leaving)13:46
uli_thanks13:46
*** iwamatsu__ <iwamatsu__!~iwamatsu_@2405:6581:5360:1800:458e:c5f7:a06f:8fa4> has joined #cip13:47
patersoncCheers13:47
*** iwamatsu__ <iwamatsu__!~iwamatsu_@2405:6581:5360:1800:458e:c5f7:a06f:8fa4> has quit IRC (Client Quit)13:49
*** jki <jki!~jki@195.145.170.177> has quit IRC (Quit: Leaving)13:52
*** monstr <monstr!~monstr@nat-35.starnet.cz> has quit IRC (Remote host closed the connection)18:25
*** monstr <monstr!~monstr@nat-35.starnet.cz> has joined #cip18:28
*** monstr <monstr!~monstr@nat-35.starnet.cz> has quit IRC (Remote host closed the connection)18:31
« Wednesday, 2025-02-26 Index Friday, 2025-02-28 »

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