Wouter0100 has quit [Remote host closed the connection]
Wouter0100 has joined #yocto
ziga has joined #yocto
zpfvo has joined #yocto
zpfvo has quit [Ping timeout: 240 seconds]
zpfvo has joined #yocto
zpfvo has quit [Ping timeout: 256 seconds]
zpfvo has joined #yocto
tnovotny has joined #yocto
Schlumpf has joined #yocto
leon-anavi has joined #yocto
tnovotny has quit [Quit: Leaving]
agners has quit [Quit: WeeChat 3.4]
Habbie has quit [Ping timeout: 260 seconds]
manuel1985 has quit [Ping timeout: 240 seconds]
dev1990 has joined #yocto
Habbie has joined #yocto
dev1990 has quit [Quit: Konversation terminated!]
dev1990 has joined #yocto
dev1990 has quit [Quit: Konversation terminated!]
zpfvo has quit [Ping timeout: 256 seconds]
zpfvo has joined #yocto
mvlad has joined #yocto
zpfvo has quit [Ping timeout: 240 seconds]
zpfvo has joined #yocto
zpfvo has quit [Ping timeout: 240 seconds]
zpfvo has joined #yocto
tre has joined #yocto
BCMM has joined #yocto
BCMM has quit [Client Quit]
BCMM has joined #yocto
zpfvo has quit [Ping timeout: 256 seconds]
zpfvo has joined #yocto
zpfvo has quit [Ping timeout: 256 seconds]
zpfvo has joined #yocto
Vonter has quit [Ping timeout: 256 seconds]
zpfvo has quit [Ping timeout: 256 seconds]
zpfvo has joined #yocto
Vonter has joined #yocto
zpfvo has quit [Ping timeout: 256 seconds]
zpfvo has joined #yocto
creich_ has joined #yocto
creich has quit [Ping timeout: 252 seconds]
<coldspark29[m]>
Is it safe to share the sstate-cache among all builds?
<coldspark29[m]>
For different boards I mean
pgowda_ has joined #yocto
olani has quit [Ping timeout: 256 seconds]
zpfvo has quit [Ping timeout: 240 seconds]
zpfvo has joined #yocto
zpfvo has quit [Ping timeout: 252 seconds]
zpfvo has joined #yocto
Schlumpf has quit [Ping timeout: 256 seconds]
chep` has joined #yocto
chep- has joined #yocto
<rburton>
yes
<rburton>
its safe to share it among *all* builds
chep has quit [Ping timeout: 256 seconds]
chep- is now known as chep
chep` has quit [Ping timeout: 240 seconds]
xmn has joined #yocto
zpfvo has quit [Ping timeout: 240 seconds]
zpfvo has joined #yocto
<RP>
rburton, jonmason: We're seeing lots of this systemtap crash on the 5.10 kernel used by poky-altcfg. I have a kernel back trace
<RP>
I guess I should create the bug
<rburton>
please
<rburton>
i need to eat in 10 minutes before a call :)
zpfvo has quit [Ping timeout: 240 seconds]
zpfvo has joined #yocto
<vd>
hi there -- still on runqemu, it seems like it's running because I was 100% CPU usage, but I don't have console, even though I use "serial" or "serialstdio" runqemu options. Any idea how to debug this?
<vd>
(or accessing the tcpserial from outside the container where runqemu is running is an option too)
zpfvo has quit [Ping timeout: 256 seconds]
zpfvo has joined #yocto
chep has quit [Read error: Connection reset by peer]
<vd>
I think there's an issue with failing to start a VNC server. How can I disable that from runqemu?
<JPEW>
vd: There are some options to disable the GUI I think
<JPEW>
I forget what they are off the top of my head
<vd>
it seems to be caused by -serial mon:vc (^C or ^A+c doesn't work)
Vonter has joined #yocto
chep has quit [Read error: Connection reset by peer]
chep has joined #yocto
chep has quit [Read error: Connection reset by peer]
chep has joined #yocto
Guest21 has joined #yocto
<Guest21>
hi Yocto Wizards, from the it's to use {AUTOREV} var to grab the last commit, but is it possible to grab the last tagged commit ? Thx
chep` has joined #yocto
<Guest21>
to add info, of course we didn't know the tag name in advance...
chep has quit [Ping timeout: 256 seconds]
<JPEW>
Guest21: I would setup an automated job to upgrade the recipe to the latest tagged commit and push a change for it; devtool can help with that
<JPEW>
That's what we do at least
<Guest21>
JPEW do you have some tips yet ?
chep` has quit [Ping timeout: 256 seconds]
<JPEW>
The nuts and bolts are highly dependent on your CI/git setup; but if you look into `devtool upgrade` it can help with the actual upgrading of the recipe
<vd>
I don't understand how runqemu defaults to -serial mon:vc, I'm not specifying any of QB_* variables nor inheriting any qemu machine config. Yet the default from qemuboot.bbclass isn't applied
akiCA has joined #yocto
tre has quit [Remote host closed the connection]
<sgw>
RP: looking
codavi has joined #yocto
zpfvo has quit [Ping timeout: 252 seconds]
zpfvo has joined #yocto
<RP>
michaelo: Just looking at the stable docs changes you merged - shouldn't we merge that fix to master first?
tnovotny has quit [Remote host closed the connection]
tnovotny has joined #yocto
chep has joined #yocto
<sgw>
RP: when I tried master-next with meta-oe, I got a cmake-native:do_configure failure! Not sure what else changed, but trying my perl patch with master instead (which built)
dmoseley has joined #yocto
goliath has joined #yocto
manuel1985 has joined #yocto
mabnhdev2 has joined #yocto
<mabnhdev2>
Hi. The last time I looked at the Releases Wiki, Dunfell was scheduled for EOL in April, 2022. Now, I see it has been extended to April, 2024. Is that correct? Can I safely count on that?
<kanavin_>
mabnhdev2, you should come up with a transition plan regardless, or you'll end up with a mountain to climb when it does end
mariusz1 has quit [Ping timeout: 256 seconds]
<RP>
kanavin_: thanks for the patch! :)
<mabnhdev2>
kanavin_: Understood. My main problem is that I still require meta-python2 and meta-openssl102 for a while. I am in a very slow transition from python2 to python3. I have no upgrade plan for openssl102 yet. If those two layers become available in Kirkstone, then I'll be able to upgrade.
* RP
wonders how to tell the difference between these two rpms. It is looking like the compression differs somehow :(
<kanavin_>
mabnhdev2, if you need those layers, then take over maintaining them. Don't expect that someone else will make them 'available'.
<kanavin_>
RP: cheers, those virgl failures are usually due to a missing entry in distro excusion list, or vgem module not having been provisioned, or incorrect permissions on the render node device
<kanavin_>
RP: I'm slightly concerned that alma sets minor revisions in distro identifiers (/etc/os-release), so this will have to be updated more often than centos 8 was
<kanavin_>
maybe this could be special-cased in meta/lib/oe/lsb.py
<RP>
kanavin_: I guessed that may be the case but decided you'd probably find the right change easier than I would. The minor version could get a little annoying :/
<mabnhdev2>
kanavin_: Not as simple as that. With those layers, it's not as much that they need to be maintained as they are legacy, but it's more making sure the the rest of the layers don't do anything that forces those layers into EOL. I suspect that would be or will soon become a sisyphean effort.
<RP>
JPEW: thanks :)
<RP>
kanavin_: so one every six months. Could be worse I guess
<kanavin_>
RP: I guess next time alma bumps the minor version, we could add code that strips that
<RP>
kanavin_: sounds like a plan
zpfvo has quit [Remote host closed the connection]
zpfvo has joined #yocto
<kanavin_>
mabnhdev2, I get ya, so you need a real plan and schedule to transition away, and management's commitment to it
<kanavin_>
but yes, you do have until spring 2024
<kanavin_>
the problem is that the more you delay it, the bigger the delta to 'current yocto' becomes
<mabnhdev2>
kanavin_: Yeah, but that's just a different sisyphean effort:) . Anyway you look at it, that rock is just going to roll over me.
tnovotny has quit [Quit: Leaving]
<vd>
QB_SERIAL_OPT is broken somehow, its default in never used
Vonter has quit [Quit: WeeChat 3.4]
vladest has quit [Remote host closed the connection]
vladest has joined #yocto
Guest21 has quit [Ping timeout: 256 seconds]
<michaelo>
RP: these patching documentation changes are in master-next too. I submitted the stable updates to the docs@ mailing list and nobody objected, so I wanted to empty my pipe :)
pgowda_ has quit [Quit: Connection closed for inactivity]
prabhakarlad has quit [Quit: Client closed]
zpfvo has quit [Quit: Leaving.]
kanavin_ has quit [Ping timeout: 240 seconds]
kanavin_ has joined #yocto
prabhakarlad has joined #yocto
<RP>
michaelo: we do have a strict backport policy though so I *have* to take them to master now ;-)
Tokamak has joined #yocto
dev1990 has joined #yocto
creich_ has quit [Quit: Leaving]
creich has joined #yocto
<michaelo>
RP> Oops, understood. So no backports before going to master. I'll remember this next time. Apologies for the trouble. By the way, don't hesitate to merge master-next as it currently is... This will make my life simpler.
florian_kc has joined #yocto
mabnhdev2 has quit [Quit: Client closed]
Guest86 has quit [Ping timeout: 256 seconds]
Tokamak has quit [Read error: Connection reset by peer]
Tokamak has joined #yocto
florian_kc has quit [Ping timeout: 240 seconds]
florian_kc has joined #yocto
vladest has quit [Remote host closed the connection]
<tgamblin>
khem: no issue, I was just looking for that myself because it wasn't in my latest patch build
<tgamblin>
khem: sent a new PR
<khem>
k
<RP>
sgw: were you able to reproduce that meta-oe issue?
<khem>
RP: perl issue ? he sent a v2
<RP>
khem: ah, yes, great :)
<khem>
he was able to and he has restricted the threading to target perl alone in v2 which fixes those 2 issue
* RP
hadn't got there yet
amitk has quit [Ping timeout: 256 seconds]
<sgw>
khem: RP: we might consider removing it again in the future though! Next is 64bit issues in perl!
<sgw>
not sure if people have really noticed though (other than the ones asking for it here).
BCMM has joined #yocto
<sgw>
RP: switching gears, I was looking at how to move kernel:do_strip() into package.py:runstrip(), biggest issue is how to get the KERNEL_IMAGE_STRIP_EXTRA_SECTIONS into runstrip()
<sgw>
I was not sure if I could just a "d" to the runstrip() method
<RP>
sgw: not with the parallelism issues. You're better off just passing in a string
<RP>
sgw: I think multiple processes are ivolved
<sgw>
Ok, so add a 4th arg to runstrip(), yes it is.
<RP>
sgw: if it is the code I think it is, it will be much less pain
mariusz1 has joined #yocto
florian_kc has quit [Ping timeout: 240 seconds]
Tokamak has quit [Ping timeout: 268 seconds]
Tokamak has joined #yocto
<vd>
IMAGE_CLASSES += "qemuboot" is more a distro, or machine conf thing?
<vd>
isn't it the responsibility of the distro to tweak images? While the responsibility of the machine is more to tweak base pacakges like packagegroup-core-boot and package-machine-base
mvlad has quit [Remote host closed the connection]