**** BEGIN LOGGING AT Tue Feb 22 02:59:56 2022 Feb 22 18:07:30 khem: can you add me as a member of the OE org on github? and ideally, an admin? I'll add some PR templates for bitbake/oe-core telling people to use the list. Feb 22 18:08:30 I dont have the capacity I think let me try Feb 22 18:08:56 hm i think templates need to be in the repo, which is annoying Feb 22 18:09:41 ah if you try to open a kernel PR it says 'An owner of this repository has limited the ability to open a pull request to users that are collaborators on this repository.' Feb 22 18:10:23 yes it needs to be in a folder called .github Feb 22 18:10:44 Perhaps Top level README is first place Feb 22 18:11:47 restricting access to collaborators sounds like an easy way to stop them being filed Feb 22 18:12:06 i'll happily poke at the settings for bitbake/oe-core if someone can give me access :) Feb 22 18:12:24 I can't see who can give me access as I can't see the member list as i'm not a member of the org :) Feb 22 18:12:37 I am not admin for this repo, so perhaps ask Phil or someone Feb 22 18:13:13 someone owing openembedded org can help youu Feb 22 18:13:20 owning Feb 22 18:15:13 by phil do you mean Crofton or Bundell? Feb 22 18:15:38 Probably means me Feb 22 18:16:03 read above please :) Feb 22 18:16:10 whats your github id Feb 22 18:16:13 rossburton Feb 22 18:26:27 Yeah Crofton is your man Feb 22 18:26:41 rburton: I ahve a plan Feb 22 18:28:06 khem: are you using sstate cache? I'm not able to reproduce locally just yet Feb 22 18:29:33 khem: or can you point me at an error log Feb 22 18:45:06 I am using sstate-cache but the native package is being rebuilt, does this changeset require sstate to be invalidated ? Feb 22 18:50:15 patch sent. it is because you have python3-wheel from meta-python... layer priority means that recipe is winning Feb 22 18:52:12 doesn't matter if you set PR etc. the layer priority keeps winning that battle :/ Feb 22 19:02:43 DEFAULT_PREFERENCE may be beneficial there? not sure if that overrides layer priority or not offhand. hmm Feb 22 19:08:56 it doesn't layer priority always wins Feb 22 19:09:23 https://bugzilla.yoctoproject.org/show_bug.cgi?id=2964 Feb 22 19:09:42 ah so python3-wheel is in two places Feb 22 19:10:02 is there a way for bitbake to find duplicate recipes Feb 22 19:10:28 yes, something like show_overlayed Feb 22 19:11:18 bitbake-layers show-overlayed Feb 22 19:11:50 moto-timo: perhaps there should be a patch to remove the recipes moved into core with your changes Feb 22 19:13:15 JaMa: ah, that's irritating Feb 22 19:18:53 khem: I sent patch for meta-python removal of python3-wheel Feb 22 19:19:44 v3 of the oe-core series just sent which _should_ fix the last couple of build failure points Feb 22 19:21:48 thanks Feb 22 19:23:55 khem: there is likely to be breakage in meta-python/meta-oe. I can't boil the ocean with one pair of hands. Feb 22 19:29:19 the pattern so far has been VERY old python recipes need tweaking or newer revisions with pyproject.toml need to switch to the new PEP-517 classes... Feb 22 19:31:03 thanks yeah Feb 22 19:31:48 there are a few recipes that have pyproject.toml and use [build-system] build-backend="poetry.core.masonry.api" but nothing in oe-core (and the python3-poetry-core brought in extra dependencies)... some work in progress https://git.yoctoproject.org/poky-contrib/commit/?h=timo/pypa-packaging-wip&id=db49bdfc33708d08a94f7bcfad49912b2e04c65a Feb 23 02:30:02 ok folks, someone with more brain cells functioning than me at the moment: https://git.yoctoproject.org/poky-contrib/commit/?h=timo/pyprojecttoml_build_backend_check&id=6829b855f36e2c778ca7bc31c06912fd08abc0a8 Feb 23 02:30:31 We need this to help us quickly identify recipes in meta-openembedded umbrella that can move to the new pyproject.toml/PEP-517 tooling **** ENDING LOGGING AT Wed Feb 23 02:59:57 2022