| *** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has joined #cip | 05:50 | |
| *** zar_ <zar_!~quassel@mail.nazaryev.ru> has quit IRC (Quit: No Ping reply in 180 seconds.) | 06:41 | |
| *** zar <zar!~quassel@mail.nazaryev.ru> has joined #cip | 06:42 | |
| *** zar <zar!~quassel@mail.nazaryev.ru> has quit IRC (Quit: No Ping reply in 180 seconds.) | 06:56 | |
| *** zar <zar!~quassel@mail.nazaryev.ru> has joined #cip | 06:57 | |
| *** monstr <monstr!~monstr@nat-35.starnet.cz> has joined #cip | 07:24 | |
| *** uli <uli!~uli@2001:4091:a246:805f:9f61:b40d:cca3:5eb> has joined #cip | 10:35 | |
| *** hiromotai <hiromotai!~hiromotai@240f:75:5bc9:1:898b:9e55:6e99:dff0> has joined #cip | 11:19 | |
| *** jki <jki!~jki@ipservice-092-210-001-046.092.210.pools.vodafone-ip.de> has joined #cip | 11:48 | |
| *** masami <masami!~masami@FL1-125-198-44-131.tky.mesh.ad.jp> has joined #cip | 11:52 | |
| jki | hi everyone | 12:00 |
|---|---|---|
| uli | hello | 12:00 |
| masami | hi | 12:00 |
| hiromotai | hi | 12:00 |
| patersonc[m] | hi | 12:01 |
| alicefm | Hi | 12:01 |
| iwamatsu | hi | 12:01 |
| jki | #startmeeting CIP IRC weekly meeting | 12:02 |
| collab-meetbot` | Meeting started Thu Apr 20 12:02:32 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-meetbot` | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 12:02 |
| collab-meetbot` | The 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 review | 12:02 |
| *** collab-meetbot` changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)" | 12:02 | |
| jki | 1. create kernelci pipeline for buster images (arisut) | 12:02 |
| jki | arisut: ? | 12:03 |
| arisut | just talked with kernelci about the project of using debian style for testing CIP kernel on KernelCI | 12:03 |
| arisut | just recently | 12:04 |
| jki | ok, so "ongoing" | 12:04 |
| arisut | yes | 12:04 |
| jki | good | 12:04 |
| jki | other AIs? | 12:04 |
| arisut | not from me | 12:05 |
| jki | then let's move on in | 12:05 |
| jki | 1 | 12:05 |
| jki | 3 | 12:05 |
| jki | 2 | 12:05 |
| jki | 1 | 12:05 |
| jki | #topic Kernel maintenance updates | 12:05 |
| *** collab-meetbot` changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)" | 12:05 | |
| masami | This week reported 8 new CVEs and 2 updated CVEs. | 12:06 |
| uli | reviewing 5.10.178 | 12:06 |
| iwamatsu | I reviewed 5.10.178. | 12:06 |
| jki | anything else? | 12:08 |
| jki | 3 | 12:09 |
| jki | 2 | 12:09 |
| jki | 1 | 12:09 |
| jki | #topic Kernel release status | 12:09 |
| *** collab-meetbot` changes topic to "Kernel release status (Meeting topic: CIP IRC weekly meeting)" | 12:09 | |
| jki | -4.4 | 12:09 |
| uli | on track | 12:09 |
| jki | -4.19 | 12:09 |
| iwamatsu | RT has not followed LTS... | 12:09 |
| jki | but we would have to release now? | 12:10 |
| jki | strictly spoken, no | 12:11 |
| jki | 0.5 per month, last 4.19-rt was end of March | 12:11 |
| jki | ok, then | 12:12 |
| jki | -5.10 | 12:12 |
| iwamatsu | same 4.19. | 12:12 |
| iwamatsu | s/same/same as / | 12:12 |
| iwamatsu | If RT is not released this week or next week, it will be difficult to release cip-rt. | 12:12 |
| jki | here we should do once per month, thus here we are affected then | 12:12 |
| jki | understood | 12:13 |
| jki | is the same one doing 4.19-RT and 5.10-RT upstream? | 12:13 |
| *** fbezdeka <fbezdeka!~flo@2a02:810d:8780:7fc:b0:fb65:f05a:7717> has joined #cip | 12:14 | |
| jki | just checked - no | 12:14 |
| jki | 4.19 is Daniel, 5.10 is Luis | 12:14 |
| iwamatsu | yes, right | 12:15 |
| *** pave1 <pave1!~pavel@jabberwock.ucw.cz> has joined #cip | 12:16 | |
| jki | sorry, SIGREALLIFE | 12:17 |
| iwamatsu | and Daniel has been release 4.19.280-rt123-rc1. he is updating. | 12:17 |
| iwamatsu | hi, pavel | 12:17 |
| pave1 | Hi! | 12:17 |
| pave1 | Sorry for the delay. I was reviewing 5.10.178. | 12:18 |
| jki | back | 12:18 |
| jki | ok, then we are done on this | 12:19 |
| jki | #topic Kernel testing | 12:19 |
| *** collab-meetbot` changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)" | 12:19 | |
| patersonc[m] | I've nothing special to report this week. Just the usual maintenance & stable-rc result reporting | 12:21 |
| arisut | the isar-cip-core work for kernelci is ongoin | 12:21 |
| jki | what's the state now for 6.1-cip? | 12:22 |
| arisut | without branch there is no testing | 12:23 |
| jki | pavel: IIRC, you wanted to follow-up with next steps needed, right? | 12:23 |
| pave1 | Yes. | 12:23 |
| arisut | if we have a branch we can start testing it | 12:24 |
| pave1 | I guess we should announce that we now expect patches for 6.1 | 12:24 |
| pave1 | for any issue fixed in 5.10. | 12:24 |
| pave1 | Then we agree on starting point, branch off, and check for any patches in | 12:25 |
| patersonc[m] | Should we also ask the members if they have any particular configs they want built/tested/supported for 6.1? | 12:25 |
| jki | sure, configs will also be needed | 12:25 |
| pave1 | 5.10 but not in 6.1. | 12:25 |
| jki | at least forward ports of the qemu configs, to have a starter | 12:25 |
| pave1 | Yes, and configs. | 12:26 |
| pave1 | We can start from those used for testing 6.1-stable. | 12:26 |
| jki | when did we branch off 5.10-cip back then? | 12:27 |
| jki | after the first backport arrived or earlier? | 12:27 |
| patersonc[m] | We already have configs copied from 5.10 (which are used for stable testing). But maybe members what to review/refresh/add to those configs | 12:27 |
| jki | pavel: can you do the call-out on the list for the configs? | 12:28 |
| patersonc[m] | https://gitlab.com/cip-project/cip-kernel/cip-kernel-config/-/merge_requests/74/diffs?commit_id=570fa322ab77a7c6b5779a6a89bccbdb77573374 | 12:28 |
| arisut | configs will be added to cip-kernel-config repo? | 12:28 |
| jki | yep | 12:28 |
| arisut | ok | 12:28 |
| jki | we already have a 6.1-cip branch there | 12:29 |
| jki | in fact, we have many branches there, not only for cip kernel it seems | 12:29 |
| jki | "6.2.y-cip"? | 12:29 |
| patersonc[m] | Could be better named 6.2.y tbh | 12:30 |
| jki | would be less confusing, yes | 12:31 |
| jki | not sure if anything elsewhere (kernelci?) is relying on the current path names, though | 12:31 |
| patersonc[m] | It was agreed in the MR to keep it like that | 12:31 |
| patersonc[m] | We don't have any -rt configs for 6.1 yet btw, so we'd also need to get those added | 12:32 |
| patersonc[m] | Assuming we're doing a linux-6.1.y-cip-rt | 12:33 |
| iwamatsu | Yes, I've heard that 6.2 is removed from cip-kernel-config when it is removed from stable. | 12:33 |
| jki | I see no reason for not doing 6.1-rt | 12:33 |
| jki | ok - so, who is doing what next? | 12:35 |
| patersonc[m] | I'll add the pipeline for 6.1 cip testing | 12:35 |
| pave1 | I have sending that mail on my todo. | 12:35 |
| pave1 | Plus I have a script for for checking if we have all the patches from old kernel. | 12:36 |
| alicefm | I will follow/do the work on kernelci for 6.1 testing | 12:36 |
| jki | sounds like a good plan, thanks | 12:37 |
| jki | anything else on testing? | 12:37 |
| arisut | same | 12:37 |
| patersonc[m] | Not from me | 12:38 |
| jki | then let's move on... | 12:38 |
| jki | 3 | 12:38 |
| jki | 2 | 12:38 |
| jki | 1 | 12:38 |
| jki | #topic AOB | 12:38 |
| *** collab-meetbot` changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)" | 12:38 | |
| jki | anyone anything? | 12:39 |
| jki | btw, no reply from Greg so far after my last, longer answer | 12:40 |
| patersonc[m] | MR for the 6.1-cip CI pipeline is up: https://gitlab.com/cip-project/cip-testing/linux-cip-pipelines/-/merge_requests/38 | 12:40 |
| pave1 | jki -- at some point it will make sense to make our bosses to talk to his boss... | 12:40 |
| jki | does he have a boss? :) | 12:41 |
| patersonc[m] | ha | 12:41 |
| pave1 | Well, no, but someone pays him ... | 12:41 |
| jki | bosses need input on what we need and how much effort we estimate for that | 12:41 |
| jki | and I think we are still at that level | 12:41 |
| patersonc[m] | It's going to take more than CIP to change the LTS length policy. It'll need lots of companies to commit to supporting the efforts. | 12:42 |
| jki | sure | 12:42 |
| jki | that's why I was proposing to something like an LTS project - if that makes sense - under LF, with real, paying members | 12:42 |
| patersonc[m] | jki: Cunning | 12:43 |
| jki | or CIP would need a different budget and partially a different mission | 12:43 |
| pave1 | Taking over -lts from greg? | 12:43 |
| jki | CIP can do that as LTS is way broader in scope and we are still too small | 12:43 |
| jki | also, CIP would need members from - say - consumer domains if consumer .configs should come into scope | 12:44 |
| jki | or server .configs | 12:44 |
| jki | but Debian LTS was also asking a bit into that direction as they have members from domains not present in CIP | 12:45 |
| Dr_Who | we've been exploring doing LTSes that pickup where Greg leaves off. (We == Linaro) | 12:46 |
| Dr_Who | We already do quite a bit of kernel regression testing that like other projects report into Greg right now | 12:47 |
| pave1 | jki -- 'can not'? | 12:47 |
| jki | Dr_Who: not sure who you are ;), but Grant was indicating this as well to me | 12:47 |
| jki | pavel: I was thinking "cannot" and then wrinting "yes, we can" ;) | 12:48 |
| jki | but I meant "cannot" | 12:48 |
| Dr_Who | so Linaro is an open source engineering company that a number of companies came together and founded back in 2010 | 12:48 |
| pave1 | Thanks, makes sense. | 12:48 |
| Dr_Who | Arm, Google, Samsung, ST just to name a few | 12:48 |
| jki | all well known | 12:49 |
| jki | and Linaro did LTS work before, that's where KernelCI and LAVA had its roots to my understanding | 12:49 |
| Dr_Who | yup | 12:49 |
| pave1 | Well, if Linaro is willing to take over lts mainainance. that would certainly help us... | 12:50 |
| jki | and if that needs extra funding, we should make that formal, but it should be scoped on LTS | 12:50 |
| jki | I can imagine that this can attract more - CIP would surely consider supporting such an effort | 12:51 |
| jki | in any case, someone needs to take a lead here IMHO | 12:51 |
| Dr_Who | We're at the exploring phase, there seem to be a number of companies in the same situation, wanting an LTS - as you rightly point out, there is a cost associated with it, engineers like to get paid | 12:51 |
| pave1 | Perhaps Linaro should be included in that mailthread with Greg? | 12:53 |
| Dr_Who | certainly up for a chat | 12:53 |
| Dr_Who | interestingly I have talked to Greg about this a few weeks back | 12:53 |
| jki | Dr_Who: who should be on the table for such a chat? | 12:53 |
| Dr_Who | that'd be me tom.gall@linaro.org is my address | 12:54 |
| jki | Dr_Who: great, will follow-up with you | 12:55 |
| Dr_Who | thank you! | 12:55 |
| jki | good | 12:56 |
| jki | anything else for today? | 12:56 |
| jki | 3 | 12:57 |
| jki | 2 | 12:57 |
| jki | 1 | 12:57 |
| jki | #endmeeting | 12:57 |
| collab-meetbot` | Meeting ended Thu Apr 20 12:57:12 2023 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 12:57 |
| collab-meetbot` | Minutes: http://ircbot.wl.linuxfoundation.org/meetings/cip/2023/04/cip.2023-04-20-12.02.html | 12:57 |
| collab-meetbot` | Minutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2023/04/cip.2023-04-20-12.02.txt | 12:57 |
| collab-meetbot` | Log: http://ircbot.wl.linuxfoundation.org/meetings/cip/2023/04/cip.2023-04-20-12.02.log.html | 12:57 |
| *** 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:57 | |
| jki | thank you! have a nice day! | 12:57 |
| pave1 | Thank you! | 12:57 |
| uli | thanks | 12:57 |
| arisut | thanks | 12:57 |
| iwamatsu | thank you! | 12:57 |
| masami | thank you | 12:57 |
| patersonc[m] | ttfn | 12:57 |
| hiromotai | thanks | 12:58 |
| *** hiromotai <hiromotai!~hiromotai@240f:75:5bc9:1:898b:9e55:6e99:dff0> has quit IRC (Quit: Leaving) | 12:59 | |
| *** jki <jki!~jki@ipservice-092-210-001-046.092.210.pools.vodafone-ip.de> has quit IRC (Quit: Leaving) | 12:59 | |
| *** uli <uli!~uli@2001:4091:a246:805f:9f61:b40d:cca3:5eb> has left #cip (Leaving) | 13:04 | |
| *** monstr <monstr!~monstr@nat-35.starnet.cz> has quit IRC (Read error: Connection reset by peer) | 13:44 | |
| *** masami <masami!~masami@FL1-125-198-44-131.tky.mesh.ad.jp> has quit IRC (Quit: Leaving) | 13:44 | |
| *** monstr <monstr!~monstr@nat-35.starnet.cz> has joined #cip | 13:44 | |
| *** monstr <monstr!~monstr@nat-35.starnet.cz> has quit IRC (Remote host closed the connection) | 14:30 | |
| *** fbezdeka <fbezdeka!~flo@2a02:810d:8780:7fc:b0:fb65:f05a:7717> has left #cip | 15:24 | |
| *** Dr_Who <Dr_Who!~tgall@70.35.96.200> has quit IRC (Quit: ZZZzzz…) | 17:28 | |
| *** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC (Quit: Client closed) | 18:36 | |
| *** Dr_Who <Dr_Who!~tgall@2600:1014:b060:e711:6d0e:d23f:eda3:ed3e> has joined #cip | 19:55 | |
| *** Dr_Who <Dr_Who!~tgall@2600:1014:b060:e711:6d0e:d23f:eda3:ed3e> has quit IRC (Quit: ZZZzzz…) | 21:24 | |
| *** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has quit IRC (Ping timeout: 246 seconds) | 21:44 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!