Wednesday, 2019-08-28

*** nerdboy <nerdboy!~sarnold@gentoo/developer/nerdboy> has joined #yocto00:56
*** stephano <stephano!stephano@nat/intel/x-esuqsdhvgnordopw> has quit IRC00:59
*** Chrusel <Chrusel!c1669b04@> has quit IRC01:26
*** JPEW_ <JPEW_!~JPEW@2605:a601:21d1:5200:620a:c230:ada8:3135> has joined #yocto01:44
*** kaspter <kaspter!~Instantbi@> has joined #yocto01:47
*** JPEW__ <JPEW__!~JPEW@2605:a601:21d1:5200:620a:c230:ada8:3135> has joined #yocto01:47
*** kaspter <kaspter!~Instantbi@> has quit IRC01:51
erakisJPEW: So how do we handle that ? I already have a recipe, so without updating the recipe's name (version) okpg will not be able to differentiate them in term of which one is the more recent ? Does it means that each time a new software release is available but the recipe does not required to be change, we even need to create a copy `1_1` of the recipe but incremented manually the version `1_2` in file name to get a new package that opkg01:54
erakiswill now see a more recent ?01:54
*** kaspter <kaspter!~Instantbi@> has joined #yocto01:59
*** erakis <erakis!~erakis@> has quit IRC01:59
*** JPEW- <JPEW-!> has joined #yocto02:08
*** JPEW__ <JPEW__!~JPEW@2605:a601:21d1:5200:620a:c230:ada8:3135> has quit IRC02:10
*** JPEW_ <JPEW_!~JPEW@2605:a601:21d1:5200:620a:c230:ada8:3135> has quit IRC02:10
*** JPEW_ <JPEW_!~JPEW@2605:a601:21d1:5200:620a:c230:ada8:3135> has joined #yocto02:10
*** JPEW_ <JPEW_!~JPEW@2605:a601:21d1:5200:620a:c230:ada8:3135> has joined #yocto02:10
*** JPEW <JPEW!cc4da337@> has quit IRC02:20
*** JPEW- <JPEW-!> has quit IRC02:23
*** JPEW <JPEW!> has joined #yocto02:27
*** JPEW <JPEW!> has quit IRC02:29
*** JPEW <JPEW!> has joined #yocto02:35
*** zopsi <zopsi!~zopsi@> has joined #yocto02:43
*** JPEW <JPEW!> has quit IRC02:54
*** radsquirrel <radsquirrel!> has quit IRC02:56
*** radsquirrel <radsquirrel!> has joined #yocto02:57
*** JPEW <JPEW!> has joined #yocto02:58
*** nameclash <nameclash!> has quit IRC03:12
*** JPEW <JPEW!> has quit IRC03:15
*** yizhao <yizhao!~zhaoyi@> has quit IRC03:18
*** yizhao <yizhao!> has joined #yocto03:19
*** JPEW <JPEW!> has joined #yocto03:23
*** yizhao <yizhao!> has quit IRC03:25
*** nerdboy <nerdboy!~sarnold@gentoo/developer/nerdboy> has quit IRC03:27
*** learningc <learningc!> has joined #yocto03:37
*** armpit <armpit!> has joined #yocto03:42
*** camus <camus!~Instantbi@> has joined #yocto04:32
*** khem <khem!~khem@unaffiliated/khem> has quit IRC04:33
*** kaspter <kaspter!~Instantbi@> has quit IRC04:34
*** camus is now known as kaspter04:34
*** camus <camus!~Instantbi@> has joined #yocto04:46
*** kaspter <kaspter!~Instantbi@> has quit IRC04:48
*** camus is now known as kaspter04:48
*** jacques2 <jacques2!~jacques@nslu2-linux/jacques> has joined #yocto05:27
*** linuxjacques <linuxjacques!~jacques@nslu2-linux/jacques> has quit IRC05:30
*** AndersD <AndersD!> has joined #yocto05:31
*** kaspter <kaspter!~Instantbi@> has quit IRC05:45
*** kaspter <kaspter!~Instantbi@> has joined #yocto05:46
*** kaspter <kaspter!~Instantbi@> has quit IRC05:55
*** kaspter <kaspter!~Instantbi@> has joined #yocto05:56
*** goliath <goliath!> has joined #yocto06:05
*** georgem <georgem!~georgem@> has quit IRC06:05
*** georgem <georgem!~georgem@> has joined #yocto06:05
*** kroon <kroon!~kroon@> has joined #yocto06:12
*** kaspter <kaspter!~Instantbi@> has quit IRC06:16
*** kaspter <kaspter!~Instantbi@> has joined #yocto06:17
*** ralu <ralu!> has joined #yocto06:27
*** tprrt <tprrt!~tprrt@> has joined #yocto06:30
*** rob_w <rob_w!~bob@unaffiliated/rob-w/x-1112029> has joined #yocto06:31
*** frsc <frsc!> has joined #yocto06:32
*** thaytan <thaytan!> has quit IRC06:36
*** thaytan <thaytan!> has joined #yocto06:37
*** frsc <frsc!> has quit IRC06:38
*** frsc <frsc!> has joined #yocto06:41
*** TobSnyder <TobSnyder!> has joined #yocto06:43
*** opennandra <opennandra!> has joined #yocto06:44
*** frsc <frsc!> has quit IRC06:47
*** frsc <frsc!> has joined #yocto06:48
ProffalkenLetoThe2nd / qschulz: I've just tried to run with "stock" poky and get exactly the same error about the *.bb files not being found.  I've uploaded the entire repo to and would really appreciate it you or someone else could take a look and see where I'm going wrong given that this isn't specific to the original project I was working on?06:56
LetoThe2ndProffalken: the repo doesn't seem to contain the layer in question?07:04
*** nslu2-log <nslu2-log!~nslu2-log@> has quit IRC07:05
*** mckoan|away is now known as mckoan07:08
mckoangood morning07:08
qschulzProffalken: cd /tmp; git clone; cd yocto-testing; source oe-init-build-env; bitbake core-image-minimal => OK for parsing, it starts to build stuff07:10
LetoThe2ndqschulz: i can't see the layer in question there anyway, its a generic poky AFAICS07:11
qschulzLetoThe2nd: yes, see last answer from Proffalken07:13
qschulz"I've just tried to run with "stock" poky and get exactly the same error about the *.bb files not being found."07:13
LetoThe2ndqschulz: i guess we are mixing things up now.07:14
*** goliath <goliath!> has quit IRC07:14
qschulzProffalken: start from scratch with new git clone from upstream repos in a new terminal?07:15
LetoThe2ndbecause "running with stock poky" means to me running the layer i question *with* stock poky. not stock poky alone, i think that this can be considered fine.07:15
*** nslu2-log <nslu2-log!~nslu2-log@> has joined #yocto07:17
qschulzLetoThe2nd: one of us misinterpreted :) Let's see what Proffalken was trying to say07:20
*** yacar_ <yacar_!> has joined #yocto07:24
*** JaMa <JaMa!> has joined #yocto07:31
*** Bunio_FH <Bunio_FH!> has joined #yocto07:37
ProffalkenHmmm, hang on, let me find out what's going on here...07:55
ProffalkenThe layer should be in the "top level" directory07:55
Proffalkenhahahah, I pushed the wrong branch... try
Proffalken(as you can see, I've just cut&pasted the commands from the quickstart to get the branch name etc)07:58
*** goliath <goliath!~goliath@> has joined #yocto07:58
LetoThe2ndok, now it makes sense :)08:05
*** khem <khem!~khem@unaffiliated/khem> has joined #yocto08:05
*** Proffalken is now known as Proffalken__08:08
*** Proffalken <Proffalken!uid388181@gateway/web/> has joined #yocto08:09
*** kaspter <kaspter!~Instantbi@> has quit IRC08:10
*** kaspter <kaspter!~Instantbi@> has joined #yocto08:10
*** Lihis <Lihis!> has quit IRC08:17
*** Lihis <Lihis!~Lihis@2001:41d0:e:f34::1> has joined #yocto08:18
*** yacar_ <yacar_!> has quit IRC08:25
*** yacar_ <yacar_!> has joined #yocto08:49
qschulzProffalken__: which machine are you building for?08:55
qschulzProffalken__: cd /tmp; git clone -b my-yocto-2.7.1; cd yocto-testing; source oe-init-build-env; [add /tmp/yocto-testing/meta-telegraf to BBLAYERS in conf/bblayers]; echo 'DISTRO_FEATURES+="systemd"' >> conf/local.conf; MACHINE=beaglebone-yocto bitbake telegraf;09:01
qschulzno warning09:01
*** opennandra <opennandra!> has quit IRC09:03
qschulzI got the warning only when building qemux86 (default machine) because your recipe is buildable for arm only (and you explicited it). Then building beaglebone-yocto which is arm-based would have the same warning because telegraf can be built only when DISTRO_FEATURES has systemd in it09:03
qschulzhence, you've got a layer without recipes in it because all the recipes (telegraf only) can't be built for the specific distro or machine09:03
LetoThe2ndqschulz: interesting, i only set qemuarm, and still got the warning. didn't make the mental transition to enabling systemd too :-(09:03
qschulzsince this is resolved durnig parsing, you're including a layer which is empty09:03
qschulzLetoThe2nd: I saw it only because I tried to build telegraf only and it failed for the two aforementioned reasons :)09:04
LetoThe2ndqschulz: kudos, good find!09:04
qschulzLetoThe2nd: \o/09:05
Proffalkenqschultz: Ah, cool, ok, so I need to add a systemd layer as well?09:07
ProffalkenI'm building for armhf (pi3/pi0) if that makes a difference?09:07
qschulzProffalken__: well that makes the recipe OK from the compatible_host/machine point of view. But you still need systemd in your DISTRO_FEATURES09:09
qschulzbecause of , I assume09:09
qschulzso 1. remove this if it's not a hard requirements09:10
qschulzor 2. add DISTRO_FEATURES += "systemd" in the correct place (and I never know where it should be, maybe conf/local.conf but I don't like putting things there, or conf/machine/machineyoureusing.conf, or recipes-*/*/ or conf/distro/distroyourebuilding.conf)09:11
ProffalkenCool, thanks, I'll give that a go...09:11
qschulzProffalken__: OR, have more than one recipe that does not depend on the compatible or distro features :)09:12
*** kaspter <kaspter!~Instantbi@> has quit IRC09:12
qschulzbut anyway, to be able to build telegraf you'll need a correct machine and a correct DISTRO_FEATURES09:12
*** kaspter <kaspter!~Instantbi@> has joined #yocto09:12
qschulzso having a second recipe "compatible-free and systemd-free" is just going to remove the warning but not going to make telegraf buildable09:13
yoctiNew news from stackoverflow: YOCTO : Where can I find my linux image kernel headers Needed to build drivers and how can I install them? <>09:13
*** PinkSnake <PinkSnake!51ff1123@> has joined #yocto09:26
*** Crofton|mini <Crofton|mini!~Crofton@2601:5c0:c100:b84:3d3f:64d6:2ba1:780b> has joined #yocto09:28
PinkSnakeI'm trying to create an extended sdk for dev team but i'm stuck here : checking target system type... Invalid configuration `x86_64-custdistro-sdk-linux': system `sdk-linux' not recognized. I can't find where the trouble is inside the distro conf ... any idea ? Full log:
*** cquast_ <cquast_!~cquast@> has joined #yocto09:32
yoctiNew news from stackoverflow: How to structure Yocto conf files for two different machines and same bblayers <>09:43
*** AndersD <AndersD!> has quit IRC09:48
*** AndersD <AndersD!> has joined #yocto09:48
*** yacar_ <yacar_!> has quit IRC09:51
*** T_UNIX <T_UNIX!uid218288@gateway/web/> has joined #yocto10:03
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has joined #yocto10:07
*** cquast_ <cquast_!~cquast@> has quit IRC10:11
*** cquast_ <cquast_!~cquast@> has joined #yocto10:16
*** learningc <learningc!> has quit IRC10:23
*** cquast_ <cquast_!~cquast@> has quit IRC10:26
*** cquast <cquast!~cquast@> has joined #yocto10:28
MarcWe1Hi, i have an issue whit my buid system/sdk ( i cant get geoclue to build ). arm-oe-linux-gnueabi-gcc gives the error  unrecognized command line option '-fstack-clash-protection'10:30
MarcWe1and i can finde somthing in geoclue that is truning on the option10:31
*** lucaceresoli_ <lucaceresoli_!> has joined #yocto10:38
*** lucaceresoli <lucaceresoli!> has quit IRC10:38
*** lucaceresoli <lucaceresoli!> has joined #yocto10:38
yoctiNew news from stackoverflow: Rotate framebuffer works only with 180° and 0° <>10:43
*** PinkSnake <PinkSnake!51ff1123@> has quit IRC10:50
yoctiNew news from stackoverflow: Why does the yocto bblayers.conf file use absolute paths? <>11:13
orzenHi, just noticed that my patch (posted on 16th of august) havn't received any comments or got merged. How far does the patch backlog stretch and when can I expect that my patch get some attention? :)11:31
*** rob_w <rob_w!~bob@unaffiliated/rob-w/x-1112029> has quit IRC11:32
*** yann <yann!~yann@> has joined #yocto11:33
*** yacar_ <yacar_!~yacar@> has joined #yocto11:39
kroonorzen, wiki page says its perfectly fine to send a reminder ping to the list, but the project is in feature freeze now I believe, so perhaps patch review/merge takes longer11:43
*** learningc <learningc!~learningc@> has joined #yocto11:45
*** berton <berton!~berton@> has joined #yocto11:53
*** rob_w <rob_w!~bob@unaffiliated/rob-w/x-1112029> has joined #yocto11:55
*** berton <berton!~berton@> has quit IRC11:56
*** berton <berton!~berton@> has joined #yocto11:58
orzenkroon: I see, thank you!11:58
*** learningc <learningc!~learningc@> has quit IRC12:06
*** ykrons <ykrons!~guillaume@> has joined #yocto12:23
zeddiiRP: sorry for not sending that series. *both* my builders had full disks, so I had to deal with that before starting my round of builds.12:27
*** nabokov <nabokov!~armand@> has joined #yocto12:40
RPzeddii:  np, I'm having fun with plenty of other patches12:40
zeddiiI'm 3/4 of the way through the builds, so it will be out today.12:44
ykronsHi all12:45
ykronsI'm trying to create a recipe from a git repository with devtool add ssh://
ykronsbut I get an error Failed to fetch URL xxxx with ERROR: Command 'script -e -q -c "recipetool --color=always create --devtool -o /tmp/devtoolertuu76w 'git://'  -x /home/guillaume/data/Fusion/stuff/oe-core-SCR2/build/workspace/sources/devtoolsrc5vqso2w4" /dev/null' failed12:48
*** JPEW <JPEW!> has quit IRC12:49
*** JPEW <JPEW!> has joined #yocto12:50
ykronsHaving a look to the recipetool commands, it seems the final SRC_URI generated is something like SRC_URI = "git://;protocol=ssh". It seems there is an issue with the custom ssh port 7999.12:51
ykronsDoes someone know the right way to pass URL to devtool / recipetool for git repository accessed through SSH on port 7999? I have tried to add ";port=7999" but it don't fix the issue12:52
*** Crofton|work <Crofton|work!~balister@2601:5c0:c100:b84:c22d:c40:ab44:9e37> has joined #yocto13:01
*** kaspter <kaspter!~Instantbi@> has quit IRC13:11
jwesselRP: Do you know where the checkvnc comes from?   I am trying to duplicate the failure that was detected to see whats up.  It will be interesting to understand the cause/effect, because I would not have expected any kind of drastic change with the fast fail tty for systemd.13:13
yoctiNew news from stackoverflow: How to build a working TPM2 image for Raspberry Pi with Yocto? <> || Change YOCTO Linux kernel version <>13:13
jwesselThe log you pointed me at showed: Running '. ./oe-init-build-env; /home/pokybuild/yocto-worker/qa-extras2/yocto-autobuilder-helper/scripts/checkvnc; DISPLAY=:1 bitbake core-image-sato:do_testimage -k' with output to /home/pokybuild/yocto-worker/qa-extras2/build/build/command.log.6c13:13
jwesselThat is the checkvnc I was asking about.13:14
RPjwessel: you mean the contents of that script?13:20
jwesselyes.  It seems to be related to the autobuilder.   I am not sure if that is part of the failure, part of the test or what.13:20
RPjwessel: its ensuring there is a DISPLAY available13:20
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has quit IRC13:21
jwesselSo in theory I just have to run:  bitbake core-image-sato:do_testimage13:23
*** AndersD <AndersD!> has quit IRC13:24
*** erakis <erakis!~erakis@> has joined #yocto13:25
RPjwessel: yes13:30
RPjwessel: that is just autobuilder boilerplate around the command13:30
*** florian_kc <florian_kc!~florian_k@Maemo/community/contributor/florian> has joined #yocto13:34
*** florian_kc is now known as florian13:45
*** Dracos-Carazza <Dracos-Carazza!~Dracos-Ca@> has quit IRC13:51
*** Dracos-Carazza_ <Dracos-Carazza_!~Dracos-Ca@> has joined #yocto13:51
*** TobSnyder <TobSnyder!> has quit IRC13:58
*** kroon <kroon!~kroon@> has quit IRC13:59
*** armpit <armpit!> has quit IRC14:15
ykronsI find the issue, it has already been fixed :
*** rob_w <rob_w!~bob@unaffiliated/rob-w/x-1112029> has quit IRC14:31
*** alessioigor_ <alessioigor_!~alessioig@> has joined #yocto14:32
*** alessioigor <alessioigor!~alessioig@> has quit IRC14:34
*** alessioigor_ is now known as alessioigor14:34
*** goliath <goliath!~goliath@> has quit IRC14:41
yoctiNew news from stackoverflow: Yocto recipe python whl package <>14:44
*** kroon <kroon!> has joined #yocto14:46
*** learningc <learningc!~learningc@> has joined #yocto14:50
*** tprrt <tprrt!~tprrt@> has quit IRC15:06
*** armpit <armpit!~armpit@> has joined #yocto15:16
*** kroon <kroon!> has quit IRC15:18
*** florian_kc <florian_kc!~florian_k@Maemo/community/contributor/florian> has joined #yocto15:20
*** goliath <goliath!> has joined #yocto15:20
*** soderstrom <soderstrom!~soderstro@gateway/shell/> has joined #yocto15:21
*** soderstrom <soderstrom!~soderstro@gateway/shell/> has joined #yocto15:26
*** soderstrom <soderstrom!~soderstro@gateway/shell/> has quit IRC15:27
*** soderstrom <soderstrom!~soderstro@gateway/shell/> has joined #yocto15:29
*** Bunio_FH <Bunio_FH!> has quit IRC15:30
__angelois there a suggested linxu distro to work with yocto ?15:32
__angelo*linux :)15:33
frayno, but there are basic functional requirements..15:33
LetoThe2nd__angelo: anything listed in the manual as being supported?15:33
LetoThe2ndfray: "it boots", "it can run vi"15:33
frayUbuntu seems to be the easiest to get a modern system to build easily, but RHEL/CentOS 7 works fine..  I've not used RHEL 8 yet..15:33
fraybut RHEL/CentOS 7 may require some additional (newer) software to be installed..15:34
__angeloLetoThe2nd, the fact is that i fight to work with an updated linux. Ok will check.15:34
*** soderstrom <soderstrom!~soderstro@gateway/shell/> has quit IRC15:34
LetoThe2ndmy vote would be in ubuntu too. if in doubt, yank up a docker container running it on whatever your preferred host system is (that my technique)15:34
*** soderstrom <soderstrom!~soderstro@gateway/shell/> has joined #yocto15:34
frayif you are on a specific release, say 'Thus' (YP 2.8).. then you should create a VM or Container with a Linux OS from that era.. say Ubuntu 18.04 LTS.. and use that for development.. because newer OSes will change interfaces that the system may depend on.15:34
fraybut for 'master', it should work on the latest versions of the common OSes15:35
__angelofray,  LetoThe2nd ok thanks15:36
*** yacar_ <yacar_!~yacar@> has quit IRC15:36
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has joined #yocto15:37
RPnrossi: let me know if/as/when you're around15:43
*** learningc <learningc!~learningc@> has quit IRC16:07
*** armpit <armpit!~armpit@> has quit IRC16:11
*** yann <yann!~yann@> has quit IRC16:17
*** mckoan is now known as mckoan|away16:22
*** nerdboy <nerdboy!~sarnold@gentoo/developer/nerdboy> has joined #yocto16:26
*** armpit <armpit!~armpit@> has joined #yocto16:27
*** florian_kc <florian_kc!~florian_k@Maemo/community/contributor/florian> has quit IRC16:39
*** frsc <frsc!> has quit IRC16:40
* zeddii waits for the last builds to complete ....16:52
* kanavin_ is running a world build in a python2-less environment17:03
kanavin_so far, ca-certificates has failed, and, surprisingly, pseudo17:04
smurraykanavin_: I did a bit of tinkering with that yesterday as well, I'm wondering did you tweak things so python -> python3, or did you remove it altogether?17:06
kanavin_smurray, I removed it on the host distro, then dropped it from HOSTTOOLS, and also dropped the python-native and python recipes for good measure17:07
kanavin_python -> python3 is a really wrong thing to do17:07
smurraykanavin_: slight issue is some distros have done it, so there are some checks for it17:08
kanavin_smurray, I have removed that bit as well17:08
smurraykanavin_: you went further than I did, I left the python recipes in place so python-native could work, as I thought that was RP was implying on the call yesterday17:09
kanavin_smurray, there are basically 3 recipes that need them, ltp, perf and kernel-devsrc17:10
kanavin_I fixed ltp, and removed perf and kernel-devsrc :)17:10
kanavin_(and tweaked the packagegroups to not include them)17:10
kanavin_I trust Bruce will get to fixing the last two17:10
kanavin_okay llvm-native is the latest to go bust17:10
smurraykanavin_: I think my having python -> python3 avoided some issues, ca-certificates and pseudo built here17:11
kanavin_smurray, good to know they're compatible with py3 then, it's probably a matter of patching them to use python3 explicitly17:11
smurraykanavin_: systemtap blew up for me, but I suspect its python3 detection logic is wonky and may work with just python3 available17:11
smurraykanavin_: I did look at kernel-devsrc a bit, afaict all the scripts in the kernel "scripts" directory are python3 compatible, though some of them use /usr/bin/python :/17:14
kanavin_smurray, right, I trust Bruce will find the right way to handle this, as he knows better what scripts are important17:16
smurraykanavin_: yeah17:16
RPkanavin_, smurray: this all sounds like good data. I suspect pseudo's python usage is really simple and easily tweaked to python3 explicitly17:20
RPzeddii: cool17:21
*** rewitt1 <rewitt1!rewitt@nat/intel/x-xxkudrzjekyughqr> has quit IRC17:21
smurraykanavin_: I think the only other thing I noticed that would need cleanup is the gpgme recipe, the python2 PACKAGECONFIG would need to be removed17:22
kanavin_smurray, yes, but it is not enabled by default, so not a priority really :)17:23
smurraykanavin_: and I just noticed with grep that there's a PACKAGECONFIG in alsa-tools  that references "python-core python-pygobject pyalsa"17:23
kanavin_smurray, same there17:23
smurrayeasy enough to fix17:23
kanavin_RP: I fixed ca-certificates and pseudo, and resumed the build17:23
kanavin_RP, it's at gcc-cross now, so the bulk of recipes are yet to be tests17:23
zeddiikanavin_, yah. I have the kernel ones done. they'll be in my series in a few hours17:24
*** T_UNIX <T_UNIX!uid218288@gateway/web/> has quit IRC17:29
smurrayheh, I need a second build machine, I switched off of python tinkering to churn some AGL builds17:30
*** yann <yann!> has joined #yocto17:37
*** rewitt <rewitt!~rewitt@> has joined #yocto17:44
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has quit IRC17:52
*** King_InuYasha <King_InuYasha!~King_InuY@fedora/ngompa> has quit IRC17:52
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has joined #yocto18:53
*** Bunio_FH <Bunio_FH!> has joined #yocto19:00
*** florian_kc <florian_kc!~florian_k@Maemo/community/contributor/florian> has joined #yocto19:03
*** learningc <learningc!~learningc@> has joined #yocto19:03
*** Bunio_FH <Bunio_FH!> has quit IRC19:03
*** learningc <learningc!~learningc@> has quit IRC19:08
*** florian <florian!~florian_k@Maemo/community/contributor/florian> has quit IRC19:19
*** florian_kc is now known as florian19:19
*** florian_kc <florian_kc!~florian_k@Maemo/community/contributor/florian> has joined #yocto19:19
*** rewitt <rewitt!~rewitt@> has quit IRC19:31
*** WillMiles <WillMiles!> has joined #yocto19:35
RPsmurray: As long as they're not on my default they're ok. We have precedent for things which add dependencies external to oe-core as long as they're not default19:59
smurrayRP: is the thinking that the python 2 recipes will shift to meta-python?20:03
RPsmurray: probably a dedicated meta-python220:12
* zeddii nods. 20:13
zeddiiRP: you’ve seen my series, I think the kernel can be out from under the python2 thumb now :D20:13
* zeddii is glad to get that fixed up. 20:14
*** rewitt <rewitt!rewitt@nat/intel/x-twfziqebxhjnkvxl> has joined #yocto20:22
Crofton|workzeddii, thanks20:54
RPzeddii: yes, sounds good thanks :)20:58
*** goliath <goliath!> has quit IRC21:09
*** neverpanic <neverpanic!> has quit IRC21:13
*** berton <berton!~berton@> has quit IRC21:15
smurrayRP: it occurs to me that u-boot is unresolved wrt python.  I asked Tartarus, aiui the python3 support for libfdt is tied to other changes that currently block a simple upgrade of libfdt in the u-boot tree21:15
*** neverpanic <neverpanic!> has joined #yocto21:16
TartarusAnd we're in turn grumbling at libfdt folks21:16
*** WillMiles <WillMiles!> has quit IRC21:18
*** nabokov <nabokov!~armand@> has quit IRC21:21
*** weltling <weltling!> has quit IRC21:42
RPTartarus: :/22:06
RPsmurray: on the call the other day it seemed uboot would be the final hurdle22:06
Crofton|workbut that doesn't inject py2 into the image?22:07
smurrayRP: yep22:07
smurrayCrofton|work: correct22:07
RPzeddii: can I just remove that foo patch?22:08
zeddiisometimes random bikeshedding on patch series tires me out.22:08
zeddiiRP. yup.22:08
zeddiiI just git rm'd it and rebased the patch.22:08
* zeddii goes into only reply to useful comments mode.22:09
RPzeddii: thanks, I'll just delete it than rejuggle patches :)22:09
zeddiiyah. my v2 was more overhead than it was worth :D22:09
zeddiithat'll teach me to "git add ." in myeta/recipes-kernel/ :D22:10
RPzeddii: just trying to think of the easiest way to fix it in my tree :)22:10
zeddiiI hear you. I'm not a fan of a single v2 in the middle of a series, but re-issuing it, seemed worse in this case.22:10
RPzeddii: right, that is fine. I just had to check that was the only difference22:11
*** rewitt <rewitt!rewitt@nat/intel/x-twfziqebxhjnkvxl> has quit IRC22:15
*** armpit <armpit!~armpit@> has quit IRC22:27
RPzeddii: first error is in: :/23:05
RPzeddii: looks like some scripts still reference "python" :/23:07
yoctiNew news from stackoverflow: How to install files in the native sysroot with yocto when doing populate_sdk? <>23:15
*** khem <khem!~khem@unaffiliated/khem> has quit IRC23:20
*** florian <florian!~florian_k@Maemo/community/contributor/florian> has quit IRC23:27
*** learningc <learningc!~learningc@> has joined #yocto23:38
*** learningc <learningc!~learningc@> has quit IRC23:45
yoctiNew news from stackoverflow: Cross compiling a kernel module issue in Makefile <>23:45

Generated by 2.11.0 by Marius Gedminas - find it at!