| *** tmerciai <tmerciai!~tmerciai3@net-188-217-51-51.cust.vodafonedsl.it> has joined #cip | 05:19 | |
| *** monstr <monstr!~monstr@nat-35.starnet.cz> has joined #cip | 05:50 | |
| *** monstr <monstr!~monstr@nat-35.starnet.cz> has quit IRC (Ping timeout: 252 seconds) | 05:54 | |
| *** monstr <monstr!~monstr@nat-35.starnet.cz> has joined #cip | 06:24 | |
| *** iwamatsu__ <iwamatsu__!~iwamatsu_@ae053227.dynamic.ppp.asahi-net.or.jp> has joined #cip | 12:51 | |
| *** masami <masami!~masami@FL1-122-134-103-12.tky.mesh.ad.jp> has joined #cip | 12:59 | |
| *** jki <jki!~jki@195.145.170.179> has joined #cip | 13:01 | |
| jki | hi all | 13:01 |
|---|---|---|
| pave1 | Hi! | 13:01 |
| uli_ | hello | 13:01 |
| arisut | hi | 13:01 |
| masami | hello | 13:01 |
| iwamatsu__ | hello | 13:01 |
| patersonc | Hey | 13:02 |
| jki | ok, let's start | 13:02 |
| jki | #startmeeting CIP IRC weekly meeting | 13:02 |
| collab-meetbot | Meeting started Thu Jun 5 13:02:32 2025 UTC and is due to finish in 60 minutes. The chair is jki. Information about MeetBot at http://wiki.debian.org/MeetBot. | 13:02 |
| collab-meetbot | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 13:02 |
| collab-meetbot | The meeting name has been set to 'cip_irc_weekly_meeting' | 13:02 |
| *** collab-meetbot changes topic to " (Meeting topic: CIP IRC weekly meeting)" | 13:02 | |
| jki | #topic AI review | 13:02 |
| *** collab-meetbot changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)" | 13:02 | |
| jki | I have none recorded | 13:02 |
| jki | anything to add? | 13:03 |
| jki | 5 | 13:03 |
| jki | 4 | 13:03 |
| jki | 3 | 13:03 |
| pave1 | Nothing from last time. | 13:03 |
| jki | 2 | 13:03 |
| jki | 1 | 13:03 |
| jki | #topic Kernel maintenance updates | 13:03 |
| *** collab-meetbot changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)" | 13:03 | |
| uli_ | i'm working on 4.19 | 13:03 |
| masami | This week reported 7 new CVEs and 31 updated CVEs. | 13:03 |
| pave1 | I was reviewing 6.12.31 and .32 | 13:04 |
| iwamatsu__ | I reviewed 6.12.31 and 32. And I released 6.12.y-cip. | 13:04 |
| pave1 | There's series of unix domain socket changes queued for 6.1.X. | 13:04 |
| pave1 | Apparently, garbage collection is hard. | 13:05 |
| pave1 | If someone uses them heavily, it may be worth testing extra hard. | 13:05 |
| jki | ok - anything to add? | 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 | all kernels are on track right now | 13:08 |
| jki | any problems ahead? | 13:08 |
| jki | 5 | 13:09 |
| jki | 4 | 13:09 |
| jki | 3 | 13:09 |
| jki | 2 | 13:09 |
| jki | 1 | 13:09 |
| jki | #topic Kernel testing | 13:09 |
| *** collab-meetbot changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)" | 13:09 | |
| patersonc | Nothing from me | 13:09 |
| arisut | sent kci-dev token | 13:09 |
| arisut | by email | 13:10 |
| patersonc | Thanks. I tested it and it works for me | 13:10 |
| arisut | nice | 13:10 |
| iwamatsu__ | alisut: I revieved. but I don't test yet. | 13:10 |
| pave1 | Attempted to test it. Did not get kci-dev to install on work machine. | 13:11 |
| arisut | pave1, did you get any error ? | 13:12 |
| pave1 | Lets talk after the meeting? | 13:12 |
| arisut | write the issue on the kci-dev github if you enconter any problem | 13:12 |
| arisut | sure | 13:12 |
| arisut | also there was a proposal from kernelci to testing this in the future https://github.com/kernelci/kernelci-pipeline/issues/1126 | 13:13 |
| arisut | .kernelci.yml file | 13:14 |
| arisut | should allow to manage kernelci pipeline from cip kernel repository | 13:14 |
| patersonc | Could be an easy way for us to control our pipelines | 13:14 |
| arisut | the issue talks about adding it in the kernel tree but after today discussion looks like that is possible to do it in different ways | 13:15 |
| arisut | like adding the file to a ad-hoc branch | 13:16 |
| arisut | today kernelci meeting discussion | 13:16 |
| jki | yeah, we should not carry (more) special CI files in-tree unless really unavoidable | 13:17 |
| pave1 | it really does not work well while bisecting, for example. | 13:17 |
| arisut | yes that was today discussion at KernelCI meeting | 13:17 |
| arisut | I agree on not carry special CI files in-tree unless unavoidable | 13:18 |
| jki | are there already discussions regarding onboarding of the new referencen board of TI for us? | 13:20 |
| arisut | ? | 13:20 |
| jki | the AM62x... we discussed at the TSC this week | 13:21 |
| jki | it was said it is already part of the kernelci farm | 13:21 |
| arisut | I'm not aware of such discussion | 13:22 |
| arisut | afair | 13:22 |
| jki | the ball is with TI, just curious | 13:22 |
| jki | but I assume we also want it then in the CIP farm, in addition to kernelci, or is that no longer needed? | 13:22 |
| arisut | there was no such discussion at today kernelci meeting | 13:23 |
| jki | i rather meant discussions in cip context | 13:23 |
| patersonc | I guess if they already have labs connected to KernelCI, once we've finished adding our confius etc. to KernelCI then we wouldn't need TI's boards specifically in CIP labs | 13:24 |
| patersonc | But that's only relevant for kernel testing | 13:24 |
| patersonc | For CIP core testing etc. we'd need a board in a CIP lab | 13:24 |
| jki | right, we could still benefit from it for core testing | 13:25 |
| jki | ok, anything else on testing? | 13:27 |
| jki | 5 | 13:28 |
| jki | 4 | 13:28 |
| jki | 3 | 13:28 |
| jki | 2 | 13:28 |
| jki | 1 | 13:28 |
| jki | #topic AOB | 13:28 |
| *** collab-meetbot changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)" | 13:28 | |
| jki | ppc32 - i just wanted to bring that topic up here as well, after only talking about it at the TSC meeting | 13:29 |
| jki | everyone followed that? or should I summarize first? | 13:29 |
| pave1 | Probably summarize. | 13:30 |
| jki | sure: we (Siemens) have a some products with PowerPC32 SoCs still under maintenance, and that long into the next decade, likely | 13:31 |
| jki | question was brought to me if the CIP kernel could help here as well | 13:31 |
| uli_ | what kernels are they running now? | 13:31 |
| jki | if there are others intested in putting this arch to rest in a similar way | 13:32 |
| jki | I don't have stats yet, but they were trying to stay very close to mainline so far | 13:32 |
| jki | and mainline did not discontinue ppc32 - yet | 13:32 |
| jki | yocto arlready did (that's what they use) | 13:32 |
| jki | but may accept the arch as tier 2 (no official support, no release blocker) still | 13:33 |
| jki | I mean, we are even getting m68k patches for CIP, don't we? :) | 13:33 |
| iwamatsu__ | Which series do we use? I understand there are many types of PPC32. | 13:33 |
| pave1 | jki: I guess adding ppc32 target to test farm would help a lot. | 13:34 |
| jki | also no data yet, I already asked the same | 13:34 |
| pave1 | jki: If it is broken, Siemens gets to fix it. After that, we can keep eye on that. | 13:34 |
| jki | that would already be a great starting point | 13:35 |
| iwamatsu__ | And what about rootfs and cross-tools? Debian is no longer supported. | 13:35 |
| pave1 | jki: I don't expect that to be too much work. | 13:35 |
| jki | given that it hard to impossible to get any EVMs for those SoCs anymore, duty would be on us anyway | 13:35 |
| jki | right | 13:35 |
| jki | my personal interest was just to find out if there aren't others with similar problems now | 13:36 |
| jki | and then the question is if we could already learn something from it thinking of the inevitible arm32 retirement one day... | 13:36 |
| pave1 | I guess I have two ppc32 machines here. One of them got indirect lightning strike tonight. | 13:36 |
| jki | ouch | 13:37 |
| pave1 | But they are called ADSL routers and I don't normally hack on them, so... :-) | 13:37 |
| jki | yes, this kind of losses will make maintenance also harder and harder over time :) | 13:37 |
| pave1 | (And I may have the architectures confused. You are talking ppc32, and this is likely mips.) | 13:37 |
| iwamatsu__ | I also have a ppc (mac mini). | 13:39 |
| iwamatsu__ | I noticed that ppc32 can be used for unstable. It is also built in debian-ports.;-) | 13:39 |
| jki | let me clarify what hardware would actually be helpful at all - and if we cannot help here | 13:40 |
| jki | but already qemu would be nice as basic test | 13:40 |
| pave1 | Yeah. If -cip had regression from -stable that would be visible on qemu, that would be kind of bad. | 13:41 |
| jki | it is already great news that you do not see general blockers | 13:41 |
| jki | anything else for today? | 13:43 |
| jki | 5 | 13:44 |
| jki | 4 | 13:44 |
| jki | 3 | 13:44 |
| jki | 2 | 13:44 |
| jki | 1 | 13:44 |
| jki | #endmeeting | 13:44 |
| collab-meetbot | Meeting ended Thu Jun 5 13:44:55 2025 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 13:44 |
| collab-meetbot | Minutes: http://ircbot.wl.linuxfoundation.org/meetings/cip/2025/06/cip.2025-06-05-13.02.html | 13:44 |
| collab-meetbot | Minutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2025/06/cip.2025-06-05-13.02.txt | 13:44 |
| collab-meetbot | Log: http://ircbot.wl.linuxfoundation.org/meetings/cip/2025/06/cip.2025-06-05-13.02.log.html | 13:44 |
| *** 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:44 | |
| jki | thanks! | 13:44 |
| uli_ | thanks | 13:45 |
| pave1 | Thank you! | 13:45 |
| iwamatsu__ | Thank you | 13:45 |
| masami | thank you | 13:45 |
| *** masami <masami!~masami@FL1-122-134-103-12.tky.mesh.ad.jp> has quit IRC (Quit: Leaving) | 13:45 | |
| pave1 | arisut: kci-dev | 13:45 |
| arisut | yes | 13:45 |
| pave1 | I don't have virtualenv here. | 13:46 |
| pave1 | I tried pip install kci-dev | 13:46 |
| pave1 | ERROR: Could not find a version that satisfies the requirement kci-dev | 13:46 |
| pave1 | ERROR: No matching distribution found for kci-dev | 13:46 |
| arisut | i see | 13:46 |
| arisut | you are on a old python version? | 13:46 |
| pave1 | python 3.9.2. Is that old? | 13:47 |
| arisut | yes we recommend at least python 3.10 | 13:48 |
| pave1 | Hmm. | 13:48 |
| arisut | is that some old ubuntu ? | 13:48 |
| pave1 | Old debian. | 13:48 |
| arisut | mm | 13:49 |
| pave1 | One more note I had: | 13:49 |
| pave1 | chmod 600 ~/.config/kci-dev/kci-dev.toml | 13:49 |
| pave1 | It contains secrets, so perhaps it should be 600 by default. | 13:49 |
| arisut | I see, thanks | 13:50 |
| pave1 | If I just clone kci-dev... what is the chance it will simply work on the old python? | 13:50 |
| arisut | gentoo is using it without virtualenv | 13:52 |
| arisut | but still I added requirement for python more than 3.10 | 13:53 |
| arisut | theoretically it should work with few version differences | 13:54 |
| arisut | but I have not tried it | 13:54 |
| arisut | so I have no idea | 13:54 |
| pave1 | Ok, perhaps I'll play with it. | 13:54 |
| pave1 | Thank you! | 13:54 |
| arisut | if you have any issue feel free to open issues on the repository | 13:55 |
| arisut | thanks you for trying it | 13:56 |
| pave1 | Ok, lets see how far do I get. | 13:57 |
| *** tmerciai <tmerciai!~tmerciai3@net-188-217-51-51.cust.vodafonedsl.it> has quit IRC (Remote host closed the connection) | 13:59 | |
| *** tmerciai <tmerciai!~tmerciai3@net-188-217-51-51.cust.vodafonedsl.it> has joined #cip | 13:59 | |
| pave1 | ~. | 14:03 |
| *** iwamatsu__ <iwamatsu__!~iwamatsu_@ae053227.dynamic.ppp.asahi-net.or.jp> has quit IRC (Quit: Client closed) | 14:05 | |
| *** tmerciai <tmerciai!~tmerciai3@net-188-217-51-51.cust.vodafonedsl.it> has quit IRC (Remote host closed the connection) | 14:51 | |
| *** jki <jki!~jki@195.145.170.179> has quit IRC (Remote host closed the connection) | 15:02 | |
| *** monstr <monstr!~monstr@nat-35.starnet.cz> has quit IRC (Remote host closed the connection) | 15:11 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!