Tuesday, 2024-01-30

*** Kubu_work <Kubu_work!~kubu@arennes-654-1-262-155.w2-13.abo.wanadoo.fr> has quit IRC (Quit: Leaving.)00:25
*** florian_kc <florian_kc!~florian@dynamic-089-013-006-011.89.13.pool.telefonica.de> has quit IRC (Ping timeout: 276 seconds)00:30
*** mulk <mulk!~mulk@pd9514f7f.dip0.t-ipconnect.de> has quit IRC (Ping timeout: 256 seconds)00:58
*** mulk <mulk!~mulk@pd9514187.dip0.t-ipconnect.de> has joined #yocto01:01
*** jmd <jmd!~user@2001:a61:2a5a:f701:bd45:e9a8:6384:9d60> has quit IRC (Remote host closed the connection)01:31
*** simonew <simonew!~ile@2a02:810d:a940:35fc:a45:69a0:2c81:576f> has quit IRC (Ping timeout: 276 seconds)01:44
*** OnkelUlla <OnkelUlla!~user@dude03.red.stw.pengutronix.de> has quit IRC (Remote host closed the connection)02:38
*** OnkelUlla <OnkelUlla!~user@dude03.red.stw.pengutronix.de> has joined #yocto02:39
*** lexano <lexano!~lexano@> has quit IRC (Ping timeout: 260 seconds)02:51
*** LocutusOfBorg <LocutusOfBorg!~locutusof@> has quit IRC (Read error: Connection reset by peer)03:04
*** LocutusOfBorg <LocutusOfBorg!~locutusof@> has joined #yocto03:08
*** jclsn <jclsn!~jclsn@2a04:4540:6511:1600:2ce:39ff:fecf:efcd> has quit IRC (Ping timeout: 260 seconds)03:12
*** jclsn <jclsn!~jclsn@2a04:4540:652c:2600:2ce:39ff:fecf:efcd> has joined #yocto03:14
*** _cslcm <_cslcm!~cslcm@2a00:b900:117b::731> has joined #yocto03:20
*** cslcm <cslcm!~cslcm@2a00:b900:117b::731> has quit IRC (Read error: Connection reset by peer)03:20
*** otavio <otavio!~otavio@189-74-214-19.user3p.brasiltelecom.net.br> has quit IRC (Ping timeout: 276 seconds)03:27
*** ablu <ablu!~m-bfyrfh@user/Ablu> has quit IRC (Ping timeout: 276 seconds)03:34
*** ablu <ablu!~m-bfyrfh@user/Ablu> has joined #yocto03:36
*** khazakar <khazakar!uid144674@id-144674.ilkley.irccloud.com> has quit IRC (Quit: Connection closed for inactivity)04:01
*** pvogelaar <pvogelaar!~pvogelaar@p200300efdf036100127b44fffe802df7.dip0.t-ipconnect.de> has quit IRC (Quit: Client closed)04:13
*** amitk <amitk!~amit@> has joined #yocto04:37
*** amitk <amitk!~amit@> has quit IRC (Ping timeout: 268 seconds)04:55
*** xmn <xmn!~xmn@pool-108-46-142-76.nycmny.fios.verizon.net> has quit IRC (Ping timeout: 256 seconds)05:00
*** Vonter <Vonter!~Vonter@user/vonter> has quit IRC (Read error: Connection reset by peer)05:08
*** Vonter <Vonter!~Vonter@user/vonter> has joined #yocto05:11
*** amitk <amitk!~amit@> has joined #yocto05:34
*** Vonter <Vonter!~Vonter@user/vonter> has quit IRC (Quit: WeeChat 4.2.1)05:35
*** Vonter <Vonter!~Vonter@user/vonter> has joined #yocto05:38
*** jatedev <jatedev!~jatedev@> has quit IRC (Quit: Client closed)05:54
*** sakman <sakman!~Thunderbi@> has quit IRC (Ping timeout: 256 seconds)06:15
*** alessioigor <alessioigor!~alessioig@> has joined #yocto06:24
*** pvogelaar <pvogelaar!~pvogelaar@p200300efdf036100127b44fffe802df7.dip0.t-ipconnect.de> has joined #yocto06:35
*** jmd <jmd!~user@2001:a61:2a5a:f701:bd45:e9a8:6384:9d60> has joined #yocto06:49
*** linfax <linfax!~linfax@eumail.topcon.com> has joined #yocto07:13
*** jmd <jmd!~user@2001:a61:2a5a:f701:bd45:e9a8:6384:9d60> has quit IRC (Remote host closed the connection)07:14
*** Vonter <Vonter!~Vonter@user/vonter> has quit IRC (Ping timeout: 255 seconds)07:19
*** goliath <goliath!~goliath@user/goliath> has joined #yocto07:25
*** mckoan|away is now known as mckoan07:31
mckoangood morning07:32
Xogiummckoan: hello07:32
* alessioigor waves all07:33
*** Vonter <Vonter!~Vonter@user/vonter> has joined #yocto07:33
*** pvogelaar <pvogelaar!~pvogelaar@p200300efdf036100127b44fffe802df7.dip0.t-ipconnect.de> has quit IRC (Quit: Client closed)07:36
LetoThe2ndyo dudX07:37
*** rfuentess <rfuentess!~rfuentess@2a01:cb14:11e8:f400:3ac7:c706:4b6:3b09> has joined #yocto07:41
*** mvlad <mvlad!~mvlad@2a02:2f08:e805:bb00:4cbc:a570:1f02:c0b3> has joined #yocto07:45
*** frieder <frieder!~frieder@i577B91A0.versanet.de> has joined #yocto07:47
*** Kubu_work <Kubu_work!~kubu@arennes-654-1-262-155.w2-13.abo.wanadoo.fr> has joined #yocto07:49
*** rob_w <rob_w!~bob@host-82-135-31-73.customer.m-online.net> has joined #yocto07:53
*** zpfvo <zpfvo!~fvo@i59F5CEF2.versanet.de> has joined #yocto08:12
*** zpfvo <zpfvo!~fvo@i59F5CEF2.versanet.de> has quit IRC (Ping timeout: 252 seconds)08:18
*** pvogelaar <pvogelaar!~pvogelaar@p200300efdf036100127b44fffe802df7.dip0.t-ipconnect.de> has joined #yocto08:28
*** zpfvo <zpfvo!~fvo@i59F5CEF2.versanet.de> has joined #yocto08:33
*** leon-anavi <leon-anavi!~Leon@> has joined #yocto08:40
*** jmiehe <jmiehe!~Thunderbi@user/jmiehe> has joined #yocto08:40
*** amitk <amitk!~amit@> has quit IRC (Quit: leaving)08:47
*** florian <florian!~florian@port-217-146-132-69.static.as20676.net> has joined #yocto09:03
yoctonXogium: I've tried some more to reproduce your problem but nothing :-( My personal bet is around the dependency tracking of .wks.in files and something with changing MACHINE (https://git.yoctoproject.org/poky/tree/meta/classes-recipe/image_types_wic.bbclass#n139).09:15
*** pvogelaar <pvogelaar!~pvogelaar@p200300efdf036100127b44fffe802df7.dip0.t-ipconnect.de> has quit IRC (Quit: Client closed)09:15
yoctonXogium: What we need to fix this are clear and precises steps (which files to change, which bitbake commands) starting from scratch. I know this is not quick to do. I'm also curious to see if you can reproduce this problem from scratch.09:21
*** camus <camus!~Instantbi@> has quit IRC (Read error: Connection reset by peer)09:30
*** camus1 <camus1!~Instantbi@> has joined #yocto09:30
*** camus1 is now known as camus09:33
Xogiumyocton: I'll try again. But mostly what I've done is as you did yesterday, but I built the stompduck machine before then09:39
Xogiumso I tried a stompduck build, found it was working, then decided to copy that machine into a stompduck2.conf file and to modify it there... And the issue started09:39
Xogiumbut maybe my tree has gotten something in it, or my build tree has a problem... I will try again from scratch09:40
*** camus <camus!~Instantbi@> has quit IRC (Quit: camus)09:42
*** camus <camus!~Instantbi@> has joined #yocto09:44
*** prabhakarlad <prabhakarlad!~prabhakar@> has joined #yocto09:49
* derRichard reads https://lists.openembedded.org/g/openembedded-architecture/message/191309:51
derRichardmaybe it's only me but the faq on kas reads a lot like handwaving09:52
*** vladest <vladest!~Thunderbi@adsl-89-217-204-83.adslplus.ch> has quit IRC (Ping timeout: 264 seconds)09:53
kanavinthere's no way kas is at all realistic, I agree with that at least10:09
friederderRichard: I agree (having only read the FAQ point for now)10:10
*** Vonter <Vonter!~Vonter@user/vonter> has quit IRC (Ping timeout: 246 seconds)10:12
kanavinwe'd have to basically rewrite kas, and break all backwards compatibility10:12
kanavinand it isn't clear if kas upstream is going to be interested or helping, in all likelihood they won't10:13
*** Vonter <Vonter!~Vonter@user/vonter> has joined #yocto10:14
friederkanavin: Can you elaborate on that? Why would kas need to be rewritten? Why would the kas community not be interested?10:14
kanavinbecause it needs to integrate with all existing code in bitbake and oe-core, and not be a self-contained, isolated thing it is now. It also needs to drop all the opinionated, idiosyncratic ways it does build config management.10:15
derRichard's just that my clients *love* kas so much and *hate* setting up yocto with passion10:15
kanavinif they love kas, they can continue to use kas. They are not the target audience for this project, rather users new to yocto are.10:16
derRichardbut you don't you love it? ;-)10:16
derRichardit just works10:16
kanavinI don't love it, at all. Bloated mess.10:17
friederkanavin: I've been using Yocto for about 10 years and I love kas, too. So what?10:17
Xogiumhmm what is wrong with it ? Honestly asking. I haven't read thefaq or anything yet. I just used it in setting up the simplest-yocto-setup repo from bootlin, and I mean, as far as I'm aware it did fine with that task ?10:17
*** prabhakarlad <prabhakarlad!~prabhakar@> has quit IRC (Quit: Client closed)10:17
Xogium*the faq10:18
kanavinXogium, I tried to give an answer above.10:18
*** alessioigor <alessioigor!~alessioig@> has quit IRC (Quit: alessioigor)10:19
kanavin'just works' is not good enough10:19
*** alessioigor <alessioigor!~alessioig@> has joined #yocto10:19
friederkas does indeed provide a user-friendly way to interact with Yocto without needing to deep-dive into the system. And I agree that this is not what everyone wants/needs. But it is what the majority of everyday users benefit from.10:19
Xogiumtbh I just used it with kas checkout ;) that is the only command I've actually used from it10:19
kanavinit's not that it works. It's that we can't have it as official way to set up builds for multiple reasons.10:20
Xogiumso what to use then, if not kas ? I'm not against manual setting up of repositories, far from it. But what if you want a somewhat easier way for users to just get started with your things ?10:21
derRichardand adding missing features to kas was impossible?10:21
friederkanavin: That's ok, though I don't really see/understand these reasons, yet.10:21
kanavinthat's the gap we're aiming to fill. The tools to set up layer repos are in master. The tools to handle build configurations are in master. What isn't there is a high level interface that ties it all together in a single ui.10:22
friederStill we will be promoting/using kas as setup tool and any alternative from the OE community will likely not be interesting for us at all.10:22
kanavinwe who?10:22
friederKontron Electronics and our customers10:23
kanavinfrieder, you should at least evaluate the official tooling, because people will ask you about it, and 'we don't know' is not the answer10:23
kanavinderRichard, kas needs to be largely rewritten, it's not about missing features10:24
derRichardkanavin: hmmm.10:25
derRicharddoes the official tooling have a tool such as kas-container?10:25
*** pvogelaar <pvogelaar!~pvogelaar@p200300efdf036100127b44fffe802df7.dip0.t-ipconnect.de> has joined #yocto10:25
friederkanavin: We evaluated the tools a year ago and decided in favor of kas. We will evaluate again if kas fails to meet any upcoming requirements and our enough of our customers ask us for alternatives.10:26
friederkanavin: This won't happen as our customers only care if the tools are easy to use and work for their purpose.10:26
*** vladest <vladest!~Thunderbi@> has joined #yocto10:26
kanavinderRichard, official tooling doesn't cover that yet: the UI to tie the specific pieces together into a single command doesn't exist yet.10:29
kanavinfrieder, can you specify what you evaluated?10:29
jclsnJPEW: If I want to set BB_ENV_EXTRAWHITE in the pyrex.ini, I have to use envvars, right?10:30
derRichardi can only say what i have evaluated, so far every single customer was in need for a tool to setup/start a yocto build with a single command (and config file!) in a deterministic environment (e.g. a container). kas gives us all of that.10:31
kanavinyes that is a gap in the official offering. but saying 'we'll continue to use kas' is not helping to close that gap.10:33
friederderRichard: Same here!10:33
derRichardkanavin: "kas sucks and needs a rewrite" does not help either, IMHO.10:36
kanavinI mean, if you seriously want to elevate kas to official status, you need to get buy-in and a promise to help from its maintainers, and you need to read RP's proposal and make a technical plan to make it happen. And find developer resources for all of it.10:36
kanavinAs things are, we're better off coming up with our own proof of concept, which can be done quicker and easier, and then gradually develop it into a full-featured solution.10:37
kanavinif kas users don't want to help, that's ok, but please don't gaslight the effort like you do here.10:37
derRichardnobody want's to gaslight, no need to worry. i just fail to understand why kas is not an option. and yes, i read rp's mail. anyway, i better go to lunch, i start to get hangry ;-)10:39
kanavinderRichard, I don't understand why the reasons I listed aren't clear to you.10:45
friederkanavin: You are misjudging our intentions. We don't want to gaslight and if you think this is the way to go that's totally fine.10:51
friederkanavin: It's just that we don't really understand why kas can't be promoted to be official Yocto/OE tooling.10:51
*** jmiehe <jmiehe!~Thunderbi@user/jmiehe> has quit IRC (Quit: jmiehe)10:51
friederI will read RP's mail in its full length and maybe I get a better understanding.10:52
kanavinI suppose you better write a response there. I'd also advice against writing and sending it hastily: let the draft sit in your mailbox for at least 24 hours. The subject is very touchy, and the 'why not kas' question the most likely to result in a flamewar.10:54
friederkanavin: "We will continue to use kas" is what I say because that is what is likely going to happen in our case. But anyone can do as they want and I won't argue against alternative efforts if people decide they are needed.10:56
*** pvogelaar <pvogelaar!~pvogelaar@p200300efdf036100127b44fffe802df7.dip0.t-ipconnect.de> has quit IRC (Quit: Client closed)11:01
kanavinfrieder, the target audience is really users which are new to the project. We can't put kas in the official documentation until it's maintained under the yocto project umbrella, and for that to happen, all of the thigs I listed (or tried to) above need to happen. It's just more effort than actually building a proof of concept from official pieces that already exist.11:01
kanavinfrieder, on the other hand the core project funding and resources are extremely limited. Everyone likes to use yocto (and derive an income from that), very few people care about sustainability of it.11:02
*** prabhakarlad <prabhakarlad!~prabhakar@> has joined #yocto11:02
friederkanavin: I totally understand these points.11:04
*** DvorkinDmitry <DvorkinDmitry!~dvorkin@> has joined #yocto11:06
kanavin(I mean, care to the degree that they actively contribute11:06
DvorkinDmitrycorrupted uw-imap build in Dunfell https://pastebin.com/rvu8wwXX11:07
DvorkinDmitryIn order to build I have to copy the uw-imap recipe from the Kirkstone11:08
JaMadunfell is almost out of support but there is still time to send a fix :)11:09
*** Ad0 <Ad0!~Ad0@> has quit IRC (Ping timeout: 255 seconds)11:10
kanavinI can't wait to see dunfell users realizing it's out of support and they have a mountain of tech debt to clear to move forward to a newer yocto.11:11
friederkanavin: The problem is the timing. Now that kas is kind of established in many cases, it will be very hard to compete with when providing an official tooling alternative.11:14
*** Ad0 <Ad0!~Ad0@> has joined #yocto11:15
friederkanavin: And this will increase the gap between the communities as there are even less people who care about the sustainability of the official tooling when they use only kas and contribute to kas.11:15
kanavinfrieder, we're not aiming to compete with it in established projects. The target audience is primarily users new to yocto. The idea is that over time there'll be enough of those to make the official tooling self-sustaining - and it gets a boost merely by being provided out of the box, and being documented in yocto docs (kas is neither).11:17
* derRichard returns less grumpy11:17
friederkanavin: The problem is that people like our customers (being new to Yocto) don't look into the Yocto docs first. First they ask us (the hardware vendor) or look at our docs and we will tell them to use kas primarily.11:19
friederOr rather "hardware and BSP vendor"11:20
derRichardwhile chewing my meal, i thought about what i don't understand. i can see that kas does not fulfill all your current requirements. but what i don't get is why it's less work to implement your own tooling instead of embracing kas.11:22
friederkanavin: So in the end, because of kas' existing "share" in the "market" you will compete with kas anyway, like it or not.11:23
kanavinderRichard, embracing kas is not just declaring it 'official'. I just told frieder and I guess I have to repeat:  We can't put kas in the official documentation until it's maintained under the yocto project umbrella, and for that to happen, all of the thigs I listed (or tried to) above need to happen.11:25
kanavinAnd we need agreement and support from kas upstream as well, which is highly unlikely, as we basically never interact with them. They're their own bubble.11:26
derRichardso, it's politics.11:27
friederkanavin: Not having interacted with them in the past is barely a good reason for not interacting with them in the future...11:27
kanavinfrieder, derRichard if you want to help, then reach out to them please11:28
derRichardthis surprises me, jan (the kas maintainer) is very open and friendly. i will talk to him about this. maybe the bubble get merged :-D11:28
kanavinpoint him to RP's email then11:28
derRichardkanavin: didn't you talk to jan at ELCE 2023? both of you had talks on yocto tooling.11:29
kanavinderRichard, we never discussed the subject because it didn't exist back then. What I mean is that they're rarely if ever seen on the mailing lists, or here.11:34
kanavinor rather it existed as a long term aspiration, nothing more than a bullet point11:35
* derRichard reaches out to jan11:36
kanavinfrieder, the point about vendors imposing things on their customers is fair. But customers do have their own minds too, and they may ask you to support official tooling, and not include anything 3rd party in the offer.11:41
friederkanavin: Yes customers might ask this. Customers might ask a lot of things. But believe me, most of our customers ask about features, bugs and results, but not about tooling.11:44
kanavinand then they hire folks like me to sort the mess vendors created for them with the tooling and configurations.11:45
friederkanavin: And from there point of view basically everything they use is third-party. They don't care if there is one institution/community more or less involved.11:45
kanavinit pays money, but isn't fun11:45
friederkanavin: I now these kind of jobs. And we are doing as much as we can to avoid downstream vendor mess.11:47
*** otavio <otavio!~otavio@189-74-214-19.user3p.brasiltelecom.net.br> has joined #yocto11:54
kanavinI have to add that kas per se is rarely the source of the vendor mess, although it does things that would never be accepted in yocto upstream (and what to do with those features is another difficult question).12:01
kanavinbuild configuration management (rewriting local.conf in opinionated ways) is one such12:01
*** ptsneves <ptsneves!~Thunderbi@031011128046.dynamic-3-poz-k-0-2-0.vectranet.pl> has joined #yocto12:14
Xogiumyocton: so, whatever this was, I can't reproduce it anymore. I have no clue what this was about. I did everything from scratch again, built stompduck2 first and it worked. I also tried building stompduck first then building stompduck2, and it worked too. I think whatever went wrong, I atomized it when I removed the entire build dir12:32
Xogiumthe weirdest thing is that before then it was consistent12:33
Xogiumeither there's just that one thing that make it fail, whatever it is, or it's an issue that can show up but so intermitantly that it is virtually impossible to debug it12:35
*** lexano <lexano!~lexano@> has joined #yocto12:49
JaMais there easy way to list all inherits (not INHERIT variable) with bitbake-getvar or bitbake -e? I'm trying to check "WARNING: Recipe.inherits: recipes-webos-ose/luna-service2/luna-service2.bb: length 262 exceeds maximum (255), truncating" from layerindex12:50
yoctonJaMa: We used bb.data.inherits_class('ptest', d)12:52
yoctonJaMa: there are examples all over https://git.yoctoproject.org/poky/tree/meta/classes-global/insane.bbclass12:53
yoctonJaMa: ...and I misread your question sorry. (You wanted "with bitbake-getvar or bitbake -e")12:54
JaMayocton: that doesn't give me the list of inherrited unless I walk over all bbclasses listed in BBINCLUDED (or listing only those in BBINCLUDED which exist (as it shows them in all possible layers))12:54
JaMayocton: I guess I need __inherit_cache12:56
*** jmiehe <jmiehe!~Thunderbi@user/jmiehe> has joined #yocto12:58
*** Xagen <Xagen!~Xagen@99-135-179-142.lightspeed.austtx.sbcglobal.net> has quit IRC (Ping timeout: 276 seconds)13:11
JaMawill have to look at layerindex code as list created from BBINCLUDED as well as __inherit_cache gives me 551 chars and global INHERIT list is less than 150 chars, so it doesn't match with 262 shown in warning13:16
RPderRichard: FWIW I've an open mind about kas. If we were to talk to them, the first question would be "what are we looking for?" or "how would kas need to change?". The proposal therefore makes the logical first step. We wouldn't want to be accused of trying to subvert an existing tool :/13:16
*** xmn <xmn!~xmn@pool-108-46-142-76.nycmny.fios.verizon.net> has joined #yocto13:20
JaMamoto-timo: if you're going to update the model for recipe-subdirectory, can you bump the lenght of inherits in https://git.yoctoproject.org/layerindex-web/tree/layerindex/models.py#n475 as well? this is what triggered that warning in last layerindex update: env.luna-service2.__inherit_cache.py | xargs13:21
JaMafeatures_check webos_public_repo webos_enhanced_submissions webos_submissions webos_version webos_cmake cmake webos_filesystem_paths webos_system_bus webos_configure_manifest webos_core_os_dep webos_lttng webos_test_provider ptest pkgconf13:22
JaMaig webos_systemd systemd13:22
* JaMa goes for another coffee13:23
*** ptsneves <ptsneves!~Thunderbi@031011128046.dynamic-3-poz-k-0-2-0.vectranet.pl> has quit IRC (Ping timeout: 256 seconds)13:24
*** Siecje <Siecje!~Siecje@> has joined #yocto13:29
*** rob_w <rob_w!~bob@host-82-135-31-73.customer.m-online.net> has quit IRC (Remote host closed the connection)13:35
*** halstead <halstead!sid505447@id-505447.ilkley.irccloud.com> has quit IRC (Ping timeout: 268 seconds)13:39
*** shivamurthy <shivamurthy!sid359794@id-359794.helmsley.irccloud.com> has quit IRC (Ping timeout: 268 seconds)13:39
*** smurray <smurray!sid98062@id-98062.hampstead.irccloud.com> has quit IRC (Ping timeout: 268 seconds)13:39
*** ndec <ndec!sid219321@id-219321.tinside.irccloud.com> has quit IRC (Ping timeout: 268 seconds)13:39
*** shivamurthy <shivamurthy!sid359794@id-359794.helmsley.irccloud.com> has joined #yocto13:39
*** smurray <smurray!sid98062@id-98062.hampstead.irccloud.com> has joined #yocto13:39
*** ndec <ndec!sid219321@id-219321.tinside.irccloud.com> has joined #yocto13:39
*** ChanServ sets mode: +v ndec13:39
*** tokamak- <tokamak-!~Tokamak@2603:c020:4004:f00:59d7:d5e1:201e:845f> has joined #yocto13:39
*** tin_ <tin_!sid610731@id-610731.ilkley.irccloud.com> has quit IRC (Ping timeout: 268 seconds)13:40
*** tokamak <tokamak!~Tokamak@2603:c020:4004:f00:59d7:d5e1:201e:845f> has quit IRC (Ping timeout: 268 seconds)13:40
*** jonesv <jonesv!e7e4272e85@2a03:6000:1812:100::10b5> has quit IRC (Ping timeout: 268 seconds)13:40
*** abelloni <abelloni!~abelloni@2001:41d0:305:1000::2a58> has quit IRC (Ping timeout: 268 seconds)13:40
*** hays <hays!rootvegeta@fsf/member/hays> has quit IRC (Ping timeout: 268 seconds)13:40
*** jonesv <jonesv!e7e4272e85@2a03:6000:1812:100::10b5> has joined #yocto13:42
*** abelloni <abelloni!~abelloni@2001:41d0:305:1000::2a58> has joined #yocto13:42
*** tin_ <tin_!sid610731@id-610731.ilkley.irccloud.com> has joined #yocto13:42
*** astlep5504018 <astlep5504018!~thelounge@107-136-136-210.lightspeed.nsvltn.sbcglobal.net> has quit IRC (Quit: Ping timeout (120 seconds))13:43
*** astlep5504018 <astlep5504018!~thelounge@107-136-136-210.lightspeed.nsvltn.sbcglobal.net> has joined #yocto13:45
JaMarburton: OSE requires meta-qt6 6.6.0 (it might still build with 6.5.2 you've used but 6.6.0 is what all internal builds use (as defined in https://github.com/webosose/build-webos/blob/master/weboslayers.py)13:47
*** halstead <halstead!sid505447@id-505447.ilkley.irccloud.com> has joined #yocto13:53
rburtonJaMa: whoops.  did that change recently? i'm sure i copied something else.13:56
JaMarburton: https://github.com/webosose/build-webos/commit/5958cdbed661a920c1f1ec4030c17b33b6eb0db113:58
JaMachanged 2,5 months ago, but got published on github just 2 weeks ago13:59
JaMahmm qemu-8.2 upgrade somehow breaks meson when ccache is enabled (c compiler for build_machine is empty, leading to http://errors.yoctoproject.org/Errors/Details/751436/)14:01
*** _cslcm <_cslcm!~cslcm@2a00:b900:117b::731> has quit IRC (Quit: Leaving)14:07
*** sakman <sakman!~Thunderbi@> has joined #yocto14:08
*** GNUmoon <GNUmoon!~GNUmoon@gateway/tor-sasl/gnumoon> has quit IRC (Ping timeout: 255 seconds)14:23
*** Haxxa <Haxxa!~Haxxa@202-65-68-206.ip4.superloop.au> has quit IRC (Ping timeout: 252 seconds)14:23
*** Haxxa <Haxxa!~Haxxa@202-65-68-206.ip4.superloop.au> has joined #yocto14:25
*** pvogelaar <pvogelaar!~pvogelaar@p200300efdf036100127b44fffe802df7.dip0.t-ipconnect.de> has joined #yocto14:25
*** Haxxa <Haxxa!~Haxxa@202-65-68-206.ip4.superloop.au> has quit IRC (Ping timeout: 264 seconds)14:32
*** GNUmoon <GNUmoon!~GNUmoon@gateway/tor-sasl/gnumoon> has joined #yocto14:33
*** Haxxa <Haxxa!~Haxxa@202-65-68-206.ip4.superloop.au> has joined #yocto14:33
*** Estrella <Estrella!~quassel@2603-8080-d700-7495-6193-6cbb-7f33-bae7.res6.spectrum.com> has quit IRC (Ping timeout: 260 seconds)14:34
*** jatedev <jatedev!~jatedev@> has joined #yocto14:37
*** GNUmoon <GNUmoon!~GNUmoon@gateway/tor-sasl/gnumoon> has quit IRC (Remote host closed the connection)14:41
*** rcw <rcw!~rcwoolley@> has joined #yocto14:41
*** GNUmoon <GNUmoon!~GNUmoon@gateway/tor-sasl/gnumoon> has joined #yocto14:42
SiecjeIs there a good starting point for building for the RaspberryPi Compute Module 4?14:55
*** marka <marka!~marka@135-23-92-18.cpe.pppoe.ca> has quit IRC (Ping timeout: 240 seconds)15:00
*** vmeson <vmeson!~rmacleod@198-48-226-243.cpe.pppoe.ca> has quit IRC (Ping timeout: 268 seconds)15:02
JPEWjclsn: No, that one (along with BB_ENV_PASSTHROUGH_ADDITIONS) is special cased in pyrex15:05
rburtonSiecje: if you're using the Pi CM in a commercial sense, it would be good to tell the Pi foundation this. if they have more customers using it with yocto then they might actually support it.15:06
Siecjerburton: Will do!15:07
*** frosteyes <frosteyes!~frosteyes@> has joined #yocto15:11
frosteyesHello folks. A small question. I am working on Kirkstone, and having a new kernel (6.6) where I would do a populate_sdk on a image. It fails with "Error: Problem: conflicting requests  - nothing provides /usr/bin/make needed by kernel-devsrc"15:17
*** jatedev <jatedev!~jatedev@> has quit IRC (Quit: Client closed)15:18
frosteyesIt seems that the reason is that in newer kernel, the debian package part is split up with a seperate "rules" file in scripts/package/debian15:19
frosteyesI guess kernel-devsrc somehow include the packing part for debian15:20
*** vladest <vladest!~Thunderbi@> has quit IRC (Ping timeout: 256 seconds)15:20
frosteyesOhh a "cp -a scripts $kerneldir/build" in https://git.openembedded.org/openembedded-core/tree/meta/recipes-kernel/linux/kernel-devsrc.bb?h=master15:25
*** xmn <xmn!~xmn@pool-108-46-142-76.nycmny.fios.verizon.net> has quit IRC (Ping timeout: 240 seconds)15:26
*** marka <marka!~marka@135-23-92-18.cpe.pppoe.ca> has joined #yocto15:27
frosteyesWould you recommend a sed in kernel-devsrc do_install like the patching for the python stuff15:29
frosteyesOr should we add "make" RDEPENDS15:30
*** vmeson <vmeson!~rmacleod@198-48-226-243.cpe.pppoe.ca> has joined #yocto15:30
moto-timoJaMa: I’m less worried about warnings at the moment. We see a lot of truncation warnings. But I can take a look.15:32
moto-timoField length impacts the size of the database storage…15:33
*** goliath <goliath!~goliath@user/goliath> has quit IRC (Quit: SIGSEGV)15:37
*** zeddii <zeddii!~zeddii@> has quit IRC (Ping timeout: 252 seconds)15:39
moto-timofrieder: if kas works for your needs, by all means keep using it. Folks that like using repo tool are also welcome to keep using that. But, fundamentally, we need a tool in bitbake itself to do the layer setup.15:39
*** jatedev <jatedev!~jatedev@> has joined #yocto15:40
derRichardmoto-timo: why does bitbake itself need this?15:42
derRichard...this was the frist wtf that came up in my head while reading the mail on tooling15:42
*** zeddii <zeddii!~zeddii@> has joined #yocto15:43
moto-timoderRichard: because that is where all the low level support for layers lives in the first place. It is also where tools like bitbake-layers and the code to interface with the layerindex rest api lives.15:44
*** vladest <vladest!~Thunderbi@adsl-89-217-204-83.adslplus.ch> has joined #yocto15:45
moto-timoderRichard: there is nothing political here. This is a fundamental problem we have been kicking down the road for many years now and it is precisely the bike shedding about other tools that has prevented us making any headway. But the proposal will in no way break any existing tooling. In fact, plugins to support kas and repo tool and git submodules have already been taken into consideration15:47
derRichardmoto-timo: but this makes a "single command to setup/build" approach almost impossible.15:47
moto-timoderRichard: we are not trying to create one ring to rule them all.15:47
derRichardbut this is what users want, this is why kas is much loved.15:48
*** DvorkinDmitry <DvorkinDmitry!~dvorkin@> has quit IRC (Quit: KVIrc 5.0.0 Aria http://www.kvirc.net/)16:01
*** jatedev <jatedev!~jatedev@> has quit IRC (Quit: Client closed)16:08
moto-timoderRichard: I have given talks about using kas. I use it a lot. I have maintained projects with repo tool, git submodules and even combolayer. I understand the strengths and weaknesses of all of them.16:12
derRichardmoto-timo: i didn't question your competence. sorry for that if you had such a impression. just from my experience a tool like kas is missed most by the kind of yocto users i come across.16:16
moto-timoderRichard: many of us have recommended kas and I have setup many customers with kas if they had nothing else (or something horrible).16:17
rburtonman i've got about 8 hours of backchat to read here16:21
*** rfuentess <rfuentess!~rfuentess@2a01:cb14:11e8:f400:3ac7:c706:4b6:3b09> has quit IRC (Remote host closed the connection)16:22
*** prabhakarlad <prabhakarlad!~prabhakar@> has quit IRC (Quit: Client closed)16:28
*** linfax <linfax!~linfax@eumail.topcon.com> has quit IRC (Ping timeout: 260 seconds)16:40
*** Xagen <Xagen!~Xagen@098-006-114-013.biz.spectrum.com> has joined #yocto16:41
kanavinrburton, or just jan's statement on oe-architecture16:43
*** alessioigor <alessioigor!~alessioig@> has quit IRC (Quit: alessioigor)16:44
*** alessioigor <alessioigor!~alessioig@> has joined #yocto16:44
derRichardexactly :-)16:50
*** mckoan is now known as mckoan|away17:03
*** vladest <vladest!~Thunderbi@adsl-89-217-204-83.adslplus.ch> has quit IRC (Remote host closed the connection)17:07
*** vladest <vladest!~Thunderbi@adsl-89-217-204-83.adslplus.ch> has joined #yocto17:08
*** jmd <jmd!~user@2001:a61:2a5a:f701:bd45:e9a8:6384:9d60> has joined #yocto17:13
*** wooosaiiii1 <wooosaiiii1!~Thunderbi@89-212-21-243.static.t-2.net> has joined #yocto17:13
*** rcw <rcw!~rcwoolley@> has quit IRC (Remote host closed the connection)17:15
*** wooosaiiii <wooosaiiii!~Thunderbi@89-212-21-243.static.t-2.net> has quit IRC (Ping timeout: 252 seconds)17:15
*** rcw <rcw!~rcwoolley@> has joined #yocto17:15
*** wooosaiiii1 is now known as wooosaiiii17:15
*** sakman <sakman!~Thunderbi@> has quit IRC (Ping timeout: 260 seconds)17:15
*** rcw <rcw!~rcwoolley@> has quit IRC (Remote host closed the connection)17:17
*** RobW <RobW!~rcwoolley@> has joined #yocto17:17
*** ederibaucourt <ederibaucourt!~ederibauc@lmontsouris-657-1-69-118.w80-15.abo.wanadoo.fr> has quit IRC (Ping timeout: 252 seconds)17:18
*** ederibaucourt <ederibaucourt!~ederibauc@lmontsouris-657-1-69-118.w80-15.abo.wanadoo.fr> has joined #yocto17:18
*** Ad0 <Ad0!~Ad0@> has quit IRC (Ping timeout: 260 seconds)17:30
*** simonew <simonew!~simonew@2a02:810d:a940:35fc:c8c8:97d4:39a4:932a> has joined #yocto17:33
*** zpfvo <zpfvo!~fvo@i59F5CEF2.versanet.de> has quit IRC (Remote host closed the connection)17:37
*** goliath <goliath!~goliath@user/goliath> has joined #yocto17:41
*** florian <florian!~florian@port-217-146-132-69.static.as20676.net> has quit IRC (Quit: Ex-Chat)17:46
simonewHi, I have a question, say I want to "adopt" a package from meta/conf/distro/include/maintainers.inc. I was thinking about libseccomp or gnutls, to keep them up2date... What would be the prereqs? I'll accept a no of course as well18:02
*** simonew <simonew!~simonew@2a02:810d:a940:35fc:c8c8:97d4:39a4:932a> has quit IRC (Quit: Client closed)18:04
*** simonew <simonew!~simonew@2a02:810d:a940:35fc:c8c8:97d4:39a4:932a> has joined #yocto18:04
*** simonew22 <simonew22!~simonew@2a02:810d:a940:35fc:8cc4:ca69:c0f8:c6b1> has joined #yocto18:07
*** simonew22 <simonew22!~simonew@2a02:810d:a940:35fc:8cc4:ca69:c0f8:c6b1> has quit IRC (Client Quit)18:07
kanavinsimonew, there are no prereqs, other than you acting in a timely manner with version updates (we run a bot called AUH twice a month that checks upstreams if they made new releases, and it can also send you a patch if the update is trivial)18:11
*** simonew78 <simonew78!~simonew@2a02:810d:a940:35fc:8cc4:ca69:c0f8:c6b1> has joined #yocto18:11
*** simonew <simonew!~simonew@2a02:810d:a940:35fc:c8c8:97d4:39a4:932a> has quit IRC (Ping timeout: 250 seconds)18:11
*** simonew78 is now known as simonew18:11
simonewOk, so I would like to try if this is fine. I would just send a patch then to add myself there and take care of the recipes :)18:13
simonewAbout AUH I am aware18:13
*** Ad0 <Ad0!~Ad0@> has joined #yocto18:25
simonewJust one thing still: timely manner means? 1d / 3d/ 7d?18:27
*** Siecje <Siecje!~Siecje@> has quit IRC (Remote host closed the connection)18:30
kanavinsimonew, two weeks I'd say, as that's how often AUH runs. if you are subscribed to oe-core list, you've seen its output18:31
*** xmn <xmn!~xmn@pool-108-46-142-76.nycmny.fios.verizon.net> has joined #yocto18:33
simonewJep, saw it. Ok, then I would just try, if thats ok18:33
kanavinsure, please do18:34
*** alessioigor <alessioigor!~alessioig@> has quit IRC (Quit: alessioigor)18:34
*** alessioigor <alessioigor!~alessioig@> has joined #yocto18:34
simonewOk, thx for answers I have sent a patch to make it "real" ;D18:39
*** khazakar <khazakar!uid144674@id-144674.ilkley.irccloud.com> has joined #yocto18:41
*** florian_kc <florian_kc!~florian@dynamic-078-049-138-197.78.49.pool.telefonica.de> has joined #yocto18:52
*** sakman <sakman!~Thunderbi@> has joined #yocto18:53
kanavinsimonew, cheers. if there are other already assigned recipes you're particularly interested in, you can ask the current maintainers if they'd like to hand them over.19:03
*** frieder <frieder!~frieder@i577B91A0.versanet.de> has quit IRC (Remote host closed the connection)19:07
*** Haxxa <Haxxa!~Haxxa@202-65-68-206.ip4.superloop.au> has quit IRC (Quit: Haxxa flies away.)19:15
*** Haxxa <Haxxa!~Haxxa@202-65-68-206.ip4.superloop.au> has joined #yocto19:18
*** Minvera <Minvera!~Minvera@user/Minvera> has quit IRC (Remote host closed the connection)19:21
*** sakman <sakman!~Thunderbi@> has quit IRC (Read error: Connection reset by peer)19:28
*** rcw <rcw!~rcwoolley@> has joined #yocto19:30
*** goliath <goliath!~goliath@user/goliath> has quit IRC (Quit: SIGSEGV)19:33
*** RobW <RobW!~rcwoolley@> has quit IRC (Ping timeout: 252 seconds)19:33
simonewOk, I will first see how it goes with those 2 :)19:38
moto-timosimonew: thank you for helping out19:53
*** ptsneves <ptsneves!~Thunderbi@031011128046.dynamic-3-poz-k-0-2-0.vectranet.pl> has joined #yocto19:56
*** sakman <sakman!~Thunderbi@> has joined #yocto19:59
*** jmd <jmd!~user@2001:a61:2a5a:f701:bd45:e9a8:6384:9d60> has quit IRC (Remote host closed the connection)20:00
khemif anyone is brave enough and has compute cycles, I have put together a gcc-14 branch, although we wont be shipping gcc-14 in next release, but it will run on distros which will be built using gcc-14 e.g. f40  and so on, so it will be good to weed out package issues that we may run into for native nativesdk etc.20:09
*** Minvera <Minvera!~Minvera@user/Minvera> has joined #yocto20:11
khemand if you use clang then clang-18 here https://github.com/YoeDistro/meta-clang/tree/kraj/clang-1820:11
*** dmoseley <dmoseley!~dmoseley@d4-50-177-189.evv.wideopenwest.com> has quit IRC (Ping timeout: 268 seconds)20:11
*** dmoseley <dmoseley!~dmoseley@d4-50-177-189.evv.wideopenwest.com> has joined #yocto20:19
*** prabhakarlad <prabhakarlad!~prabhakar@> has joined #yocto20:29
*** wicki <wicki!~wicki@user/wicki> has quit IRC (Ping timeout: 264 seconds)20:30
*** vladest <vladest!~Thunderbi@adsl-89-217-204-83.adslplus.ch> has quit IRC (Quit: vladest)21:13
*** alessioigor <alessioigor!~alessioig@> has quit IRC (Quit: alessioigor)21:26
*** leon-anavi <leon-anavi!~Leon@> has quit IRC (Quit: Leaving)21:30
*** simonew <simonew!~simonew@2a02:810d:a940:35fc:8cc4:ca69:c0f8:c6b1> has quit IRC (Quit: Client closed)21:33
*** jmiehe <jmiehe!~Thunderbi@user/jmiehe> has quit IRC (Quit: jmiehe)21:35
*** vladest <vladest!~Thunderbi@adsl-89-217-204-83.adslplus.ch> has joined #yocto21:41
*** ptsneves <ptsneves!~Thunderbi@031011128046.dynamic-3-poz-k-0-2-0.vectranet.pl> has quit IRC (Ping timeout: 240 seconds)21:42
*** xmn <xmn!~xmn@pool-108-46-142-76.nycmny.fios.verizon.net> has quit IRC (Read error: Connection reset by peer)21:57
*** Xagen <Xagen!~Xagen@098-006-114-013.biz.spectrum.com> has quit IRC (Quit: My MacBook has gone to sleep. ZZZzzz…)22:20
*** prabhakarlad <prabhakarlad!~prabhakar@> has quit IRC (Ping timeout: 250 seconds)22:34
*** Kubu_work <Kubu_work!~kubu@arennes-654-1-262-155.w2-13.abo.wanadoo.fr> has quit IRC (Quit: Leaving.)22:35
*** adrianf is now known as AdrianF22:39
*** GNUmoon <GNUmoon!~GNUmoon@gateway/tor-sasl/gnumoon> has quit IRC (Ping timeout: 255 seconds)22:46
*** GNUmoon <GNUmoon!~GNUmoon@gateway/tor-sasl/gnumoon> has joined #yocto23:07
*** ak77 <ak77!~ak77@93-103-41-115.dynamic.t-2.net> has quit IRC (Ping timeout: 276 seconds)23:14
*** florian_kc <florian_kc!~florian@dynamic-078-049-138-197.78.49.pool.telefonica.de> has quit IRC (Ping timeout: 256 seconds)23:15
*** prabhakar <prabhakar!~prabhakar@> has quit IRC (Ping timeout: 264 seconds)23:43
*** khazakar <khazakar!uid144674@id-144674.ilkley.irccloud.com> has quit IRC (Quit: Connection closed for inactivity)23:56

Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!