10:23 <kroon> RP, how can we be so sure that native sstate cache built in one build directory can be reused in another build directory, even when the binaries contain references to build-specific paths ? Is it because of testing, or the fact that the embedded build paths only exist during the recipe build itself anyway ?

10:56 <RP> kroon: the binaries are always moved to new sysroots and things like rm_work remove the originals so whilst we can't be 100% sure and we do find issues now and again, in general it would effectively be tested

10:58 <kroon> RP, ok, I see

17:14 <dvorkindmitry> where can I find the SRC_URI local files search path logic?

20:18 <zeddii> can anyone think of a reason why when I manually extract a rpm that is present in my rootfs assembly, I see the files I expect .. but yet they aren't in the rootfs/ ?

20:18 <zeddii> some sort of sstate reuse that is preventing assembly from using it ?

20:19 <fray> in the past I saw an issue where the rootfs didn't regenerate for some reason.. a simple -c cleanall on the rootfs fixed it

20:19 <fray> I'd suggest you try that first

20:20 <fray> Also if you enable package managemetn on the rootfs.. login, you can check if it should have been installed..

20:20 <zeddii> it looks like the rootfs is being yanked out of state, yah. but I tried that. same thing ahppend second time.

20:20 <zeddii> i.e. I *see* the rpm staged: ./oe-rootfs-repo/rpm/core2_64/kubernetes-cni-v1.23.1+gitdd1b0a124713105e94ed58ffc2115ee8c1fd9f72-r0.0.core2_64.rpm

20:20 <fray> Ya, if you add package-management.. then you can get rpm to verify what is installed is actually on the disk

20:20 <fray> you can easily query the DB as well...

20:21 <zeddii> I always have packagemanagent on, and yah, the #@$@ thing is NOT on the rootfs, even though I have it in the rdpends of another rpm now.

20:21 <zeddii> what's the quick way to get RPM to show me the depends again ?

20:21 <fray> rpm -q <package> --requires

20:21 <zeddii> I can run it on target, so that's easy enough

20:21 <fray> note, package is just the name, not the filename

20:21 <fray> to get a list of what is installed.. rpm -qa

20:22 <fray> you can also use rpm -qp <pacakge _FILE_> --requires to query what is on your build system

20:22 <zeddii> so that's weird. I SEE my package in the requires

20:22 <zeddii> but it isn't installed.

20:22 <zeddii> https://paste.debian.net/1223058/

20:23 <zeddii> I'm looking for my kubernetes-cni package

20:23 <fray> something else might provide kubernetes-cni

20:23 <zeddii> root@qemux86-64-7b:~# rpm -qa | grep cni

20:23 <zeddii> cni-v0.8.0+gitb5ab16f010e822936eb974690ecec38ba69afc01-r0.0.core2_64

20:23 <fray> rpm -q --what-provides kubernetes-cni

20:23 <zeddii> I just created the package, so that is unlikely that it is provided by anything else.

20:23 <zeddii> the packages-split in the build have what I'd expect it to install.

20:24 <zeddii> never say never, let me try that query

20:24 <zeddii> hmm. no what-provides ..

20:24 <fray> command worked, but reported back nothing?

20:25 <zeddii> naw, it said "rpm: --what-provides: unknown option"

20:25 <fray> sec

20:25 <fray> rpm -q --whatprovides (no middle -)

20:26 <zeddii> aha. i was googling, should have guessed

20:26 <zeddii> ahah. oddly, something else claims to provide it .. also a package I created, I'll have to check, it isn't breaking k3s, but only k8s.

20:26 <zeddii> that's just what I needed. I'll keep a log of the tricks

20:26 <fray> ya, that is usually hwat the trick is.. something else provides the thing and it breaks you

20:29 <zeddii> I guess I could go with a preferred provider for the conlict, but I think I can just delete the generic one.

20:30 <fray> preferred provider only affects build-time, not runtime.. So this could still happen.. definitely need to resolve it in the packaging side of things

20:30 <zeddii> I nuked the kubernetes-cni rprovides from the cni package, and now my kubernetes build should provide it itself, that should fix it up.

20:31 <zeddii> I see it rebuilding, so that's a positive sign

20:58 <JosefHolzmayrThe> NUKE IT FROM ORBIT!

20:58 <JosefHolzmayrThe> ...

20:58 <JosefHolzmayrThe> what are we talking about anyway?