geoffhp has quit [Remote host closed the connection]
geoffhp has joined #yocto
OnkelUlla has joined #yocto
bps2 has joined #yocto
bps2 has quit [Ping timeout: 250 seconds]
alessioigor has joined #yocto
ecdhe_ has quit [Read error: Connection reset by peer]
ecdhe has joined #yocto
camus has quit [Ping timeout: 248 seconds]
mvlad has joined #yocto
rob_w has joined #yocto
amitk_ has joined #yocto
goliath has joined #yocto
<LetoThe2nd>
yo dudX
camus has joined #yocto
barometz has quit [Quit: you can't fire me!]
kanavin has quit [Quit: Leaving]
davidinux has joined #yocto
barometz has joined #yocto
rfuentess has joined #yocto
<paulbarker>
RP: Unfortunately I'm not able to do anything with patchtest these days, my name should be removed from there
<RP>
paulbarker: I suspected that but just wanted to check, thanks for confirming
<RP>
khem: it is just more load, more testing time ;-). I guess arm64 and x86-64 ?
Thorn has joined #yocto
abbasalichezgi[m has joined #yocto
zpfvo has joined #yocto
<abbasalichezgi[m>
i have a problem in building kernel with CONFIG_DEBUG_INFO_BTF. can anybody help me? it says libelf.h: No such file or directory. i also added elfutils to DEPENDS.
Schlumpf has joined #yocto
bps2 has joined #yocto
prabhakarlad has joined #yocto
frieder has joined #yocto
bps3 has joined #yocto
hpsy[m] has joined #yocto
<Ad0>
thanks geoffhp
bps2 has quit [Ping timeout: 268 seconds]
<geoffhp>
Ad0: glad to help
yannd has joined #yocto
leon-anavi has joined #yocto
Guest49 has joined #yocto
<Guest49>
Good morning, besides configuring the image using recipes, what more (advanced) things are there to learn? I'm trying to become an advanced yocto user but I need to know what to learn first :)
kanavin has joined #yocto
<LetoThe2nd>
Guest49: that entirely depends on your use case, but generally I would say "creating and maintaining recipes" is one of the foundations.
<Guest49>
LetoThe2nd the use case is: "building custom images for custom devices", I am wondering what I should learn next (the topics) such that I can become a more advanced yocto user
<LetoThe2nd>
Guest49: "writing and maintaining recipes", "properly versioning your build set up"
<Ad0>
LetoThe2nd, the issue I had with boot was that the firmware files in dunfell were too old for my PI which had a newer revision of the PMIC leading to no boot
zpfvo has quit [Remote host closed the connection]
zpfvo has joined #yocto
florian_kc has quit [Ping timeout: 276 seconds]
xmn has joined #yocto
<rburton>
LetoThe2nd: someone should update the meta-rpi firmware in the stable branches :)
d-s-e has joined #yocto
florian has joined #yocto
amitk__ has joined #yocto
amitk_ has quit [Ping timeout: 276 seconds]
tunahan has quit [Quit: tunahan]
tunahan has joined #yocto
Schlumpf has quit [Ping timeout: 245 seconds]
<JaMa>
Mickal[m]: not sure if it's the exactly same root cause, but I had issues with openssl-sys when building solana in meta-webosose with kirkstone and upgrade to newer rust from langdale helped IIRC
starblue1 has quit [Ping timeout: 248 seconds]
d-s-e has quit [Ping timeout: 248 seconds]
starblue1 has joined #yocto
mahdi_sh has joined #yocto
<mahdi_sh>
Hello, Does anyone know any LTE/4G USB dongle that really works with Yocto based Linux?
xmn has quit [Quit: ZZZzzz…]
rber|res has quit [Ping timeout: 252 seconds]
rber|res has joined #yocto
Schlumpf has joined #yocto
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
yssh has joined #yocto
yssh has quit [Client Quit]
yssh has joined #yocto
bradfa has joined #yocto
tunahan has quit [Quit: tunahan]
tunahan has joined #yocto
amitk__ has quit [Ping timeout: 268 seconds]
jpuhlman has quit [Ping timeout: 268 seconds]
<__ad>
hi, i am in zeus, upgrading a recipe
<__ad>
getting
<__ad>
The license listed LGPL-2.1-or-later was not in the licenses collected for recipe util-linux
<__ad>
how should be proper way to remove such warning ?
amitk_ has joined #yocto
louis_ has joined #yocto
<RP>
__ad: add an entry for the license to the list of licenses in the recipe?
tunahan has quit [Quit: tunahan]
tunahan has joined #yocto
louis_ has quit [Ping timeout: 265 seconds]
d-s-e has joined #yocto
louis_ has joined #yocto
seninha has quit [Remote host closed the connection]
tgamblin has quit [Read error: Connection reset by peer]
tgamblin has joined #yocto
<tgamblin>
RP: excellent, thank you
<RP>
tgamblin: merged
<RP>
kanavin: I have patchelf and qemu upgrades being worked through FWIW
d-s-e has quit [Ping timeout: 240 seconds]
<kanavin>
RP: you mean version upgrades? I'm just starting now to work through these
<kanavin>
we probably need to unassign quite a bit more maintainers
<kanavin>
(though these, meaning all of AUH, with failed ones given priority)
yssh has quit [Quit: Client closed]
<sudip>
failed=67
mahdi_sh has quit [Quit: Client closed]
<__ad>
RP: thanks
seninha has joined #yocto
otavio has joined #yocto
seninha has quit [Quit: Leaving]
seninha has joined #yocto
prabhakarlad has quit [Quit: Client closed]
Xagen has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
otavio has quit [Quit: Lost terminal]
otavio has joined #yocto
rob_w has quit [Quit: Leaving]
otavio has quit [Client Quit]
otavio has joined #yocto
<RP>
kanavin: yes, those two failed and I'm listed as maintainer
<RP>
kanavin: we should perhaps email maintainers and ask if they still are able to handle them or if we should unassign ?
d-s-e has joined #yocto
<kanavin>
RP: yes, should you do that, or me?
<RP>
kanavin: Good question. I guess I should perhaps do it
tnovotny has joined #yocto
<RP>
kanavin: done
<kanavin>
RP: thanks, I suppose some will not reply at all, and if they've been otherwise inactive, their items go to unassigned
<RP>
kanavin: I wondered about asking people to confirm but lets see how this goes
<kanavin>
"One last word: please remember to be polite. We are all volunteers and cannot dedicate all of our time to Debian. Also, you are not aware of the circumstances of the person who is involved. Perhaps they might be seriously ill or might even have died — you do not know who may be on the receiving side. Imagine how a relative will feel if they read the e-mail of the deceased and find a very impolite, angry and accusing message!
<kanavin>
On the other hand, although we are volunteers, a package maintainer has made a commitment and therefore has a responsibility to maintain the package. So you can stress the importance of the greater good — if a maintainer does not have the time or interest anymore, they should let go and give the package to someone with more time and/or interest."
<RP>
kanavin: right, it is a balancing act
<kanavin>
RP: haha, debian has a whole team with their own infra and tooling specifically for this :) https://wiki.debian.org/Teams/MIA
<kanavin>
I think we can keep things simpler for now :)
<sudip>
but the MIA team are also volunteers :)
<RP>
kanavin: rburton is the most responsive maintainer to the email :)
<kanavin>
RP: other than me, who is in his own category ;)
<RP>
kanavin: right, we'd talked about it here and I know if you wanted to make changes I'd have already had patches :D
<kanavin>
'all you can eat' public transport, across all of Germany (not just Berlin), for 49 euros a month
<rburton>
you don't want to know how much a standard commuter monthly season ticket is for any town just outside london to the city would cost :)
<kanavin>
rburton, sadly, I do, as we have a friend living in High Wycombe
<rburton>
ah
<rburton>
i actually haven't looked at how much they cost now, i haven't commuted to london for quite some time now :)
<rburton>
yeah my old commute isn't cheap
<kanavin>
rburton, of course this kind of thing has to be subsidised, which is fine. I have no problem paying EU-level income tax rates, if I can jump on any train without thinking, or walk down any street at any time without worrying about getting stabbed.
rber|res has quit [Ping timeout: 268 seconds]
rber|res has joined #yocto
Xagen has joined #yocto
amitk_ has quit [Ping timeout: 265 seconds]
rber|res has quit [Ping timeout: 240 seconds]
rber|res has joined #yocto
amitk_ has joined #yocto
amitk_ has quit [Ping timeout: 268 seconds]
sakoman has joined #yocto
<zeddii>
crap. I've lost the link to the CFP for the OE dev day in prague, did the deadline come and go ?
<Mickal[m]>
I'll make a ticket/repro once I'm done. In the end for openssl-sys the issue is that in some case the build dependencies need a native library. In that case Cargo sets the TARGET and HOST to the same value. Ideally Yocto would be able to update the env accordingly when this happen, but this may require patching cargo I guess. Unless it supports making a wrapper for this kind of things (it's my early days with rust/cargo :))
<hutchman>
Tried to use devtool upgrade to go from lttng-tools 2.11 to 2.13 and it failed. Not sure next steps
<rburton>
hutchman: look at the failure, fix out how to fix it
<rburton>
RP: oh dear god
<hutchman>
Lets say I resolve all the conflicts, what's the next step? Cause the thing it was complaining about was a patch I don't think I needed so I skipped it and now devtool status says it's clean.
<rburton>
devtool update-recipe
<hutchman>
.. but yet I have no recipe in the workspace.
<hutchman>
I'm on dunfell using meta-freescale & poky on a i.MX8 if any of that matters.
<hutchman>
Wondering if it would be easier to just edit my current recipe an have it pull new source and patches that's on mainline.
<Saur[m]>
hutchman: An alternative may be to look at the difference between Dunfell and master for the lttng-tools recipe. Since the latter is using 2.13, all information should be there as what needs to be done for upgrading.
<hutchman>
Sometimes I've gotten away with stealing the .bb from a newer release but that trick didn't work this time either.
<hutchman>
I keep trying to use these fancy upgrade tools that are talked about at ELC etc. and I can't ever appear to get them to work ha, ha.
<hutchman>
Sure, timo gets it to work for Nano but anything that is a complicated pkg always has issues I can't figure out.
<Saur[m]>
Well, upgrading from 2.11 to 2.13 is a pretty big leap and (based on the differences between Dunfell and master) so I would expect it to be non-trivial.
<hutchman>
RP indeed!
<hutchman>
kirkstone is earliest 2.13 shows up unfortunately.
<hutchman>
So how would you "well versed" guys go about it?
<nerdboy>
<sigh> i think my build env finally broke my build
<nerdboy>
khem: is gcc 13.1.0/binutils 2.40 "approved"?
<hutchman>
lttng-modules for 2-13 built ironically by stealing the latest recipe but lttng-tools did not. Kept saying it depended on "${LTTNGMODULES}" and I can't figure out what it's talking about. lttng-modules built!
<hutchman>
Commcast still treating you ok khem?
jclsn has quit [Quit: WeeChat 3.8]
jclsn has joined #yocto
<Saur[m]>
hutchman: `LTTNGMODULES` is defined in `meta/recipes-kernel/lttng/lttng-platforms.inc`. That file does not exist in Dunfell, so if you did not copy that too when you copied the `lttng-tools` recipe, then the variable will not be defined.
<hutchman>
Yeah, I just realized I missed a .inc file. Fixed it a bit ago and got a bit further.
mvlad has quit [Remote host closed the connection]
<hutchman>
Got past more, now liburcu needs updated
Xagen has quit [Ping timeout: 246 seconds]
camus1 has joined #yocto
camus has quit [Ping timeout: 250 seconds]
camus1 is now known as camus
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
seninha has joined #yocto
seninha has quit [Remote host closed the connection]
seninha has joined #yocto
seninha has quit [Remote host closed the connection]