Thursday, 2017-11-09

*** rburton <rburton!> has quit IRC00:03
*** catch22 <catch22!> has joined #yocto00:04
*** sgw <sgw!> has quit IRC00:06
*** Argylelabcoat <Argylelabcoat!~textual@2605:a000:454d:42f0::2000> has joined #yocto00:06
*** sgw <sgw!swold@nat/intel/x-ybbrfhvjgwwhkpzc> has joined #yocto00:06
*** andycooper <andycooper!uid246432@gateway/web/> has quit IRC00:07
*** ZubairLK <ZubairLK!~Thunderbi@unaffiliated/zubairlk> has quit IRC00:09
*** lamego <lamego!~jose@> has quit IRC00:10
*** ZubairLK <ZubairLK!~Thunderbi@unaffiliated/zubairlk> has joined #yocto00:16
*** rburton <rburton!> has joined #yocto00:18
*** nathani_ <nathani_!> has joined #yocto00:20
*** majuk <majuk!> has quit IRC00:22
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has joined #yocto00:23
*** tgraydon <tgraydon!~tgraydon@> has quit IRC00:24
*** tgraydon <tgraydon!~tgraydon@> has joined #yocto00:24
*** dreyna <dreyna!> has quit IRC00:26
*** ant_home <ant_home!> has quit IRC00:30
*** rburton <rburton!> has quit IRC00:33
*** rburton <rburton!> has joined #yocto00:34
*** armpit <armpit!~armpit@2601:202:4001:9ea0:1866:ccc1:2b3a:60cc> has joined #yocto00:36
*** nighty- <nighty-!> has joined #yocto00:43
*** christner_home <christner_home!> has quit IRC00:44
*** dave0x6d <dave0x6d!uid190567@gateway/web/> has quit IRC00:50
*** rburton <rburton!> has quit IRC00:55
*** diego_r <diego_r!~diego@> has quit IRC00:59
*** martinkelly <martinkelly!~martin@> has quit IRC00:59
*** bodangly <bodangly!> has joined #yocto00:59
*** bodangly_ <bodangly_!> has joined #yocto01:02
*** bodangly <bodangly!> has quit IRC01:05
*** bodangly_ is now known as bodangly01:06
*** silviof <silviof!~silviof@unaffiliated/silviof> has quit IRC01:06
*** User12345678 <User12345678!> has joined #yocto01:08
*** rburton <rburton!> has joined #yocto01:16
*** silviof <silviof!~silviof@unaffiliated/silviof> has joined #yocto01:21
*** martinkelly <martinkelly!~martin@> has joined #yocto01:21
*** rburton <rburton!> has quit IRC01:25
yoctiNew news from stackoverflow: How can a build environment introduce new LDFLAGS into an autoconfig build <>01:29
*** martinkelly <martinkelly!~martin@> has quit IRC01:30
*** anselmolsm <anselmolsm!~anselmols@> has quit IRC01:33
*** silviof1 <silviof1!> has joined #yocto01:45
*** silviof <silviof!~silviof@unaffiliated/silviof> has quit IRC01:48
*** Nilesh_ <Nilesh_!uid116340@gateway/web/> has joined #yocto01:52
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has quit IRC02:06
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has joined #yocto02:18
*** majuk <majuk!> has joined #yocto02:24
*** stephano <stephano!~stephano@> has quit IRC02:25
-YoctoAutoBuilder- build #595 of nightly-x86 is complete: Failure [failed Running Sanity Tests] Build details are at
*** majuk <majuk!> has quit IRC02:29
*** Sir_Gallantmon <Sir_Gallantmon!~King_InuY@fedora/ngompa> has joined #yocto02:48
*** yocti <yocti!> has joined #yocto02:53
*** lsandov <lsandov!~lsandov1@> has joined #yocto02:53
*** ulf` <ulf`!~ulf@> has joined #yocto02:54
*** blueness <blueness!~blueness@gentoo/developer/blueness> has joined #yocto02:54
*** tf <tf!> has joined #yocto02:56
*** volestorm <volestorm!> has joined #yocto02:56
*** rewitt <rewitt!~rewitt@> has joined #yocto02:56
*** dreyna <dreyna!> has joined #yocto02:57
*** sveinse <sveinse!> has joined #yocto02:58
*** gattuso <gattuso!> has joined #yocto02:58
*** Argylelabcoat <Argylelabcoat!~textual@2605:a000:454d:42f0::2000> has quit IRC03:00
*** tgraydon <tgraydon!~tgraydon@> has left #yocto03:00
*** dengke <dengke!~dengke@> has joined #yocto03:04
*** rubdos <rubdos!> has joined #yocto03:05
*** j241 <j241!> has joined #yocto03:13
*** phako[m] <phako[m]!phakomatri@gateway/shell/> has quit IRC03:14
*** georgem_home <georgem_home!uid210681@gateway/web/> has quit IRC03:14
*** jjardon <jjardon!jjardonmat@gateway/shell/> has quit IRC03:14
*** georgem_home <georgem_home!uid210681@gateway/web/> has joined #yocto03:15
*** TurBoss <TurBoss!turbossjau@gateway/shell/> has quit IRC03:15
*** Persuader72[m] <Persuader72[m]!persuader7@gateway/shell/> has quit IRC03:15
*** berton <berton!fabioberto@gateway/shell/> has quit IRC03:15
*** chessnokov[m] <chessnokov[m]!chessnokov@gateway/shell/> has quit IRC03:16
*** bachp <bachp!bachpmatri@gateway/shell/> has quit IRC03:16
*** dddooo <dddooo!psaavedrai@gateway/shell/> has quit IRC03:17
bodanglyhow come even with DL_DIR set, and files all there, it seems my build is still trying to reach out to download files?03:24
bodanglyalso BB_GENERATE_MIRROR_TARBALLS is set03:24
*** rburton <rburton!> has joined #yocto03:28
bluelightningbodangly: all files or just some files?03:32
*** promach <promach!promach@gateway/shell/suchznc/x-vouolcojrzzmybzo> has joined #yocto03:33
bodanglywell, I just realized I forgot to mount the NFS share lol, false alarm.03:34
*** Bryanstein <Bryanstein!~Bryanstei@shellium/admin/bryanstein> has quit IRC03:48
bluelightningbodangly: heh, well, at least the mystery is solved :D03:49
*** Artox <Artox!~Artox@> has quit IRC03:51
*** Artox <Artox!~Artox@> has joined #yocto03:55
*** rodgort` <rodgort`!> has joined #yocto03:55
*** Bryanstein <Bryanstein!~Bryanstei@shellium/admin/bryanstein> has joined #yocto03:55
*** zzeroo <zzeroo!> has quit IRC03:56
*** rodgort <rodgort!> has quit IRC03:56
*** YoctoAutoBuilder <YoctoAutoBuilder!~YoctoAuto@> has quit IRC03:56
*** YoctoAutoBuilder <YoctoAutoBuilder!~YoctoAuto@> has joined #yocto03:56
*** blueness <blueness!~blueness@gentoo/developer/blueness> has quit IRC03:58
*** blueness <blueness!~blueness@gentoo/developer/blueness> has joined #yocto04:01
*** Sir_Gallantmon <Sir_Gallantmon!~King_InuY@fedora/ngompa> has quit IRC04:19
*** zzeroo <zzeroo!> has joined #yocto04:20
*** ranran <ranran!4fb3156a@gateway/web/freenode/ip.> has quit IRC04:45
*** pohly1 <pohly1!> has joined #yocto04:51
*** rburton <rburton!> has quit IRC04:53
*** rburton <rburton!> has joined #yocto04:53
*** georgem_home <georgem_home!uid210681@gateway/web/> has quit IRC04:54
*** pohly <pohly!> has quit IRC04:55
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has joined #yocto04:56
*** rburton <rburton!> has quit IRC04:57
*** rburton <rburton!> has joined #yocto04:58
*** rburton <rburton!> has quit IRC05:15
*** rburton <rburton!> has joined #yocto05:20
*** rburton <rburton!> has quit IRC05:25
*** tyler-baker <tyler-baker!~tyler@unaffiliated/tyler-baker> has quit IRC05:29
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has quit IRC05:30
*** thaytan <thaytan!~jan@> has quit IRC05:37
*** berton <berton!fabioberto@gateway/shell/> has joined #yocto05:38
*** tyler-baker <tyler-baker!~tyler@2603:3023:704:46f0:dc67:1dc9:2918:445b> has joined #yocto05:42
*** bachp <bachp!bachpmatri@gateway/shell/> has joined #yocto05:45
*** jjardon <jjardon!jjardonmat@gateway/shell/> has joined #yocto05:45
*** chessnokov[m] <chessnokov[m]!chessnokov@gateway/shell/> has joined #yocto05:45
*** TurBoss <TurBoss!turbossjau@gateway/shell/> has joined #yocto05:45
*** dddooo <dddooo!psaavedrai@gateway/shell/> has joined #yocto05:45
*** phako[m] <phako[m]!phakomatri@gateway/shell/> has joined #yocto05:45
*** Persuader72[m] <Persuader72[m]!persuader7@gateway/shell/> has joined #yocto05:45
*** rburton <rburton!> has joined #yocto06:00
*** fabo_ <fabo_!> has joined #yocto06:14
*** tlwoerner <tlwoerner!~Trevor@unaffiliated/tlwoerner> has quit IRC06:14
*** kjokinie1 <kjokinie1!~kjokinie@> has joined #yocto06:14
*** m2 <m2!> has quit IRC06:15
*** slips <slips!> has quit IRC06:15
*** kjokinie <kjokinie!~kjokinie@> has quit IRC06:15
*** Net147 <Net147!~Net147@unaffiliated/net147> has quit IRC06:15
*** fabo <fabo!~fabo@linaro/fabo> has quit IRC06:15
*** m2 <m2!> has joined #yocto06:16
*** tyler-baker <tyler-baker!~tyler@2603:3023:704:46f0:dc67:1dc9:2918:445b> has quit IRC06:16
*** cpo <cpo!> has quit IRC06:16
*** tlwoerner <tlwoerner!~Trevor@> has joined #yocto06:18
*** tlwoerner <tlwoerner!~Trevor@unaffiliated/tlwoerner> has joined #yocto06:18
*** slips <slips!> has joined #yocto06:18
*** Net147 <Net147!~Net147@unaffiliated/net147> has joined #yocto06:18
*** Mylene <Mylene!> has quit IRC06:18
*** zbr <zbr!~zibri@2a01:7e01::f03c:91ff:febb:9538> has joined #yocto06:20
*** blueness_ <blueness_!~blueness@gentoo/developer/blueness> has joined #yocto06:21
*** j241 <j241!> has quit IRC06:21
*** blueness <blueness!~blueness@gentoo/developer/blueness> has quit IRC06:22
*** zibri <zibri!~zibri@2a01:7e01::f03c:91ff:febb:9538> has quit IRC06:22
*** blueness_ is now known as blueness06:23
*** Aethenelle <Aethenelle!Elite19980@gateway/shell/elitebnc/x-njaceiyneykyrsrg> has quit IRC06:25
*** Hauke <Hauke!> has quit IRC06:27
*** j241 <j241!> has joined #yocto06:29
yoctiNew news from stackoverflow: why u-boot source code remove while compiling? <>06:29
*** Bretos <Bretos!> has joined #yocto06:30
*** ranran <ranran!1fa87f8c@gateway/web/freenode/ip.> has joined #yocto06:36
ranranDoes anyone knows the meaning of PACKAGE_CLASSES ?= "package_rpm package_ipk" ? Does it mean there are 2 package managers ?06:37
*** dreyna <dreyna!> has quit IRC06:37
*** Hauke <Hauke!> has joined #yocto06:40
*** rburton <rburton!> has quit IRC06:42
*** rburton <rburton!> has joined #yocto06:44
*** Guest52700 <Guest52700!~xdanger@> has joined #yocto06:46
ranranDoes anyone knows the meaning of PACKAGE_CLASSES ?= "package_rpm package_ipk" . Does it mean there are 2 package managers ?06:51
*** hamis <hamis!~irfan@> has joined #yocto06:52
*** nrossi <nrossi!uid193926@gateway/web/> has joined #yocto06:58
*** gtristan_ <gtristan_!~tristanva@> has quit IRC07:01
*** rburton <rburton!> has quit IRC07:03
*** rburton <rburton!> has joined #yocto07:04
*** Guest52700 <Guest52700!~xdanger@> has quit IRC07:04
*** gtristan_ <gtristan_!~tristanva@> has joined #yocto07:09
*** el_robin <el_robin!> has quit IRC07:09
*** beneth <beneth!> has quit IRC07:09
*** gtristan_ is now known as gtristan07:09
*** smartin <smartin!> has quit IRC07:09
*** on1x <on1x!> has quit IRC07:10
*** Hauke <Hauke!> has quit IRC07:10
*** rperier <rperier!~rperier@2001:41d0:52:100::44a> has quit IRC07:10
*** clopez <clopez!> has quit IRC07:10
*** grumble <grumble!~grumble@freenode/staff/grumble> has quit IRC07:16
ranranI see that my image have both rpm and opkg, is it possible to use 2 package manager at the same time ?07:21
*** Bretos <Bretos!> has quit IRC07:28
*** agust <agust!> has joined #yocto07:30
*** T_UNIX <T_UNIX!uid218288@gateway/web/> has joined #yocto07:35
*** fl0v0 <fl0v0!> has joined #yocto08:02
*** boucman_work <boucman_work!~jrosen@wesnoth/developer/boucman> has joined #yocto08:10
*** boucman_work <boucman_work!~jrosen@wesnoth/developer/boucman> has quit IRC08:12
*** ant_work <ant_work!> has joined #yocto08:14
*** fabo_ is now known as fabo08:14
*** fabo <fabo!~fabo@linaro/fabo> has joined #yocto08:15
*** Bunio_FH <Bunio_FH!> has joined #yocto08:15
*** t0mmy <t0mmy!~tprrt@> has joined #yocto08:18
*** Bretos <Bretos!> has joined #yocto08:24
*** diego_r <diego_r!> has joined #yocto08:27
*** Kakounet <Kakounet!> has joined #yocto08:28
*** suvirb <suvirb!uid16371@gateway/web/> has joined #yocto08:30
*** rajm <rajm!> has joined #yocto08:32
*** edgar444 <edgar444!uid214381@gateway/web/> has joined #yocto08:34
*** j241 <j241!> has quit IRC08:35
*** zero_note <zero_note!~zero@> has joined #yocto08:39
*** hnje <hnje!> has joined #yocto08:42
*** fl0v0 <fl0v0!> has quit IRC08:44
*** yann <yann!> has quit IRC08:45
*** colrack <colrack!~colrack@> has joined #yocto08:47
*** j241 <j241!> has joined #yocto08:49
*** toscalix <toscalix!~toscalix@> has joined #yocto08:53
*** cassidy <cassidy!cassidy@nat/collabora/x-ndciulkbblgunvst> has joined #yocto08:55
cassidyHi all. GStreamer 1.12.3 (latest stable release) is in master but not rocko. Are you planning to update or is it freeze to 1.12.2? I'm not sure what's Yocto policy on stable releases.08:56
*** morphis <morphis!> has joined #yocto09:00
LetoThe2ndcassidy: here you go
zzerooranran: PACKAGE_CLASSES ?= "package_rpm package_ipk" means .rpm AND .ipk packages are build. You can use both at the same time. Even with two package managers installed on the same image09:01
LetoThe2ndzzeroo: BUT it means that the first one is used for the image creation processm AND it means that if you mix up two runtime package managements you are completely on your own09:02
*** j241 <j241!> has quit IRC09:03
cassidyLetoThe2nd, thanks. So that means you don't update even for upstream stable releases in the same branch, right?09:04
zzerooLetoThe2nd: this is true thank you for clarifying that. but isn't it standard?09:04
LetoThe2ndzzeroo: what is standard?09:04
*** hnje <hnje!> has quit IRC09:05
LetoThe2ndcassidy: if there is no security or bugfixing necessity then not, right09:05
cassidyLetoThe2nd, thanks for the clarification :)09:05
zzerooLetoThe2nd: Sorry I thought that this is the default in local.conf. But it isn't my mistake09:08
*** sjolley <sjolley!~sjolley@> has quit IRC09:09
*** sjolley <sjolley!~sjolley@> has joined #yocto09:09
LetoThe2ndzzeroo: the standard is rpm. mind, i didn't say that "rpm is standar", i said the first is standard. thats why PACKAGE_CLASSES ?= "package_rpm package_ipk" is not the same as PACKAGE_CLASSES ?= "package_ipk package_rpm", although the values seem to bge identical09:10
*** hnje <hnje!~hnje@> has joined #yocto09:11
*** ed21 <ed21!Adium@nat/intel/x-zqcxkzpxzjdccqrn> has joined #yocto09:21
*** beneth <beneth!> has joined #yocto09:28
*** marquiz_ <marquiz_!marquiz@nat/intel/x-ooassdumrrmncnen> has joined #yocto09:29
*** marquiz <marquiz!marquiz@nat/intel/x-swbksljykewrhban> has quit IRC09:30
*** clement <clement!> has quit IRC09:32
*** clement <clement!> has joined #yocto09:32
*** smartin <smartin!~smartin@> has joined #yocto09:34
*** el_robin <el_robin!~el_robin@> has joined #yocto09:35
*** on1x <on1x!~on1x@> has joined #yocto09:35
*** Hauke <Hauke!> has joined #yocto09:35
*** grumble <grumble!~grumble@freenode/staff/grumble> has joined #yocto09:37
nrossiHmmm that busybox bug... looks like a big one... rocko (/bin/sh -> /bin/busybox.nosuid), master (/bin/sh -> /bin/busybox.suid) :|09:38
*** yann <yann!~yann@> has joined #yocto09:38
*** joshuagl <joshuagl!~joshuagl@> has joined #yocto09:41
*** cassidy <cassidy!cassidy@nat/collabora/x-ndciulkbblgunvst> has left #yocto09:42
*** User12345678 <User12345678!> has quit IRC09:56
*** dengke <dengke!~dengke@> has quit IRC09:57
*** grma <grma!~gruberm@> has joined #yocto09:59
*** rajm <rajm!> has quit IRC10:09
-YoctoAutoBuilder- build #596 of nightly-x86 is complete: Success [build successful] Build details are at
*** rajm <rajm!~robertmar@> has joined #yocto10:23
*** t0mmy <t0mmy!~tprrt@> has quit IRC10:24
*** t0mmy <t0mmy!~tprrt@> has joined #yocto10:25
*** agust <agust!> has quit IRC10:27
*** georgem_home <georgem_home!uid210681@gateway/web/> has joined #yocto10:30
*** agust <agust!> has joined #yocto10:43
*** edgar444 <edgar444!uid214381@gateway/web/> has quit IRC10:44
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has joined #yocto10:48
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has joined #yocto10:52
yoctiNew news from stackoverflow: Put files which are compiled in yocto <>11:00
*** Bretos <Bretos!> has quit IRC11:03
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has quit IRC11:04
*** hamis <hamis!~irfan@> has quit IRC11:06
*** Noor <Noor!~quassel@> has quit IRC11:06
*** xtron <xtron!~xtron@> has quit IRC11:06
*** hamis <hamis!~irfan@> has joined #yocto11:07
*** xtron <xtron!~xtron@> has joined #yocto11:07
*** Noor <Noor!~quassel@> has joined #yocto11:07
*** j241 <j241!> has joined #yocto11:09
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has joined #yocto11:10
rburtonnrossi: what?!  i thought i ripped that out of my branches11:17
rburtonnrossi: oh yay you found the problem \o/11:20
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has quit IRC11:25
nrossirburton: :)11:25
rburtoni wonder why my check-bashisms script didn't notice that earlier11:26
rburtonnrossi: tbh probably worth adding a check in the recipe that the bad linking doesn't happen11:28
*** dave0x6d <dave0x6d!uid190567@gateway/web/> has joined #yocto11:29
*** gtristan <gtristan!~tristanva@> has quit IRC11:38
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC11:45
-YoctoAutoBuilder- build #612 of nightly-oe-selftest is complete: Success [build successful] Build details are at
nrossirburton: yes, probably worth having a sanity check for suid, so that it only creates the symlinks expected and fails otherwise11:56
yoctiNew news from stackoverflow: Is it possible to import a command-line build into toaster? <>12:00
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has joined #yocto12:02
*** egavin <egavin!> has joined #yocto12:03
*** Argylelabcoat <Argylelabcoat!~textual@2605:a000:454d:42f0::2000> has joined #yocto12:05
nrossirburton: should the busybox recipe just check to see if the links file has the same link in both .suid and .nosuid? and show a warning for it?12:17
rburtonnrossi: that could work.  or just explicitly check that sh isn't suid and error if so.12:17
nrossirburton: should it matter that the binary could still have sh builtin? even if it doesn't provide the symlink?12:18
rburtonspecial-casing a check that if sh->busybox.suid then error out would be good enough for me12:19
nrossirburton: ok will sort a patch that checks it (just fail in do_compile is fine right?)12:21
rburtonwherever is good enough to check12:21
rburton possible bashism in do_compile line 176 (should be 'b = a'):12:22
rburtoni'll run it over the entire repo just to see if anything else has sneaked in12:22
*** nighty- <nighty-!> has quit IRC12:22
*** georgem_home <georgem_home!uid210681@gateway/web/> has quit IRC12:40
*** luneff <luneff!~yury@> has joined #yocto12:42
*** ranran <ranran!1fa87f8c@gateway/web/freenode/ip.> has quit IRC12:53
*** kpo_ <kpo_!> has joined #yocto13:08
otaviorburton: rp: the lttng-modules are not compatible with 4.14 kernel. We are using it on meta-freescale and it has been made a new release which fixes those issues.13:11
otaviorburton: being the release just to fix those intrumentation issues, it seems that upgrading makes more sense then backporting13:12
*** nighty- <nighty-!> has joined #yocto13:22
RPotavio: to rocko?13:24
*** ant_work <ant_work!> has quit IRC13:25
*** hnje <hnje!~hnje@> has quit IRC13:26
*** kpo_ <kpo_!> has quit IRC13:27
*** hnje <hnje!~hnje@> has joined #yocto13:29
*** kaspter <kaspter!~Instantbi@> has quit IRC13:34
*** marka <marka!~masselst@> has joined #yocto13:35
sveinseis there a simple way to show task and recipe dependencies? Using -g creates too large sheets to gain any real overview...13:38
sveinsecan it be limited to, say 2 or 3 levels?13:38
*** thaytan <thaytan!~jan@> has joined #yocto13:38
otavioRP: ye13:41
otavioRP: yes13:41
otavioRP: I sent the patch and it includes the changelog provided by upstream13:41
otavioRP: once it goes in, I can work on upgrading lttng to 2.1013:42
sveinsefound it, bitbake -g -u taskexp13:45
sveinseIs recipes listed in RDEPENDS always dependencies when building a recipe?13:45
sveinse*packages listed in RDEPENDS13:46
otaviosveinse: they are added to the build list but not a dependency of the recipe13:47
otaviosveinse: so order is not deterministic13:47
sveinseotavio: ok, I just noticed that when i have a recipe "a" which has RDEPENDS="b" in it also builds "b" when I write "bitbake a"13:49
sveinseI didn't expect that13:49
otaviosveinse: because it is an installation dependency; package a cannot be installed without b13:50
otaviosveinse: so it must be ready at rootfs generation or for package feed13:50
sveinseI'd expect that it would be built from IMAGE_INSTALL="a" would build and install "a" and "b" to satify RDEPENDS. But not when only building recipe "a".13:51
* otavio goes for lunch!13:51
kanavinsveinse: if you are building packages for a remote package feed, then you would want all of the dependencies13:52
sveinsekanavin: yes, of course. But does a "bitbake recipe" imply that you need to rebuild all RDEPENDS?13:54
*** lamego <lamego!~jose@> has joined #yocto13:54
sveinseBut ok, this is one of the implicit rules in bitbake I suppose13:54
kanavinsveinse: if the resulting package is not in sstate cache, then you certainly do13:55
kanavinsveinse: otherwise, the package is taken from the cache and moved to deploy dir, which is a lot faster13:55
*** T_UNIX <T_UNIX!uid218288@gateway/web/> has quit IRC13:55
*** stephano <stephano!~stephano@> has joined #yocto13:55
*** ed21 <ed21!Adium@nat/intel/x-zqcxkzpxzjdccqrn> has quit IRC13:57
sveinsekanavin: yeah, I am probably not seeing the whole picture for it. In other packaging system, RDEPENDS is only something which comes into play when installing a image. A local recipe is ignorant to if a RDEPENDS is updated or not at buildtime.13:58
sveinseBut granted, bitbake has different behaviours, which was my question.13:58
kanavinsveinse: we want consistent, reproducible builds. If you build something, and I build something, we should get the same set of resulting packages, but if RDEPENDS is ignored, then that is not guaranteed.14:00
*** xtron <xtron!~xtron@> has left #yocto14:03
*** jaack <jaack!jaackmatri@gateway/shell/> has joined #yocto14:03
kanavinso then you have a runtime issue which you want me to look into, and I can't easily reproduce it, because I can't easily get the same set of packages as you :)14:04
*** paulg <paulg!~paulg@> has joined #yocto14:04
sveinsekanavin: but you do, don't you? Because to have a runtime issue, you need to install it somewhere. And install will honor RDEPENDS. Thus it's deterministic, isn't it.14:06
sveinseBut 'bitbake recipe' has nothing to do with run time has it? It just builds and packages it, right?14:07
*** paulg_ <paulg_!> has quit IRC14:07
*** thaytan <thaytan!~jan@> has quit IRC14:08
kanavinsveinse: when installing using remote feeds, you would have one set of packages, and I would have another.14:08
sveinseright, so it is a policy to update the full dependency tree, even RDEPENDS. Fine.14:12
kanavinsveinse: but what would the other option be?14:13
kanavinyou do need to build all of the runtime dependencies before placing the package into the package feed, otherwise you'll end up with a package in a feed, but not its dependencies14:14
sveinselike other packaging systems do: care not about RDEPENDS until install or feed deployment.14:16
sveinseI think the difference with other systems is that 'bitbake recipe' implies that its being built for image or feed deployment, while other are just building the recipe packages.14:17
RPsveinse: its actually due to debian.bbclass - the package names depend on the contents of the packages14:17
RPsveinse: so before it can depend on "b", it needs to know what "b" will be called14:17
RPsveinse: so packaging for a needs b14:17
sveinseright. even on RDEPENDS14:18
RPsveinse: even for RDEPENDS since it has to know whether to rename it or not14:18
sveinsegot it14:18
sveinsewell, thanks a lot for the insight14:19
RPsveinse: if you drop debian.bbclass, the dependencies do simplify14:19
*** geheimnis` <geheimnis`!~geheimnis@> has quit IRC14:21
sveinseSomething else: I have qmake5 based recipe, and for some unknown reason it ends up in "cortexa9hf-neon-mx6qdl-poky-linux-gnueabi", while the other non-qmake based recipes ends up in "cortexa9hf-neon-poky-linux-gnueabi" when being built to tune. For some reason qt picks up MACHINE_SOCARCH_SUFFIX14:22
sveinseThe strange thing is that I just modified another qmake5 recipe and all of the sudden it changed directory from the -mx6qdl to the one without. What could cause something like this?14:23
*** geheimnis` <geheimnis`!~geheimnis@> has joined #yocto14:24
yoctiNew news from stackoverflow: Yocto Multifile compilation <>14:31
*** luneff <luneff!~yury@> has quit IRC14:32
*** j241 <j241!> has quit IRC14:35
*** stephano <stephano!~stephano@> has quit IRC14:35
*** j241 <j241!> has joined #yocto14:38
*** sgw <sgw!swold@nat/intel/x-ybbrfhvjgwwhkpzc> has quit IRC14:49
*** melonipoika <melonipoika!> has joined #yocto14:50
*** Willy-- <Willy--!63c02b9b@gateway/web/freenode/ip.> has joined #yocto14:50
*** adelcast <adelcast!~adelcast@> has quit IRC14:50
*** adelcast <adelcast!~adelcast@> has joined #yocto14:50
*** adelcast <adelcast!~adelcast@> has quit IRC14:53
*** adelcast <adelcast!~adelcast@> has joined #yocto14:53
sveinseIf I want to rsync sources into the build tree, can I simply override do_fetch, or does this task have additional roles other than copying/fetching?14:56
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has quit IRC14:57
*** hamis <hamis!~irfan@> has quit IRC14:58
sveinseAt what task is the src hash-sum evaluated?15:01
*** diego__ <diego__!> has joined #yocto15:02
*** zarzar <zarzar!~zarzar@> has quit IRC15:03
*** diego_r <diego_r!> has quit IRC15:03
sveinseI'm trying to find an efficient way to handle larger in-meta-source trees15:05
*** tyler-baker <tyler-baker!~tyler@2603:3023:704:46f0:dc67:1dc9:2918:445b> has joined #yocto15:07
*** stephano <stephano!~stephano@> has joined #yocto15:07
*** zarzar <zarzar!> has joined #yocto15:08
*** melonipoika <melonipoika!> has quit IRC15:10
*** rperier <rperier!~rperier@2001:41d0:52:100::44a> has joined #yocto15:14
*** rperier <rperier!~rperier@ubuntu/member/rperier> has joined #yocto15:14
*** aragua <aragua!> has joined #yocto15:17
*** tyler-baker <tyler-baker!~tyler@2603:3023:704:46f0:dc67:1dc9:2918:445b> has quit IRC15:22
*** andycooper_ <andycooper_!~Andrew_Co@> has quit IRC15:22
*** andycooper <andycooper!~Andrew_Co@> has joined #yocto15:23
*** tyler-baker <tyler-baker!~tyler@2603:3023:704:46f0:dc67:1dc9:2918:445b> has joined #yocto15:24
*** melonipoika <melonipoika!> has joined #yocto15:25
sveinseWill SRC_URI = " file://directory/" work? Will it monitor changes in directory?15:30
*** tyler-baker <tyler-baker!~tyler@2603:3023:704:46f0:dc67:1dc9:2918:445b> has quit IRC15:31
*** sgw <sgw!~swold@> has joined #yocto15:32
*** hmwel <hmwel!> has quit IRC15:33
*** andycooper <andycooper!~Andrew_Co@> has quit IRC15:33
*** ranran <ranran!1fa87f8c@gateway/web/freenode/ip.> has joined #yocto15:34
ranranIs anyone familiar with web browser which can be added to image in yocto ?15:34
*** User12345678 <User12345678!~User@> has joined #yocto15:35
joshuaglthere's epiphany in meta/recipes-gnome15:35
rburtonother browsers are in meta-browser, eg chromium15:36
kanavinranran: also, see meta-browser layer (has mozilla and chrome i think)15:36
kanavinsveinse: what you need is probably externalsrc.bbclass15:36
zzerooOne of my projects need access to Because an issue with meta-rust I cannot just use meta-clang. What can I do?15:37
kanavinzzeroo: describe your issue to meta-clang and meta-rust maintainers15:39
zzerookanavin: &&
sveinsekanavin: I might be wrong, but I think externalsrc will force a rebuild every time15:40
*** yates <yates!> has joined #yocto15:42
*** andycooper <andycooper!~Andrew_Co@> has joined #yocto15:42
yatesis there a way to cause do_compile to emit the actual compile commands with all options? i'm tracing down a bug in a .dts compile and running the yocto build takes 10-15 minutes just to get to that phase - too long. i'd like to just run the compile interactively while tracking my bug15:43
*** melonipoika <melonipoika!> has quit IRC15:43
*** luneff <luneff!~yury@> has joined #yocto15:43
kanavinyates: devtool modify <recipe>15:44
*** rcw <rcw!~rwoolley@> has joined #yocto15:44
*** gtristan <gtristan!~tristanva@> has joined #yocto15:45
yateskanavin: i am already doing a devtool modify <recipe>, and it takes too long15:45
kergothdevtool modify is a one-time operation, after that you just devtool build or bitbake -c compile, which will only run the one task15:46
sveinseDoes yocto/bitbake have any concepts for having sources and recipes together. Much like native deb packages (not to be intermixed with yocto's "native" term)15:47
*** darknighte <darknighte!~darknight@pdpc/supporter/professional/darknighte> has joined #yocto15:48
kergothcan be done locally, as long as BBFILES includes the recipe where it lives in the source tree, and you can set S relative to FILE/FILE_DIRNAME/THISDIR. but it wouldn't handle fetching/unpacking the sources+recipe, that'd have to be done already. i don't know of anyone who has done much with that sort of thing15:48
sveinseWe have a large, multi application codebase that compiles to different kinds of platforms, including yocto. However yocto, tends to want one source repo per recipe (or at least it checks out one per recipe). We did explore having a separate meta-layer for our apps, but that complete fell out of sync with the main apps repo. Thus our meta-layer has been incorporated into the main app repo.15:51
yateskergoth: ah. thanks for the clarification. i missed that.15:51
yatesor had forgotten..15:51
kergothdevtool modify unpacks/patches the source tree locally and appends the recipe to make it use it there, making local source modifications more convenient and safer than trying to dig around inside of tmp/work/, and making bitbake no longer re-unpack/patch unnecessarily15:52
*** JPEWhacker <JPEWhacker!cc4da371@gateway/web/freenode/ip.> has quit IRC15:52
sveinseI have been experiment with setting S="${THISDIR}/../appsrc" in a qmake5 recipe, and it did seem to work... Until today, where I sometimes see that the source tree is deleted. But I have no clue to what task is cleaning too much.15:55
*** vdehors <vdehors!> has joined #yocto15:55
kergothsveinse: my guess would be a cleandirs flag15:56
kergoththat's the dirs to wipe before running the task in question15:56
sveinsethanks, let me grep the sources for it15:56
*** WillMiles <WillMiles!> has joined #yocto15:57
*** gtristan <gtristan!~tristanva@> has quit IRC15:58
sveinsekergoth: is cleandirs scm aware? If the said dir contains .git it will not clean registered files from that repo? So if the dir is a subdir of a git-repo, it would not see the .git dir and thus clean it completely? Plausible?15:58
kergothi doubt it's that complex, likely just a naïve rm -rf by bitbake. should be able to explicitly remove it if needed, though, or even write an event handler in the metadata to remove it if .git exists at that level15:59
*** Willy-- <Willy--!63c02b9b@gateway/web/freenode/ip.> has quit IRC16:00
*** boucman_work <boucman_work!~jrosen@wesnoth/developer/boucman> has joined #yocto16:01
sveinsekergoth: thing is that my recipe that use S="${THISDIR}/.." which points to the root of the layer/sources, does not delete anything, while putting a subdir does16:01
*** gtristan <gtristan!~tristanva@> has joined #yocto16:01
kergothi'd just remove S from cleandirs in the recipe16:05
sveinseI wish there were a way to point to a in-tree source, but not copy it to ${WORKDIR}, but still keep hash-sum record of it.16:06
kergothmight be doable with file-checksums flag16:06
kergothnot sure if that can handle a directory offhand or not16:06
kergothbut even easier would be to just aadd to SRC_URI but use the url parameter to disable unpack16:07
kergothi.e. file://some-path;unpack=no16:07
sveinsekergoth: let me try that16:07
kergothmight be easier to just use externalsrc class, though, and point to the xisting THISDIR-based path as EXTERNALSRC16:08
kergothsince that class is expected to handle all the "this source tree already exists at this path" stuff, including checksumming hte tree16:08
*** ojdo <ojdo!~ojdo@unaffiliated/ojdo> has quit IRC16:11
sveinsekergoth: is externalsrc handling checksumming?16:12
kergothi just said that, yes16:12
sveinsebecause I've experienced that it wants to rebuild the reciped using externalsrc all the time, but I might not be right with that16:12
kergothit arranges for bitbake to do it, anyway16:12
kergothi think that changed somewhat recently16:12
kergothit used to just nostamp the thing16:12
sveinsethats perfect actually16:12
sveinseyeah, i'm on pyro16:13
kergothit's possible i'm remembering wrong, but i think that's the case now, i saw the patches hit the list ages ago16:13
kergothshould chec the master version of the bbclass16:13
*** ojdo <ojdo!~ojdo@unaffiliated/ojdo> has joined #yocto16:18
*** anselmolsm <anselmolsm!anselmolsm@nat/intel/x-pkpwusrjnkglzlwl> has joined #yocto16:23
otaviosveinse: the MACHINE_SOCARCH is a meta-freescale thing; it allows for sharing binaries  across same SoC family processors. This is because some packages need to have changes for i.MX (qtbase, in your case) so it becomes machine specific but to avoid rebuilding it for every machine we ended using this dynamic package arch schema.16:24
*** Bunio_FH1 <Bunio_FH1!> has joined #yocto16:25
*** User12345678 <User12345678!~User@> has quit IRC16:27
*** Bunio_FH <Bunio_FH!> has quit IRC16:29
*** Bunio_FH1 <Bunio_FH1!> has quit IRC16:33
*** stephano <stephano!~stephano@> has quit IRC16:34
*** stephano <stephano!stephano@nat/intel/x-klzhhvypricesccj> has joined #yocto16:34
*** aratiu <aratiu!~adi@> has quit IRC16:34
*** Bunio_FH <Bunio_FH!> has joined #yocto16:34
*** Bunio_FH <Bunio_FH!> has left #yocto16:34
*** User12345678 <User12345678!~User@> has joined #yocto16:35
*** aratiu <aratiu!~adi@> has joined #yocto16:37
*** bodangly <bodangly!> has quit IRC16:38
sveinseotavio: aha, thanks, so thats why all my qt5 based apps are specific to SOCARCH. thanks16:40
*** georgem_home <georgem_home!uid210681@gateway/web/> has joined #yocto16:43
*** j241 <j241!> has quit IRC16:47
*** Nilesh_ <Nilesh_!uid116340@gateway/web/> has quit IRC16:51
*** rajm <rajm!~robertmar@> has quit IRC16:51
*** toscalix <toscalix!~toscalix@> has quit IRC16:54
*** User12345678 <User12345678!~User@> has quit IRC16:56
*** yates <yates!> has quit IRC16:58
yoctiNew news from stackoverflow: GStreamer source code understanding (gst-pligins-base,... gst-plugin-vspfilter, element, pipeline) <>17:01
*** Aethenelle <Aethenelle!Elite19980@gateway/shell/elitebnc/x-qceulioeuyjfnfed> has joined #yocto17:03
*** vdehors <vdehors!> has quit IRC17:05
*** j241 <j241!> has joined #yocto17:09
sveinseAm I reading externalsrc.bbclass:L176 in Pyro where srctree_hash_files() is only making hashindex if the external src is a git repo?17:12
sveinseAm I reading this correctly?17:12
*** yann <yann!~yann@> has quit IRC17:13
*** egavin <egavin!> has quit IRC17:15
luneffhey guys! I'm hitting some strange problem with WebEngineView of meta-qt5 on a Raspberry Pi 3. Detailed log here. . Most noticeable: glGetError 0x505, GL ERROR :GL_OUT_OF_MEMORY : glTexImage2D:, Error: 5 for Command kTexImage2D, GLES2DecoderImpl: Trying to make lost context current. All this results in a white screen with EGLFS backend17:17
*** ranran <ranran!1fa87f8c@gateway/web/freenode/ip.> has quit IRC17:17
*** bavery_fn <bavery_fn!bavery@nat/intel/x-gllbgpnjzhsazufn> has quit IRC17:19
otaviosveinse: yw17:20
*** dreyna <dreyna!> has joined #yocto17:21
*** dreyna <dreyna!> has quit IRC17:22
*** dreyna <dreyna!> has joined #yocto17:22
*** Kakounet <Kakounet!> has quit IRC17:31
*** bodangly_ <bodangly_!> has joined #yocto17:40
*** tyler-baker <tyler-baker!~tyler@2603:3023:704:46f0:dc67:1dc9:2918:445b> has joined #yocto17:40
*** grma <grma!~gruberm@> has quit IRC17:44
sveinseThis is excellent: I'm using EXTERNALSRC to point to the in-meta-tree-source, and use SRC_URI="file://...;unpack=no" in addition to allow the checksummer to detect any src changes. I had to use QMAKE_PROFILES="`ls ${EXTERNALSRC}/*.ori`" to allow qmake to pick up the external source. But now, finally, it works17:45
sveinsethanks, kergoth for pointing me in the right direction17:46
*** bodangly_ is now known as bodangly17:46
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has quit IRC17:47
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has joined #yocto17:48
*** mckoan|away is now known as mckoan17:48
*** mckoan is now known as mckoan|away17:48
*** j241 <j241!> has quit IRC17:51
*** bavery_fn <bavery_fn!~bavery@> has joined #yocto17:55
*** fitzsim <fitzsim!> has quit IRC17:58
*** CTtpollard <CTtpollard!~CTtpollar@> has quit IRC17:59
*** armpit <armpit!~armpit@2601:202:4001:9ea0:1866:ccc1:2b3a:60cc> has quit IRC18:00
yoctiNew news from stackoverflow: GStreamer source code understanding (gst-pligins-base,... gst-plugin-vspfilter, element, pipeline) [on hold] <>18:01
*** bavery_fn <bavery_fn!~bavery@> has quit IRC18:05
*** colrack <colrack!~colrack@> has quit IRC18:18
*** t0mmy <t0mmy!~tprrt@> has quit IRC18:22
*** User12345678 <User12345678!~User@> has joined #yocto18:25
*** bodangly <bodangly!> has quit IRC18:32
*** bodangly <bodangly!> has joined #yocto18:37
*** User12345678 <User12345678!~User@> has quit IRC18:39
*** morphis <morphis!> has quit IRC18:43
*** User12345678 <User12345678!~User@> has joined #yocto18:43
*** dfaught <dfaught!> has joined #yocto18:44
*** suvirb <suvirb!uid16371@gateway/web/> has quit IRC18:46
*** luneff <luneff!~yury@> has quit IRC18:48
*** bodangly <bodangly!> has quit IRC18:51
*** dfaught <dfaught!> has quit IRC18:57
*** dfaught <dfaught!> has joined #yocto18:58
*** bodangly_ <bodangly_!> has joined #yocto18:58
*** dfaught <dfaught!> has quit IRC18:58
*** dfaught <dfaught!> has joined #yocto19:00
*** bavery_fn <bavery_fn!bavery@nat/intel/x-tcpgamdzmixkypnc> has joined #yocto19:01
*** bluelightning <bluelightning!> has joined #yocto19:03
*** bluelightning <bluelightning!> has quit IRC19:03
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto19:03
*** bodangly_ <bodangly_!> has quit IRC19:03
*** bavery_fn <bavery_fn!bavery@nat/intel/x-tcpgamdzmixkypnc> has quit IRC19:08
*** Bunio_FH <Bunio_FH!> has joined #yocto19:09
*** bodangly <bodangly!> has joined #yocto19:15
*** martinkelly <martinkelly!> has joined #yocto19:17
*** Bunio_FH <Bunio_FH!> has quit IRC19:19
*** bodangly_ <bodangly_!> has joined #yocto19:20
*** bodangly <bodangly!> has quit IRC19:20
rewittIf I want the entire build to fail/stop during parsing due to some configuration check I have in a recipe using anonymous python, do I have to raise parse.ParseError? I tried using bb.error() but everything continues on happily19:24
rewittWell, the error message shows up, but it proceeds to run tasks19:24
bluelightningrewitt: try bb.fatal()19:36
*** bavery_fn <bavery_fn!bavery@nat/intel/x-sgkhkthnhopmjjdv> has joined #yocto19:46
*** armpit <armpit!> has joined #yocto19:49
*** Aethenelle <Aethenelle!Elite19980@gateway/shell/elitebnc/x-qceulioeuyjfnfed> has quit IRC19:50
*** bodangly_ is now known as bodangly19:54
*** marka <marka!~masselst@> has quit IRC20:00
*** neverpanic <neverpanic!> has quit IRC20:09
*** neverpanic <neverpanic!> has joined #yocto20:10
RPWhy does recompiling the kernel appear to cause half my userspace to rebuild :(20:11
smurrayheh, in AGL it's usually because of mesa -> qt -> *20:12
neverpaniclinux kernel headers -> libc -> your userspace?20:13
RPI didn't touch the headers, that I would have understood...20:14
RPI'll poke around it shortly and figure out why its doing this. It just seems bad :(20:14
*** bodangly <bodangly!> has quit IRC20:17
*** bodangly <bodangly!> has joined #yocto20:18
bluelightningRP: I wonder if we should be diffing task graphs between releases, assuming that's even practical20:18
*** yann <yann!> has joined #yocto20:19
rewittbluelightning: That does it thanks20:22
armpitmaybe the kernel is self-aware ?20:28
*** t0mmy <t0mmy!> has joined #yocto20:31
RPbluelightning: there are probably patters we should be looking for20:33
*** paulg_ <paulg_!> has joined #yocto20:34
*** rcwoolley_ <rcwoolley_!~rwoolley@> has joined #yocto20:35
*** Aethenelle <Aethenelle!Elite19980@gateway/shell/elitebnc/x-vcbapjexolhaodhu> has joined #yocto20:36
*** rcw <rcw!~rwoolley@> has quit IRC20:38
*** hnje <hnje!~hnje@> has quit IRC20:39
neverpanicRP: Does it actually matter if the contents of the headers change if the checksum of the task that produces them changes?20:42
*** kpo_ <kpo_!> has joined #yocto20:43
RPneverpanic: sadly the checksums aren't intelligent like that20:43
neverpanicYeah, that's what I thought. Even if the headers don't change, bitbake will still rebuild your entire userland, wouldn't it?20:44
neverpanicWe actually have some code to re-use sstate if the dependencies didn't change (for some defined notion of change)20:46
*** Bretos <Bretos!> has joined #yocto20:51
rewittbluelightning: So here is another question. I basically don't want an image to be built unless the kernel provider is a particular kernel. However, I don't want to wait until the build phase to tell the user things are wrong. So I'm trying to do it during parse. But that won't really work because the recipe always gets parsed.21:00
rewittbluelightning: So what is the best way to error early, but only if the image is in the task graph?21:01
*** WillMiles <WillMiles!> has quit IRC21:03
*** jku <jku!> has joined #yocto21:07
bodanglyif I don't want dropbear in my image (have my own version of SSH in a custom layer), what is the best way to remove it? IMAGE_INSTALL_remove += ?21:12
*** georgem_home <georgem_home!uid210681@gateway/web/> has quit IRC21:13
*** rcwoolley_ <rcwoolley_!~rwoolley@> has quit IRC21:14
*** dreyna <dreyna!> has quit IRC21:18
rewittbodangly: I'm pretty sure you need to remove ssh-server-dropbear from IMAGE_FEATURES, otherwise some things will still happen during rootfs creation21:19
rburtonbodangly: find why its being pulled in and remove it, its not in all images out of the box21:19
rburtonyes, if you have it in IMAGE_FEATURES then remove that21:20
*** dv_ <dv_!~quassel@> has quit IRC21:22
bodanglyI removed it from IMAGE_FEATURES and it still ended up in my image21:29
*** dv_ <dv_!~quassel@> has joined #yocto21:30
bodanglycan I do IMAGE_FEATURES_remove ?21:30
bodanglyif I put that in my image recipe, (and its the last one included), shouldn't that ensure it gets removed?21:30
kergoth_remove is always processed at expansion time. doesn't matter where it's defined, it'll remove it last21:31
rburtonbodangly: presumably this is your image recipe?21:31
rburtoni'd be using taskexp to find out what is pulling it in if you don't mention it in your recipe21:31
bodanglyyeah my image recipe had IMAGE_FEATURES += "ssh-server-dropbear"21:31
bodanglyI deleted that line, but it still ended up in there21:32
kergothsee EXTRA_IMAGE_FEATURES in your local.conf21:32
rewittrburton: I didn't think you could use IMAGE_FEATURES in an image recipe21:32
bodanglyah where can I find documentation for taskexp?21:32
kergothyes, you can, image features are by definition image specific21:32
rburtonbodangly: bitbake -g -u taskexp <imagename>21:32
rewittkergoth: Ahh I thought it was another global config thing21:32
rburtonnope, just a terrible example being set by local.conf :)21:33
rburtonmuch fun when you do IMAGE_FEATURES_append=dbg-pkgs and wonder why your initramfs is giant :)21:33
kergothEXTRA_IMAGE_FEATURES is, it's provided so the user doesn't have to muck with _append, but it's still just pulled in and used by the image, which can override it (and does, in some cases, i.e. initramfs images)21:33
kergothbeen there21:33
rburtonyeah, i think my time was with tools-sdk21:33
bodanglyso I see its in an EXTRA_IMAGE_FEATURES in one of the "require"'d parent inc files21:34
*** Bretos <Bretos!> has quit IRC21:34
bodanglyI guess I can remove it there, but I would prefer to remove it from my own recipe21:34
rburtonbodangly: use _remove in the recipe but i'd be looking at sorting out the parent inc so it wasn't setting stuff that isn't actually universal21:35
bodanglyits from Technexion's BSP layer21:35
rburtonbsp layer in being rubbish shocker21:35
*** gtristan <gtristan!~tristanva@> has quit IRC21:35
bodanglyfuck it I keep it in my own repo anyhow I'll remove it from the BSP21:36
bodanglysounds like thats how it should have been done anyhow21:36
rewittbecause an ssh server is totally needed for a bsp :-D21:36
bodanglyyeah haha21:36
rburtonnot sure why a bsp needs to have a .inc that you need to include for images to work either21:36
bodanglytheir layers are shit to be honest I am learning not to question it and just fix it myself21:37
bodanglyalso stuck on Jethro21:37
rewittbsp="bsp+distro" for most places unfortunately21:37
bodanglyyeah thats what it is21:38
* kergoth shakes head21:38
bodanglyits part of their "guI" image recipe21:38
bodanglywhich is their distro21:38
rburtongood news is that YP layer guidelines v2 explicitly block that sort of behaviour21:38
kergothwe really should provide a nicer way for bsps to identify gui-specific desired components, i.e. x11 driver, gstreamer plugin, etc21:38
kergotha lot of them end up appending images and crap21:38
bodanglybut still, why does a GUI distro need to have the SSH server either?21:38
kergothwell, x11 is at least covered by XSERVER21:39
rewittbodangly: It probably doesn't need it, but you don't need half the stuff on most distros that get installed21:39
kergothssh in an image is often a development/debugging tool more than anything else, unless they really want that open in production..21:39
bodangly"Unable to import extension module "taskexp" from bb.ui. Valid extension modules: knotty or ncurses"21:39
bodanglyis that something from a later version?21:39
bodanglyrewitt: Yeah, I am trying to pare down this distro for production. Its a touch screen controller for an oven, and has CUPS in it among other nonsensical things lol21:40
*** uglyoldbob <uglyoldbob!~uglyoldbo@> has joined #yocto21:40
*** armpit <armpit!> has quit IRC21:41
rewittIf you use "bitbake -e" that will also let you see what caused what to get added to variables21:41
bodanglyalso has tools-debug in the distro lol21:41
rewitti.e. bitbake -e foo-image, then look and see what all touched IMAGE_FEATURES, or IMAGE_INSTALL, etc21:42
uglyoldbobhow can i do a git bisect on a repository of a recipe (ie uses somewhere/over/there/bla.git, i want to git bisect somewhere/over/there/bla.git)21:42
bodanglyI have used bitbake -e, didn't realize I could pass a recipe21:42
kergothuglyoldbob: devtool modify blabla; cd workspace/sources/blablah; git bisect21:43
rewitt+1 devtool, so glad it's not devshell anymore :)21:43
*** Bunio_FH <Bunio_FH!> has joined #yocto21:44
*** luc4 <luc4!> has joined #yocto21:44
rewittI remember a guy freaking out once because he had been doing all of his development in devshell, and then ran bitbake and it refetched21:45
uglyoldbobkergoth: what if devtool fails?21:47
bodanglyso after removing packages from my image, is doing bitbake -f my-image enough to force it to not include them in the rootfs/21:47
bodanglyor do I need to clean the build first21:47
bodanglylooks like that worked as I shaved off 100 megs from my build last night21:49
bodanglyby getting rid of qt5 demos, tools-debug, tools-profile21:50
bodanglyany suggestions on a strategy to implement overlayfs? possible to get it built that way, or should I do it with post-inst scripts?21:51
kergothuglyoldbob: i don't understand the question. devtool just unpacks and patches the sources. if it fails, you've got bigger problems21:54
bodanglyanother question, how do I pick which package manager I want to be used on the system? this build I was given doesn't have opkg or rpm installed into the rootfs, but its building rpm files22:02
kergothshould be an example in local.conf/local.conf.sample/local.conf.sample.extended22:03
bodanglyok thanks22:03
uglyoldbobkergoth: "fatal: Not a git repository: '/tmp/devtoolGYHNbU/workdir/git'"22:03
uglyoldbobkergoth: what should i look at?22:04
nerdboyanybody else get a morty udev image to stop right after init?22:07
nerdboyall i get is Error opening /dev/fb0: No such file or directory and then  udevd[96]: starting eudev-3.222:07
nerdboy*neo basic with mainline kernel/u-boot22:08
bodanglykergoth: I see PACKAGE_CLASSES, and i do have rpm selected, but the resulting system has no rpm binary on it...22:11
kergothsounds like your'e using an image that lacks pakcage-management in IMAGE_FEATURES22:11
kergothwhich results in no package manager22:11
bodanglyah I see22:12
*** dv_ <dv_!~quassel@> has quit IRC22:12
nerdboyotavio: do i need to enable systemd i suppose?22:13
*** dv_ <dv_!~quassel@> has joined #yocto22:15
*** User12345678 <User12345678!~User@> has quit IRC22:17
*** sgw <sgw!~swold@> has quit IRC22:18
*** pohly1 <pohly1!> has quit IRC22:33
*** t0mmy <t0mmy!> has quit IRC22:39
*** bodangly <bodangly!> has quit IRC22:42
*** jku <jku!> has quit IRC22:52
*** User12345678 <User12345678!> has joined #yocto22:52
*** stephano <stephano!stephano@nat/intel/x-klzhhvypricesccj> has quit IRC22:58
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has joined #yocto22:58
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has quit IRC22:59
*** lamego <lamego!~jose@> has quit IRC23:03
*** yizhao <yizhao!~zhaoyi@> has quit IRC23:10
*** joshuagl <joshuagl!~joshuagl@> has quit IRC23:15
RPhalstead: I've been debugging random qemu image hangs. It looks like the AB workers are running out of entropy23:22
RPhalstead: Could we install haveged or rng-tools onto the workers to try and increase it?23:23
halsteadRP, Inside the VM? I don't think the host should run low easily.23:23
RPhalstead: the hosts are running low afaict23:23
RPhalstead: we already have rng-tools inside the VMs and pass host entropy in through virtio23:23
*** majuk <majuk!> has joined #yocto23:24
halsteadRP, Okay. Wow. Yes I can add an entropy daemon.23:24
RPhalstead: I can make images "hang" by running "dd if=/dev/random of=/dev/null bs=1" on the hosts23:24
RPThe hang looks the same as the hangs in the images23:25
RPhalstead: partly its due to the VMs discarding bits quite happily upon startup in a crusade to improve the quality  :/23:26
halsteadThat's expected if you pull all the entropy with dd but weird under normal usage. The test VMs are generating a lot of ssh host keys at boot though.23:26
halsteadThat makes sense. Stop wasting good entropy VMs!  ;)23:26
*** georgem_home <georgem_home!uid210681@gateway/web/> has joined #yocto23:27
RPhalstead: I think this is the next thing we need to try and see if these hangs stop appearing23:27
RPhopefully its not too hard to do23:27
halsteadJust a few minutes I expect.23:28
RPhalstead: thanks23:28
*** nighty- <nighty-!> has quit IRC23:32
*** rburton <rburton!> has quit IRC23:37
*** stephano <stephano!~stephano@> has joined #yocto23:37
*** nathani_ <nathani_!> has quit IRC23:42
RPhalstead: I'll write up my findings tomorrow about all this...23:44
halsteadRP, I've added rng-tools and have it working except on the debian hosts.23:44
*** rburton <rburton!> has joined #yocto23:54

Generated by 2.11.0 by Marius Gedminas - find it at!