Friday, 2017-08-04

*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has quit IRC00:02
-YoctoAutoBuilder- build #812 of nightly-arm64 is complete: Success [build successful] Build details are at
*** khem <khem!~khem@unaffiliated/khem> has quit IRC00:20
-YoctoAutoBuilder- build #1204 of nightly-multilib is complete: Success [build successful] Build details are at
*** khem <khem!~khem@unaffiliated/khem> has joined #yocto00:24
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has quit IRC00:28
-YoctoAutoBuilder- build #1202 of nightly-ppc is complete: Success [build successful] Build details are at
*** rick_0 <rick_0!~Thunderbi@2001:8003:804a:b500:e1c4:1324:df00:9cbb> has joined #yocto00:34
*** berndhs <berndhs!> has quit IRC00:36
*** clsulliv <clsulliv!clsulliv@nat/intel/x-wqjqbuckmvoqxlfe> has quit IRC00:41
*** clsulliv <clsulliv!clsulliv@nat/intel/x-nockrqrpjsweqfzs> has joined #yocto00:42
*** Trinners <Trinners!> has quit IRC00:42
*** nighty-- <nighty--!> has joined #yocto00:48
*** rburton <rburton!> has quit IRC00:49
*** rburton <rburton!> has joined #yocto00:50
*** georgem_home <georgem_home!uid210681@gateway/web/> has joined #yocto00:51
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has joined #yocto01:05
*** stephano <stephano!~stephano@> has quit IRC01:08
*** morphis_ <morphis_!> has joined #yocto01:11
*** gartin <gartin!~Gav@> has joined #yocto01:13
*** morphis <morphis!> has quit IRC01:14
*** martinkelly1 <martinkelly1!~martin@> has quit IRC01:16
*** lsandov1 <lsandov1!lsandov1@nat/intel/x-dhktzxisokltzsvg> has quit IRC01:17
*** catch22__ <catch22__!~catch22__@> has joined #yocto01:22
*** armpit <armpit!> has quit IRC01:24
*** catch22 <catch22!~catch22__@> has quit IRC01:24
*** catch22__ <catch22__!~catch22__@> has quit IRC01:27
*** catch22__ <catch22__!~catch22__@> has joined #yocto01:28
*** mattsm <mattsm!~mattsm@2605:6000:1019:e0:a18a:b87d:ad92:a3b5> has quit IRC01:57
*** http_GK1wmSU <http_GK1wmSU!~deep-book@> has joined #yocto02:11
*** http_GK1wmSU <http_GK1wmSU!~deep-book@> has left #yocto02:14
-YoctoAutoBuilder- build #518 of nightly-musl is complete: Success [build successful] Build details are at
*** rburton <rburton!> has quit IRC02:16
*** rburton <rburton!> has joined #yocto02:17
*** yizhao <yizhao!~zhaoyi@> has quit IRC02:34
*** yizhao <yizhao!~zhaoyi@> has joined #yocto02:35
*** dreyna <dreyna!> has quit IRC02:41
*** rburton <rburton!> has quit IRC02:54
*** Guest78534 <Guest78534!uid116340@gateway/web/> has joined #yocto03:03
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has quit IRC03:04
*** catch22 <catch22!> has joined #yocto03:10
-YoctoAutoBuilder- build #1166 of build-appliance is complete: Success [build successful] Build details are at
-YoctoAutoBuilder- build #1169 of nightly-ppc-lsb is complete: Success [build successful] Build details are at
-YoctoAutoBuilder- build #1151 of nightly-arm-lsb is complete: Success [build successful] Build details are at
-YoctoAutoBuilder- build #1292 of nightly is complete: Success [build successful] Build details are at
*** garbados <garbados!~garbados@2601:1c2:303:6b0:e437:e5ff:f7ee:8828> has quit IRC03:31
*** georgem_home <georgem_home!uid210681@gateway/web/> has quit IRC03:41
*** shiyer <shiyer!~shiyer@> has quit IRC03:42
*** hamis <hamis!~irfan@> has joined #yocto03:44
*** shiyer <shiyer!~shiyer@> has joined #yocto03:45
*** itseris_ <itseris_!~emikulin@> has joined #yocto03:50
*** itseris <itseris!~emikulin@> has quit IRC03:50
*** mattsm <mattsm!~mattsm@2602:304:b0d5:feaa:9903:6cd4:c44f:d740> has joined #yocto04:18
*** catch22__ <catch22__!~catch22__@> has quit IRC04:19
*** mattsm <mattsm!~mattsm@2602:304:b0d5:feaa:9903:6cd4:c44f:d740> has quit IRC04:25
*** mattsm <mattsm!> has joined #yocto04:29
*** catch22__ <catch22__!~catch22__@> has joined #yocto04:33
-YoctoAutoBuilder- build #1189 of nightly-world is complete: Success [build successful] Build details are at
-YoctoAutoBuilder- build #912 of nightly-world-lsb is complete: Success [build successful] Build details are at
*** agust <agust!> has joined #yocto05:23
*** rburton <rburton!> has joined #yocto05:34
*** Jefro <Jefro!> has quit IRC05:54
*** Jefro <Jefro!> has joined #yocto05:59
*** melonipoika <melonipoika!~jose@> has quit IRC06:01
*** Heinzer123 <Heinzer123!> has joined #yocto06:07
*** hnje <hnje!~hnje@> has joined #yocto06:09
*** melonipoika <melonipoika!~jose@> has joined #yocto06:10
*** tasslehoff <tasslehoff!~Tasslehof@> has joined #yocto06:13
*** armpit <armpit!~armpit@2601:202:4001:9ea0:35b2:9b56:f157:2b7f> has joined #yocto06:17
*** rob_w <rob_w!~bob@unaffiliated/rob-w/x-1112029> has joined #yocto06:18
*** Fuddl <Fuddl!> has joined #yocto06:27
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto06:30
-YoctoAutoBuilder- build #1182 of nightly-qa-extras is complete: Success [build successful] Build details are at
*** ojdo <ojdo!~ojdo@unaffiliated/ojdo> has quit IRC06:54
*** tavish <tavish!~tavish@unaffiliated/tavish> has joined #yocto07:01
*** ojdo <ojdo!~ojdo@unaffiliated/ojdo> has joined #yocto07:06
*** groleo <groleo!> has joined #yocto07:06
*** Kakounet <Kakounet!> has joined #yocto07:10
*** BarBQ <BarBQ!> has joined #yocto07:12
*** BarBQ <BarBQ!> has quit IRC07:14
*** gtristan <gtristan!~tristanva@> has quit IRC07:16
*** rajm <rajm!~robertmar@> has joined #yocto07:19
*** joshuagl <joshuagl!~joshuagl@> has joined #yocto07:32
*** boucman_work <boucman_work!~jrosen@wesnoth/developer/boucman> has joined #yocto07:32
sveinsekergoth: I tested the new gist, had to modify the d.getVar("STAMP") to d.getVar("STAMP",True)07:37
*** alkino <alkino!~alkino@> has joined #yocto07:39
alkinohi o/07:39
alkinoOnly a stupid question07:39
sveinsekergoth: but it fails the same way: setscenes fails under do_populate_sysroot_setscene with exit code '1' - real task will be run instead, and then massively errors under 'runtaskdeps' and do_fetch07:39
alkinoi'm trying to make the same rdepends for native and cross07:39
alkinoRDEPENDS_${PN} = XXX doesn't work07:39
*** ed2 <ed2!Adium@nat/intel/x-skfbnzukgwhaesem> has joined #yocto07:40
sveinseIs there a way to configure a recipe to disable sstate generation it?07:40
*** Jefro <Jefro!> has quit IRC07:41
*** http_GK1wmSU <http_GK1wmSU!> has joined #yocto07:41
*** ldts <ldts!~jro@linaro/ldts> has joined #yocto07:43
*** http_GK1wmSU <http_GK1wmSU!> has left #yocto07:43
*** vdehors <vdehors!> has joined #yocto07:44
*** catch22 <catch22!> has quit IRC07:45
bluelightningmorning all07:46
*** ant_work <ant_work!> has joined #yocto07:48
*** diego_r <diego_r!> has quit IRC07:49
*** vdehors <vdehors!> has quit IRC07:54
*** yizhao <yizhao!~zhaoyi@> has quit IRC07:55
*** yizhao <yizhao!~zhaoyi@> has joined #yocto07:56
*** vdehors <vdehors!> has joined #yocto07:58
*** vdehors <vdehors!> has quit IRC08:04
*** toscalix <toscalix!> has joined #yocto08:04
*** vdehors <vdehors!> has joined #yocto08:11
*** tavish <tavish!~tavish@unaffiliated/tavish> has quit IRC08:13
*** rick_0 <rick_0!~Thunderbi@2001:8003:804a:b500:e1c4:1324:df00:9cbb> has quit IRC08:14
*** colrack <colrack!~colrack@> has joined #yocto08:15
*** berndhs <berndhs!> has joined #yocto08:15
*** rodgort <rodgort!> has quit IRC08:24
*** Snert__ <Snert__!> has quit IRC08:30
*** rodgort <rodgort!> has joined #yocto08:32
*** yann|work <yann|work!> has quit IRC08:33
*** Snert <Snert!> has joined #yocto08:34
*** luc4 <luc4!~luca@> has joined #yocto08:45
*** gtristan <gtristan!> has joined #yocto08:59
*** colrack <colrack!~colrack@> has quit IRC09:03
*** T_UNIX <T_UNIX!uid218288@gateway/web/> has joined #yocto09:05
*** nighty-- <nighty--!> has quit IRC09:25
*** yann|work <yann|work!> has joined #yocto09:39
*** tavish <tavish!~tavish@unaffiliated/tavish> has joined #yocto09:43
*** colrack <colrack!~colrack@> has joined #yocto09:45
*** slips <slips!> has quit IRC09:54
*** msvb-lab <msvb-lab!> has joined #yocto09:59
*** tavish <tavish!~tavish@unaffiliated/tavish> has quit IRC10:00
sveinseNow this is interesting: I get "ERROR: vsi-image-1.0-r0 do_rootfs_wicenv: Taskhash mismatch bab73ab34a1aba01309a34f5c0163815 verses c333c3682393bc0e62f2ebe32c3bb3e9 for /srv/builds/yocto-default-dev/sp/yocto/recipes-system/images/"10:08
sveinseI have finally been able to generate the sigdata for these two hashes, and they're equal!10:09
sveinsethat is bitbake-diffsigs lists nothing. Doing bitbake-dumpsig and diffing the output is also equal10:09
sveinseWhy then are the hashes different?10:10
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has joined #yocto10:12
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has joined #yocto10:13
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has quit IRC10:22
*** nighty-__ <nighty-__!> has quit IRC10:22
*** prabhakarlad <prabhakarlad!~prabhakar@> has quit IRC10:39
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC10:42
*** eduardas_m <eduardas_m!~eduardas@> has joined #yocto10:46
eduardas_mHello. How do I clean the generated SDKs I got via populate_sdk by using bitbake?10:47
rburtonyou mean, delete them from tmp/deploy?10:49
rburtonuse rm?10:49
eduardas_mrburton: tmp/deploy only contains the packaged SDK and manifest files as far as I understand... what if I need to clean in such a way so that I rebuild all of the SDK components from scratch next time?10:55
eduardas_mthe next time I do a populate_sdk I mean10:55
sveinseIs there a way to configure recipes not to upload to the sstate cache?10:58
*** rburton <rburton!> has quit IRC10:58
*** rburton <rburton!> has joined #yocto10:58
*** pohly <pohly!> has joined #yocto10:59
*** prabhakarlad <prabhakarlad!~prabhakar@> has joined #yocto11:00
rburtonkanavin: packages/corei7-64-poky-linux/xserver-xorg/xserver-xorg: RDEPENDS: removed "libcrypto (['>= 1.0.2l'])", added "openssl (['>= 1.1.0f'])"11:01
rburtonkanavin: unexpected fallout from openssl1.111:01
rburtonhm actually it was wrong before - recipe says use openssl...11:02
rburtonreally could do with a nice ui around buildhistory-diff right now11:03
rburtonaah, libcrypto != libgcrypt, i can't read. that's openssl.11:04
rburtonkanavin: is there a good reason to not continue splitting libssl and libcrypto out like 1.0 did?11:05
*** slips <slips!> has joined #yocto11:09
*** rob_w <rob_w!~bob@unaffiliated/rob-w/x-1112029> has quit IRC11:10
sveinseA taskhash mismatch A verses B. If I search for files with A and B in their filenames, I find only B and 0 of A. Where then does it get the other taskhash from?11:11
*** peacememories <peacememories!> has joined #yocto11:13
*** ZubairLK <ZubairLK!~Thunderbi@unaffiliated/zubairlk> has joined #yocto11:15
*** peacememories <peacememories!> has quit IRC11:15
*** ed2 <ed2!Adium@nat/intel/x-skfbnzukgwhaesem> has quit IRC11:15
*** peacememories <peacememories!> has joined #yocto11:16
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has joined #yocto11:18
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has quit IRC11:22
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has joined #yocto11:23
*** Fuddl <Fuddl!> has quit IRC11:27
*** ed2 <ed2!Adium@nat/intel/x-pzwzonuxmiqumucd> has joined #yocto11:27
peacememorieshmm, can i bake bootargs into a kernel image?11:33
kanavinrburton: I rewrote openssl 1.1 recipe from scratch, as 1.0 has astronomical amounts of old cruft. That includes not splitting those libs - how about approaching it it the other way, if there is a specific reason to do it, then it can be done :)11:35
rburtonkanavin: i guess is there a use case for linking to just libcrypto and not all the rest.  xserver appears to be a usecae, it just wants the sha implementation in libcrypto and not the full stack11:36
*** http_GK1wmSU <http_GK1wmSU!> has joined #yocto11:37
*** http_GK1wmSU <http_GK1wmSU!> has left #yocto11:38
kanavinrburton: sure, but realistically, the full stack is very likely to be pulled in anyway11:38
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto11:39
*** peacememories <peacememories!> has quit IRC11:39
*** morphis_ <morphis_!> has quit IRC11:42
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC11:44
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto11:53
*** morphis_ <morphis_!> has joined #yocto11:57
sveinseIs there a way to run bitbake and parse the recipes and then quit? A kind of do-nothing command12:02
neverpanicbitbake -e recipename >/dev/null12:02
rburtonor even better --help tells you that --parse-only exists :)12:03
rburtonkanavin:   /etc/ssl/certs/e8de2f56.0 changed symlink target from /usr/share/ca-certificates/mozilla/Buypass_Class_3_Root_CA.crt to Buypass_Class_3_Root_CA.pem12:04
rburtonkanavin: not sure if thats good, bad, or indifferent :)12:04
*** Shurelous <Shurelous!~igor@> has joined #yocto12:04
*** peacememories <peacememories!~textual@> has joined #yocto12:05
rburtonkanavin: also packages/corei7-64-poky-linux/gstreamer1.0-plugins-bad/gstreamer1.0-plugins-bad-dtls: RDEPENDS: removed "libssl (['>= 1.0.2l']) libcrypto (['>= 1.0.2l'])", added "openssl (['>= 1.1.0f'])"12:05
rburtonso -bad is linking to both nettle and openssl now12:05
*** JosePerez <JosePerez!~jgperezc@> has joined #yocto12:06
*** JosePerez1 <JosePerez1!~jgperezc@> has joined #yocto12:07
*** JosePerez2 <JosePerez2!~jgperezc@> has joined #yocto12:09
rburtonkanavin: and does ptest pass on target?12:09
kanavinrburton: yep, because -bad has a ton of various plugins developed pretty much independently12:09
*** JosePerez2 <JosePerez2!~jgperezc@> has quit IRC12:09
kanavinrburton: one plugin is incompatible with openssl 1.1, but can be configured to use nettle, the other is compatible with 1.112:10
kanavinrburton: it does, I checked :)12:10
kanavinrburton: (small print: checked when ptest support was added, which is not recent :)12:10
*** JosePerez <JosePerez!~jgperezc@> has quit IRC12:10
*** Sbrubles <Sbrubles!~igor@> has joined #yocto12:12
*** tavish <tavish!~tavish@unaffiliated/tavish> has joined #yocto12:14
*** Shurelous <Shurelous!~igor@> has quit IRC12:16
*** ant_work <ant_work!> has quit IRC12:18
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC12:21
* rburton wonders if its time to remove oprofile12:27
*** christner <christner!> has joined #yocto12:28
*** bluelightning <bluelightning!> has joined #yocto12:31
*** bluelightning <bluelightning!> has quit IRC12:31
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto12:31
*** Guest78534 <Guest78534!uid116340@gateway/web/> has quit IRC12:31
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has quit IRC12:32
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has joined #yocto12:32
sveinseIt turns out that the taskhash mismatch only occurs the first time bitbake is run in an empty build (not tmp/ present).12:34
sveinseIf I run another uncorrelated recipe, or even just do --parse-only, I won't run into the taskhash mismatch issue12:34
sveinseSo the immediate fix for the buildserver is to run --parse-only first before starting the actual build.12:35
sveinseIsn't this very wierd thou?12:35
*** grumble <grumble!~grumble@freenode/staff/grumble> has quit IRC12:36
rburtonhm yes12:38
rburtonare you using uninative? (default in poky, not in oe-core iirc)12:38
sveinsedunno, I am using poky krogoth12:39
rburtonyou know because you enabled it in your distro and the LSB string in bitbake startup header says universal12:40
rburtonthats very odd though.  can you dump the stamps to see what it thinks the difference is now?12:41
sveinseWhen I dump the stamps, they are equal!12:42
sveinsesigdata I mean12:42
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has quit IRC12:50
*** zero_note <zero_note!~zero@> has quit IRC12:54
kanavinrburton: g-introspection with meson fixed \0/12:58
kanavinrburton: the only issue is that the flags to enable/disable it are non-standardized, and, I suspect, it's not just json-glib that tries to be clever and disables it when cross-compiling12:59
rburtonjust moaned at json-glib maintainer :)13:00
kanavinrburton: we should moan at webkit maintainers too13:00
kanavinrburton: I can publish my branches perhaps? then we'll see what to do next13:02
rburtonyes, definitely13:02
rburtonkhem: new glibc is much happier13:09
*** pohly <pohly!> has quit IRC13:10
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC13:11
*** pohly <pohly!> has joined #yocto13:12
*** filt3r <filt3r!> has quit IRC13:12
*** pohly <pohly!> has quit IRC13:14
*** stephano <stephano!~stephano@> has joined #yocto13:16
*** CoLa|work <CoLa|work!~cordlandw@> has quit IRC13:20
*** Heinzer123 <Heinzer123!> has left #yocto13:20
*** hnje <hnje!~hnje@> has quit IRC13:20
*** T_UNIX <T_UNIX!uid218288@gateway/web/> has quit IRC13:22
*** lsandov1 <lsandov1!~lsandov1@> has joined #yocto13:25
*** peacememories <peacememories!~textual@> has quit IRC13:28
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has joined #yocto13:35
kanavinrburton: published in akanavin/meson, on poky-contrib (json-glib changes) and metaoe-contrib (meson changes)13:35
rburtoncan you mail me those URLs so i don't forget on monday? :)13:36
kanavinrburton: yep13:36
kanavinrburton: done13:38
kanavinrburton: care to take a quick look now?13:39
rburtoncoffee first :)13:40
rburtonand rebooting all my stuff to make it ***** work again13:40
*** darknighte <darknighte!~darknight@pdpc/supporter/professional/darknighte> has quit IRC13:46
*** lamego <lamego!~jose@> has joined #yocto13:47
*** ed2 <ed2!Adium@nat/intel/x-pzwzonuxmiqumucd> has quit IRC13:48
*** grumble <grumble!~grumble@freenode/staff/grumble> has joined #yocto13:48
*** filt3r <filt3r!> has joined #yocto13:48
*** gjohnson <gjohnson!ad198ff2@gateway/web/freenode/ip.> has joined #yocto13:50
gjohnsonHello, I am looking for some help debugging.  I have a nvidia recipe that provides virtual/libgl and the mesa recipe has virtual/libgl removed.  When do_rootfs is run I keep getting recipes complaining that libgl dependency isn't found13:54
*** tavish <tavish!~tavish@unaffiliated/tavish> has quit IRC13:59
sveinseIt seems I have a race condition while executing a initramfs.do_rootfs. It generates the deb archives (generates the packages and release files). It dies because of "E: Could not open file ./sp-data_99.14.0+hg0-025f4d16d400-r0_armhf.deb - open (2: No such file or directory)". But when I later inspect the dir, its all there. Also note that the initramfs does not use this packages, so its only the deb repo14:03
sveinsegeneration which makes this die14:03
sveinseHow can I serialize the execution for this?14:03
rburtonsounds like a bug in package_deb14:06
rburtonwhich is the least tested of all the packaging formats we support14:06
sveinserpm is the most tested?14:06
rburtonrpm and ipkg equally i guess14:07
*** tasslehoff <tasslehoff!~Tasslehof@> has quit IRC14:07
rburtonrpm is exercised more but ipkg is simpler :)14:08
yatesis "DISTRO" part of the string printed by uname -a?14:08
yatesi read the uname manpage and i see no DISTRO14:08
rburtonDISTRO is an openembedded thing, uname just prints what the kernel tells it14:10
rburtonso you won't see any mention of DISTRO in the uname man page14:11
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has quit IRC14:12
yatesis it documented somewhere what DISTRO is meant to signify? what should i set it to?14:12
rburtonif you're asking that then i suggest you start with the yocto documentation14:13
yatesah. section 5.1414:13
rburtonyeah thats a good start14:14
yatesok thanks.14:15
*** Trinners <Trinners!> has joined #yocto14:17
*** gjohnson <gjohnson!ad198ff2@gateway/web/freenode/ip.> has quit IRC14:20
yatesalso, isn't MACHINE a bit of a misnomer? it's not JUST the machine, i.e., the CPU/architecture (x86_64, arm7hf, etc.), more like the machine and board hosting it?14:21
yatesand the mfr14:22
*** gjohnson <gjohnson!ad198ff2@gateway/web/freenode/ip.> has joined #yocto14:23
kanavinyates: machine is the board+cpu, cpu architecture is architecture :)14:23
*** roric_ <roric_!~roric@> has joined #yocto14:24
*** groleo <groleo!> has quit IRC14:24
yateskanavin: oh, there is a separate ARCHITECTURE specification somewhere?14:24
yatesthat helps, thanks14:25
kanavinyates: not really, architectures are defined through a set of include files in conf/machine/include14:25
roric_Is there any documented restriction on package names?14:28
roric_Its turns out for me if the package name start with an uppercase no postinst/postrm is generated... changing the name to lower case -> bam it works..14:29
roric_...and the postinst/rm in this case was generated by systemd..14:29
roric_...and I'm running pyro14:30
rburtonroric_: yes, uppercase is forbidden in some package managers14:30
roric_rburton, thanks that explains, what about having some QA check for it..?14:30
roric_rburton, but I think the bug might be in oe, because it was lacking in the .spec-file to (using rpm)14:31
kanavinroric_: yocto is what you make it, so you are welcome to write a patch :)14:32
roric_rburton, thanks ;-)14:32
*** gjohnson <gjohnson!ad198ff2@gateway/web/freenode/ip.> has quit IRC14:34
roric_rburton, speaking of that (sorry for buggering you). I sent a patch fixing broken support for no_recommendations in the new dnf-code. Whats the process if I want to recommend to get that patch into some release branch like pyro?14:35
*** prabhakarlad <prabhakarlad!~prabhakar@> has quit IRC14:36
kanavinroric_: you rebase the patch on pyro, and send it with [pyro] prefixed in the subject14:36
otaviorburton: what is holding up the gstreamer upgrade?14:37
otaviodv__: ?14:37
*** dv__ is now known as dv_14:42
dv_what concerns me in particular is that other patches have been pushed to oe-core, so the previous 1.12 upgrade patches now have conflicts14:43
*** hamis <hamis!~irfan@> has quit IRC14:44
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has quit IRC14:47
*** stephano <stephano!~stephano@> has quit IRC14:52
*** royalpurple <royalpurple!> has joined #yocto14:53
rburtondv_, otavio: oh meant to reply to that, sorry.  it was breaking intel but i think that has been fixed and now doesn't apply.  if someone can rebase...14:55
*** royalpurple <royalpurple!> has quit IRC14:56
*** royalpurple <royalpurple!> has joined #yocto14:57
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has quit IRC14:58
*** mckoan|away is now known as mckoan14:59
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has joined #yocto14:59
mckoanhow can you tell to autotools that you want to build a library.a too ?15:00
rburtonmckoan: that happens by default but if you're using poky then you'll be passing --disable-static as poky disables static libraries15:00
rburtonnote: poky is an example, only use it for real work if you've read the conf and know what it does :)15:01
sveinseIs it safe to remove package-management from IMAGE_FEATURES of poky?15:01
mckoanrburton: so it overrides the normal AC_PROG_LIBTOOL?15:01
rburtonno, it just passes --disable-static15:01
sveinseSomeone once told me that without it, postinstalls that have to run on target doesn't, but I don't know if that's correct15:02
mckoanrburton: thanks, I try15:02
dv_in general, yocto recipes tend to pass many configuration switches, to ensure deterministic builds15:02
rburtonsveinse: if you want to remove package management from the images then thats exactly what you want.15:02
mckoandv_: thx15:03
sveinserburton: Not if some package I don't know of depend on some postinstall setup -- if that is indeed the case15:03
sveinsehence the question15:03
mckoanparticularly my recipe worked well with fido, but I'm switching to morty15:04
rburtonsveinse: you should write a two line recipe to find out15:04
rburtonsveinse: if it does then its trivial enough to write a sanity check to abort builds in that case15:04
rburtonwe already do that read only rootfs: pending postinsts and readonly rootfs are incompatible15:05
sveinserburton: right, good. Then this statement is false.15:05
rburtonsveinse: no, i said you should find out.  i'm not sure.15:06
sveinsealright, thanks15:06
sveinseI'm suspecting that yocto will install a run-once service and run those postinst scripts15:07
sveinsewithout any pkg mgmt system15:07
rburtonyeah i think it persists the scripts that are left behind15:08
rburtonwe definitely have a first boot service to run them15:08
rburtonbut the maze of code is such that its easier to test it than read the code ;)15:08
sveinseI am now15:08
*** wouterstreamit <wouterstreamit!589f1708@gateway/web/freenode/ip.> has quit IRC15:09
*** eduardas_m <eduardas_m!~eduardas@> has quit IRC15:12
*** avalluri <avalluri!~avalluri@> has quit IRC15:16
*** avalluri <avalluri!~avalluri@> has joined #yocto15:17
mckoanrburton: EXTRA_OECONF = "--enable-static" in the recipe didn't solve15:19
*** majuk <majuk!> has joined #yocto15:19
rburtonmckoan: that would be because no-static-libs uses _append15:19
*** hbruce <hbruce!~hbruce@> has quit IRC15:19
rburtonhave a look at what poky is actualy doing and you'll see what to do15:20
rburton(either 1) don't use poky or 2) clear DISABLE_STATIC)15:20
*** hbruce <hbruce!~hbruce@> has joined #yocto15:21
*** lsandov1 <lsandov1!~lsandov1@> has quit IRC15:22
*** msvb-lab <msvb-lab!> has quit IRC15:24
*** msvb-lab <msvb-lab!> has joined #yocto15:26
mckoanrburton: DISABLE_STATIC = "", it woks, thank you so much15:27
mckoanrburton: ./meta/conf/distro/include/no-static-libs.inc15:27
*** groleo <groleo!~groleo@> has joined #yocto15:30
rburtonsveinse: looks like we already have a test for this and it does what you expect: postinsts are saved and ran on boot15:38
sveinserburton: yes, that is what Ive found too. The run-postinst script is run by a service by the same name. This in turn calls postinst of ipk, deb or rpm if such is installed.15:40
*** stephano <stephano!stephano@nat/intel/x-pcvdnpaxichaplpv> has joined #yocto15:43
*** boucman_work <boucman_work!~jrosen@wesnoth/developer/boucman> has quit IRC15:43
*** lsandov1 <lsandov1!lsandov1@nat/intel/x-gthtkjssnauenjzn> has joined #yocto15:44
khemrburton: good deal15:44
*** Kakounet <Kakounet!> has quit IRC15:49
*** Jefro <Jefro!> has joined #yocto15:50
sveinseoh wait, how does the fs respond if you set commit= to a large time? Could it be that my issue with files missing from the deb repo be an error in the fs due to a large commit time?15:55
rburtoncommit just impacts when stuff actually hits disk, the kernel knows what is really happening15:55
sveinseBecause that is a change we've just had15:55
rburtoncommit just changes how much data you lose if you pull the power15:56
sveinseyes, I'd expect the fs to be consistent about its meta data. But I'm starting to wonder thou15:56
rburtonfwi my build machine has a two minute commit on the build disk15:56
sveinseI think ours was increased to 30 secs15:56
*** lsandov1 <lsandov1!lsandov1@nat/intel/x-gthtkjssnauenjzn> has quit IRC15:57
kergothif the fs wasn't consistent, no one would bother using it :)15:57
kergothwould be useless15:57
sveinsekergoth: welcome back!15:57
sveinsekergoth: FYI I had to modify the gist to make it work: I had to encapsulate it in try except. Otherwise *everything* returned error code 1 and said bork bork!15:58
yatesdoes fsl mean "freescale layer"? what does fslc mean?16:00
*** marka <marka!> has joined #yocto16:00
sveinsefreescale linux, iirc16:00
yatesyou mean fsl == freescale linux?16:01
yatesthen what is fslc?16:01
rburtonfsl is short for freescale, yes16:01
rburtoniirc fscl is freescale community16:01
rburtonping otavio ^^^^16:01
*** gtristan <gtristan!> has quit IRC16:02
*** aehs29 <aehs29!~aehernan@> has joined #yocto16:02
*** lsandov1 <lsandov1!~lsandov1@> has joined #yocto16:03
yatesi don't understand why this is failing: ->
*** tavish <tavish!~tavish@unaffiliated/tavish> has joined #yocto16:03
sveinseFreescale has two versions, one community and one, uhm, non-community. Let me see if I can find the link16:04
yatesthe file exists: ->
sveinseyates, see down "The differences between FSL Community BSP and Freescale Official Release"16:06
yatesi'm not using build_x11 but a build under sources/poky16:06
yatessveinse: thanks!16:06
*** toscalix <toscalix!> has quit IRC16:09
*** yann|work <yann|work!> has quit IRC16:11
yatesdoes yocto search for files under sources/<layer>/blah/files/<machine> ?16:12
*** luc4 <luc4!~luca@> has quit IRC16:12
kergotha file:// uri in SRC_URI is found by seraching FILESPATH16:12
*** ldts <ldts!~jro@linaro/ldts> has quit IRC16:12
kergothwhich includes quite a few possible locations16:13
kergothsee also the bitbake user manual16:13
yatesthen why isn't it finding the file here sources/meta-variscite-fslc/recipes-connectivity/bluez5/files/imx6ul-var-dart/variscite-bt.conf16:13
*** alkino <alkino!~alkino@> has quit IRC16:14
yateskergoth: i may not have asked my question clearly.16:14
yateswhen yocto is searching for a file and it considers a path that begins with sources/<layer>/blah/files/, does it only look for it under the extended path sources/<layer>/blah/files/<machine> ?16:16
kergothno, as i just said, it searches any path in FILESPATH, which includes quite a few paths, including variants for every override listed in OVERRIDES16:16
kergothof which MACHINE is one of many16:17
*** lsandov1 <lsandov1!~lsandov1@> has quit IRC16:17
yatesok, i'll do some more searching / reading.16:17
kergothassuming file://variscite-bt.conf is in SRC_URI, and assuming the recipe lives in sources/meta-variscite-fslc/recipes-connectivity/bluez5 (the recipe, not a bbappend), and assuming MACHINE is imx6ul-var-dart, then it'll pick it up from sources/meta-variscite-fslc/recipes-connectivity/bluez5/files/imx6ul-var-dart/variscite-bt.conf, yes16:18
yatesthis might just be a pivotal "teachable moment" for me, then.16:22
*** mckoan is now known as mckoan|away16:23
yateswe are defining our own machine under our own layer but want to utilize as much of the existing meta-varascite-fslc as possible. since our machine name is not imx6ul-var-dart, it is not finding the file.16:24
kergothright. the best way to handle that is to use MACHINEOVERRIDES16:24
kergothyou can have both the original machine name and your new machine name in overrides with that16:25
kergoththat'll ensure that both variable overrides and files will still be applied an dfound, respectively16:25
*** joshuagl <joshuagl!~joshuagl@> has quit IRC16:25
kergothbest way to handle making your own variant of a machine16:25
yatesexcellent. i'll read up on MACHINEOVERRIDES.16:25
kergothwe've done that when we need to tweak an upstream machine when we have no control over the upstream layer, make our own version of the machine16:26
kergothso your machine .conf can require the other machine .conf and adjust MACHINEOVERRIDES and should be good to go16:26
*** gtristan <gtristan!> has joined #yocto16:29
*** todor <todor!~todor@> has quit IRC16:31
*** WillMiles <WillMiles!> has joined #yocto16:32
*** colrack <colrack!~colrack@> has quit IRC16:35
*** m_kim <m_kim!> has quit IRC16:37
yatesnow ->
yatesdo i also have to create a COMPATIBLE_MACHINE line in my <machine>.conf?16:39
kergothCOMPATIBLE_MACHINE is a recipe variable used to make the recipe unparseable for machines where it won't b euseful or won't build16:40
kergothit's not a variable for use in a machine .conf at all. doing so would affect every recipe you build, not good16:41
kergothbut no, iirc base.bbclass will check MACHINEOVERRIDES when applying COMPATIBLE_MACHINE, so you should be fine16:41
*** todor <todor!~todor@> has joined #yocto16:44
*** vdehors <vdehors!> has quit IRC16:45
*** yann|work <yann|work!> has joined #yocto16:47
yatesso yes, put a MACHINEOVERRIDES in machine/conf/machine/<machine>.conf ?16:51
majukI have to say, I think I'm a pretty smart guy, but this system is very difficult to get a handle on.16:51
kergothyates: yes16:51
majukYou guys are awesome for developing it. Kudos.16:51
*** balister_ <balister_!> has joined #yocto16:51
*** pohly <pohly!> has joined #yocto16:52
kergothmajuk: the learning curve is fairly steep. the main issue, both positive and negative, is the flexibility, i think. there's a lot of power, but it also means there are often multiple ways of doing things, and pieces come from various places to ensure we can meet every need. once you're up to speed, it's great, though :)16:52
majukkergoth: Yea. I'm wading through the 300 slide presentation on Even after having used Yocto for the past couple months, I don't have much of a handle on how things are happening.16:53
*** Crofton|work <Crofton|work!~balister@> has quit IRC16:54
balister_majuk, magic16:54
kergothmajuk: might help with some background / big picture16:54
*** itseris_ <itseris_!~emikulin@> has quit IRC16:55
kergothrather poky-heavy, terminology wise, given it's really describing bitbake+oe-core behavior, but good info16:56
*** stephano <stephano!stephano@nat/intel/x-pcvdnpaxichaplpv> has quit IRC16:56
balister_Rudi's book is also recent16:58
majukI've been trying to find examples of modifying existing builds. I have a functional build for the reference board I'm working with, but transitioning that into a custom build for custom hardware is evading me because I can't seem to get a grasp on how the recipe I'm using is coming together.17:01
*** stephano <stephano!~stephano@> has joined #yocto17:01
*** itseris <itseris!~emikulin@> has joined #yocto17:02
*** gtristan <gtristan!> has quit IRC17:07
*** groleo <groleo!~groleo@> has quit IRC17:07
majuk'recipe' probably isn't even the right term, lol17:07
*** dreyna <dreyna!> has joined #yocto17:08
majuk'image', that's it17:08
balister_images are built with recipes17:10
balister_what is the existing build?17:10
*** balister_ is now known as Crofton|work17:11
majukDon't know how to answer that question.17:11
kergothto clarify further, an image *is* a recipe :) just one that inherits a class that arranges to run different tasks17:11
Crofton|workwhat do you build?17:11
kergoththat's so vague as to be a non-response17:11
majukWell it's a vague question that I don't know how to answer.17:12
kergothyou've told us absolutely nothing about what you're building17:12
kergothnot what yocto version, what hardware, what distro, nothing17:12
majukYou want a list of every package? The image name I invoke? The hardwre?17:13
Crofton|workimage name17:13
*** rajm <rajm!~robertmar@> has quit IRC17:13
majukcore-image-x11 is the image name17:13
Crofton|workWhat do you want to change17:14
majukImmediately, uboot register settings for DDR.17:15
Crofton|workso then we need to know the bsp layer used17:17
Crofton|workakak hardware17:17
majukThe Freescale Community BSP, specifically the Wandboard w/ iMx6 Solo17:18
* Crofton|work hasn't used that part17:18
yatesdoes anyone know of an emacs shell that will work with yocto/bitbake? ->
Crofton|workI could help with Xilinx :)17:18
Crofton|workbut asking in a Freescale focused place would be better for that question17:19
majukYea. No worries, thanks.17:19
Crofton|workalso reading the u-boot recipes in the freescale BSP's might give you some ideas17:19
Crofton|workthat is pretty intimate with the board startup, which OE handles, but the smarts for that will be in the bsp layers and can be pretty hacky at times, dpending on who did the work :)17:20
majukSure. My exercise today was to try to trace from the highest level, image, down to the BSP uboot stuff17:21
*** Guma <Guma!> has joined #yocto17:21
majukand I see no reference to anything uboot in the image. So that's not going so well. :D17:22
Crofton|workdoes that layer stack on top of meta-freescale17:22
majukIf I could build an image that just got me to a uBoot shell, that would be great.17:22
kergothmajuk: see the machine .conf17:23
kergothit'll define the bits to pull in the bootloader to the build17:23
kergothnot the imga itself, since it's machine specific, and is independent of the image17:23
kergothdistro, machine, and image are orthogonal. any combination of the three should work, in general, so we're careful to keep changes for them in the right place17:24
majukThat makes sense.17:24
majukkergoth: Ok, hearing that, the local.conf makes more sense17:25
majukDefinitely didn't get that out of any docs I've read. :D17:25
kergoththat separation is pretty critical to the project's success, i think, along with our OVERRIDES. between the two we have the ability to share a ton of common stuff between people with widely varying use cases, hardware, and policy decisions17:25
kergothmajuk: might help in that regard. substitute references to 'task' with 'packagegroup' in most cases. haven't updated that in a while17:26
majukCool, thanks.17:26
kergothbut it's about the distro/machine/image thing17:26
kergothi think our docs could probably use a bit more coverage of high level concepts. we have some good howto-style info, and reference material, but less of the big picture, i think17:27
majukI'm a hard/firmware guy, the inherent hierarchy of system software is not a context I know a lot about, so this is great.17:27
kergothof course some folks do better at drilling down from high level to low, but others do better at going the other direction, so what's helpful for one might not help the other, depending on where they are in the learning process..17:28
majukYea, I'm a low-to-high level guy for building understanding. I learn-by-doing and find it difficult to apply high-level concepts into low-level, actionable, understandable steps with anticipatable consequences.17:32
majukAnyway, thanks for the input, I appreciate y'alls time.17:33
*** lsandov1 <lsandov1!~lsandov1@> has joined #yocto17:33
*** lsandov11 <lsandov11!lsandov1@nat/intel/x-gcitiibaytdxrzot> has joined #yocto17:33
*** lsandov1 <lsandov1!~lsandov1@> has quit IRC17:33
*** lsandov1 <lsandov1!~lsandov1@> has joined #yocto17:34
*** lsandov11 <lsandov11!lsandov1@nat/intel/x-gcitiibaytdxrzot> has quit IRC17:34
*** rob_w <rob_w!~rob@unaffiliated/rob-w/x-1112029> has joined #yocto17:51
*** boucman_work <boucman_work!~jrosen@wesnoth/developer/boucman> has joined #yocto17:56
*** nemunaire <nemunaire!> has quit IRC17:56
*** dv__ <dv__!~quassel@> has joined #yocto17:56
*** dv_ <dv_!~quassel@> has quit IRC17:56
*** nemunaire <nemunaire!~nemunaire@2a01:e35:8bb7:3c60::a> has joined #yocto17:57
*** groleo <groleo!~groleo@> has joined #yocto18:03
*** boucman_work <boucman_work!~jrosen@wesnoth/developer/boucman> has quit IRC18:14
*** Sbrubles <Sbrubles!~igor@> has quit IRC18:15
*** boucman_work <boucman_work!~jrosen@wesnoth/developer/boucman> has joined #yocto18:16
*** Sbrubles <Sbrubles!~igor@> has joined #yocto18:16
*** boucman_work <boucman_work!~jrosen@wesnoth/developer/boucman> has quit IRC18:28
*** Sbrubles <Sbrubles!~igor@> has quit IRC18:29
*** Sbrubles <Sbrubles!~igor@> has joined #yocto18:31
*** majuk <majuk!> has quit IRC18:31
*** majuk <majuk!> has joined #yocto18:31
*** martinkelly <martinkelly!> has joined #yocto18:35
*** majuk <majuk!> has quit IRC18:36
*** itseris <itseris!~emikulin@> has quit IRC18:42
*** itseris <itseris!~emikulin@> has joined #yocto18:49
*** Sbrubles <Sbrubles!~igor@> has quit IRC18:52
*** majuk <majuk!> has joined #yocto19:02
*** Sbrubles <Sbrubles!~igor@> has joined #yocto19:04
*** WillMiles <WillMiles!> has quit IRC19:05
yatesmy new machine build ran for a couple of hours but eventually encountered the following error: ->
yatesagain this is happening because we are using a new MACHINE name19:09
yatesthe fw_env.config file for the machine we are deriving from (imx6ul-var-dart) is fine. how do we "inherit" this uboot file ?19:11 fine for our machine and purposes...19:11
yatesour machine name is imx6ul-ebtron-x5, as from this line of the error outptu: install: cannot stat '/home/yocto-project-x5-r1/sources/meta-variscite-fslc/recipes-bsp/u-boot/u-boot-fw-utils/imx6ul-ebtron-x5/fw_env.config': No such file or directory19:12
majukcopy-paste it into "home/yocto-project-x5-r1/sources/meta-variscite-fslc/recipes-bsp/u-boot/u-boot-fw-utils/imx6ul-ebtron-x5/fw_env.config"?19:12
*** aehs29 <aehs29!~aehernan@> has quit IRC19:14
yatesmajuk: we are only going to change a small portion of the existing imx6ul-var-dart u-boot (and kernel) configuration. isn't there a way to inherit everything from imx6ul-var-dart except for a few special "tweaks"?19:14
majukyates: I imagine there is, but I don't know what it is. Sorry.19:19
*** ash_charles <ash_charles!~acharles@2607:fad8:4:6:c8a6:17d:5ad6:1157> has joined #yocto19:20
yateskergoth: any pointers here?19:23
yatesor rburton?19:27
yateseveryone having a beer already? :)19:27
*** pohly <pohly!> has quit IRC19:31
sveinseyeeah, finally. Build is up and running again after 2 days down.19:37
sveinsebitbake and yocto is certainly not the easiest beast when not walking on the happy path ;)19:37
*** ash_charles <ash_charles!~acharles@2607:fad8:4:6:c8a6:17d:5ad6:1157> has quit IRC19:39
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto19:41
Marexbluelightning: oh hey, just the guy I'm looking for :)19:46
Marexbluelightning: are you aware that NPM is broken-ish in YPRR 2.3 , but not in YPRR 2.2 ?19:46
bluelightningMarex: hey19:46
bluelightningMarex: I'm aware there are a lot of problems with it yes...19:47
bluelightningin fixing one issue I created others19:47
Marexbluelightning: surprisingly, it worked in 2.2 , but it's broken in 2.3 , does that ring a bell or shall I start bisecting ?19:47
Marex(btw no, I didn't turn to the dark side and didn't start doing nodejs :) )19:47
bluelightningMarex: I think you will find the issues start with the commit where do_install was changed19:47
Marexbluelightning: heh, that sounds vaguely familiar19:48
Marexbluelightning: yeah, do_install is where it dies19:49
bluelightningwithout that fix there are other issues unfortunately19:50
bluelightningbasically npm has fought us every step of the way :(19:51
bluelightningI am holding out hope for npm v519:51
Marexbluelightning: ... insert opinionated comment on quality of nodejs here ...19:51
Marexbluelightning: there is no hope for nodejs19:52
*** Shurelous <Shurelous!~igor@> has joined #yocto19:52
Marexbluelightning: but thanks for pointing me out to this do_install, I'll try reverting a few and see if I can track it down19:53
bluelightningv5 suggests they are learning some lessons (from yarn mostly)19:53
bluelightningI'm told it can be installed on top of non-bleeding-edge versions of node.js19:53
*** yates <yates!> has quit IRC19:55
Marexbluelightning: I'm waiting for the "but" :)19:55
*** Sbrubles <Sbrubles!~igor@> has quit IRC19:55
bluelightningMarex: well, someone I work with is sort of looking at it, but I'm not sure how much time he has to spend doing so19:57
bluelightningwhat he's told me so far sounds very promising19:58
*** groleo <groleo!~groleo@> has quit IRC20:00
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has quit IRC20:00
Marexbluelightning: ok, reverting ebe531b38bea54bd29ed7b3d2ea6c533b9331953 helped20:02
Marexbluelightning: I expect this will fsck something else up :)20:03
Marexbluelightning: thanks20:03
bluelightningMarex: np20:03
*** clsulliv <clsulliv!clsulliv@nat/intel/x-nockrqrpjsweqfzs> has quit IRC20:04
*** clsulliv <clsulliv!~clsulliv@> has joined #yocto20:05
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has joined #yocto20:05
*** tavish <tavish!~tavish@unaffiliated/tavish> has quit IRC20:11
*** berndhs <berndhs!> has quit IRC20:17
*** msvb-lab <msvb-lab!> has quit IRC20:20
*** garbados <garbados!~garbados@2601:1c2:303:6b0:a159:7e6c:dc03:b08> has joined #yocto20:21
garbadoswhen `bitbake-layers add-layers` produces an error like 'Parse failure with the specified layer added' how do i... debug that?20:28
garbadoseven with the -d flag i don't get additional info about the failure20:29
garbadosjust... that a parse failure occurred20:29
*** lsandov1 <lsandov1!~lsandov1@> has quit IRC20:30
*** rob_w <rob_w!~rob@unaffiliated/rob-w/x-1112029> has quit IRC20:30
*** Snert <Snert!> has quit IRC20:31
*** Snert__ <Snert__!> has joined #yocto20:31
*** rburton <rburton!> has quit IRC20:43
*** marka <marka!> has quit IRC20:52
*** christner <christner!> has quit IRC20:58
CircuitsoftIs there a way to add a file to tmp/deploy from a bbappend? I want bios/win32/syslinux.exe accessible from the output20:58
*** alimon <alimon!alimon@nat/intel/x-vnbaaofjjzeqtjha> has quit IRC21:00
*** gtristan <gtristan!~tristanva@> has joined #yocto21:04
lamegohalstead: are you around?21:04
halsteadlamego, Yes sir!21:04
lamegohalstead: Hi Michael! Please take a look at my latest emails to you when you have the time. I have a couple request there where you can help.21:06
*** morphis_ <morphis_!> has quit IRC21:07
halsteadlamego, I see 2 pings that were threaded out so I missed them about patchwork.  Oh this is done or very close. I see where I said I'd update you and didn't.21:08
halsteadlamego, I'm sorry. Once I get all the AB machines updated and rebooted I'll finish this.21:09
lamegohalstead:  those are the ones. Please help when you have the time.21:09
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has quit IRC21:09
lamegohalstead: Thanks, and have a nice weekend :)21:09
halsteadlamego, I will. Are you heading out soon or can I check in with you here?21:10
lamegohalstead: I'm around one more hour or so. Next Monday from 9:00 AM CST :)21:11
halsteadlamego, Reliable. :)21:11
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has joined #yocto21:13
*** bully4u <bully4u!Adium@nat/intel/x-crjzqvcvdjhxjcfj> has joined #yocto21:41
*** willdye <willdye!> has joined #yocto21:42
*** King_InuYasha <King_InuYasha!> has joined #yocto21:46
*** King_InuYasha <King_InuYasha!~kvirc@fedora/ngompa> has joined #yocto21:46
*** lsandov1 <lsandov1!lsandov1@nat/intel/x-zrudqxisvlohaorb> has joined #yocto21:46
*** willdye <willdye!> has joined #yocto21:48
*** lsandov1 <lsandov1!lsandov1@nat/intel/x-zrudqxisvlohaorb> has quit IRC21:48
*** lsandov11 <lsandov11!lsandov1@nat/intel/x-hctucbeoyyclirtq> has joined #yocto21:48
*** willdye <willdye!> has quit IRC21:49
*** |King_InuYasha| <|King_InuYasha|!> has quit IRC21:49
*** royalpurple <royalpurple!> has quit IRC21:52
*** royalpurple <royalpurple!> has joined #yocto21:53
*** Shurelous <Shurelous!~igor@> has quit IRC21:53
*** zerus <zerus!> has joined #yocto21:59
kergothbluelightning: any thoughts? fails to load any oe package modules from non-oe-core layers, despite the sys.path modification in base.bbclass, but only happens with devtool, not a regular parse or build22:04
*** phyllip <phyllip!> has joined #yocto22:16
*** zerus <zerus!> has quit IRC22:16
*** ldts <ldts!~jro@linaro/ldts> has joined #yocto22:16
phyllipcan anyone explain why running bitbake on a particular image target with two different machine targets seems to cause conflicts? the tmp work directory for one machine will have empty git directories for certain packages, for example, causing their compiles to fail22:17
phyllipi'm assuming it's something relating to one of the caches but i'm having trouble determining which and how to work around this issue22:18
phyllipis in inadvisable to build for multiple machine targets using the same base yocto directory?22:19
kergothit's the same build directory that's the issue, but even that isn't a problem as long as you wipe tmp between them22:19
kergoththat said, multi-machine builds with a single tmpdir *should* work, if it doesnt', that's a bug22:19
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC22:21
*** lamego <lamego!~jose@> has quit IRC22:23
phyllipkergoth: i can say for certain that it doesn't seem to work without wiping tmp in between builds22:23
phyllipideally i wouldn't need to do so since i'd like to have a copy of u-boot and a rootfs for each machine22:24
phyllipwithout having to manually back it up elsewhere22:24
*** itseris <itseris!~emikulin@> has quit IRC22:25
*** itseris <itseris!~emikulin@> has joined #yocto22:25
phyllipkergoth: one fix i've found is manually running a cleanall task for each package that fails22:25
phyllipworkaround, i should say22:25
phyllipkergoth: is it a specific bug? one that has been fixed in a particular version?22:28
*** dmoseley <dmoseley!> has joined #yocto22:33
*** ldts <ldts!~jro@linaro/ldts> has quit IRC22:38
*** lsandov11 <lsandov11!lsandov1@nat/intel/x-hctucbeoyyclirtq> has quit IRC22:40
*** agust <agust!> has quit IRC22:41
*** majuk <majuk!> has quit IRC22:54
*** lsandov1 <lsandov1!lsandov1@nat/intel/x-kuamazxhjiximdiq> has joined #yocto23:00
*** stephano <stephano!~stephano@> has quit IRC23:15
*** sjolley <sjolley!sjolley@nat/intel/x-hfyltpplzgfnaffo> has quit IRC23:16
*** phyllip <phyllip!> has quit IRC23:27
*** adca1 <adca1!~adca@> has joined #yocto23:27
*** adca <adca!~adca@> has quit IRC23:29
*** Trinners <Trinners!> has quit IRC23:32
*** Trinners <Trinners!> has joined #yocto23:32
*** fischerm <fischerm!> has quit IRC23:45

Generated by 2.11.0 by Marius Gedminas - find it at!