*** vidda has joined #cip | 01:28 | |
*** moxavict2r has left #cip | 01:32 | |
*** moxavictor has joined #cip | 01:35 | |
*** szlin_ is now known as szlin | 01:48 | |
*** vidda has left #cip | 01:54 | |
*** patersonc has joined #cip | 07:02 | |
*** rajm has joined #cip | 07:30 | |
*** rajm has left #cip | 07:32 | |
*** kristerman has joined #cip | 07:50 | |
*** toscalix has joined #cip | 08:11 | |
*** takuo has joined #cip | 08:15 | |
*** takuo has quit IRC | 08:19 | |
*** CTtpollard is now known as tpollard | 08:50 | |
*** rajm has joined #cip | 09:14 | |
*** rajm has quit IRC | 09:24 | |
*** rajm has joined #cip | 09:24 | |
patersonc | rajm: This ethernet issue, is there a ticket for it? Or is it just mentioned in #167? | 10:15 |
---|---|---|
rajm | I think there's just the mention in #167 | 10:16 |
rajm | runs a BBB healthcheck with email to the list but the renesas one is failing this morning :-( | 10:16 |
patersonc | For the same reason? | 10:18 |
rajm | the same reason? bootloader-commands timed out after 294 seconds - this was after editing the HC to use the kernelci built stuff | 10:19 |
rajm | yesterday I was using a lava-tool submission but I doubt that would make any difference | 10:20 |
patersonc | rajm: Is it just the tftp command that times out? Or have you seen others do so as well? | 10:27 |
rajm | I think it's just that I'm retrying with the yocto built stuff so I can (hopefully!) get the board back online with the lava system | 10:28 |
patersonc | Okay. Are you re-flashing u-boot though? Or does it remain the same? It looks like the issue is happening in u-boot so it won't matter how you build the Kernel/RFS | 10:30 |
rajm | that's a relief it works - email to the list but the description in the email is a lie! | 10:30 |
rajm | it's remaining the same, will now test with the lava-tool and the kernelci built stuff | 10:31 |
rajm | and the lava-tool one using my kernelci built stuff also works! I'll put the health check back to see if it still fails | 10:36 |
*** CTtpollard has joined #cip | 10:49 | |
*** tpollard has quit IRC | 10:49 | |
* rajm thinks it's going to time out again - so why does lava tool work and HC doesn't? | 10:49 | |
patersonc | rajm: Do you have the actual console log from the target? | 10:53 |
rajm | let me see - but very interesting I've commented out the notification section and the HC with kernelci works! | 10:56 |
rajm | and there's a working one with notification but run as a lava-tool rather than a HC, I'll carefully diff the 2 files! | 11:10 |
rajm | notify - email went to the list | 11:10 |
patersonc | Received | 11:11 |
rajm | no significant differences between the two files | 12:07 |
*** toscalix has quit IRC | 12:12 | |
* rajm tries HC again removing some elements from the notify section | 12:14 | |
rajm | and that works too! (as cip-testing-results receivers will see!) | 12:19 |
rajm | I'll update the journal... | 12:19 |
rajm | rather verbosely! and I've put something similar in the #167 ticket, will email lava-users | 12:27 |
*** CTtpollard has quit IRC | 12:37 | |
*** tpollard has joined #cip | 12:38 | |
*** CTtpollard has joined #cip | 12:40 | |
*** tpollard has quit IRC | 12:40 | |
*** toscalix has joined #cip | 14:33 | |
toscalix | bwh ping | 14:35 |
bwh | hi | 14:35 |
toscalix | patersonc: can you please repeat your questions, now that bwh is available_ | 14:35 |
toscalix | szlin: around? | 14:35 |
toscalix | bwh: patersonc and szlin had questions for you yesterday at the meeting | 14:36 |
toscalix | let's see if they are around to ask you. If not, I will tell them to send a mail to cip-dev | 14:36 |
patersonc | Hello world | 14:38 |
toscalix | paterson, shoot | 14:39 |
patersonc | bwh: I was asking about Debian LTS, specifically a couple of questions... | 14:41 |
patersonc | 1) What packages are supported? | 14:41 |
patersonc | 2) What is actually maintained? Just CVE security issues? Or bug fixes etc. as well? | 14:41 |
bwh | The support list is driven by what LTS contributors are prepared to support | 14:42 |
bwh | Most LTS contributors are being paid through Freexian and Freexian surveys its customers to find out what they need to be supported | 14:42 |
toscalix | LTS includes sources and packages, right? | 14:43 |
bwh | Some packages are explicitly excluded (see the debian-security-support package) because they tend to have complex security issues that depend on upstream help to fix, and upstream doesn't support the version in LTS (or has gone away completely) | 14:44 |
bwh | toscalix: Currently it's mostly concerned with delivering binary packages | 14:45 |
toscalix | what challenges do you see in CIP maintaining some sources on our own, extending LTS, for our platforms? | 14:45 |
toscalix | beyond capacity restrictions | 14:46 |
bwh | toscalix: Let me cover patersonc's number 2 first | 14:46 |
toscalix | of course | 14:46 |
bwh | Almost all the work is concerned with security fixes, but other important bug fixes can be done. Certainly for the kernel I'm applying other bug fixes. | 14:47 |
bwh | OK, so the main challenge I see ais in maintaining the build infrastructure over a longer period | 14:49 |
toscalix | bwh: I see it also as a challenge, but not as a big one as maintaining yocto :-) | 14:51 |
toscalix | bitbake, I mean | 14:51 |
toscalix | we will need to analise the packages required to install and maintain the build infra | 14:52 |
toscalix | in debian | 14:52 |
toscalix | and add those to our Core system | 14:52 |
toscalix | lots of packages, I predict | 14:52 |
toscalix | it is going to be fun | 14:52 |
toscalix | thanks bwh | 14:56 |
patersonc | Bwh: thank you so much. I'm sorry I had to go to a meeting! | 15:27 |
*** patersonc has quit IRC | 15:32 | |
szlin | toscalix: I'm here | 15:33 |
*** CTtpollard has quit IRC | 15:35 | |
rajm | prepares to depart have a good weekend all! | 15:37 |
*** rajm has quit IRC | 15:39 | |
szlin | bwh: Two questions for CIP kernel maintenance | 15:42 |
szlin | 1. CIP kernel maintenance team working flow | 15:42 |
szlin | e.g., by subsystem driven. | 15:42 |
szlin | 2. Hands-on tasks for team member | 15:42 |
bwh | szlin: Hi! | 15:51 |
bwh | Sorry I couldn't make yesterday's meeting | 15:51 |
bwh | At the moment I'm the sole maintainer. I review changes in the 4.4 LTS branch (on stable@vger.kernel.org) and merge them after review. Any other patches are sent to the cip-dev list and I apply them after review. | 15:53 |
bwh | I would like to see more people start doing thorough reviews of changes on the LTS branch | 15:54 |
bwh | I made some notes about how to review changes and they're on the wiki: https://wiki.linuxfoundation.org/civilinfrastructureplatform/cipkernelmaintenance#patch-review-howto | 15:55 |
szlin | bwh: thanks, we read the wiki already. But how to start some hands-on tasks? | 16:05 |
szlin | back to question #1, do we have any CIP kernel maintenance team working flow so far | 16:05 |
szlin | Do you think the working model of Debian kernel team is suitable for us? | 16:06 |
toscalix | szlin: bwh is doing an internal talk now at codethink. Not sure if he will come back today. I suggest to write a mail to cip-dev wiith this question. I am sure others are interested in the answers aswell | 16:18 |
szlin | toscalix: got it, thanks | 16:38 |
*** kristerman has quit IRC | 17:05 | |
*** toscalix has quit IRC | 18:44 |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!