LetoThe2nd changed the topic of #yocto to: Welcome to the Yocto Project | Learn more: https://www.yoctoproject.org | Community: https://www.yoctoproject.org/community | IRC logs: http://irc.yoctoproject.org/irc/ | Having difficulty on the list, with someone on the list or on IRC, contact Yocto Project Community Manager Letothe2nd | CoC: https://www.yoctoproject.org/community/code-of-conduct
frgo has joined #yocto
florian has quit [Ping timeout: 265 seconds]
frgo has quit [Ping timeout: 252 seconds]
dgriego has quit [Quit: Computer going to sleep]
dgriego has joined #yocto
tammranil has quit [Remote host closed the connection]
tammranil has joined #yocto
konsgn has joined #yocto
konsgn has left #yocto [#yocto]
frgo has joined #yocto
dgriego has quit [Quit: Computer going to sleep]
frgo has quit [Ping timeout: 252 seconds]
frgo has joined #yocto
dgriego has joined #yocto
frgo has quit [Ping timeout: 246 seconds]
dgriego has quit [Quit: Computer going to sleep]
enok has joined #yocto
enok has quit [Ping timeout: 268 seconds]
jclsn has quit [Ping timeout: 272 seconds]
jclsn has joined #yocto
frgo has joined #yocto
frgo has quit [Ping timeout: 260 seconds]
frgo has joined #yocto
frgo has quit [Ping timeout: 268 seconds]
starblue has quit [Ping timeout: 248 seconds]
starblue has joined #yocto
frgo has joined #yocto
frgo has quit [Ping timeout: 246 seconds]
frgo has joined #yocto
frgo has quit [Ping timeout: 268 seconds]
frgo has joined #yocto
frgo has quit [Ping timeout: 246 seconds]
vvn has joined #yocto
frgo has joined #yocto
uartz has quit [Ping timeout: 272 seconds]
frgo has quit [Ping timeout: 265 seconds]
mj_ has quit [Quit: Reconnecting]
crazy_imp has joined #yocto
vvn has quit [Quit: WeeChat 4.5.1]
frgo has joined #yocto
frgo has quit [Ping timeout: 268 seconds]
frgo has joined #yocto
frgo has quit [Ping timeout: 276 seconds]
frgo has joined #yocto
frgo has quit [Ping timeout: 244 seconds]
frgo has joined #yocto
frgo has quit [Ping timeout: 245 seconds]
enok has joined #yocto
frgo has joined #yocto
leon-anavi has joined #yocto
frgo has quit [Ping timeout: 276 seconds]
frgo has joined #yocto
frgo has quit [Read error: Connection reset by peer]
frgo_ has joined #yocto
frgo_ has quit [Remote host closed the connection]
frgo has joined #yocto
rob_w has joined #yocto
prabhakalad has quit [Quit: Konversation terminated!]
prabhakalad has joined #yocto
CrazyGecko has joined #yocto
mckoan|away is now known as mckoan
Kubu_work has joined #yocto
rfuentess has joined #yocto
BoergeSt has joined #yocto
goliath has joined #yocto
florian has joined #yocto
florian has quit [Client Quit]
florian has joined #yocto
kanavin_ has joined #yocto
kanavin has quit [Ping timeout: 252 seconds]
florian has quit [Read error: Connection reset by peer]
florian_kc has joined #yocto
florian_kc is now known as florian
<qschulz> tgamblin: not sure there's going to be a v5 but I changed it locally already so if i need to send one it should be ready already :)
ablu has quit [Ping timeout: 268 seconds]
enok has quit [Ping timeout: 265 seconds]
ablu has joined #yocto
vThor has quit [Read error: Connection reset by peer]
vThor has joined #yocto
vThor has quit [Changing host]
vThor has joined #yocto
<RP> qschulz: quick question - in poky, should the component b4 config files be present or not (e.g. the one in yocto-docs)?
<qschulz> RP: as far as I could tell, they don't matter because regardless of where you're running b4 from within poky git repo, the one at the root of the git repo will be used
<qschulz> if that was your question
<RP> qschulz: it was, thanks
<qschulz> I can triple check from b4 source code if you want
<qschulz> "A project may ship their own b4 configuration file with some defaults, located at the top-level of the git tree."
<qschulz> seems to confirm this
druppy has joined #yocto
<mcfrisk> rburton: could genericarm64 default to 6.12 kernel? testing 6.6 with poky-altcfg is not that useful since a lot of features are not in the kernel
druppy has quit [Ping timeout: 260 seconds]
<mcfrisk> I presume poky-altcfg is frozen to the alternative kernel 6.6
<mcfrisk> if I want to test genericarm64 with latest stable kernel and systemd, I need to manually tweak the machine or distro config now. local.conf override for kernel update doesn't work in poky-altcfg. and plain poky distro doesn't build with systemd by default, though that I could override in local.conf
<mcfrisk> then systemd-serialgetty seems to be slowing boot to systemd "running" state by minutes while real serial console login already works as it was started by systemd/udev
<RP> qschulz: it is fine, I just wanted to check before I try and merge things
<RP> mcfrisk: if 6.6 doesn't work, we should probably be disabling it
<mcfrisk> RP: it does work for serial console but for more advanced things like graphics not. kanavin_ said that poky-altcfg selection of 6.6 kernel is on purpose and thus I did not think we can change it.
<mcfrisk> for genericarm64 machine, I think testing latest stable kernel is better to catch regressions earlier, and broad HW support without systemd and udev is not really working
<RP> mcfrisk: we are supposed to test both kernels
<mcfrisk> both kernel, with both sysvinit and systemd? AFAIK, official builds are only poky with latest kernel and sysvinit, and poky-altcfg for old stable kernel and systemd.
<RP> mcfrisk: both kernels and both initsystems, we don't test all four combinations
<RP> zeddii: are we keeping 6.6 for this release?
<mcfrisk> yes, that's the problem for me. latest stable kernel and systemd is not an official configuration from poky or poky-altcfg
vquicksilver has quit [Quit: WeeChat 4.4.2]
vquicksilver has joined #yocto
<kanavin_> mcfrisk, there's only so many combinations we can test :-/
<RP> qschulz: I've merged it. I created a commit for meta-yocto
<RP> Hopefully i got it all right
<mcfrisk> kanavin_: I know, but testing newer kernels with systemd makes sense too, and many features need it. This could be a genericarm64 thing if rburton agrees.
<RP> mcfrisk: but then where does the 6.6 kernel get tested with genericarm64?
<mcfrisk> but then I would like poky-altcfg to allow overriding kernel version in machine config
<qschulz> RP: .b4-config in poky looks ok, so I guess it is :)
<qschulz> RP: thanks!
<RP> qschulz: thanks for working through it :)
<mcfrisk> RP: good question
<qschulz> RP: any plan on backporting it to older releases?
<qschulz> FWIW, we should be able to add send-prefixed to .b4-config for older releases
<qschulz> and it would add the branch the patch was developed against
<kanavin_> mcfrisk, maybe you can convince the vendor (e.g. ARM) to do this testing, rather than 'official yocto'
<qschulz> (a different send-prefixed will be needed for each branch of course)
<qschulz> send-prefixes*
<RP> qschulz: hmm, this is straying into feature territory but I can see the advantage to doing it
<qschulz> RP: i'm not pushing for it, the answer could be "don't know yet" or "let's see how it goes with master first"
<qschulz> I believe the send-prefixes one could be beneficial to the project
<RP> qschulz: I'm leaning to the latter, lets test this with master
<qschulz> RP: cool, will check with agodard what's our plan(s) for the yocto-docs part
<qschulz> how to document it since we only can use it on the master branch for now
<RP> sakoman: you might find the above food for thought...
<qschulz> RP: ah, I just realized I should have made changes to .b4-config return a To to the poky ML
<qschulz> (it's not a big deal)
<qschulz> because this script is only used when in poky git repo, so we know the .b4-config is poky's!
<RP> qschulz: we can patch things :)
<qschulz> and when changing OE-Core's .b4-config, this can only be done from OE-Core git repo
<qschulz> which doesnt' call this script at all :)
<qschulz> RP: will do :)
<qschulz> RP: thanks for your patience and the poky-config patch, I hope this will make contribution easier
<mcfrisk> kanavin_ RP : answer to testing 6.6 kernel is poky stable branch, not master branch
<RP> qschulz: I figured I know combo-layer better than anyone else at this point
<RP> mcfrisk: we don't do something different on release branches from development, that would be madness
<qschulz> RP: the difficult part is I don't think anyone uses that tool except the maintainer? So that makes it a bit less accessible :)
<RP> qschulz: right, it is just steve and I and sometimes rburton
<mcfrisk> RP: that is fine, 6.6 kernel will be tested in poky and poky-altcfg builds from stable/LTS branch. master should move away from it.
<rburton> RP mcfrisk: i tried that v4 uki/systemd series in meta-arm ci and it still fails
<rburton> 2025-02-05 21:41:17 - INFO - | NOTE: Signing systemd-boot binary /builds/software/yocto/meta-arm/work/build/tmp/work/cortexa57-poky-linux/systemd-boot/257.1/build/src/boot/efi/systemd-bootaa64.efi with /builds/software/yocto/meta-arm/work/build/sbkeys/db.key and /builds/software/yocto/meta-arm/work/build/sbkeys/db.crt
<rburton> 2025-02-05 21:41:17 - INFO - | Error reading file /builds/software/yocto/meta-arm/work/build/tmp/work/cortexa57-poky-linux/systemd-boot/257.1/build/src/boot/efi/systemd-bootaa64.efi: No such file or directory
<mcfrisk> rburton: you need to take https://lists.yoctoproject.org/g/meta-arm/message/6350 too, Jon rejected that because of the failures in ukify which the poky side series fixes
<rburton> aha thanks
<mcfrisk> I've been testing this and the upstream systemd fixes on meta-arm qemuarm64-secureboot builds with all oeqa tests enabled
<rburton> ok fired again, cheers
<mcfrisk> no problem, it should pass. if not, just let me know
jmiehe has joined #yocto
ThomasRoos has joined #yocto
<ThomasRoos> Has anyone installed openssl 1 and 3 together in a image yet?
florian has quit [Ping timeout: 260 seconds]
Schlumpf has joined #yocto
<Schlumpf> Hi, stupid question: I have an image with an application, that uses GTK+3. If I populate a SDK for this image, the gtk3 headers and pkg-config .pc files are missing. Why?
ThomasRoos has quit [Quit: Client closed]
ThomasRoos has joined #yocto
enok has joined #yocto
enok has quit [Client Quit]
enok has joined #yocto
enok has quit [Read error: Connection reset by peer]
enok has joined #yocto
florian has joined #yocto
florian_kc has joined #yocto
florian has quit [Ping timeout: 248 seconds]
<rburton> Schlumpf: shouldn't be. can you replicate that with eg the core-image-sato sdk?
jmiehe has quit [Quit: jmiehe]
enok has quit [Ping timeout: 268 seconds]
enok has joined #yocto
ptsneves has joined #yocto
<zeddii> RP: No, I planned on removing it, was waiting for M3, and then with FOSDEM fell behind on actually doing it. I'll send that with my next series.
<RP> zeddii: great, that will sort the problem then :)
<RP> zeddii: I thought that was the plan but I could have lost track
olani_ has joined #yocto
cyxae has joined #yocto
amitk_ has joined #yocto
amitk has quit [Ping timeout: 246 seconds]
rob_w has quit [Remote host closed the connection]
rob_w has joined #yocto
mkazantsev has joined #yocto
florian_kc is now known as florian
kanavin_ has quit [Remote host closed the connection]
rob_w has quit [Ping timeout: 244 seconds]
kanavin_ has joined #yocto
mckoan is now known as mckoan|away
mkazantsev has quit [Quit: Leaving]
goliath has quit [Quit: SIGSEGV]
uartz has joined #yocto
olani_ has quit [Ping timeout: 260 seconds]
olani_ has joined #yocto
<rburton> RP: fwiw I approve of mikko's patches
Minvera has joined #yocto
Xagen has joined #yocto
olani_ has quit [Remote host closed the connection]
<RP> rburton: which ones? :)
<rburton> well i tested v4
behanw has joined #yocto
<RP> rburton: so no the meta-yocto-bsp one for example? :)
<RP> rburton: but I do know know which ones you mean
* mcfrisk sends too many patches, rburton talks about systemd-boot-native/ukify :)
<rburton> yes :)
dgriego has joined #yocto
frgo has quit [Remote host closed the connection]
frgo has joined #yocto
goliath has joined #yocto
Schlumpf has quit [Quit: Client closed]
enok has quit [Ping timeout: 276 seconds]
zhmylove has joined #yocto
<zhmylove> Hello! Is there any way to share a single python dict() between tasks? Even any dirty ways? I don't want to write it in file and read it hundreds times
jmiehe has joined #yocto
<rburton> if there was, can you _guarantee_ that with sstate involved and short-circuiting lots of operations that it would make sense still?
frgo has quit [Remote host closed the connection]
frgo has joined #yocto
<rburton> like what if only one of the tasks re-ran in a build
<rburton> much easier to write a file. pickle it if speed is a priority.
jmiehe has quit [Client Quit]
dgriego has quit [Quit: Computer going to sleep]
<zhmylove> I need to share read-only data structure being created at the stage of sstate cache checking with tasks defined in sstate.bbclass
<zhmylove> I can guarantee, yes
<zhmylove> I do not want pickle and write to a temp file
<rburton> maybe explain what you're trying to do because there might be a better way?
dgriego has joined #yocto
<zhmylove> OK, I'll try. Right now I'm creating index file for my 156 sstate-cache servers. Yocto is really slow now iterating over those servers
<zhmylove> It asks for each cachefile all of them with HEAD query
<rburton> sounds like the fix would be to implement a session cache so it can pipeline the requests
<zhmylove> I have dict() with key = sstatefile and value = mirror url. I want to share it with tasks inherited from sstate.bbclass in order to shor-circuit cache search
<zhmylove> The problem is not in sessions. The problem is that Yocto iterates over the sstate mirror URLs one by one for each task
<zhmylove> Given 6000 tasks and 156 servers it results into a 1 million of HEAD queries
<rburton> 156 servers?!
<zhmylove> YES
<Slimey> thats over 9000
<rburton> erm why
dgriego has quit [Client Quit]
dgriego has joined #yocto
<zhmylove> Our system is very distributed due to power loss issues. Moreover, all those 156 sstate cache servers sometimes keep their different versions of cache
<zhmylove> BTW returning to my question. How can I share a data structure constructed before do_* tasks executed with them?
<rburton> you can add something to d before any tasks run but each task has a copy-on-write clone of the data store so you need to be sneaky
<rburton> i still say you're working around the wrong thing. don't have 156 separate sstate mirrors, or maybe bitbake should stop iterating when it finds a match
<rburton> as you admit that your mirrors are not in sync, it sounds like your solution should be a proper distributed file store
<zhmylove> Yeah, this optimization is clearly our future plan. Thank you Ross! And have a nice day!
zhmylove has quit [Quit: Leaving]
druppy has joined #yocto
mjm has joined #yocto
florian has quit [Ping timeout: 260 seconds]
rfuentess has quit [Remote host closed the connection]
ptsneves has quit [Ping timeout: 245 seconds]
florian has joined #yocto
druppy has quit [Ping timeout: 252 seconds]
florian has quit [Ping timeout: 252 seconds]
dmoseley_ has joined #yocto
dmoseley has quit [Ping timeout: 248 seconds]
leon-anavi has quit [Quit: Leaving]
ThomasRoos has quit [Quit: Client closed]
cabazon has joined #yocto
jmiehe has joined #yocto
BoergeSt has quit [Quit: WeeChat 4.1.1]
Vonter has quit [Ping timeout: 248 seconds]
Vonter has joined #yocto
cabazon has quit [Quit: Client closed]
frgo_ has joined #yocto
frgo_ has quit [Read error: Connection reset by peer]
frgo has quit [Ping timeout: 244 seconds]
druppy has joined #yocto
frgo has joined #yocto
mkazantsev has joined #yocto
pbsds35 has quit [Quit: The Lounge - https://thelounge.chat]
pbsds35 has joined #yocto
Kubu_work has quit [Quit: Leaving.]
mkazantsev has quit [Remote host closed the connection]
frgo has quit [Read error: Connection reset by peer]
frgo_ has joined #yocto
frgo_ has quit [Read error: Connection reset by peer]
frgo has joined #yocto
cyxae has quit [Quit: cyxae]
Lihis has quit [Quit: Quitting]
Lihis has joined #yocto
florian has joined #yocto
frgo has quit [Remote host closed the connection]
frgo has joined #yocto
<rburton> hm
<rburton> ERROR: dbus-1.16.0-r0 do_package_qa: QA Issue: File /usr/lib/systemd/user/dbus.socket in package dbus-common contains reference to TMPDIR [buildpaths] <-- anyone seen that?
<rburton> (mathieudb specifically ;)
frgo has quit [Ping timeout: 252 seconds]
florian has quit [Remote host closed the connection]
frgo has joined #yocto
florian has joined #yocto
frgo has quit [Ping timeout: 244 seconds]
frgo has joined #yocto
frgo has quit [Ping timeout: 245 seconds]
druppy has quit [Ping timeout: 268 seconds]
Xagen has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
enok has joined #yocto
frgo has joined #yocto
frgo has quit [Ping timeout: 268 seconds]
jmiehe has quit [Quit: jmiehe]
enok has quit [Quit: enok]
enok71 has joined #yocto
GNUmoon has quit [Ping timeout: 264 seconds]
frgo has joined #yocto
enok71 has quit [Ping timeout: 252 seconds]
frgo has quit [Ping timeout: 252 seconds]
<khem> Equinix is shutting down its operations with us on April 30, 2025. They have graciously supported us for almost 5 years, but all good things come to an end.
<khem> shows up when you go to https://gitlab.freedesktop.org/
<khem> so I wonder if its another SRC_UTI rewrite time coming in few months
<khem> hope it finds a new home soon
frgo has joined #yocto
frgo has quit [Ping timeout: 252 seconds]
frgo has joined #yocto
frgo has quit [Ping timeout: 252 seconds]
frgo has joined #yocto
frgo has quit [Ping timeout: 252 seconds]
florian has quit [Ping timeout: 252 seconds]
sotaoverride has quit [Killed (silver.libera.chat (Nickname regained by services))]
ctraven has joined #yocto
goliath has quit [Quit: SIGSEGV]