qschulz has quit [Remote host closed the connection]
qschulz has joined #yocto
florian_kc has quit [Ping timeout: 252 seconds]
goliath has quit [Quit: SIGSEGV]
rber|res has joined #yocto
RobertBerger has quit [Ping timeout: 252 seconds]
sakoman has quit [Quit: Leaving.]
dmoseley has joined #yocto
geoffhp has joined #yocto
Vonter has joined #yocto
jmiehe1 has joined #yocto
jmiehe has quit [Ping timeout: 256 seconds]
jmiehe1 is now known as jmiehe
camus1 has joined #yocto
camus has quit [Ping timeout: 252 seconds]
camus1 is now known as camus
vd has quit [Ping timeout: 256 seconds]
wwilly has joined #yocto
wwilly has quit [Remote host closed the connection]
wwilly has joined #yocto
geoffhp has quit [Quit: Leaving]
kanavin_ has joined #yocto
kanavin has quit [Read error: Connection reset by peer]
kanavin_ has quit [Remote host closed the connection]
kanavin_ has joined #yocto
wwilly has quit [Ping timeout: 256 seconds]
wwilly has joined #yocto
goliath has joined #yocto
wwilly has quit [Ping timeout: 252 seconds]
pgowda_ has joined #yocto
kanavin_ has quit [Ping timeout: 252 seconds]
wwilly has joined #yocto
Starfoxxes has quit [Ping timeout: 268 seconds]
goliath has quit [Quit: SIGSEGV]
kanavin has joined #yocto
Starfoxxes has joined #yocto
florian_kc has joined #yocto
jmiehe has quit [Quit: jmiehe]
florian_kc has quit [Ping timeout: 252 seconds]
xmn has joined #yocto
Guest2183 has quit [Quit: WeeChat 3.1]
kroon has joined #yocto
<kroon>
Shouldn't bitbake detect modified python functions in .bbclass:es and rerun tasks as is appropriate ? Or do I have to help it in some way by being explicit about dependent variables ?
<RP>
kroon: it will detect functions if they are task specific in most cases
<RP>
kroon: so it depends which python function and what the function changes
florian_kc has joined #yocto
florian_kc is now known as florian
florian has quit [Ping timeout: 252 seconds]
<kroon>
RP, whatabout "process_file_linux()" in chrpath.bbclass ?
<RP>
kroon: at the very least the python parser won't see through that function name manipulation I suspect
<kroon>
aha
alejandrohs has quit [Ping timeout: 256 seconds]
jpuhlman_ has joined #yocto
maoti__ has quit [Ping timeout: 252 seconds]
nodeboy[m] has joined #yocto
<jaskij[m]>
RP: those CMake toolchain files I wanted to make for easier IDE setup? CLion (my IDE of choice) added support for using environment setup scripts in latest release, even specifically using Yocto as an example in their release post (albeit 1.8...)
<jaskij[m]>
I'll still try to get on it during Christmas (both that and that dependency script I wrote are on the back burner for now due to real life stuff)
pgowda_ has quit [Quit: Connection closed for inactivity]
<RP>
jaskij[m]: thanks for the info. Cool that the IDE is supporting the scripts
<RP>
jaskij[m]: I would love to improve if we can somehow
<jaskij[m]>
My weekends are unfortunately quite busy currently, but I have a staycation planned for at least two weeks over the Christmas and New Year period. I will look into generating those extra CMake toolchain files like we discussed some time ago then.
<jaskij[m]>
I don't do any C or C++ nowadays, but will try figuring something out with a demo project or something.
goliath has joined #yocto
CosmicPenguin has quit [Ping timeout: 245 seconds]
CosmicPenguin has joined #yocto
<RP>
jaskij[m]: time is a challenge but happy to have any help if/as/when you can, thanks
<jaskij[m]>
RP: for the CMake part I have a template more or less written, so I think I'll just file an issue for OE core including it and will go from there if no one picks up the generation in the meantime.
florian has joined #yocto
<RP>
jaskij[m]: sounds good, documenting where things are at does help a lot
<RP>
rburton: I think I found out why your libxkbcommon patches break things, debian.bbclass bug
<RP>
Another week, another vim CVE
ana_gasi has quit [Ping timeout: 256 seconds]
<jaskij[m]>
it's so bad?
<jaskij[m]>
(issue filed)
florian has quit [Ping timeout: 252 seconds]
<RP>
jaskij[m]: I think someone did some kind of security analysis against it so we're seeing one or two a week for the several weeks
<jaskij[m]>
wow
rber|res has quit [Quit: Leaving]
Wouter0100 has quit [Remote host closed the connection]
<smurray>
RP: I wasn't looking down in lib, see it now
<RP>
smurray: the checks have had a few tweaks alreadt
<smurray>
RP: I can put in some entries to get it passing, may need discuss with dl9pf to nail down some of them
<RP>
smurray: probably good thinks to get nailed down :)
<smurray>
RP: I didn't think the layers other than meta-agl-core were getting checked in that repo, tbh
<RP>
smurray: we could always remove it as an alternative
<RP>
smurray: I think we added what passed the tests previously
jmiehe has joined #yocto
<smurray>
RP: if they're all being tested now, better to keep them, not hard to fix the READMEs
<RP>
smurray: that is what I was thinking
<RP>
smurray: these are just the layer compat checks, not builds
<smurray>
RP: I'll push something after the F1 race
bradfa has quit []
bradfa has joined #yocto
Vonter has quit [Ping timeout: 256 seconds]
camus has quit [Quit: camus]
vd has joined #yocto
awafaa has quit [Read error: Connection reset by peer]
awafaa has joined #yocto
kroon has quit [Quit: Leaving]
kroon has joined #yocto
wwilly_ has joined #yocto
kroon has quit [Remote host closed the connection]
kroon has joined #yocto
chep has quit [Read error: Connection reset by peer]
chep has joined #yocto
stkw0 has quit [Quit: No Ping reply in 180 seconds.]
sakoman has quit [Ping timeout: 256 seconds]
stkw0 has joined #yocto
bunk_ has joined #yocto
sakoman has joined #yocto
wwilly has quit [Ping timeout: 256 seconds]
bunk has quit [Ping timeout: 256 seconds]
sakoman has quit [Quit: Leaving.]
<kroon>
RP, while looking at the perl reproducibility issues it occured to me that maybe the sstate code should disallow absolute symlinks from entering the sstate cache.
<kroon>
RP, or at least in the perlcross-native case there were symlinks in the sstate cache that pointed back to wherever oe-core was checked out for that particular build
amitk has joined #yocto
amitk_ has quit [Ping timeout: 252 seconds]
<RP>
kroon: that isn't supposed to happen :/
<vd>
is there such thing as a 'devel' or 'debug' distro feature, the whole software stack (bootloader, kernel, images) can be tweaked to add verbosity and such?
<vd>
so that* the whole software stack
<RP>
vd: no, not really
vquicksilver has joined #yocto
<vd>
RP: a distro or machine feature can be really convenient to add custom bootloader splash screen, add delay in boot timeout, debug kernel command line etc., but I guess the issue is that such "profiles" (e.g. devel, debug, production, etc.) are very subjective so it might be hard to define a generic feature set.
<RP>
vd: it would be nice but nobody has ever done the work, it would be quite tricky to do that everywhere you mention
<vd>
RP: yeah and I'm not sure what would be preferred between having such df-debug override or adding a variant for your package that you select with PREFERRED_PROVIDER.
troth has quit [Ping timeout: 256 seconds]
GNUmoon has quit [Ping timeout: 276 seconds]
<kroon>
RP, doing "find -type l -lname '/*'" in my sysroot-components/ only lists the ones in perlcross-native, and kanavin is fixing those in master-next. so maybe we can add a check insane.bbclass
florian has joined #yocto
<smurray>
RP: heh, looking for "patch" in the README is interesting wrt AGL which uses Gerrit, I'd not be surprised if layers that use git forges also might not use the word "patch"
<moto-timo>
JPEW: the add label UI experience could be improved... lol
<JPEW>
Agreed
<moto-timo>
JPEW: sorry for the momentary thrash
<JPEW>
moto-timo: doesn't bother me ;)
<JPEW>
I had to make zuul unset the label when it starts, so you can't "cheat" the review and change it after the label is applied. It is unexpected
<JPEW>
This is why the code-review would be better (automatically cleared when a new change is pushed), but I can't self review :(
<RP>
smurray: right, this may need some improveent
florian has quit [Ping timeout: 252 seconds]
<smurray>
heh, quite easy to find layers that won't pass the new y-c-l README checks when I go looking for examples
<smurray>
I could imagine rev-ing the compatibility spec to include some form of fixed metadata format
<RP>
smurray: I did think the existing layers had passed when I merged, I'd not quite realised what the testing didn't test :(
GNUmoon has joined #yocto
kroon has quit [Quit: Leaving]
prabhakarlad has joined #yocto
troth has joined #yocto
<smurray>
RP: I've pushed README updates for the layers I believe are tested on the autobuilder setup. There are couple w/o READMEs in meta-agl, but I don't think they get tested (and they would not pass due to other reasons ATM)
<RP>
smurray: thanks, much appreciated. Sorry I didn't spot this on the way in
<RP>
I'd have reverted except that I think improving things is good in this case
<smurray>
RP: no worries. We'll likely improve the READMEs further, they're pretty lacking
<RP>
smurray: I think we need to do better all around
troth has quit [Ping timeout: 252 seconds]
<smurray>
RP: yeah
* RP
wonders how many more ways libxkbcommon can break in builds