| *** hiromotai <hiromotai!~Thunderbi@240f:75:5bc9:1:dc4c:91f:bc5c:4e9c> has quit IRC (Quit: hiromotai) | 01:19 | |
| *** monstr <monstr!~monstr@nat-35.starnet.cz> has joined #cip | 06:48 | |
| *** monstr <monstr!~monstr@nat-35.starnet.cz> has quit IRC (Read error: Connection reset by peer) | 08:16 | |
| *** monstr <monstr!~monstr@nat-35.starnet.cz> has joined #cip | 08:32 | |
| *** monstr <monstr!~monstr@nat-35.starnet.cz> has quit IRC (Ping timeout: 252 seconds) | 08:47 | |
| *** prabhakalad <prabhakalad!~prabhakar@165.225.197.26> has joined #cip | 09:45 | |
| *** masami <masami!~masami@FL1-118-111-145-206.tky.mesh.ad.jp> has joined #cip | 12:39 | |
| *** iwamatsu__ <iwamatsu__!~iwamatsu_@2405:6581:5360:1800:5959:4f95:68a7:5d32> has joined #cip | 12:59 | |
| *** jki <jki!~jki@62.156.206.47> has joined #cip | 13:00 | |
| jki | happy new year, everyone :) | 13:00 |
|---|---|---|
| uli_ | happy new year! | 13:01 |
| pave1 | Happy New Year! | 13:01 |
| iwamatsu__ | happy new year ! | 13:01 |
| masami | happy new year! | 13:01 |
| arisut | happy new year | 13:01 |
| jki | ok, let's go | 13:03 |
| jki | #startmeeting CIP IRC weekly meeting | 13:03 |
| collab-meetbot` | Meeting started Thu Jan 9 13:03:34 2025 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 review | 13: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 |
| jki | basically done, will trigger the publication soon | 13:04 |
| jki | were there other AIs in the past weeks? | 13:04 |
| jki | 5 | 13:05 |
| jki | 4 | 13:05 |
| jki | 3 | 13:05 |
| jki | 2 | 13:05 |
| jki | 1 | 13:05 |
| jki | #topic Kernel maintenance updates | 13:05 |
| *** collab-meetbot` changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)" | 13:05 | |
| masami | This week reported 32 new CVEs and 5 updated CVEs. | 13:05 |
| uli_ | no updates from me | 13:05 |
| pave1 | I was reviewing 6.1.123 and .124 | 13:06 |
| iwamatsu__ | I did not review this week. | 13:06 |
| jki | anything else? | 13:07 |
| jki | 5 | 13:08 |
| jki | 4 | 13:08 |
| jki | 3 | 13:08 |
| jki | 2 | 13:08 |
| jki | 1 | 13:08 |
| jki | #topic Kernel release status | 13:08 |
| *** collab-meetbot` changes topic to "Kernel release status (Meeting topic: CIP IRC weekly meeting)" | 13:08 | |
| jki | 4.19 is late | 13:08 |
| jki | would be our first own release, right? any blockers? | 13:09 |
| iwamatsu__ | We need to decide how often to update 4.19 and change the script. | 13:09 |
| pave1 | That's where the self-mainainance fun starts. | 13:10 |
| jki | 4.19 is once per month already | 13:10 |
| jki | just like 4.4 | 13:10 |
| iwamatsu__ | aha, OK | 13:11 |
| pave1 | I believe we should do full release based on last 4.19 and then start preparing next one. | 13:11 |
| jki | what did we do for 4.4 back then? | 13:11 |
| jki | and roles will remain the same for 4.19? | 13:14 |
| iwamatsu__ | We checked the patches to be included in 4.9 and applied the necessary patches. 4.19 should do the same. | 13:14 |
| pave1 | Dunno. I guess that depends if Iwamatsu-san has enough time for that? | 13:15 |
| iwamatsu__ | Just as Uli is in charge of 4.4, it may be necessary to assign 4.19 as well... | 13:16 |
| uli_ | i wonder how much synergy there is between 4.4 and 4.19 | 13:17 |
| uli_ | i suppose 4.19 will act as a filter for the patch torrent from stable | 13:17 |
| iwamatsu__ | Hmmm, I will have to check with my boss (Yoshi). | 13:17 |
| pave1 | uli: yes. 4.4 should be easier to maintain from that point. | 13:17 |
| jki | please clarify, ideally before next TSC so that we can report or start discussing alternatives | 13:18 |
| uli_ | i have the process of ingesting stable patches dialed in, i wouldn't mind taking on 4.19. | 13:18 |
| pave1 | uli: if it does not apply to 4.19 and is not critical, it will be filtered out. | 13:18 |
| pave1 | I can also help. | 13:18 |
| iwamatsu__ | Me too. | 13:19 |
| jki | ok, then the next 4.19 will be from uli | 13:20 |
| uli_ | maybe iwamatsu__ can do the last 4.19 release, following the existing process | 13:20 |
| uli_ | then i'll take over | 13:20 |
| pave1 | I guess that would be better. | 13:21 |
| jki | iwamatsu__: fine for you as well? | 13:21 |
| iwamatsu__ | OK, I will release -cip with 4.19.325. | 13:22 |
| uli_ | thank you! | 13:23 |
| jki | perfect, thanks! | 13:23 |
| jki | then let's move on | 13:24 |
| jki | 5 | 13:24 |
| jki | 4 | 13:24 |
| jki | 3 | 13:24 |
| jki | 2 | 13:24 |
| jki | 1 | 13:24 |
| jki | #topic Kernel testing | 13:24 |
| *** collab-meetbot` changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)" | 13:24 | |
| arisut | Currently adding a experimental option to kci-dev, `kci-dev results` | 13:24 |
| arisut | `kci-dev results` is able to check informations from the current folder and if we are into a git repository, like linux-cip, and give in formations about the current status on KernelCI | 13:25 |
| arisut | give informations about the current status on KernelCI of a linux repository folder | 13:26 |
| arisut | like on this examples https://gist.github.com/aliceinwire/c00388a318b84ce5fe4ba595623ccc5e | 13:26 |
| jki | btw, are our maintainers using kci-dev already? | 13:26 |
| arisut | I know internally KernelCI is using kci-dev daily | 13:27 |
| pave1 | Not yet, but its on my todo list. | 13:29 |
| arisut | not sure if some maintainer started already to use kci-dev, I know some maintainer is interested on kci-dev but I don't have yet detailed information about usage | 13:29 |
| arisut | on new year kci-dev 0.1.1 as been released | 13:30 |
| arisut | https://pypi.org/project/kci-dev/ | 13:30 |
| arisut | that is the first "stable" release | 13:30 |
| arisut | but the getting results directory from the git repository folder is still in development and I hope it will get in the next release | 13:31 |
| arisut | s/directory/directly/ | 13:31 |
| arisut | documentation is here https://docs.kernelci.org/kci-dev/ | 13:32 |
| jki | was just a reminder to us to check it out as well :) | 13:33 |
| arisut | yes would be nice to get some feedback | 13:34 |
| arisut | also from CIP | 13:34 |
| arisut | any question? | 13:35 |
| arisut | if there are no question I have another topic today | 13:36 |
| jki | I would have an unrelated problem report: | 13:37 |
| jki | "requests.exceptions.HTTPError: 502 Server Error: Bad Gateway for url: https://api.kernelci.org/upload" | 13:37 |
| jki | https://gitlab.com/cip-project/cip-core/isar-cip-core/-/jobs/8807718502 | 13:37 |
| jki | anyone any ideas? kernelci hick-up? | 13:38 |
| arisut | jki, yes | 13:38 |
| arisut | I was just talking today with denys about that problem | 13:38 |
| arisut | KernelCI is changing the storage api but the new api are still in progress | 13:38 |
| arisut | will fix when we have the new storage api | 13:39 |
| jki | is that going to happen in the next days, likely? | 13:39 |
| jki | pipeline is red now, and that comes with the risk of papering over real issues | 13:40 |
| arisut | I think it will take some week, we are in the process of deprecating legacy and making the new api | 13:40 |
| jki | then we should probably disable the futile deployment attempts for now | 13:41 |
| jki | will write a patch | 13:41 |
| arisut | ok | 13:41 |
| arisut | my other topic is about lava-docker. | 13:41 |
| arisut | anyone using lava-docker? | 13:42 |
| arisut | lava-docker as been recently moved to baylibre | 13:42 |
| jki | I was just recommending it internally as quick-start tool | 13:43 |
| jki | what does that mean for it? | 13:43 |
| arisut | As been just moved, and I'm not aware of the maintaining process of baylibre | 13:44 |
| arisut | montjoie, the creator and co-maintainer will keep maintaining lava-docker | 13:44 |
| arisut | on the baylibre github account | 13:45 |
| arisut | but I don't have any more detail on this topic | 13:45 |
| jki | will the URL change or be forwarded? | 13:46 |
| jki | I think we have a reference in some project to the original repo | 13:46 |
| arisut | the idea was at first that lava gitlab organization would take lava-docker | 13:46 |
| arisut | https://docs.kernelci.org/org/maintainers/#lava-docker-interim | 13:47 |
| jki | hmm, it comes from github, that prevents easy forwarding | 13:48 |
| jki | anyway, we will see | 13:48 |
| jki | thanks for the heads-up | 13:48 |
| arisut | but now is on baylibre that is on github | 13:48 |
| arisut | https://github.com/BayLibre/lava-docker | 13:48 |
| arisut | not sure what have happened since that email | 13:49 |
| jki | and it is here: https://github.com/kernelci/lava-docker | 13:49 |
| jki | confusing | 13:49 |
| arisut | yes | 13:49 |
| jki | hope they will sort that out properly | 13:50 |
| arisut | hope too | 13:50 |
| jki | ok, other testing topics? | 13:51 |
| arisut | no that was the last one from me | 13:51 |
| jki | good - anyone else? | 13:51 |
| jki | 5 | 13:52 |
| jki | 4 | 13:52 |
| jki | 3 | 13:52 |
| jki | 2 | 13:52 |
| jki | 1 | 13:52 |
| jki | #topic AOB | 13:52 |
| *** collab-meetbot` changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)" | 13:52 | |
| jki | anything else for today? | 13:52 |
| jki | 5 | 13:53 |
| jki | 4 | 13:53 |
| jki | 3 | 13:53 |
| jki | 2 | 13:53 |
| jki | 1 | 13:53 |
| jki | #endmeeting | 13:53 |
| collab-meetbot` | Meeting ended Thu Jan 9 13:53:41 2025 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 13:53 |
| collab-meetbot` | Minutes: http://ircbot.wl.linuxfoundation.org/meetings/cip/2025/01/cip.2025-01-09-13.03.html | 13:53 |
| collab-meetbot` | Minutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2025/01/cip.2025-01-09-13.03.txt | 13:53 |
| collab-meetbot` | Log: http://ircbot.wl.linuxfoundation.org/meetings/cip/2025/01/cip.2025-01-09-13.03.log.html | 13:53 |
| *** 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:53 | |
| jki | thanks all | 13:53 |
| arisut | thx | 13:53 |
| uli_ | thanks! | 13:53 |
| iwamatsu__ | Thank you | 13:53 |
| masami | thank you | 13:53 |
| pave1 | thank you! | 13:53 |
| *** masami <masami!~masami@FL1-118-111-145-206.tky.mesh.ad.jp> has quit IRC (Quit: Leaving) | 13:54 | |
| *** iwamatsu__ <iwamatsu__!~iwamatsu_@2405:6581:5360:1800:5959:4f95:68a7:5d32> has quit IRC (Quit: Client closed) | 14:26 | |
| *** shoragan <shoragan!~shoragan@user/shoragan> has quit IRC (Ping timeout: 252 seconds) | 14:46 | |
| *** shoragan <shoragan!~shoragan@user/shoragan> has joined #cip | 15:40 | |
| *** jki <jki!~jki@62.156.206.47> has quit IRC (Quit: Leaving) | 15:49 | |
| *** prabhakalad <prabhakalad!~prabhakar@165.225.197.26> has quit IRC (Ping timeout: 252 seconds) | 20:36 | |
| *** prabhakalad <prabhakalad!~prabhakar@147.161.236.127> has joined #cip | 20:37 | |
| *** prabhakalad <prabhakalad!~prabhakar@147.161.236.127> has quit IRC (Ping timeout: 272 seconds) | 21:47 | |
| *** prabhakalad <prabhakalad!~prabhakar@165.225.197.26> has joined #cip | 21:48 | |
| *** Dr_Who <Dr_Who!~tgall@70.35.96.200> has quit IRC (Read error: Connection reset by peer) | 22:24 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!