[2025-04-07 00:01:57] ⇐ zeemate quit (~chris@2001:16b8:b102:fe00:9c7f:2147:ce70:9957): Ping timeout: 248 seconds | ||
[2025-04-07 00:46:04] → sanbeam joined (~Sanjeev@207-47-242-214.regn.hsdb.sasknet.sk.ca) | ||
[2025-04-07 00:47:47] ⇐ jerrycash3 quit (~jerrycash@user/jerrycash): Read error: Connection reset by peer | ||
[2025-04-07 00:48:11] → jerrycash3 joined (~jerrycash@user/jerrycash) | ||
[2025-04-07 00:55:13] → sanbeam9 joined (~Sanjeev@207-47-242-214.regn.hsdb.sasknet.sk.ca) | ||
[2025-04-07 00:58:33] ⇐ sanbeam quit (~Sanjeev@207-47-242-214.regn.hsdb.sasknet.sk.ca): Ping timeout: 276 seconds | ||
[2025-04-07 01:10:49] <paulg> khem, that was precisely the problem. I couldn't ignore everything else about it. | ||
[2025-04-07 01:16:44] → sanbeam18 joined (~Sanjeev@207-47-242-214.regn.hsdb.sasknet.sk.ca) | ||
[2025-04-07 01:19:14] ⇐ sanbeam9 quit (~Sanjeev@207-47-242-214.regn.hsdb.sasknet.sk.ca): Ping timeout: 248 seconds | ||
[2025-04-07 01:22:13] → sanbeam9 joined (~Sanjeev@207-47-242-214.regn.hsdb.sasknet.sk.ca) | ||
[2025-04-07 01:23:38] ⇐ sanbeam9 quit (~Sanjeev@207-47-242-214.regn.hsdb.sasknet.sk.ca): Client Quit | ||
[2025-04-07 01:24:33] ⇐ sanbeam18 quit (~Sanjeev@207-47-242-214.regn.hsdb.sasknet.sk.ca): Ping timeout: 248 seconds | ||
[2025-04-07 01:42:35] → enok joined (~Thunderbi@213-114-76-223.customers.ownit.se) | ||
[2025-04-07 01:46:39] ⇐ enok quit (~Thunderbi@213-114-76-223.customers.ownit.se): Ping timeout: 245 seconds | ||
[2025-04-07 01:46:52] ⇐ nerdboy quit (~sarnold@user/nerdboy): Ping timeout: 252 seconds | ||
[2025-04-07 01:58:53] → nerdboy joined (~sarnold@47.143.129.176) | ||
[2025-04-07 01:58:53] * nerdboy changed host: sarnold@47.143.129.176 → sarnold@user/nerdboy | ||
[2025-04-07 03:23:37] ⇐ Bardon quit (~Bardon@user/Bardon): Quit: ZNC - https://znc.in | ||
[2025-04-07 03:23:56] → Bardon joined (~Bardon@user/Bardon) | ||
[2025-04-07 04:02:35] ⇐ wooosaiiii quit (~Thunderbi@89-212-21-243.static.t-2.net): Remote host closed the connection | ||
[2025-04-07 04:02:54] → wooosaiiii joined (~Thunderbi@89-212-21-243.static.t-2.net) | ||
[2025-04-07 04:20:30] → tlwoerner joined (~tlwoerner@pppoe-209-91-167-254.vianet.ca) | ||
[2025-04-07 05:12:23] → goliath joined (~goliath@user/goliath) | ||
[2025-04-07 05:53:10] * Dracos-Carazza_ → Dracos-Carazza | ||
[2025-04-07 06:05:50] → enok joined (~Thunderbi@213-114-76-223.customers.ownit.se) | ||
[2025-04-07 06:13:54] ⇐ sakman quit (~sakman@208.111.77.233): Quit: Leaving | ||
[2025-04-07 06:26:55] → rob_w joined (~bob@host-82-135-31-73.customer.m-online.net) | ||
[2025-04-07 06:29:15] → alessio joined (~alessio@185.178.95.238) | ||
[2025-04-07 06:41:19] → Zosma joined (jorrit@2a03:f80:7:213:183:56:28:1) | ||
[2025-04-07 06:45:47] * mckoan|away → mckoan | ||
[2025-04-07 06:46:48] → leon-anavi joined (~Leon@46.55.231.62) | ||
[2025-04-07 06:47:15] → rfuentess joined (~rfuentess@lfbn-lyo-1-1566-5.w90-52.abo.wanadoo.fr) | ||
[2025-04-07 06:50:15] → Kubu_work joined (~kubu@2a01cb05949d580083fd25921c9c7a4f.ipv6.abo.wanadoo.fr) | ||
[2025-04-07 07:07:55] → frieder joined (~frieder@i59F664E2.versanet.de) | ||
[2025-04-07 07:27:25] → florian_kc joined (~florian@2a02:3100:3b51:6800:90b8:92:4da8:dc7) | ||
[2025-04-07 07:36:00] ⇐ florian_kc quit (~florian@2a02:3100:3b51:6800:90b8:92:4da8:dc7): Ping timeout: 246 seconds | ||
[2025-04-07 07:40:49] ⇐ alessio quit (~alessio@185.178.95.238): Quit: alessio | ||
[2025-04-07 07:41:11] → alessio joined (~alessio@185.178.95.238) | ||
[2025-04-07 07:46:07] ⇐ alessio quit (~alessio@185.178.95.238): Read error: Connection reset by peer | ||
[2025-04-07 07:48:57] → alessio joined (~alessio@185.178.95.238) | ||
[2025-04-07 07:52:58] → zeemate joined (~chris@2001:16b8:b120:ef00:5bc7:88eb:7f86:8549) | ||
[2025-04-07 07:59:08] → Guest76 joined (~Guest76@2001:a61:3b4e:4801:1fd3:8b3f:66a3:77a5) | ||
[2025-04-07 08:12:24] → bhstalel joined (~bhstalel@196.179.231.146) | ||
[2025-04-07 08:28:58] → eduter joined (~eduter@5.206.199.77) | ||
[2025-04-07 08:32:24] → frgo joined (~frgo@p548a3acc.dip0.t-ipconnect.de) | ||
[2025-04-07 08:32:39] <eduter> Hi. I am facing an error where a package is duplicated, meaning that has been added twice to the PACKAGES list. | ||
[2025-04-07 08:32:40] <eduter> Error message i get form the Yocto build: ERROR: firmware-nxp-wifi-1.1-r0 do_package: QA Issue: firmware-nxp-wifi-nxpiw610-sdio is listed in PACKAGES multiple times, this leads to packaging errors. [packages-list] | ||
[2025-04-07 08:32:40] <eduter> I investigated and I can see that it is actually added from at least two different external static layers that I am using in my Yocto build system: | ||
[2025-04-07 08:32:41] <eduter> 1) "meta-freescale/recipes-bsp/firmware-imx/firmware-nxp-wifi_1.1.bb" | ||
[2025-04-07 08:32:41] <eduter> 2) "meta-imx/meta-imx-bsp/recipes-bsp/firmware-imx/firmware-nxp-wifi_%.bbappend" | ||
[2025-04-07 08:32:42] <eduter> Is this an error? Can someone please let me know if this could be an issue on my end or on the Yocto end? | ||
[2025-04-07 08:33:05] ⇐ frgo_ quit (~frgo@p548a3acc.dip0.t-ipconnect.de): Read error: Connection reset by peer | ||
[2025-04-07 08:33:37] <eduter> Those layers are not my custom layer, that is why I am asking if this is something to report to the Yocto project or if I may be doing something wrong on my side. | ||
[2025-04-07 08:37:23] → florian joined (~florian@port-217-146-132-69.static.as20676.net) | ||
[2025-04-07 08:43:43] <eduter> I am aiming to build up base on LTS "scarthgap". I can see that the "meta-nxp" layer has this "firmware-nxp-wifi..." recipe present in "scarthgap" branch, which it was not present in "kirkstone". On the other hand, the "firmware-nxp-wifi..." recipe has been present since "kirkstone" branch for meta-freescale layer. | ||
[2025-04-07 08:44:26] <mcfrisk> eduter: these layers are from NXP not yocto community. You can fork the layers and amend them with fixes to issues like this, or if you know that one of the files is not needed in your builds, BBMASK the file away with path matching it | ||
[2025-04-07 08:45:13] <LetoThe2nd> Yo dudx | ||
[2025-04-07 08:45:45] <eduter> mcfrisk thanks a lot. I just got the tip about masking from googling. I will go down for that just to try to move forward. NXP is a private vendor, you have a point... sorry about that. It is not Yocto project responsability (y) (y) | ||
[2025-04-07 08:46:24] <eduter> thanks for the tip about masking, that is why I was looking for to be able to continue making progress. Thanks! | ||
[2025-04-07 08:47:06] <bhstalel> LetoThe2nd did you receive my question regarding the Yocto Speaker badges for the latest summit ? | ||
[2025-04-07 08:48:09] <LetoThe2nd> bhstalel: yup, and they should have been assigned right after the last summit. Sounds like you didn't get a notification? Can you check your badge account? | ||
[2025-04-07 08:49:08] <mcfrisk> eduter: if you carefully review the changes and recipes you need from each layer, and then BBMASK all the rest away, it is possible to do upstream yocto layer version updates while keeping an old BSP layer working and providing needed bootloader, kernel, drivers etc. I've done this multiple times. It's about reducing layers and their dependencies to bare minimum. | ||
[2025-04-07 08:49:52] <mcfrisk> that is, the BSP layer provider, e.g. HW/SoC provider, does not dictate the yocto version which you use for the general purpose SW stack which includes the cross compiler | ||
[2025-04-07 08:50:59] ⇐ alessio quit (~alessio@185.178.95.238): Read error: Connection reset by peer | ||
[2025-04-07 08:52:24] <bhstalel> LetoThe2nd I am checking ... | ||
[2025-04-07 08:53:02] <bhstalel> Got it, thansk | ||
[2025-04-07 08:53:04] <bhstalel> thanks* | ||
[2025-04-07 08:54:27] → savolla joined (~savolla@159.146.29.48) | ||
[2025-04-07 08:54:35] <LetoThe2nd> bhstalel: NP | ||
[2025-04-07 08:56:27] <eduter> mcfrisk thanks for the info. I am taking my time to diggest it. So my understanding of what you are telling me to keep in mind is that, upgrading Yocto-layers in my Yocto build system to "scarthgap" LTS, does not mean that I need to upgrade my "HARDWARE BSP private vendor" layers to the same. I can just mask anything I may not need to keep the | ||
[2025-04-07 08:56:28] <eduter> functionality to the minimum possible. I understand the tip and I will keep it in mind. At the moment I have to admit that I am just trying to upgrade everything to "scarthgap", as that was the general purpose of the task I was given. While I am just trying to make progress and successfully upgrade all branches from all layers to the "scarthgap", | ||
[2025-04-07 08:56:28] <eduter> as I increase my knowledge on this project and BSP, etc. I will keep in mind the advice you are giving me. Thanks :-) | ||
[2025-04-07 08:59:03] <mcfrisk> updating everything is the best case. Doing the update for high level SW stack, or preparing for the next, don't wayt for the BSP vendor to provide their support first... | ||
[2025-04-07 09:00:40] <mcfrisk> some changes are needed to compile BSP layers, e.g. for bitbake to parse them, and some adaptations due to changes in e.g. kernel.bbclass, but for the rest, including kernel major version changes. You can just wait but move on for the reset of the SW stack and especially open source layers | ||
[2025-04-07 09:00:44] <eduter> mcfrisk got you. Ok. I will updating everything if doable, that is the idea scenario for moving from LTS to LTS, for example, I am trying to do for my task. I will not wait for BSP private vendor to support... I know... that may be more tedious. | ||
[2025-04-07 09:02:13] <eduter> mcfrisk Yes ok. I will aim for updating the open source layers to the next LTS. And for the vendors if I can fantastic, otherwise, I can always "mask" or basically choose the bits that I need... instead of waiting for them to provide me with the support I need. | ||
[2025-04-07 09:02:17] <eduter> :-) | ||
[2025-04-07 09:14:04] → alessio joined (~alessio@185.178.95.238) | ||
[2025-04-07 09:15:24] ⇐ enok quit (~Thunderbi@213-114-76-223.customers.ownit.se): Ping timeout: 245 seconds | ||
[2025-04-07 09:16:05] <Zosma> Hi, commit https://web.git.yoctoproject.org/poky/commit/?id=89ccf603d8119c34f5398dbd737e6a0b805234d3 of the wget fetcher seems to break our sstate caching that makes use of the Azure fetcher. | ||
[2025-04-07 09:16:19] <Zosma> Specifically, the commit seems to completely discard the query string from any URL. But the Azure fetcher needs to set the authentication token as part of a query string. See https://web.git.yoctoproject.org/poky/tree/bitbake/lib/bb/fetch2/az.py line 39 and 72. | ||
[2025-04-07 09:23:31] <Zosma> I'm unsure how to get this patched back upstream without breaking again what the author wanted to fix. | ||
[2025-04-07 09:29:29] <yocton> Zosma: Can't the azure fetcher use a .netrc file? As far as I understood the strategy here, we try to avoid handling authentication data as much as possible in Yocto recipes/confs/... | ||
[2025-04-07 09:33:40] <Zosma> yocton: the Azure SAS token is not your classic username/password, just a token. Azure only supports adding the token as part of a query string see https://learn.microsoft.com/en-us/azure/storage/common/storage-sas-overview#sas-token | ||
[2025-04-07 09:35:19] <Zosma> Furthermore, isn't it weird that *any* query string gets discarded, be it authentication or not? With the commit I mentioned it seems that I can't even add a '?option=value' if some API would need it. | ||
[2025-04-07 09:36:55] ⇐ prabhakalad quit (~prabhakar@165.225.17.42): Ping timeout: 272 seconds | ||
[2025-04-07 09:37:57] → prabhakalad joined (~prabhakar@165.225.17.42) | ||
[2025-04-07 09:45:59] ⇐ eduter quit (~eduter@5.206.199.77): Quit: Client closed | ||
[2025-04-07 09:49:22] ⇐ tlwoerner quit (~tlwoerner@pppoe-209-91-167-254.vianet.ca): Remote host closed the connection | ||
[2025-04-07 09:49:40] → tlwoerner joined (~tlwoerner@pppoe-209-91-167-254.vianet.ca) | ||
[2025-04-07 09:53:04] ⇐ paulg quit (~paulg@38.147.253.174): Ping timeout: 252 seconds | ||
[2025-04-07 09:53:28] → paulg joined (~paulg@38.147.253.174) | ||
[2025-04-07 10:41:09] → eduter joined (~eduter@5.206.199.77) | ||
[2025-04-07 11:09:16] → jbo_ joined (~jbo@user/tct) | ||
[2025-04-07 11:10:39] ⇐ jbo quit (~jbo@user/tct): Ping timeout: 260 seconds | ||
[2025-04-07 11:15:35] ⇐ eduter quit (~eduter@5.206.199.77): Quit: Client closed | ||
[2025-04-07 11:16:19] → eduter joined (~eduter@95-154-54-91.norlyscustomer.net) | ||
[2025-04-07 11:20:30] ⇐ eduter quit (~eduter@95-154-54-91.norlyscustomer.net): Ping timeout: 240 seconds | ||
[2025-04-07 11:28:36] → eduter joined (~eduter@5.206.199.77) | ||
[2025-04-07 11:43:03] → GillesM joined (~gilles@159.92.69.37.rev.sfr.net) | ||
[2025-04-07 11:43:10] ⇐ GillesM quit (~gilles@159.92.69.37.rev.sfr.net): Remote host closed the connection | ||
[2025-04-07 11:59:36] ⇐ GNUmoon quit (~GNUmoon@gateway/tor-sasl/gnumoon): Ping timeout: 264 seconds | ||
[2025-04-07 12:03:10] → enok joined (~Thunderbi@213-114-76-223.customers.ownit.se) | ||
[2025-04-07 12:04:17] → GNUmoon joined (~GNUmoon@gateway/tor-sasl/gnumoon) | ||
[2025-04-07 12:06:05] * jbo_ → jbo | ||
[2025-04-07 12:07:48] ⇐ enok quit (~Thunderbi@213-114-76-223.customers.ownit.se): Ping timeout: 265 seconds | ||
[2025-04-07 12:19:08] → florian_kc joined (~florian@port-217-146-132-69.static.as20676.net) | ||
[2025-04-07 12:19:29] → Guest61 joined (~Guest61@ip1f13f1d8.dynamic.kabel-deutschland.de) | ||
[2025-04-07 12:20:46] ⇐ ablu quit (~m-bfyrfh@user/Ablu): Ping timeout: 252 seconds | ||
[2025-04-07 12:21:00] * Guest61 → Brox | ||
[2025-04-07 12:22:41] <yocton> Zosma: Sorry, we do not use Azure here, I can't tell what does/doesn't work and how :/ | ||
[2025-04-07 12:24:09] → ablu joined (~m-bfyrfh@user/Ablu) | ||
[2025-04-07 12:42:31] → enok joined (~Thunderbi@213-114-76-223.customers.ownit.se) | ||
[2025-04-07 12:47:10] ⇐ enok quit (~Thunderbi@213-114-76-223.customers.ownit.se): Ping timeout: 252 seconds | ||
[2025-04-07 12:51:39] <Zosma> yocton: no worries, appreciate your response! | ||
[2025-04-07 13:08:06] → eduter7 joined (~eduter@5.206.199.77) | ||
[2025-04-07 13:08:14] <rburton> Zosma: file a bug - more complete url passing might work. or we need a azure fetcher that can add custom logic. | ||
[2025-04-07 13:11:42] ⇐ eduter quit (~eduter@5.206.199.77): Ping timeout: 240 seconds | ||
[2025-04-07 13:14:40] <Zosma> rburton: aight, will do so, thanks. | ||
[2025-04-07 13:15:54] ⇐ sakoman quit (~sakoman@2602:feb4:3b:2100:1fc4:e1bf:a115:f3b0): Ping timeout: 268 seconds | ||
[2025-04-07 13:16:31] → sakoman joined (~sakoman@98.142.47.158) | ||
[2025-04-07 13:24:50] → cyxae joined (~cyxae__@2607:fad8:4:6:612e:317a:4acd:eff3) | ||
[2025-04-07 13:31:25] ⇐ florian_kc quit (~florian@port-217-146-132-69.static.as20676.net): Ping timeout: 260 seconds | ||
[2025-04-07 13:33:37] ⇐ eduter7 quit (~eduter@5.206.199.77): Quit: Client closed | ||
[2025-04-07 13:53:49] ⇐ alessio quit (~alessio@185.178.95.238): Quit: alessio | ||
[2025-04-07 13:57:19] → enok joined (~Thunderbi@213-114-76-223.customers.ownit.se) | ||
[2025-04-07 14:00:10] ⇐ goliath quit (~goliath@user/goliath): Quit: SIGSEGV | ||
[2025-04-07 14:10:15] <fullstop> I am using scarthgap and generating multiple machine images in the same tree. It consistently messes up with the do_create_spdx task when I switch between machines. I must cleansstate systemd and rebuild the image. | ||
[2025-04-07 14:20:40] ⇐ rob_w quit (~bob@host-82-135-31-73.customer.m-online.net): Remote host closed the connection | ||
[2025-04-07 14:22:03] ⇐ enok quit (~Thunderbi@213-114-76-223.customers.ownit.se): Quit: enok | ||
[2025-04-07 14:22:09] → enok71 joined (~Thunderbi@213-114-76-223.customers.ownit.se) | ||
[2025-04-07 14:26:12] ⇐ enok71 quit (~Thunderbi@213-114-76-223.customers.ownit.se): Ping timeout: 246 seconds | ||
[2025-04-07 14:33:31] <rburton> fullstop: file a bug with a reproducer please | ||
[2025-04-07 14:42:50] ⇐ jerrycash3 quit (~jerrycash@user/jerrycash): Read error: Connection reset by peer | ||
[2025-04-07 14:43:59] <landgraf> fullstop: this happens to me if PV changes https://bugzilla.yoctoproject.org/show_bug.cgi?id=15442 | ||
[2025-04-07 14:45:54] <fullstop> rburton: I will try | ||
[2025-04-07 14:48:27] <fullstop> landgraf: mine is a different error: https://pastebin.com/raw/Dtk40Sd2 | ||
[2025-04-07 15:13:49] <rburton> if python says dict iterator order is insertion order, just _how_ horrible is FOO, BAR = oeqa.utils.commands.get_bb_var(['FOO', 'BAR']).values() | ||
[2025-04-07 15:14:05] <rburton> erm, get_bb_vars obviously | ||
[2025-04-07 15:50:18] ⇐ Brox quit (~Guest61@ip1f13f1d8.dynamic.kabel-deutschland.de): Quit: Client closed | ||
[2025-04-07 15:55:00] ⇐ Articulus quit (~Articulus@2601:642:4f7f:1df1:16ac:60ff:fed8:386b): Quit: Leaving | ||
[2025-04-07 16:00:39] <khem> rburton: dicts do preserve insertion order in newer pythons but I dont know what get_bb_var is doing w.r.t insertion is it creating a dictionary internally ? | ||
[2025-04-07 16:00:49] <rburton> yeah | ||
[2025-04-07 16:01:26] <khem> mydict = oeqa.utils.commands.get_bb_var(['FOO', 'BAR']) | ||
[2025-04-07 16:01:50] ⇐ rfuentess quit (~rfuentess@lfbn-lyo-1-1566-5.w90-52.abo.wanadoo.fr): Remote host closed the connection | ||
[2025-04-07 16:01:59] <khem> FOO = mydict['FOO'] | ||
[2025-04-07 16:02:15] <khem> and same for BAR might ensure the order | ||
[2025-04-07 16:03:22] <rburton> yeah thats tedious though :) | ||
[2025-04-07 16:17:26] ⇐ frieder quit (~frieder@i59F664E2.versanet.de): Remote host closed the connection | ||
[2025-04-07 16:25:59] → florian_kc joined (~florian@2a02:3100:3b51:6800:fcf3:8858:6ba3:2139) | ||
[2025-04-07 16:32:54] → goliath joined (~goliath@user/goliath) | ||
[2025-04-07 16:53:55] ⇐ leon-anavi quit (~Leon@46.55.231.62): Quit: Leaving | ||
[2025-04-07 16:55:42] * mckoan → mckoan|away | ||
[2025-04-07 17:03:33] → micka| joined (~micka@reverse-177-98.fdn.fr) | ||
[2025-04-07 17:04:03] ⇐ micka quit (~micka@reverse-177-98.fdn.fr): Ping timeout: 272 seconds | ||
[2025-04-07 17:04:03] * micka| → micka | ||
[2025-04-07 17:37:59] ⇐ savolla quit (~savolla@159.146.29.48): Quit: WeeChat 4.4.3 | ||
[2025-04-07 17:59:24] ⇐ bhstalel quit (~bhstalel@196.179.231.146): Quit: Client closed | ||
[2025-04-07 18:06:39] → enok joined (~Thunderbi@213-114-76-223.customers.ownit.se) | ||
[2025-04-07 18:26:30] ⇐ Guest76 quit (~Guest76@2001:a61:3b4e:4801:1fd3:8b3f:66a3:77a5): Ping timeout: 240 seconds | ||
[2025-04-07 18:39:34] ⇐ enok quit (~Thunderbi@213-114-76-223.customers.ownit.se): Ping timeout: 245 seconds | ||
[2025-04-07 18:45:58] ⇐ reatmon_ quit (~reatmon@192.91.75.12): Remote host closed the connection | ||
[2025-04-07 18:46:23] → reatmon_ joined (~reatmon@192.91.75.30) | ||
[2025-04-07 18:49:06] <tlwoerner> rburton: i haven't sent my wic patch yet. i've updated the issue with my findings, how to reproduce, explain how i've fixed the issue, and demonstration of it fixed | ||
[2025-04-07 18:49:20] <tlwoerner> rburton: i'm running the wic and wic2 self tests and looking at adding a new test for this case | ||
[2025-04-07 18:57:29] → enok joined (~Thunderbi@213-114-76-223.customers.ownit.se) | ||
[2025-04-07 19:07:29] ⇐ florian_kc quit (~florian@2a02:3100:3b51:6800:fcf3:8858:6ba3:2139): Ping timeout: 248 seconds | ||
[2025-04-07 19:18:30] ⇐ enok quit (~Thunderbi@213-114-76-223.customers.ownit.se): Ping timeout: 260 seconds | ||
[2025-04-07 19:19:41] → florian_kc joined (~florian@2a02:3100:3b51:6800:5ebf:fae4:db34:904f) | ||
[2025-04-07 19:26:36] → skandigraun joined (~skandigra@51.154.145.205) | ||
[2025-04-07 19:33:08] <khem> vmeson:can you reach out to Changqing Li and report this build failure - https://errors.yoctoproject.org/Errors/Details/851668/ with mariadb 11.4.5 upgrade I see the patch on lore.kernel.org but not in my inbox, mysterious world of emails | ||
[2025-04-07 19:34:30] ⇐ skandigraun quit (~skandigra@51.154.145.205): Ping timeout: 240 seconds | ||
[2025-04-07 19:38:54] → enok joined (~Thunderbi@213-114-76-223.customers.ownit.se) | ||
[2025-04-07 19:44:18] <gmorell> r | ||
[2025-04-07 19:49:11] → eduter7 joined (~eduter7@83.137.123.152) | ||
[2025-04-07 20:12:36] → GillesM joined (~gilles@159.92.69.37.rev.sfr.net) | ||
[2025-04-07 20:23:59] ⇐ enok quit (~Thunderbi@213-114-76-223.customers.ownit.se): Quit: enok | ||
[2025-04-07 20:24:08] → enok joined (~Thunderbi@213-114-76-223.customers.ownit.se) | ||
[2025-04-07 20:25:12] ⇐ Kubu_work quit (~kubu@2a01cb05949d580083fd25921c9c7a4f.ipv6.abo.wanadoo.fr): Quit: Leaving. | ||
[2025-04-07 20:27:33] → druppy joined (~Thunderbi@user/druppy) | ||
[2025-04-07 20:39:41] ⇐ dankm quit (~dan@user/dankm): Remote host closed the connection | ||
[2025-04-07 20:41:48] → dankm joined (~dan@user/dankm) | ||
[2025-04-07 20:47:04] ⇐ druppy quit (~Thunderbi@user/druppy): Ping timeout: 245 seconds | ||
[2025-04-07 20:47:46] ⇐ GillesM quit (~gilles@159.92.69.37.rev.sfr.net): Remote host closed the connection | ||
[2025-04-07 20:48:01] → GillesM joined (~gilles@159.92.69.37.rev.sfr.net) | ||
[2025-04-07 20:48:31] ⇐ GillesM quit (~gilles@159.92.69.37.rev.sfr.net): Remote host closed the connection | ||
[2025-04-07 20:48:51] → GillesM joined (~gilles@159.92.69.37.rev.sfr.net) | ||
[2025-04-07 20:50:08] ⇐ eduter7 quit (~eduter7@83.137.123.152): Quit: Client closed | ||
[2025-04-07 20:50:33] → GillesMM joined (~gilles@159.92.69.37.rev.sfr.net) | ||
[2025-04-07 20:51:21] ⇐ GillesMM quit (~gilles@159.92.69.37.rev.sfr.net): Remote host closed the connection | ||
[2025-04-07 20:52:31] → Kubu_work joined (~kubu@lfbn-nan-1-335-137.w82-120.abo.wanadoo.fr) | ||
[2025-04-07 20:56:27] ⇐ GillesM quit (~gilles@159.92.69.37.rev.sfr.net): Remote host closed the connection | ||
[2025-04-07 20:56:41] <vmeson> khem: done, no the list and CCed you. | ||
[2025-04-07 20:56:42] → GillesM joined (~gilles@159.92.69.37.rev.sfr.net) | ||
[2025-04-07 20:56:45] <vmeson> *on the list | ||
[2025-04-07 20:57:37] ⇐ GillesM quit (~gilles@159.92.69.37.rev.sfr.net): Remote host closed the connection | ||
[2025-04-07 21:02:51] → sakman joined (~sakman@208.111.77.233) | ||
[2025-04-07 21:06:06] → GillesM joined (~gilles@159.92.69.37.rev.sfr.net) | ||
[2025-04-07 21:08:23] → druppy joined (~Thunderbi@user/druppy) | ||
[2025-04-07 21:08:46] ⇐ GillesM quit (~gilles@159.92.69.37.rev.sfr.net): Client Quit | ||
[2025-04-07 21:11:39] ⇐ enok quit (~Thunderbi@213-114-76-223.customers.ownit.se): Ping timeout: 245 seconds | ||
[2025-04-07 21:34:39] <khem> thanks, I have replied with a potential fix to try out | ||
[2025-04-07 21:40:21] <JPEW> RP: I'm not seeing any tests for the python module parsing in bitbake... can I just not find them or do they not exist? | ||
[2025-04-07 21:40:47] <RP> JPEW: we may not have any :( | ||
[2025-04-07 21:41:21] <JPEW> RP: K, just checking | ||
[2025-04-07 21:43:38] ⇐ goliath quit (~goliath@user/goliath): Quit: SIGSEGV | ||
[2025-04-07 21:49:56] <khem> RP:clang merge and mesa fixes have conflicts, I am thinking of rebasing on top of mesa fixes, so sequence it mesa and than clang probably, I see value in having mesa fixes first so I have one more test for the merge | ||
[2025-04-07 21:55:38] → GillesM joined (~gilles@159.92.69.37.rev.sfr.net) | ||
[2025-04-07 21:55:42] ⇐ GillesM quit (~gilles@159.92.69.37.rev.sfr.net): Client Quit | ||
[2025-04-07 22:06:30] ⇐ druppy quit (~Thunderbi@user/druppy): Ping timeout: 260 seconds | ||
[2025-04-07 22:08:11] <RP> khem: ok, I had reported the clang issue to Dimitry and I think he was working on things. Are you ok with what the series does? | ||
[2025-04-07 22:16:19] ⇐ florian_kc quit (~florian@2a02:3100:3b51:6800:5ebf:fae4:db34:904f): Ping timeout: 265 seconds | ||
[2025-04-07 22:48:48] ⇐ GNUmoon quit (~GNUmoon@gateway/tor-sasl/gnumoon): Ping timeout: 264 seconds | ||
[2025-04-07 22:51:16] → GNUmoon joined (~GNUmoon@gateway/tor-sasl/gnumoon) | ||
[2025-04-07 23:45:13] <khem> ideally I would have merged both together | ||
[2025-04-07 23:45:56] <khem> because some of the work will be undone by this change especially the meta-clang patches which are proposed to get going with the set proposed for work | ||
[2025-04-07 23:46:05] <khem> in core as of now |
Generated by irclog2html.py 4.0.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!