Thursday, 2019-11-21

*** jae1 <jae1!95c73e81@> has quit IRC00:48
*** chandana73 <chandana73!~ckalluri@> has quit IRC01:29
*** stephano <stephano!> has quit IRC01:43
*** nrossi <nrossi!uid193926@gateway/web/> has joined #yocto03:49
*** chandana73 <chandana73!~ckalluri@> has joined #yocto04:03
*** chandana73 <chandana73!~ckalluri@> has quit IRC04:04
*** chandana73 <chandana73!~ckalluri@> has joined #yocto04:04
*** chandana73 <chandana73!~ckalluri@> has quit IRC04:15
*** anujm <anujm!~anujm@> has quit IRC04:23
*** comptroller <comptroller!> has quit IRC04:49
*** comptroller <comptroller!> has joined #yocto05:04
*** fatalhalt <fatalhalt!> has quit IRC05:54
*** thaytan <thaytan!> has quit IRC06:29
*** frsc <frsc!~frsc@2003:a:e7a:6200:a427:c148:e286:fbe7> has joined #yocto06:33
*** agust <agust!> has joined #yocto06:58
*** blankscape <blankscape!~arcanscap@> has joined #yocto06:59
blankscapehow can i get a python function in a bbclass to run before the do_install task?07:01
blankscapei have tried do_install[prefuncs] += "function_name " but i dont see any print outputs in the log.dorootfs log07:02
blankscapenot having much luck with the mega manual or google...07:02
*** guerinoni <guerinoni!> has joined #yocto07:08
*** AndersD <AndersD!> has joined #yocto07:08
*** yann|work <yann|work!> has quit IRC07:21
*** iceaway <iceaway!~pelle@> has joined #yocto07:21
iceawayI have an issue that might not be Yocto-specific, but maybe someone recognizes it. I have a dhcp server (dhcp-server, dhcp-server-config) installed on my board (using Yocto Sumo). But when the server is started as a regular daemon it seems to hang badly. It does not respond to DHCP requests, and I can only kill it with kill -9. If I start the server manually though, with the -f flag, it works as expected.07:24
*** alessioigor <alessioigor!> has quit IRC07:35
*** leon-anavi <leon-anavi!~Leon@> has joined #yocto07:37
*** alessioigor <alessioigor!> has joined #yocto07:39
*** johnnylintw <johnnylintw!> has quit IRC07:47
*** hpsy <hpsy!> has quit IRC07:49
*** blankscape <blankscape!~arcanscap@> has quit IRC07:50
*** blankscape <blankscape!~arcanscap@> has joined #yocto07:51
*** jklare <jklare!~jklare@> has quit IRC07:57
*** jklare <jklare!~jklare@> has joined #yocto07:59
*** tz <tz!> has quit IRC08:07
*** farnerup <farnerup!> has joined #yocto08:12
mcfriskadelcast RP: I also was debugging an opkg crash from poky master after innocent looking opkg tar ball was in sstate cache. had to port valgrind to native and found out the libarchive error path problems. just ran out of time polishing and publishing the patch :(08:13
*** diego_r <diego_r!> has joined #yocto08:16
*** yann|work <yann|work!~yann@> has joined #yocto08:17
*** tz <tz!> has joined #yocto08:28
RPmcfrisk: any idea why we started generating these ipks all of a sudden?08:30
*** xtron <xtron!~xtron@> has joined #yocto08:32
*** Bunio_FH <Bunio_FH!> has joined #yocto08:32
*** AndersD <AndersD!> has quit IRC08:33
rcrudowhat is the recommended way to handle multiple distros? I have a local.conf which sets DISTRO to a specific distro in meta/recipes-core/images. to build another distro I would have to edit local.conf?08:37
LetoThe2ndrcrudo: you can just put it in through the call08:38
LetoThe2ndDISTRO="yourdistro" bitbake your-image08:38
LetoThe2nd(assuming that you kept the ?= assignment in local.conf=08:38
blankscapeanyone know how to run a python function before do_install of a bitbake recipe ?08:40
*** leon-anavi <leon-anavi!~Leon@> has quit IRC08:41
*** leon-anavi <leon-anavi!~Leon@> has joined #yocto08:42
yoctiNew news from stackoverflow: What is the meaning of '__anonymous' function in a yocto/bitbake recipe? <>08:44
*** rburton <rburton!> has joined #yocto08:49
rcrudoLetoThe2nd: I see. In that case I'd have to keep in local.conf only settings which applies for all distros08:49
LetoThe2ndrcrudo: yep08:49
*** blankscape <blankscape!~arcanscap@> has quit IRC08:58
rburtonkanavin: dude are you reading my mind09:14
rburtonkanavin: 11pm i scribbed down 'port p11-kit to meson' and 'update gettext'09:15
rburtonkanavin: unfortunately one of my patches i have here is moving autopoint to -minimal09:16
rburtonhaha and i just prepped 'remove console-tools'09:16
*** T_UNIX <T_UNIX!uid218288@gateway/web/> has joined #yocto09:18
iceawayI would like to store the revision of my custom layer used during the build in a file in the resulting file system. Is there any way to get that info into the i.e. image recipe?09:19
LetoThe2ndiceaway: look at the buildinfo, buildstats stuff.09:21
iceawayLetoThe2nd: thanks, will have a look!09:21
mcfriskRP: I had an old sstate cache dir not wiped in months and been updating poky master and rebuilding a lot in the last 8 months. still have tree available for debugging but haven't had time to polish all patches, e.g. to enable valgrind for native when host version nolonger works etc..09:23
*** varjag <varjag!> has joined #yocto09:25
GeneralStupidqschulz: is there a way to get an output of the overridings for a recipe?09:25
qschulzGeneralStupid: bitbake-layers show-appends09:26
qschulzah wait... are you talking bbappends or OVERRIDES?09:27
qschulzbbappends, see above. OVERRIDES, use bitbake -e and look for a line starting with OVERRIDES09:27
qschulzor read the log.do_fetch to see the order in which directories are "traversed"/checked09:28
*** warthog9 <warthog9!> has quit IRC09:29
*** warthog9 <warthog9!> has joined #yocto09:29
*** bluelightning_ <bluelightning_!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto09:35
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC09:40
*** jmiehe <jmiehe!> has joined #yocto09:42
*** florian_kc <florian_kc!~florian_k@Maemo/community/contributor/florian> has joined #yocto09:43
qschulzquick question: is it possible to devtool deploy-target glibc?09:50
*** bluelightning_ <bluelightning_!~paul@pdpc/supporter/professional/bluelightning> has quit IRC09:56
* LetoThe2nd thrusts mcfrisk and compares with a flying pig.09:59
*** JaMa <JaMa!~martin@> has joined #yocto10:03
qschulzrburton: mentioning you just because you answered to some glibc devtool stuff a while ago on the ML. Is it possible to devtool deploy-target glibc?10:05
qschulzdirname: error while loading shared libraries: cannot open shared object file: No such file or directory10:05
qschulzthat's what my people get when trying.10:06
*** hpsy <hpsy!~hpsy@> has joined #yocto10:09
qschulzFYI, glibc from thud with a patch implementing what's being discussed here:!topic/generic-abi/bX460iggiKg10:09
*** bluelightning_ <bluelightning_!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto10:10
GeneralStupidqschulz: ok this lists my bbappend file... Amazing.  But maybe i should have mentioned that its using my overridden SRC_URI ... But not my overriden LOCALVERSION for example10:10
GeneralStupidqschulz: thats why i tried to use a different defconfig name... Its always using the default defconfig. Is it a good idea to override the "FILESEXTRAPATH" instead of prepending?10:14
qschulzGeneralStupid: no. Because only the directory pointed by your bbappend will be used for everything in that recipe, including everything in the original one10:15
qschulzand it'll break if there is a bbappend applied after yours10:15
qschulzor before10:15
qschulzwhat's the machine you're building for10:16
kayterinahello hello.10:23
kanavinrburton, thanks for sorting the lrzsz issue :)10:25
GeneralStupidqschulz: imx6. its imx6ullevk.10:27
qschulzGeneralStupid: put your defconfig in a subdirectory named imx, that should make it work10:33
qschulzGeneralStupid: meta-foo/recipes-kernel/linux/<whateveryouputinyourbbappend>/imx10:34
qschulzGeneralStupid: but really, try to also document yourself on the OVERRIDES mechanism, it's pretty powerful and that's not the only time you'll encounter it or scratch your head about something that does not get applied10:35
LetoThe2ndqschulz: re your append topic idea: qou're right, this probably can use some explanations.10:35
qschulzGeneralStupid: let me know if that works. Anyhow, learning about OVERRIDES can't hurt :)10:38
*** goliath <goliath!> has joined #yocto10:39
qschulzGeneralStupid: also, FYI, you don't need to recompile every time, you can check with bitbake virtual/kernel -c menuconfig if the options of your defconfig are (un)selected.10:41
*** alin___ <alin___!~alin___@> has joined #yocto10:43
rburtonqschulz: never used devtool deploy :)10:43
rburtonkanavin: if you like poking at gettext you might be interested in my autopoint and gettext-tiny branches.  neither actually work yet but WIP10:44
qschulzrburton: never did either :/ Do you know who I could ping about that?10:44
LetoThe2ndqschulz: devtool deploy-target only works for packages you actually have in your workspace, AFAIK10:45
rburtonqschulz: try bluelightning_10:45
rburton(if he hasn't gone to bed)10:46
qschulzGeneralStupid: why imx? => the defconfig is specific to either imx or imx8 so you need to have your defconfig as specific or more specific.10:46
qschulzGeneralStupid: which is more specific than and (though I have never seen/used the EXTENDER stuff10:48
qschulzLetoThe2nd: devtool modify -x glibc, devtool build glibc, devtool deploy-target glibc is what they do (not the exact commands but that's their workflow)10:49
qschulzbluelightning_: maybe you'll be helpful :) Is it possible to devtool deploy-target glibc? what my people get when trying: dirname: error while loading shared libraries: cannot open shared object file: No such file or directory; FYI, glibc from thud with a patch implementing what's being discussed here:!topic/generic-abi/bX460iggiKg10:50
LetoThe2ndqschulz: *might* work. in my experience devtool work the better the more simple and canonical the recipes in question are.10:50
qschulz@all: or even better, how do you debug the glibc :) ?10:50
GeneralStupidqschulz: Ahhh NXP10:51
bluelightning_qschulz: it should work... but glibc is quite a beast, I guess there are complications10:52
qschulzLetoThe2nd: my worry is that this deploy-target stuff depends on some glibc stuff on the target and that it breaks in the middle of the transfer. But 1) no experience in deploy-target, I don't even know how it does it, 2) no experience in glibc either :/10:52
bluelightning_I certainly haven't tried it myself, maybe I can give it a shot tomorrow10:52
LetoThe2ndqschulz: it depends on a shell and ssh/scp being fully functional, AFAICS10:52
bluelightning_qschulz: deploy-target is basically tar over ssh10:52
qschulzbluelightning_: alright! Do you want me to ping you tomorrow at one point?10:53
qschulzGeneralStupid: TI is doint it as well ;)10:53
bluelightning_qschulz: sure10:53
qschulzbluelightning_: thanks for the explanation, now there's only 2) which isn't going to be easy to tackle :D I don't know how much glibc is involved/safe in that tar/ssh combination. I'll let you sleep tight and ping you tomorrow when I arrive at the office (2-3hours before now in your timezone)10:55
bluelightning_qschulz: ok, I should be around10:57
kanavinrburton, may I ask that you act on the AUH patches please :)10:58
kanavin(not sure if you're planning to anyway)10:58
kanavinrburton, what is autopoint for?11:00
rburtonkanavin: its basically gettextize11:01
rburtonwe historically disable it, and do it ourselves in autotools.bbclass11:01
rburtontrying to remove that kludge11:01
kanavinrburton, tbh I have no particular interest in gettext other than getting it up to date11:01
rburtonshame :)11:02
*** Chrusel <Chrusel!c1669b04@> has joined #yocto11:03
*** alin___ <alin___!~alin___@> has left #yocto11:10
* RP wonders what to prioritise. hashequiv debugging is eating time, meanwhile patches mount up :/11:11
kanavinRP: if there's a show of hands, mine goes to hashequiv11:13
LetoThe2ndcan't we have a show of metal?11:21
LetoThe2ndkanavin: exactly that.11:25
*** berton <berton!~berton@> has joined #yocto11:27
*** berton <berton!~berton@> has quit IRC11:30
bojonesIm using Sumo in my current yocto build and I have a simple recipe that has a "require <somefile>.inc" in the top.11:33
*** berton <berton!~berton@> has joined #yocto11:34
bojonesIf I modify the .inc file, the package isn't rebuilt - am I missing something or is this how it is supposed to be?11:34
paulbarkerbojones: What are you modifying in the inc file? Bitbake dependencies are more granular than recipe or inc files11:36
RPLetoThe2nd: I quite like mercury as liquid metal at room temperature is quite cool...11:37
bojonesI removed a patch from the SRC_URI in the .inc file11:38
kanavinrburton, I have a patch that fixes lrzsz now11:40
paulbarkerbojones: I recommend dumping the env using `bitbake -e <recipe>` and looking at how SRC_URI is set, see if your change is picked up or if it's clear what's gone wrong11:40
yoctiNew news from stackoverflow: Yocto: patch kernel module Makefile <>11:45
RPgah, found the "hashequiv" corruption issue which isn't hashequiv at all11:46
LetoThe2ndRP: hrhrhr11:49
LetoThe2ndRP: on a more serious note, can you (or somebody else) give me a short rundown on multiconfig? we're just getting started with it, and have quite a confusing time in understanding what can be set/left out/overwritten where11:50
LetoThe2ndFWWW the local.conf (or generally, the build) still needs to have a valid DISTRO/MACHINE setting combination. with MACHINE obviously being able to be overwritten later11:52
Crofton|workOK I ned to remove a couple of packages from an SDK, anyone know how?11:53
*** radsquirrel <radsquirrel!> has quit IRC11:53
*** radsquirrel <radsquirrel!> has joined #yocto11:56
bojonesI just investigated some more... There was a SRC_URI[md5sum] and SRC_URI[shasum} defined in the .inc file.11:59
bojonesIf I remove those, it seems to work11:59
bojonesWhy would you have those defined for a SRC_URI?11:59
rburtonbecause SRC_URIs that fetch tarballs need to provide checksums12:03
RPLetoThe2nd: biggest confusion with multiconfig is that local.conf is one of the multiconfigs12:03
*** goliath <goliath!> has quit IRC12:03
RPLetoThe2nd: then the others are added to it as other build options12:04
RPLetoThe2nd: you can set anything in a multiconfig however you need to be mindful about sharing TMPDIR, if the builds all use the same one, they need to be compatible (i.e. same DISTRO)12:04
LetoThe2ndRP: so if thats the confusion,whats the correct mindset?12:05
RPso changing MACHINE is fine, if you change DISTRO, set TMPDIR too12:05
RPLetoThe2nd: well, just realise that local.conf is your first multiconfig12:05
RPbitbake bash builds whatevr local.conf is set to. bitbake mc:A:bash multiconfig A's bash target12:06
LetoThe2ndhaving a TMPDIR for several DISTROs is actually bad? (didn't realize taht)12:06
RPLetoThe2nd: the same TMPDIR with different distros means it will uninstall and install other things12:06
RPassuming the distro configs are different12:07
RPand if they're not different, why do you have them?12:07
LetoThe2ndah, /me confused TMPDIR and SSTATE one more time12:07
RPit can't uninstall and reinstall in a multiconfig build the same way as it normally would12:08
LetoThe2ndkay, good point.12:08
LetoThe2ndwill try to keep that in mind12:08
RPloads of new ways to shoot yourself in the foot :)12:09
RP(or worse)12:09
*** bluelightning_ <bluelightning_!~paul@pdpc/supporter/professional/bluelightning> has quit IRC12:09
LetoThe2ndthats my fear if we start acutally using it in production.12:09
LetoThe2ndthx, will try and inverstigate.12:09
*** xtron <xtron!~xtron@> has quit IRC12:09
RPLetoThe2nd: its quite neat, just requires a little thought12:10
LetoThe2ndRP: additional question: best practise to set TMPDIR depending on mc? some override syntax?12:13
RPLetoThe2nd: set it in the multiconfig conf file?12:13
RPLetoThe2nd: I can't even remember if we did multiconfig overrides :/12:14
LetoThe2ndRP: hm. din't like that as we want to carry the mc file with the layers.12:15
*** hyper_dave <hyper_dave!~dave@> has joined #yocto12:25
*** hyper_dave <hyper_dave!~dave@> has quit IRC12:28
GeneralStupidqschulz: so do i need to fork the kernel? Do i need to create a custom machine (i wanted to do this later)12:30
RPLetoThe2nd: I often use TMPDIR = "${TOPDIR}/tmp-XXX"12:40
RPadelcast: when you're around I have answers to some of our questions12:41
LetoThe2ndRP: would TMPDIR_distro1 = ... also work?12:42
RPLetoThe2nd: yes12:42
yoctiNew news from stackoverflow: How can I call functions from an Anonymous Python Function in bb recipe files? <>12:45
*** tgamblin <tgamblin!~tgamblin@> has joined #yocto12:47
LetoThe2ndRP: coworker seems to be happy12:54
*** jklare <jklare!~jklare@> has quit IRC12:58
kayterinaI have  DISTRO_FEATURES_remove="x11" in distro/conf, why would bitbake compile libx11-1_1.6.3-r0?13:00
LetoThe2ndkayterina: probably something depends on it.13:00
LetoThe2ndand no, DISTRO_FEATURES are no magic bullets. they're only as good as the recipes that either evaluate them, or not.13:01
*** jklare <jklare!~jklare@> has joined #yocto13:02
kayterinaPACKAGECONFIG_remove += "x11"?13:02
LetoThe2ndkayterina: DEPENDS (TM)13:02
LetoThe2ndif the package in question has that switch, then probably.13:02
LetoThe2ndbut it really all dependes.13:02
GeneralStupidqschulz: Hm i raised the version of my layer but sstill no success. This makes no sense to me13:06
*** thaytan <thaytan!> has joined #yocto13:17
GeneralStupidwhy is KERNEL_DEFCONFIG := "my_def" not working?13:20
GeneralStupidok iam starting to figure it out. kernel-imx is not using kernel.bb13:24
GeneralStupidok ok so there is a do_preconfigure task. They are taking a hardlinked defconfig file :)13:30
*** dstriker <dstriker!> has joined #yocto13:48
dstrikerHi, anybody here?13:48
qschulzGeneralStupid: what are you doing?13:50
dstrikerI've a little question about 'gstreamer1.0-plugins-bad' in meta-oe and I'm not sure, if should send a patch to the mailing-list...13:51
qschulzyou have a bbappend with your defconfig in it. It should be in a path with more priority than the original one. Here it seems to me it is "imx" that is used in meta-freescale. So you need AT LEAST to name your subdirectory "imx". Or it can be something more specific (on the right side of "imx" in OVERRIDES variable).13:52
qschulzthe defconfig HAS to be named "defconfig"13:52
qschulzGeneralStupid: and it's KBUILD_DEFCONFIG, not KERNEL_DEFCONFIG AFAICT. This is only handled by recipes which are inheriting kernel-yocto bbclass which is not that common and is not the case of linux-imx IIRC13:54
rburtondstriker: ask, don't ask to ask13:54
rburtondstriker: also that recipe is in oe-core13:54
mcfriskdifferent BSPs have different customs. It's best to devshell into them and figure out how to override the configs. and lot of testing..13:54
dstrikerI build an image with zbar enabled in gstreamer1.0-plugins-bad, so right now I need to create a seperate bbappend-file, where I:13:55
dstrikeradd zbar to DEPENDS, remove '--disable-zbar' from EXTRA_OECONF, append '--enable-zbar' to EXTRA_OECONF13:56
GeneralStupidqschulz: But that means NXP is doing some bad recipe style?13:56
qschulzGeneralStupid: why?13:56
qschulzGeneralStupid: I mean, what seems wrong to you (not judging, really asking)13:56
rburtondstriker: right, so send a patch to add a pacakgeconfig for the zbar option so you can just toggle the packageconfig13:57
dstrikerin the recipe of 'gstreamer1.0-plugins-bad' it says: "# these plugins have no corresponding library in OE-core or meta-openembedded:" and zbar is in there... so I was not sure, if I should send a patch or not...13:57
rburtonyes please do send a patch13:58
dstrikerokay, thanks13:58
qschulzplease use that13:58
*** goliath <goliath!> has joined #yocto14:00
qschulzdstriker: the comment dates from the original commit which is in 2013. The zbar recipe was more recently added so no problem :)14:01
*** ericch <ericch!> has joined #yocto14:03
kayterinaso, to remove a recipe, only through the dot diagram I can find the dependencies?14:04
LetoThe2ndkayterina: its the most reliably ways AFAIK.14:06
GeneralStupidqschulz: i think it would be "common sense" to inherit from kernel.bbclass or something like that14:07
GeneralStupidFor me it feels bad to have this highly customazible yocto recipes but they are not working because NXP is doing their own stuff14:08
*** WillMiles <WillMiles!> has joined #yocto14:10
qschulzGeneralStupid: it inherits from kernel.bbclass, not kernel-yocto.bbclass.14:11
GeneralStupidqschulz: Ah ok then it makes sense, a bit14:11
qschulzGeneralStupid: I've never used or seen kernel-yocto.bbclass. In any BSP I've used. Ever.14:11
GeneralStupidIam not able to add a task in a bbappend file?14:12
qschulzGeneralStupid: you are :)14:12
GeneralStupidOr does ".bb" include ".bbclass" in the manual. Ok14:12
qschulzGeneralStupid: "inherit foo" will inherit foo.bbclass14:12
qschulzinclude and require need the file extension, but inherit assumes it's only bbclass that are inherited14:13
yoctiNew news from stackoverflow: In Yocto, how do I specify a version restriction of package A to be the current version of package B? <>14:15
*** anujm <anujm!~anujm@> has joined #yocto14:20
*** palate <palate!~palate@unaffiliated/palate> has joined #yocto14:20
*** dstriker <dstriker!> has quit IRC14:24
GeneralStupidqschulz: ok now ${B} is not working :D14:26
qschulzGeneralStupid: I'll need a bit more than that :)14:28
*** stephano <stephano!> has joined #yocto14:29
*** farnerup <farnerup!> has quit IRC14:29
qschulzRP: what's the policy for fixing bugs in old and unmaintained software in Yocto? I'm pretty sure we've found some bugs in libdbus-c++ which is still in meta-openembedded but is dead for the last ~3 years already.14:37
GeneralStupidqschulz: they are copying defconfig to  ${B}/.config . So now i just try to echo "" > ${B}/.config . That the build fails... But its working :D14:37
GeneralStupidbut my new task is in the list14:37
qschulzsorry for mentioning. Not really targetted to you but YP community as a whole.14:37
RPqschulz: well, if the recipe is still there I'd guess a patch would be taken14:38
qschulzIn my mind, you try to fix upstream and send a patch to build systems while your patch gets reviewed/merged upstream. But here, it's never going to make it to upstream and it's slightly changing the behaviour14:38
qschulzGeneralStupid: What are you doing? I'm absolutely not following you. Why are you resetting .config?14:39
qschulzWhat are you trying to achieve?14:39
RPqschulz: upstream is definitely the preferred model, as you say its not always possible14:39
GeneralStupidqschulz: i want to use a custom defconfig. Or is there a better way?14:41
qschulzRP: okay, we'll work on a patch and send something in the next few weeks and we can discuss from there14:41
qschulzGeneralStupid: I explained you twice already what to do.14:41
qschulzyour bbappend only has a FILEEXTRAPATHS_prepend := "" in it. That should be enough14:42
qschulzyour defconfig NAMED defconfig (exactly like this) in meta-foo/recipes-kernel/linux/<whateveryouputinyourbbappend>/imx/defconfig (defconfig here is the name of the file not a directory)14:43
qschulzyour bbappend is meta-foo/recipes-kernel/linux/linux-imx_%.bbappend14:43
qschulzthat should be enough for a custom defconfig.14:43
qschulzIf that is not enough we have to work out the OVERRIDES thing and try to find out which file is taking precedence and why14:44
GeneralStupidqschulz: FILE* * EXTRAPARH or FILE*S*EXTRAPATH14:46
GeneralStupidI have the the FILES EXTRAPATH14:46
qschulzGeneralStupid: I can't never type that one correctly.14:47
T_UNIXwhat's the recommended way to have a `_append`  only  be applied, if a certain IMAGE feature is enabled?14:47
GeneralStupidAh ok14:47
T_UNIXi.e. `do_install_append() {..}`14:47
qschulzT_UNIX: IMAGE_FEATURE can be used only in image recipes14:48
qschulzyou can use DISTRO_FEATURES and MACHINE_FEATURES in there though14:48
qschulzT_UNIX: I've been there :)14:49
qschulzT_UNIX: what do you want to do exactly?14:49
*** anujm <anujm!~anujm@> has quit IRC14:49
T_UNIXhmm.. maybe I'm going wrong about it: In production I'm using systemd to set capabilities to allow an application to modify the date14:50
T_UNIXfor development purposes, however, I'd like to allow users to modify date as they please.14:50
*** goliath <goliath!> has quit IRC14:50
T_UNIXso there is `busybox.conf`. But it seems broken in combination with the barebox.{no,}suid split.14:50
GeneralStupidqschulz: This is pulled in and for me it looks like its always taking the default defconfig out of $WORKDIR14:57
kayterinaso, to remove "qemu-native" I must remove every package that points to qemu-native. through IMAGE_INSTALL_remove? and if it still gets compiled, I missed something?15:00
LetoThe2ndkayterina: what makes you so sure you don't need qemu-native?15:03
LetoThe2ndkayterina: -native means its being built for the development host, not for your target.15:04
LetoThe2ndand it being pulled in means that something acutally needs it.15:04
kayterinaha ha.I just want to remove something15:04
kayterinabut what if I don;t use qemu?15:05
LetoThe2ndthats why qemu-native is a particularly bad example. there are recipes that use it under the hodd to do things that you do not obviously see.15:05
LetoThe2ndso if you want to remove qemu, just becasue you want to remove qemu - then chances are that you are just being wrong.15:06
LetoThe2ndkayterina: basically all things that start with "I just want to" are wrong with high probability.15:07
kayterinaiik. ok, x11 and libxau xproto  libx11, I don't have graphics,so I don't need them.15:09
kanavinRP, I have a bit of spare cycles if you need help with something15:10
kergothkayterina: use a distro that disables x11, then, or your own (see DISTRO_FEATURES)15:15
T_UNIXqschulz: but there are many places that are like `PACKAGECONFIG = "bb.utils.contains("${IMAGE_FEATURES}", 'foo', 'add_x', '')}"`15:16
T_UNIXobviously not exactly like that15:16
T_UNIXI was just wondering whether PACKAGECONFIG would recognize that its value depends on `IMAGE_FEATURES`15:16
*** varjag <varjag!> has quit IRC15:17
T_UNIXlxdm for example: `DISTRO_TYPE ?= "${@bb.utils.contains("IMAGE_FEATURES", "debug-tweaks", "debug", "",d)}"`15:17
RPkanavin: thanks, I just got to the bottom of the thing which has been really bothering me (the empty ipks). For better or worse most of the issues I'm looking at are hard to reproduce autobuilder failures :/15:17
qschulzGeneralStupid: sorry was afk. Yes it takes the defconfig out of WORKDIR. But the defconfig that is put in WORKDIR depends on FILESEXTRAPATHS and OVERRIDES. It should be fine, you're debugging the wrong thing I think15:19
kayterinakergoth: we've gone through this with leto: it all depends. DISTRO_FEATURES_REMOVE+="x11" didn't do it for me. perhaps because I am on older yocto and vendor's layer based on meta-freescale15:19
kayterinaso removing them by hand seems more certain15:19
qschulzT_UNIX: where?15:20
qschulzT_UNIX: if I remember correctly what LetoThe2nd told me. IMAGE_FEATURES can't be used outside of image recipes. And if I remember correctly... from experience it cannot.15:21
LetoThe2ndqschulz: not entirely correct.15:21
LetoThe2ndit depends on where they have been set.15:21
GeneralStupidqschulz: ok good to know -.-15:21
qschulzLetoThe2nd: all ears15:22
LetoThe2ndit the usual: "conf things are global, recipe things are local"15:22
LetoThe2ndso if you happen to set them in local.conf, you can *technicall* trigger on them everywhere. and if you set them in your image recipe, you cannot.15:22
LetoThe2ndwhat does this tell us? don't use the first technique, as it will confuse everybody including your future self.15:23
qschulzLetoThe2nd: ah yes, I always forgot this conf/local.conf thingy. thanks!15:23
kanavinRP, I'll keep doing long-delayed recipe updates then15:23
kanavinshame that the lrzsz thing blew up like this15:24
T_UNIXthat seems a bit odd. Because you'd obviously create an developer image. That's a local recipe.15:24
LetoThe2ndthat is not odd at all, its just the evalutaion scheme.15:24
T_UNIXyet you'd need the corresponding IMAGE_FEATURE to be set in `local.conf` or in the distro conf?15:24
LetoThe2ndand IMAGE_FEATURES being a variable just like all others, no special15:25
RPkanavin: I'm just drowning on these hard to reproduce issues. I know its even harder for others to find the time to dive in and help though :(15:25
RPkanavin: the lrzsz thing I think had calmed down now15:25
qschulzT_UNIX: depending on what exactly you need to do, you could always do it but put that feature in a separate package. Then create a new image recipe with that specific package in it15:25
qschulzalways do it = always have your do_install_append15:25
kergothkayterina: removing them by hand is unlkikely to work at all unless you find each and every recipe that depends on them, which will be many. i'm assuming you mean DISTRO_FEATURES_remove, since the variable you mentioned doesn't exist, though?15:27
T_UNIXin this particular case it seems breaks expected behavior by busybox.15:27
kanavinRP, here's an idea: can we somehow give more people some kind of control over the autobuilder? If I or other people have no rights there, it follows that we're clueless in the face of those failures.15:28
*** dreyna <dreyna!> has joined #yocto15:28
*** blankscape <blankscape!~blankscap@> has joined #yocto15:28
RPkanavin: you mean ssh access?15:28
T_UNIXi.e. busybox.conf is basically ignroed, if your applet is within the `suid` binary. If you put it into the `.nosuid` split, it will never be able to gain suid.15:29
RPkanavin: its available to anyone who has need, just takes time to setup15:29
qschulzT_UNIX: and usually when you think something is a good idea and only a handful of recipes are doing it in upstream layers (and some maintained by YP people), it's usually not a good tale :)15:29
T_UNIXyeah, sure.15:29
blankscapeanyone know how to run a python function from a bbclass before do_install of a bitbake recipe ?15:30
T_UNIXbut, as LetoThe2nd explained, this particular point is not reasonable. It's just owed to the evaluation priorities/order.15:30
kergothdo_install[prefuncs] += "your_function"15:30
kergoththen define python your_function() { } as usual15:31
blankscapemm, i did exactly that but i dont see any print output in log.do_rootfs15:32
blankscapeive tried printing with just print() and bblog15:32
hpsy : The fetch command there appears to be incorrect, the one that worked for me is here:
qschulzT_UNIX: I'm sorry that's going too far in busybox behavior (or maybe you can explain a bit more beginner-friendly for me from the point of view of Yocto). Maybe depending on what you're going to work on, you can contribute that back to the appropriate layers :) good luck15:33
LetoThe2ndT_UNIX: no, its just not the intended use case that you are describing for IMAGE_FEATURES. the documentation pretty much clearly explains where it shall be set, what it means, and how it shall be extended if needed.
LetoThe2ndT_UNIX: if "developer image" means to you "add just this couple of packages", then you don't need them anyways. then you just extend IMAGE_INSTALL. but if "developer image" means for you "this and this and this have to beuilt differently, and this and that." thenyou are effectively changing the ABI of the image. and that is *EXACTLY* what a DISTRO is about.15:37
LetoThe2ndT_UNIX: feel free to argue about badly picked names (we have quite a few of those and used to the complaints), but the mindset and architectural underpinnings are *VERY* clear here.15:38
*** goliath <goliath!> has joined #yocto15:44
T_UNIXLetoThe2nd: hm... how would you  classify the passwordless root access?15:45
T_UNIXor maybe let me rephrase: how would you classify changing the suid behavior of busybox?15:47
LetoThe2ndT_UNIX: i would classify that being part of an image ABI.15:48
LetoThe2ndand hence to be affected by the distribution.15:48
LetoThe2ndof course, other opinions are valid too.15:49
adelcastRP: I just saw your opkg-utils patch on the ml, so without pipeline opkg-build was failing silently....15:50
T_UNIXfollowing that logic, wouldn't allowing "root no passwort" be an ABI break too?15:50
T_UNIXi.e. if the image was a blackbox you're interacting with on a binary level.15:51
LetoThe2ndit would, you are absolutely correct.15:51
T_UNIXyet it's a image feature?15:52
LetoThe2ndmind, i explicitly said that the names are far from being perfect.15:52
*** blankscape <blankscape!~blankscap@> has quit IRC15:52
LetoThe2ndand hence, we're stuck with "IMAGE_FEATURES".15:53
T_UNIXI guess I just need to let that sink for a moment to get the described concepts more clearly/straight in my head :)15:53
silviofHi #yocto! I'm facing the problem that own written task gets the error message "basehash value changed from <HASH1> to <HASH2> The metadata is not deterministic and this needs to be fixed." What could be the problem?15:53
LetoThe2ndsilviof: in the simplest case your task somewhere expands date or such.15:54
qschulzsilviof: most likely something with DATE or DATETIME in it15:54
* LetoThe2nd hi5es qschulz 15:54
qschulzLetoThe2nd: shoot. too slow.15:54
T_UNIXLetoThe2nd: so thanks for explaining the concepts behind and especially for pointing out that names *might* sometimes be a bit odd :)15:54
*** frsc <frsc!~frsc@2003:a:e7a:6200:a427:c148:e286:fbe7> has quit IRC15:55
silviofAh - oh thanks. will ook for this LetoThe2nd  anf qschulz15:55
*** guerinoni <guerinoni!> has quit IRC15:56
qschulzsilviof: a task is parsed multiple times I guess and if it changes between the times, it complains with the same message. What is the most straightforward change between the two parsings (parses? damn English is hard at that time of the day) is the current date15:56
T_UNIXLetoThe2nd: I guess we're both currently like :-D15:56
silviofI have included $DATETIME, but after removing I have still this message. Can I have a list of variables which get changed many times at pasring time?15:58
adelcast mcfrisk: were you able to get to the bottom of why opkg was crashing?15:58
*** hyper_dave <hyper_dave!~quassel@> has joined #yocto16:01
qschulzsilviof: which yocto version?16:02
silviofqschulz: 2.3.416:03
GeneralStupidqschulz: Ok, i watched the .config file and your right. Its my configuration. But when i boot the Image, it displays "Linux version 4.9.123-imx+g6a71cbc08975 (oe-user@oe-host) (gcc version 8.2.0 (GCC) ) #1 SMP PREEMPT Wed Nov 20 14:47:52 UTC 2019" but i built today16:04
GeneralStupidqschulz: maybe ... I forgot the "gunzip" step16:05
kergothsilviof: bitbake -S none yourrecipe; bitbake -S printdiff yourrecipe; if it's changing between parse runs, that would show it, since the first writes the data and the second compares to it16:06
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has joined #yocto16:06
silviofqschulz: Ahh thanks.16:07
silviofIt seems that I can also ignore this stuff when I set "BB_HASH_IGNORE_MISMATCH". Because I want a relation between imagenames (with DATETIME) I go this way. Thnaks for your help.16:07
qschulzkergoth: whaaaaaaaaat. And I here about it just now /o\? Thanks!!!!16:07
GeneralStupidqschulz: thanks a lot16:08
qschulzGeneralStupid: my pleasure.16:09
qschulzsilviof: be careful with your use of DATETIME. The mismatch is there for a reason, so if your task does not get retriggered because of a changed DATETIME but you're still using it to do some things... might get the wrong datetime I think16:10
qschulzsilviof: and you should thank kergoth as well :)16:10
kergothyeah, it's a fair point, excluding a varibale from the checksum will mean changes to it don't re-run the tasks.. sometimes that's just what you want, other times not so much16:11
Piratyadelcast: nice thing abot empty payloads, i didn't know opkg didn't support meta packages yet16:11
silviofkergoth: sorry think the answer came from qschuld. thanks a lot. 🙂16:12
adelcastPiraty: I am a bit mystified myself, I thought it already did16:12
adelcasthaven't had a chance to poke around, but I am almost certain that there are already supported virtual packages that installed correctly16:13
adelcastactually maybe virtual packages just don't have a payload, mmm16:13
Piratyehm, virtual packages is a differenct concept than meta packages (for me at least)16:15
Piratymeta meaning empty, just to provide sth like "base-system" that depends on everyhing relevant16:15
Piratyvirtual meaning sth like "java" which can be provided by different packages which all fulfill the virtual package requirement16:16
adelcastyes, sorry, I meant meta packages16:16
adelcastok, I  just looked inside packagegroup-core-buildessential16:17
adelcastwhich is a meta does have a data.tar.xz which is *almost* empty16:18
adelcastjust opening the file with vim I get that it has ./ as content16:19
adelcaston a truly empty payload, like in the one RP found, there was no I am wondering if all the created meta packages are *almost* empty and maybe they shouldn't...mmmmm16:20
RPadelcast: I suspect they contain an entry for "."16:22
JPEW^^ Sweeten your yocto build times with icecream16:22
Piratyicecream has some drawbacks16:23
moto-timothank you for saving me finding it16:23
RPadelcast: forwarded you my "fix" for opkg-build16:23
JPEWPiraty: It's not perfect, but it saves us a whole lot of time16:23
RPadelcast: curious what you make of it and how you think we should proceed16:23
adelcastRP: the odd thing is that if I run unxz data.tar.xz on one of the metapackages, I get a newly created data.tar file, mmm16:23
PiratyJPEW: default icecream doesn't allow VPN interfaces ( i think there is PR on their github for that though) which makes it highly dependant on secure infra16:24
moto-timoJPEW: in particular, some of the things that have a lot of compile time, like WebKit, must be better with distributed compile :)16:24
JPEWOh, ya. You'd have to have a *really* fast VPN to make it worth while anyway16:24
JPEWmoto-timo: Indeed it does. I didn't cover webkit in my presentation, but it's a pretty similar setup to qemu, which was a huge improvement16:25
moto-timothe beneficial use case is with co-located massive numbers of nodes16:25
RPadelcast: just checked and they do indeed have a "." entry16:25
JPEWmoto-timo: Also, this the container setup we use internally for all our builds:
moto-timoinstead of one aging dual Xeon box with 40 "cores", you could have 1000s.16:26
JPEWmoto-timo: Ya. As long as you have the bandwidth to back it up :)16:27
adelcastRP: ok, then it might just be just that the "." entry hide the empty payload bug for a while16:27
Piratyadelcast: RP: howto even create truly empty tar archives? tar -caf . on an empty one still gives ./ as content16:27
moto-timoJPEW: thank you16:27
JPEWmoto-timo: Pyrex also supports podman, so you don't need root privledges to run it :)16:27
moto-timoI've been thinking a lot about containerized builds specifically for ancient distros16:28
moto-timoJPEW: BONUS!16:28
adelcastRP: by the way your patch looks good and makes sense, I will pull it in16:28
LetoThe2ndwhenever i hear pyrex i think of the glass lid of my frying pan.16:28
moto-timoI think of my former life doing a lot more chemistry and beakers and such16:28
JPEWmoto-timo: I don't have it in yet, but I have been working on an image that can run oe-selftest also.16:29
RPadelcast: thanks! :)16:29
moto-timoJPEW: maybe we can collaborate on that, or at least I can be a guineau pig16:29
adelcastPiraty: I believe this will work tar cvf empty.tar --files-from /dev/null16:29
JPEWmoto-timo: Ya, that would be great! kergoth has already been trying it out also (and found and fixed a number of bugs)16:30
RPadelcast: we could probably save some space if we lose the "." entry...16:30
Piratyadelcast: indeed, now vim pukes at me16:30
*** vmeson <vmeson!> has quit IRC16:30
Piraty(opening that empty tar)16:30
RPadelcast: I wasn't keen on the bash dependency but for opkg-build it probably doesn't matter16:31
moto-timoJPEW: not surprised kergoth would be interested :)16:31
JPEWmoto-timo: The hard part with oe-selftest is qemu (as you pointed out). However, I think the solution to that is actually just to run qemu outside the container. Due to the magic of uninative, it just works AFAICT16:31
*** Bunio_FH <Bunio_FH!> has quit IRC16:31
LetoThe2ndnow i'm hungry.16:32
*** Chrusel <Chrusel!c1669b04@> has quit IRC16:32
moto-timoJPEW: I had the same instinct, but hadn't thought through the implementation details yet16:32
kergothJPEW: nice, oe-selftest support would be helpful16:32
* kergoth is using pyrex most days now, not all, but most16:33
JPEWkergoth: I meant to ask, are you using a custom built image, or pulling the prebuilt ones?16:33
kergothi just don't trust the sanity of my hosts anymore, regardless of distro. there's a reason i use asdf or pyenv to install global pythons in the homedir rather than using the host python.. and that's true for every langauge-specific setup16:33
moto-timokergoth: I second and third that sentiment.16:34
moto-timoI use pipenv for everything. everytime.16:34
kergotheven use homebrew on linux for a newer neovim on some of them :)16:34
moto-timothe overhead is trivial16:34
*** goliath <goliath!> has quit IRC16:35
kergothoh yeah, pipenv is handy. i tried poetry, i think it's nicer in theory than reality though. completely ditching means pip install . doesn't work, stuck with their tooling at the moment, and doing a full version lockdown of deps recursively can cause problems if one of your deps depends on a different version of one of its deps depending on the python verison you're using, end up having to16:36
kergothre-update/lock when you change python versions.. course pipenv probably hits that one too..16:36
kergothJPEW: i've been using a locally built stock pyrex image just to pick up those fixes, but will probably switch back to prebuilt since everything got merged and you updated the release, just haven't gotten around to it16:39
kergothmight need to play with a customized dockerfile for mentor / MEL needs eventually, but for now this is good16:39
armpitmoto-timo, when will the meta-py2 layer git published?16:39
adelcastRP: mmm, you are right, I haven't realized pipefail is a bashism16:40
RPadelcast: its why I changed the first line sh -> bash16:42
adelcastRP: hehe, I missed that part...I guess I need more coffee16:43
moto-timoarmpit: I have a script using 'git filter-branch' that is mostly there, but 'git filter-repo' is now the favored approach. Essentially, I want to inject the "From meta-openembeddecd commit: foo" into thee commit messages from meta-pythonn git history16:43
moto-timoarmpit: my priorities have changed very recently and I also have Thanksgiving to work on meta-python2, since it is mostly owntime.16:44
adelcastRP: targets that use lighterweight shells are unlikely to run opkg-build, I think?16:44
moto-timoif anybody uses 'git filter-repo' or 'git filter-branch' and knows how to do what I am suggesting above... I'm all ears16:44
RPadelcast: that was my thinking, installing bash when you're building ipks doesn't sound too onerous16:44
moto-timomy sed foo is failing me for some dumb reason16:45
moto-timoI'll send what I have to the ML16:45
armpitmoto-timo, its more in the light of having it available for folks to participate in16:45
armpitnot the its perfect16:45
moto-timoarmpit: yes, but I strongly desire to keep the former history in the new repo.16:45
moto-timoarmpit: and I am 80% there.16:46
*** xtron <xtron!~xtron@> has joined #yocto16:47
*** hpsy <hpsy!~hpsy@> has quit IRC16:48
adelcastRP: regarding the extra  "." entry, I think that should be an easy fix to opkg-build, I'll build a patch, now that opkg works with empty archives16:50
RPadelcast: ok, sounds good :)16:51
*** florian_kc <florian_kc!~florian_k@Maemo/community/contributor/florian> has quit IRC16:56
*** vmeson <vmeson!> has joined #yocto16:58
JPEWRP: regarding: It's very possible that might break something in oe-selftest17:00
*** yann|work <yann|work!~yann@> has quit IRC17:04
*** jmiehe <jmiehe!> has quit IRC17:08
RPJPEW: what kind of thing may break?17:08
*** diego_r <diego_r!> has quit IRC17:17
*** vmeson <vmeson!> has quit IRC17:18
JPEWRP: I don't have a specific and I haven't seen anything in my testing, just a heads up.17:23
*** armpit <armpit!~armpit@2601:202:4180:a5c0:74ae:93d3:f7e4:1219> has quit IRC17:24
JPEWOtherwise, I think I have core-image-sato and core-image-full-cmdline reproducible17:24
JPEWAt least, with rbutons pod2man patches17:25
*** vmeson <vmeson!> has joined #yocto17:28
*** xtron <xtron!~xtron@> has quit IRC17:38
rburtonperl won't be reproducbile with my patches17:38
*** goliath <goliath!> has joined #yocto17:50
RPrburton: we had some questions about those and the status in the call earlier17:52
khemRP: I am seeing nodejs-native builds failing on AB due to missing on host this is new I wonder what changed in master-next17:53
rburtonRP: i thought i put all my thoughts into the relevant bugs17:54
rburtonmaye not17:54
khemmight be this patch
khembut this existed before as well so why now18:00
khemoh centos-7, it has very old gcc ( 4.8 IIRC ) and does not install libatomic by default hmmm18:01
rburtonRP: doing a build in a container with no py218:02
*** ericch <ericch!> has quit IRC18:03
khembut blindly asking for libatomic is not good18:03
khemwe should ensure that gcc intrinsics do not have atomics before falling back to libatomic18:03
kergothhmm, did the glibc-locale host-user-contaminated issue ever get resolved?18:05
RPrburton: thanks. I figured if we could work out the current status we could then divide and conquer18:05
RPkergoth: yes!18:06
RPkergoth: its a makefile bug iirc18:06
kergothah, awesome18:06
rburtonkergoth: i haven't seen it since the race in the makefile was sorted18:06
rburtonok people18:06
* kergoth removes chown hack from one of his layers18:06
rburtonbets on first recipe to fail without host python2?18:06
RPkergoth: not quite makefile but kind of :)18:08
RPrburton: xcb ?18:08
rburtongood guess18:08
rburtoninherit autotools pkgconfig python3native18:08
rburtonbut maybe not18:08
rburtoni can smell dinner, i'll return in an hour and let you know :)18:09
*** leon-anavi <leon-anavi!~Leon@> has quit IRC18:15
*** yann|work <yann|work!> has joined #yocto18:19
khemkergoth: we fixed it by not particularly pretty fix but gets jobs done18:28
rburtonhuh its still building18:42
kergothdamn i forgot how much i love the topre switches in this happy hacking keyboard. kind of makes me sad given i can't use all my nice cherry-compatible keycaps with it..18:43
rburtonCurrently 13 running tasks (6822 of 7186)  94% |######################################   | that far through a sato build without any py2 on the host18:46
rburtonany bets on what task number it fails at? or, will it build?18:46
JPEWPrice is Right rules? I'll guess 6822 :)18:47
rburtontoo low!18:51
rburton~5500, tried to build python-native18:51
rburtonwhich needs host py18:51
kergothhuh. python-native needs host python? interesting18:51
rburtonhillariously it tried to use py3 on the host but the source isn't py3 friendly18:51
rburtonyeah it bootstraps a parser18:51
khemits python, rightly named18:58
khemmaybe it should be now called burmese python18:59
khemadelcast: I am using the latest patch you posted to ml and I am seeing opkg is taking like 10+ mins in do_rootfs its largish image but I think something has slowed down19:15
rburtonCurrently 20 running tasks (9467 of 12548)  75% |##############################          | and only python-native failed so far!19:19
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto19:22
JPEWrburton: Too bad. No new set of encyclopedias for me :(\19:23
*** T_UNIX <T_UNIX!uid218288@gateway/web/> has quit IRC19:29
RP - that graph looks periodic?! :/19:34
tgamblinRP: build times?19:39
RPtgamblin: yes, of our performance tests19:40
RPthose are isolated to run in a contained way so should be consistent19:40
tgamblinIt certainly does look periodic19:40
RPtgamblin: and it shouldn't be :/19:45
* RP really can't afford to look into that right now19:45
yoctiNew news from stackoverflow: My other imx7d pico android things start kit died, again <>19:46
*** ericch <ericch!> has joined #yocto19:46
*** Sandrita <Sandrita!d0586e2e@gateway/web/cgi-irc/> has quit IRC19:50
*** armpit <armpit!~armpit@> has joined #yocto19:51
*** florian <florian!~florian_k@Maemo/community/contributor/florian> has joined #yocto19:53
RPrburton: nice! :)20:11
rburtonRP: very periodic.  what day is the spike on i wonder20:11
RPrburton: the ubuntu perf doesn't do that20:12
RPrburton: that is a good question. Its as if there is a cron job20:12
rburtonRP: i was thinking a weekly purge job causing IO20:12
RPrburton: or a man page indexer or similar20:13
rburtonthat shouldn't take so long, but yes something like that20:15
*** Phanes <Phanes!Phanes@surro/founder/phanes> has quit IRC20:19
*** goliath <goliath!> has quit IRC20:22
RPrburton: probably tracker :)20:25
RPhmm, had a great idea to do with the autobuilder, went to file the bug, got distracted and now can't remember what it was20:26
*** Phanes <Phanes!~Phanes@surro/founder/phanes> has joined #yocto20:26
* RP did remember and filed it20:30
*** tgamblin <tgamblin!~tgamblin@> has quit IRC20:40
*** nrossi <nrossi!uid193926@gateway/web/> has quit IRC20:44
*** goliath <goliath!> has joined #yocto21:02
*** aidanh_ <aidanh_!~aidanh@unaffiliated/aidanh> has joined #yocto21:07
*** marble_visions_ <marble_visions_!~user@> has joined #yocto21:07
*** Dracos-Carazza <Dracos-Carazza!> has quit IRC21:10
*** iceaway_ <iceaway_!~pelle@> has joined #yocto21:10
*** alicef <alicef!~none@gentoo/developer/alicef> has quit IRC21:12
*** marble_visions <marble_visions!~user@> has quit IRC21:12
*** aidanh <aidanh!~aidanh@unaffiliated/aidanh> has quit IRC21:12
*** Saur <Saur!pkj@nat/axis/x-itclrcmwlhsuqvhr> has quit IRC21:12
*** iceaway <iceaway!~pelle@> has quit IRC21:12
*** aidanh_ is now known as aidanh21:12
*** Dracos-Carazza_ <Dracos-Carazza_!> has joined #yocto21:12
*** alicef <alicef!~none@gentoo/developer/alicef> has joined #yocto21:13
*** Saur <Saur!pkj@nat/axis/x-qewlovcmryuamlgx> has joined #yocto21:14
JaMaRP: looks like you sent last batch of oe-core patches to bitbake-devel ML21:16
*** __angelo <__angelo!~prefetch@unaffiliated/ad/x-0785363> has quit IRC21:16
khemRP: sanlock is showing sstate errors I cant co-relate it to anything in recipe21:17
*** tgamblin <tgamblin!> has joined #yocto21:17
khemException: KeyError: 'getpwuid(): uid not found: 6000'21:17
RPJPEW: you may want to look at that backtrace, its from your code :)21:20
RPkhem: I'm guessing this recipe generates something with build UID leakage into its target21:20
RPkhem: pseudo is quite correctly saying uid 6000 doesn't exist on the target21:20
RP6000 is the UID of pokybuild on that worker iirc21:21
RPso its host contamination into the target package21:21
RPthe backtrace could be better21:21
RPJaMa: gah, sorry :( (thanks)21:21
RPkhem: the reason its showing up is we enabled hash equivalence but I suspect a bug in the sanlock recipe21:23
khemRP: I know it needs sanlock user/group which I added but it still fails21:23
khemRP:yes thats what I am interested in fixing21:23
RPkhem: let me see if can build it locally to debug21:26
*** stephano <stephano!> has quit IRC21:27
khemRP: cp -a /mnt/b/yoe/build/tmp/work/core2-32-yoe-linux-musl/sanlock/3.8.0-r0/image//usr/lib21:28
khemcp -a /mnt/b/yoe/build/tmp/work/core2-32-yoe-linux-musl/sanlock/3.8.0-r0/image//usr/lib21:28
khemcp -a /mnt/b/yoe/build/tmp/work/core2-32-yoe-linux-musl/sanlock/3.8.0-r0/image//usr/lib21:28
khemcp -a /mnt/b/yoe/build/tmp/work/core2-32-yoe-linux-musl/sanlock/3.8.0-r0/image//usr/lib21:28
khemwill that do it21:28
RPkhem: yes21:28
RPkhem: they will be owned by the build user21:28
khemright -a21:28
RPkhem: do a chown root.root afterwards21:29
khemits in its makefiles so maybe replace cp  -a with install -D 0755 ?21:30
RPkhem: right21:30
RPkhem: or a blanket do_install_append chown21:30
RPkhem: depends on context really21:30
*** chandana73 <chandana73!~ckalluri@> has joined #yocto21:38
khemmaybe fixing makefile is better21:40
*** stephano <stephano!> has joined #yocto21:44
*** jae1 <jae1!95c73e81@> has joined #yocto21:44
JPEWRP: Hmm, that is annoying. Is that something the QA check would have caught, but couldn't because outhash calc ran first?21:45
RPJPEW: probably, yes21:49
JPEWRP: Would it be better to bail out without reporting a hash in that case (maybe just issue a warning)?21:52
RPJPEW: probably, we should check the QA tests pick it up though21:55
rburtonOH GOD why does llvm take over 10 minutes to package21:57
rburtonright package finished in 12 minutes22:00
RPrburton: bitbake -P ;-)22:00
RPmeans you'd have to rerun it though22:00
rburtoni know why really, its the fact that its is HUUGE22:00
RPah, debug sources22:01
RPkhem: +do_install_append () {22:03
RP+    chown root.root ${D} -R22:03
RPkhem: that fixed it locally FWIW22:03
*** hpsy <hpsy!~hpsy@> has joined #yocto22:05
*** dv_ <dv_!> has quit IRC22:06
khemRP: cool. I am testing this
RPkhem: ok22:07
*** armpit <armpit!~armpit@> has quit IRC22:17
rburtonhm py2 really does appear to need py2 to build22:19
*** dv_ <dv_!> has joined #yocto22:19
tgamblinhmm. Anyone else doing any active build tests on Fedora 31?22:19
kergothrburton: that seems odd, there must be a way to bootstrap it..especially since cpython is written in C mostly..22:23
JPEWtgamblin: I'm building on Fedora 3122:23
tgamblinJPEW: done an update recently? I'm running into "corrupt GNU build attribute note: wrong note type: bad value" when building poky. Wasn't happening prior to the update, but maybe it's something else22:25
rburtonkergoth: for native you might be able to get away with not regenerating, but we might be doing something to force the regen22:25
JPEWtgamblin: No, I think I'm a bit behind22:25
JPEWtgamblin: Ya, I have 333 package updates pending22:26
tgamblinJPEW: K. I'll keep pok(y)ing around22:32
tgamblinIt seems that someone has asked about the issue on the Fedora subreddit under a different context22:32
JPEWWell, maybe I'll put off updating a little longer :)22:32
tgamblinNot a bad idea!22:33
*** jae1 <jae1!95c73e81@> has quit IRC22:35
*** WillMiles <WillMiles!> has quit IRC22:36
RPJPEW, khem: Worryingly if I bypass that keyerror, there is no QA warning :(22:36
JPEWThats not good22:36
RPdo i investigate or file a bug I wonder22:37
JPEWYou can file a bug to make outhash calc fail more gracefully and assign it to me at least22:38
JPEWUnless you already have a sufficent patch22:38
RPJPEW: not yet22:39
rburtonNOTE: Tasks Summary: Attempted 12502 tasks of which 12340 didn't need to be rerun and 1 failed.22:40
rburtonwell strike me down with a feature22:40
rburtonerm, feather22:40
RPrburton: wow!22:40
rburtonoe-core world minus python and u-boot builds without py2 on the host22:40
rburtoni was expecting some bits to call /usr/bin/python directly, but apparently not22:41
*** dreyna <dreyna!> has quit IRC22:42
RPrburton: yes, quite surprising22:46
RPJPEW, khem: do_package_qa sees uid as 0, the sstatesig code sees uid as 100022:47
kergothrburton: nice22:48
RPJPEW, khem: the files in package/ are owned by build UID, when they get to package-split they've been "fixed" to root/root, probably by the packaging fixup code22:55
RPso the end packages are correct but the data written into the sstate object includes package/22:56
RPhence why the QA doesn't see it but hashequiv does22:56
RPfiles get stripped so the hardlink doesn't help22:56
RPIf anyone has some spare cycles, the remaining failures on looks reproducible (postinst failing with reproducible builds)23:03
RPso close...23:03
* RP -> sleep23:13
yoctiNew news from stackoverflow: Toolchain build using yocto <>23:17
*** ericch <ericch!> has quit IRC23:29
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has quit IRC23:43
*** agust <agust!> has quit IRC23:46
*** tgamblin <tgamblin!> has quit IRC23:53
*** goliath <goliath!> has quit IRC23:58

Generated by 2.11.0 by Marius Gedminas - find it at!