<wyre>
when I run bitbake pjproject it builds 2.12.1 ... but not sure how should I proceed to build another version 🤔
amitk_ has quit [Ping timeout: 252 seconds]
<LetoThe2nd>
yo dudX
<wyre>
hi LetoThe2nd :-)
Guest89 has quit [Ping timeout: 260 seconds]
<LetoThe2nd>
wyre: if somebody does that, then it is usually because the versions are incompatible, or one is seeing long term support. you can select via PREFERRED_VERSION in your distro
<wyre>
hmmm, I see ... but I guess by default is built the higher version, right?
amitk_ has joined #yocto
<LetoThe2nd>
yes, by default the highest version gets chosen.
mckoan|away is now known as mckoan
<mckoan>
good morning
amitk has quit [Ping timeout: 265 seconds]
frieder has joined #yocto
amitk has joined #yocto
<yocton>
Hello!
rfuentess has joined #yocto
gho has joined #yocto
amitk has quit [Ping timeout: 268 seconds]
nemik has quit [Ping timeout: 268 seconds]
nemik has joined #yocto
xmn has quit [Ping timeout: 256 seconds]
mvlad has joined #yocto
amitk has joined #yocto
amitk has quit [Ping timeout: 272 seconds]
<qschulz>
wyre: IFF both versions are in the same layer, AND DEFAULT_PREFERENCE is not set to -1 foir example
bps2 has joined #yocto
adams[1] has quit [Quit: Client closed]
nemik has quit [Ping timeout: 252 seconds]
nemik has joined #yocto
PhoenixMage has quit [Ping timeout: 268 seconds]
PhoenixMage has joined #yocto
leon-anavi has joined #yocto
nemik has quit [Ping timeout: 260 seconds]
nemik has joined #yocto
florian has joined #yocto
seninha has joined #yocto
lamm has joined #yocto
d-s-e has joined #yocto
amitk_ has quit [Remote host closed the connection]
<qschulz>
RP: nice article you wrote there :)
agners has joined #yocto
<RP>
qschulz: thanks! I'm still unsure if it was the right thing to publish that or not...
amitk has joined #yocto
<yocton>
RP: It will definitely be used to justify my time if I may tip the scale toward "right thing"
Guest8 has joined #yocto
amitk has quit [Remote host closed the connection]
<RP>
yocton: that is good to know :). I wanted to try and make some of the issues more visible, I just hope it doesn't scare people off using the project
<mcfrisk>
link?
<yocton>
I've not considered the "scaring potential users" aspect...
<qschulz>
RP: that's a fair worry. But like you said most (if not all?) open source projects are underfunded and understaffed, so I'm not sure what the other alternatives for those scared users would be?
<yocton>
qschulz: +1
<qschulz>
I don't think Buildroot is doing that much better? what are the other options?
<RP>
qschulz: I did have one large existing member say "oh, we'll just switch to something else then", they didn't tell me what that was
<qschulz>
RP: mmmmm, from my point of view... do we want those users "using" the project and not caring about it?
<RP>
qschulz: there is that too :)
<qschulz>
I mean sure, most of our users are like this (heck, I'm probably one of those :/) but should we care if they leave without actually investing any effort in it?
<RP>
qschulz: you contribute time which is very valuable
<qschulz>
RP: I see this a bit as customers going into a coffee shop with employees on strike/limited staff and they complain they see the shit that is going on
<qschulz>
and say "we'll bring our business somewhere else"
<qschulz>
I mean, yeah, please do so?
<RP>
qschulz: if we lose members, I end up losing my income
<qschulz>
RP: yeah, mistook "members" for "users"
<yocton>
For the alternative, I've got a customer switching its future product from Yocto to Debian (but it is looks more like a server/IT maintenance project than your traditionnal embedded system)
starblue has quit [Ping timeout: 260 seconds]
<RP>
yocton: debian has pros and cons. Good luck if you ever need to reproduce debian :)
ptsneves has joined #yocto
<yocton>
RP: You may have a new member in the near future ;)
<RP>
:)
starblue has joined #yocto
<mcfrisk>
I've now been using yocto for 10 years and following community and mailing list, but seem to miss completely the details of project side build and test automation bits, how things get tested for a release. To help, I'd need to understand and replicate these, in the best case before I even send the patches. Hints to docs, scripts, repos and blog posts welcome..
<RP>
I can't claim it is complete, if you spot things which are missing let me know and I'll see what I can write down to add things
florian_kc has joined #yocto
<LetoThe2nd>
played with dependency track a bit, and the integration layer by bgnetworks. kinda like it!
<mcfrisk>
RP: I hope you can let go and see things also crash and burn a bit. There are many developers and contributors who can and need to step in and do more. My self in included.
<mcfrisk>
how I missed those docs... /facepalm
Sario has left #yocto [#yocto]
<RP>
mcfrisk: lettings things crash/burn is a last resort, I hope it doesn't come to that!
<mcfrisk>
RP: but let the project and technical things burn before you do! In the worst case reducing features, reverting changes is fine. I think we are spoiled by you being always there picking up when things fall apart.
tnovotny has joined #yocto
d-s-e has quit [Ping timeout: 260 seconds]
azcraft has joined #yocto
<LetoThe2nd>
out of curiousity - loading a sbom from an up to date kirkstone build gives me quite a high vulnerability score for curl. due to the host one? or where does it actually come from?
manuel1985 has quit [Ping timeout: 246 seconds]
azcraft has quit [Quit: Leaving]
<rburton>
LetoThe2nd: loading the sbom into what
<LetoThe2nd>
rburton: dependency track
<rburton>
LetoThe2nd: and that is doing cve analysis?
<rburton>
action for you: find out how to tell it that we've fixed cves and how to embed that in the spdx
alessioigor has joined #yocto
<LetoThe2nd>
rburton: hehe, first this is cyclone dx - and second, my action item usually is "how do i tell people about that".
<RP>
mcfrisk: I'm trying my best not to burn out. I think I worry that if things did destabilise, the work in putting things back together would be even worse, I think I fear that.
<rburton>
LetoThe2nd: tell them then. from a glance their format has a way of saying "this vuln is fixed".
<mcfrisk>
AFAIK, there is no standard way to add patched or ignored CVE to SPDX... Took a long time to explain that to a lot of people, that SPDX does not solve CVE patching and tracking
<LetoThe2nd>
exactly that I am playing around with.
<rburton>
LetoThe2nd: wow the 'sbom' generation in that layer is really incredibly basic
<LetoThe2nd>
rburton: just discovered it when looking for things to do once you actually have an sbom.
<rburton>
its no more than a list of pn/pv
<mcfrisk>
in a galaxy far away, a security department required SPDXes for all products, then started filing bug reports about old SW versions possible impacted by CVEs... rejected all tickets by saying CVE patches have been applied and CVE reports are clean. Point to an actual unpatched, not-ignored CVE and we talk again. Never heard back.
<mcfrisk>
RP: it is ok to reduce features, supported configurations etc. It's ok that you say this out and require someone else, paid or not, to take over.
<RP>
mcfrisk: in principle that is nice, in practise it doesn't work out that way, not least due to the ripple/time lag effects :/
prabhakarlad has joined #yocto
yssh has joined #yocto
Herrie|Laptop has quit [Ping timeout: 260 seconds]
demirok has quit [Quit: Leaving.]
sakoman has joined #yocto
agners has quit [Remote host closed the connection]
sakoman has quit [Remote host closed the connection]
sakoman has joined #yocto
d-s-e has joined #yocto
<Crofton>
is JPEW aware of teh CVE patching to spdx hole?
Piraty has quit [Read error: Connection reset by peer]
yssh has quit [Quit: Client closed]
Piraty has joined #yocto
davidinux has quit [Ping timeout: 260 seconds]
davidinux has joined #yocto
yssh has joined #yocto
<rburton>
Crofton: LetoThe2nd's thing isn't spdx
demirok has joined #yocto
<landgraf>
looks like systemd+musl is broken again :(
<JPEW>
Crofton: No?
<JPEW>
Oh, yes
<JPEW>
That is a known problem. There is no standardized way (in SPDX 2.2 anyway) to report patched or ignored CVEs
<JPEW>
We add a non-standard way in our SPDX, but obviously not ideal.
<JPEW>
This should be fixed in the SPDX 3.0
Herrie|Laptop has joined #yocto
<RP>
kanavin: around? Looks like virgl has a problem with pkgconfig from buildtools if you fancy fixing that?
<kanavin>
RP: sure
xmn has joined #yocto
<RP>
kanavin: I've just posted my findings on the mailing list, it explains why we started seeing virgl failures on hosts which used to work. It must have stopped when we enabled buildtools there
<RP>
kanavin: not sure how to get the search path from the host pkg-config
<kanavin>
RP: I'll take a look, I'm in a meeting just now
rob_w has quit [Remote host closed the connection]
<RP>
kanavin: in fact looking at the paths I pulled out of pkgconfig, it is totally broken atm in buildtools, it isn't relocating correctly
<RP>
kanavin: np, I just thought I'd better write down what I'd found out somewhere
kscherer has joined #yocto
xmn has quit [Quit: ZZZzzz…]
Guest8 has quit [Quit: Connection closed]
manuel1985 has joined #yocto
xmn has joined #yocto
<kanavin>
RP: so do I need to do something, or will you fix the relocation?
<kanavin>
(the last two messages make me unsure :)
<RP>
kanavin: I've just debugged the problem, I've not started on any kind of solution
<abelloni>
RP: I was going to open a bug for this issue, should I ?
<RP>
abelloni: probably, yes. I don't think anyone has a fix immediately ready
<ecdhe>
When I look in poky/build/tmp/work/<myarch>/myrecipe/<pv>/git
<ecdhe>
I see that no files were fetched
<rburton>
not sure inheriting rm_work in a recipe will work
seninha has quit [Quit: Leaving]
<rburton>
you can't have versions in DEPENDS
seninha has joined #yocto
<rburton>
and that PROVIDES is redundant if its the recipe name
<rburton>
i'd do bitbake myrecipe -C unpack and see what happens
<rburton>
but i wonder if rm_work is breaking as its not meant to be included per-recipe, afaik
<RP>
I was wondering about rm_work too
<RP>
try removing that
<RP>
rburton: you can have a version in DEPENDS, it just doesn't do anything
<ecdhe>
`bitbake -c listtasks myrecipe` didn't show rm_work until I inherited that
<rburton>
ecdhe: you usually inherit it in local.conf or similar
<RP>
ecdhe: normally you'd inherit it globally from local.conf
<ecdhe>
my local.conf doesn't contain an inherit or "rm_work" syntax
<RP>
ecdhe: INHERIT += "rm_work"
<rburton>
this assumes you want rm_work
<RP>
rburton: we should probably move rm_work to classes-global
<rburton>
yes
PhoenixMage has quit [Ping timeout: 260 seconds]
rcw has quit [Quit: Leaving]
PhoenixMage has joined #yocto
PhoenixMage has quit [Ping timeout: 272 seconds]
<ecdhe>
I added rm-work because I wanted to be able to clear the recipe out out to force a rebuild. I didn't understand that it would automatically remove the source as part of the build process
PhoenixMage has joined #yocto
seninha has quit [Ping timeout: 265 seconds]
<rburton>
yeah that's not what rm_work is for
<rburton>
if you want to force a rebuild, then force the rebuild. bitbake -C unpack recipename is good for that
zhmylove has quit [Remote host closed the connection]
PhoenixMage has quit [Ping timeout: 260 seconds]
PhoenixMage has joined #yocto
PhoenixMage has quit [Ping timeout: 255 seconds]
PhoenixMage has joined #yocto
iago has joined #yocto
yssh has joined #yocto
frieder has quit [Remote host closed the connection]
AntA has joined #yocto
iago has quit [Quit: Leaving]
prabhakarlad has quit [Quit: Client closed]
florian_kc has joined #yocto
florian_kc has quit [Ping timeout: 252 seconds]
mvlad has quit [Remote host closed the connection]
mark_ has quit [Quit: mark_]
yssh has quit [Quit: Client closed]
seninha has joined #yocto
invalidopcode has quit [Remote host closed the connection]
invalidopcode has joined #yocto
prabhakarlad has joined #yocto
florian_kc has joined #yocto
jatedev has quit [Quit: Client closed]
<moto-timo>
does anybody know how to tell kas to build an sdk?
<moto-timo>
(from the kas yml file, not from command line)
ptsneves has quit [Ping timeout: 260 seconds]
<moto-timo>
oh "task: "
manuel1985 has joined #yocto
yssh has joined #yocto
seninha has quit [Remote host closed the connection]
Herrie|Laptop has quit [Ping timeout: 265 seconds]
nemik has quit [Ping timeout: 252 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 260 seconds]
nemik has joined #yocto
Herrie|Laptop has joined #yocto
florian_kc has joined #yocto
nemik has quit [Ping timeout: 246 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 268 seconds]
nemik has joined #yocto
manuel1985 has quit [Ping timeout: 248 seconds]
mario-goulart has quit [Remote host closed the connection]
mario-goulart has joined #yocto
florian_kc has quit [Ping timeout: 260 seconds]
Herrie|Laptop has quit [Ping timeout: 246 seconds]
zhmylove has quit [Quit: Leaving]
<abelloni>
khem: I have busybox-1.36.0-r0 do_package_qa: QA Issue: busybox: ELF binary /bin/busybox.nosuid has relocations in .text [textrel] with your patch applied
florian_kc has joined #yocto
prabhakarlad has quit [Quit: Client closed]
zwelch has joined #yocto
agners has quit [Quit: WeeChat 3.8]
yssh has quit [Ping timeout: 260 seconds]
invalidopcode has quit [Remote host closed the connection]