Friday, 2016-03-11

*** ecdhe <ecdhe!> has joined #yocto00:00
*** DriverCoder <DriverCoder!~mdrustad@> has joined #yocto00:07
*** eraineri <eraineri!~eraineri@2605:6000:151e:814d:224:d7ff:febc:c3d0> has quit IRC00:08
*** sjolley <sjolley!sjolley@nat/intel/x-gljtlmoiuhwftrgs> has joined #yocto00:09
*** ecdhe <ecdhe!> has quit IRC00:26
*** clopez <clopez!> has quit IRC00:36
*** sameo <sameo!~samuel@> has quit IRC00:36
*** jbrianceau_away <jbrianceau_away!uid10952@gateway/web/> has quit IRC00:38
*** ecdhe <ecdhe!> has joined #yocto00:39
*** clopez <clopez!> has joined #yocto00:40
*** evanmeagher <evanmeagher!~evanmeagh@> has quit IRC00:44
*** dreyna4529 <dreyna4529!> has quit IRC00:44
*** roccof <roccof!~rocco@> has quit IRC00:47
*** evanmeagher <evanmeagher!~evanmeagh@> has joined #yocto00:49
*** dreyna4529 <dreyna4529!> has joined #yocto00:52
*** sgw_ <sgw_!> has quit IRC00:56
*** evanmeagher <evanmeagher!~evanmeagh@> has quit IRC01:02
*** evanmeagher <evanmeagher!~evanmeagh@> has joined #yocto01:03
*** deviosity_ <deviosity_!> has joined #yocto01:10
*** deviosity <deviosity!> has quit IRC01:13
*** deviosity_ is now known as deviosity01:13
*** deviosity_ <deviosity_!> has joined #yocto01:14
*** seebs <seebs!> has quit IRC01:16
*** seebs <seebs!> has joined #yocto01:17
*** deviosity <deviosity!> has quit IRC01:17
*** deviosity_ is now known as deviosity01:17
*** ecdhe <ecdhe!> has quit IRC01:43
*** Lucretia <Lucretia!~laguest@pdpc/supporter/active/lucretia> has quit IRC01:43
*** PortaLu <PortaLu!~laguest@pdpc/supporter/active/lucretia> has joined #yocto01:43
*** PortaLu <PortaLu!~laguest@pdpc/supporter/active/lucretia> has quit IRC01:48
*** PortaLu <PortaLu!~laguest@pdpc/supporter/active/lucretia> has joined #yocto01:49
*** ecdhe <ecdhe!> has joined #yocto01:55
*** evanmeagher <evanmeagher!~evanmeagh@> has quit IRC02:08
*** PortaLu <PortaLu!~laguest@pdpc/supporter/active/lucretia> has quit IRC02:12
*** PortaLu <PortaLu!~laguest@pdpc/supporter/active/lucretia> has joined #yocto02:13
*** coolmouse <coolmouse!~coolmouse@> has joined #yocto02:14
*** DriverCoder <DriverCoder!~mdrustad@> has quit IRC02:16
*** cbzx <cbzx!> has joined #yocto02:25
*** cbzx <cbzx!> has quit IRC02:30
*** coolmouse <coolmouse!~coolmouse@> has joined #yocto02:30
*** deviosity <deviosity!> has quit IRC02:33
*** PortaLu is now known as Lucretia02:41
*** coolmouse <coolmouse!~coolmouse@> has quit IRC02:41
*** coolmouse <coolmouse!~coolmouse@> has joined #yocto02:54
*** Aethenelle_ <Aethenelle_!~Aethenell@> has joined #yocto03:21
*** sa2ajj <sa2ajj!> has joined #yocto03:21
*** aehs291 <aehs291!~aehernan@> has joined #yocto03:23
*** sujith_h_ <sujith_h_!~toaster@> has joined #yocto03:24
*** Aethenelle <Aethenelle!~Aethenell@> has quit IRC03:30
*** aehs29 <aehs29!~aehernan@> has quit IRC03:30
*** sujith_h <sujith_h!~toaster@kde/developers/sujithh> has quit IRC03:30
*** vquicksilver <vquicksilver!~nobody@gentoo/contributor/vquicksilver> has quit IRC03:30
*** Aethenelle_ is now known as Aethenelle03:30
*** sujith_h_ is now known as sujith_h03:30
*** vquicksilver <vquicksilver!~nobody@gentoo/contributor/vquicksilver> has joined #yocto03:31
*** vquicksilver_ <vquicksilver_!~nobody@gentoo/contributor/vquicksilver> has joined #yocto03:54
*** vquicksilver <vquicksilver!~nobody@gentoo/contributor/vquicksilver> has quit IRC03:55
*** pidge <pidge!~pidge@2a02:8084:ac1:d80:f1ff:1b95:401c:359b> has quit IRC03:56
*** dreyna4529 <dreyna4529!> has quit IRC04:02
*** cbzx <cbzx!> has joined #yocto04:58
*** cbzx <cbzx!> has quit IRC05:00
*** driftingblues <driftingblues!~driftingb@> has joined #yocto05:08
*** driftingblues <driftingblues!~driftingb@> has left #yocto05:09
*** hamis_lt_u <hamis_lt_u!~irfan@> has joined #yocto05:15
*** coolmouse <coolmouse!~coolmouse@> has quit IRC05:17
*** Aethenelle <Aethenelle!~Aethenell@> has quit IRC05:24
*** ka6sox is now known as zz_ka6sox05:47
*** blitz00 <blitz00!stefans@unaffiliated/blitz00> has quit IRC05:48
*** blitz00 <blitz00!stefans@nat/intel/x-qnvzhrirgwmloxfa> has joined #yocto05:48
*** blitz00 <blitz00!stefans@unaffiliated/blitz00> has joined #yocto05:48
*** |Sno| <|Sno|!> has joined #yocto05:50
*** Lucretia <Lucretia!~laguest@pdpc/supporter/active/lucretia> has quit IRC05:51
*** Nilesh__ <Nilesh__!uid116340@gateway/web/> has joined #yocto05:52
*** marquiz <marquiz!~marquiz@> has joined #yocto05:52
*** marquiz_ <marquiz_!~marquiz@> has quit IRC05:52
*** [Sno] <[Sno]!> has quit IRC05:52
*** icanicant <icanicant!~icanicant@> has quit IRC05:53
*** freanux <freanux!~freanux@unaffiliated/freanux> has quit IRC05:54
*** Nilesh__ <Nilesh__!uid116340@gateway/web/> has quit IRC05:56
*** fitzsim <fitzsim!~user@2001:420:284a:1300:6e0b:84ff:fe09:4e9f> has quit IRC05:56
*** morphis <morphis!> has joined #yocto05:57
*** Nilesh__ <Nilesh__!uid116340@gateway/web/> has joined #yocto06:02
*** fitzsim <fitzsim!~user@2001:420:284a:1300:6e0b:84ff:fe09:4e9f> has joined #yocto06:02
*** Nilesh__ <Nilesh__!uid116340@gateway/web/> has quit IRC06:02
*** Nilesh__ <Nilesh__!uid116340@gateway/web/> has joined #yocto06:02
*** icanicant <icanicant!~icanicant@> has joined #yocto06:03
*** Lucretia <Lucretia!~laguest@pdpc/supporter/active/lucretia> has joined #yocto06:03
*** AndersD <AndersD!> has joined #yocto06:08
*** agust <agust!> has joined #yocto06:33
*** sujith_h <sujith_h!~toaster@> has quit IRC06:34
*** pohly <pohly!> has joined #yocto06:44
*** sujith_h <sujith_h!~toaster@kde/developers/sujithh> has joined #yocto06:53
*** t0mmy <t0mmy!> has quit IRC07:06
*** Nilesh__ <Nilesh__!uid116340@gateway/web/> has quit IRC07:10
*** fitzsim <fitzsim!~user@2001:420:284a:1300:6e0b:84ff:fe09:4e9f> has quit IRC07:10
*** marek_ <marek_!> has joined #yocto07:14
*** freanux <freanux!~freanux@unaffiliated/freanux> has joined #yocto07:15
*** Nilesh__ <Nilesh__!uid116340@gateway/web/> has joined #yocto07:21
*** fitzsim <fitzsim!~user@2001:420:284a:1300:6e0b:84ff:fe09:4e9f> has joined #yocto07:21
*** Nilesh__ <Nilesh__!uid116340@gateway/web/> has quit IRC07:21
*** Nilesh__ <Nilesh__!uid116340@gateway/web/> has joined #yocto07:21
*** yann|work <yann|work!> has quit IRC07:27
*** TobSnyder <TobSnyder!> has joined #yocto07:39
*** wfailla <wfailla!~wfailla@2001:6f8:12d9:13:1208:b1ff:fee8:f733> has joined #yocto07:42
*** Nilesh__ <Nilesh__!uid116340@gateway/web/> has quit IRC07:47
*** fitzsim <fitzsim!~user@2001:420:284a:1300:6e0b:84ff:fe09:4e9f> has quit IRC07:47
*** t0mmy <t0mmy!~tprrt@> has joined #yocto07:47
*** tasslehoff <tasslehoff!~Tasslehof@> has joined #yocto07:49
*** jbrianceau_away <jbrianceau_away!uid10952@gateway/web/> has joined #yocto07:53
*** dreyna4529 <dreyna4529!> has joined #yocto07:53
*** jbrianceau_away is now known as jbrianceau07:53
*** Nilesh__ <Nilesh__!uid116340@gateway/web/> has joined #yocto07:54
*** fitzsim <fitzsim!~user@2001:420:284a:1300:6e0b:84ff:fe09:4e9f> has joined #yocto07:54
*** Nilesh__ <Nilesh__!uid116340@gateway/web/> has quit IRC07:57
boucman_workhello, I have a patch I want to contribute to yocto (meta/) but I can't figure out what branch to follow, is it master or master-next08:01
boucman_workit seems master-next is regularly rebased, so I would guess master, but i couldn't find any doc08:01
*** mckoan|away is now known as mckoan08:03
*** zz_ka6sox is now known as ka6sox08:03
*** vmesons <vmesons!> has joined #yocto08:04
*** vmeson <vmeson!> has quit IRC08:05
*** dreyna4529 <dreyna4529!> has quit IRC08:06
-YoctoAutoBuilder- build #702 of nightly-world is complete: Success [build successful] Build details are at
*** jonatan <jonatan!~jonatan@> has quit IRC08:09
*** fl0v0 <fl0v0!> has joined #yocto08:14
*** townxelliot <townxelliot!~ell@> has joined #yocto08:15
*** florian <florian!~fuchs@Maemo/community/contributor/florian> has joined #yocto08:20
mborzeckiboucman_work: master08:22
boucman_workand do you follow the convention of using --- in the commit message to separate the actual message from the comment to the ML ? or do you rather have a [0/1] message where i discuss stuff about the patch ?08:24
*** matteo <matteo!~matteo@openwrt/developer/matteo> has joined #yocto08:28
mborzeckiboucman_work: i prefer cover letter if the patch requires more explanation than what's in the commit message08:36
*** joshuagl <joshuagl!joshuagl@nat/intel/x-meaifydlbujjlmip> has joined #yocto08:39
*** tasslehoff <tasslehoff!~Tasslehof@> has quit IRC08:42
*** edbart <edbart!ebartosh@nat/intel/x-bfandqbrkulfimch> has joined #yocto08:42
*** yann|work <yann|work!> has joined #yocto08:42
*** sameo <sameo!samuel@nat/intel/x-bmcsaizoqtsxuiuh> has joined #yocto08:43
*** belen <belen!~Adium@> has joined #yocto08:46
RPboucman_work: [0/1] is for the discussion08:47
RPboucman_work: although the commit message should be self supporting08:48
*** ant_work <ant_work!> has joined #yocto08:49
*** LinuxMice <LinuxMice!~LinuxMice@> has joined #yocto08:49
*** roccof <roccof!> has joined #yocto08:50
LinuxMicehi everyone Good Morning, i build java 7 jre package with bitbake, i must to run this command: bitbake openjdk-7-jre, Am i right ?08:55
*** wfailla <wfailla!~wfailla@2001:6f8:12d9:13:1208:b1ff:fee8:f733> has quit IRC08:57
LinuxMiceLetoThe2nd: i think LetoThe2nd exactly know this question ^_^ ?08:57
LetoThe2ndwhy should i?08:58
LinuxMiceLetoThe2nd: My question is : hi everyone Good Morning, i build java 7 jre package with bitbake, i must to run this command: bitbake openjdk-7-jre, Am i right?? and i think u exactly know this answer ^_^08:59
*** wfailla <wfailla!~wfailla@2001:6f8:12d9:13:1208:b1ff:fee8:f733> has joined #yocto08:59
LetoThe2ndLinuxMice: i actually fail to understand the question, and what makes you think that i specifically know it?08:59
LetoThe2ndLinuxMice: i guess you *want* to build that thing, right?09:00
LinuxMiceLetoThe2nd: Yes i want to build java with bitbake command and this command bitbake openjdk-7-jre is right command ?09:01
LetoThe2ndbesides that, about everything i know about java in OE is this:
*** Anticom <Anticom!~timo.m@> has joined #yocto09:03
AnticomHi all.09:03
LetoThe2ndand generally speaking bibaking a package will compile and package it - not magically move it somewhere, especially not to a target or filesystem09:03
AnticomDISTRO_FEATURES_DEFAULT features are not enabled, if i set DISTRO_FEATURES are they?09:03
*** rburton <rburton!> has joined #yocto09:04
*** fl0v01 <fl0v01!> has joined #yocto09:05
*** fl0v0 <fl0v0!> has quit IRC09:08
*** wfailla <wfailla!~wfailla@2001:6f8:12d9:13:1208:b1ff:fee8:f733> has quit IRC09:09
LetoThe2ndAnticom: thats what docs suggest, yes.
*** freanux <freanux!~freanux@unaffiliated/freanux> has quit IRC09:19
*** maxin <maxin!~maxin@2001:998:22:0:a91b:4efe:a9f3:1e15> has joined #yocto09:26
*** john55 <john55!3cfa6ee2@gateway/web/freenode/ip.> has joined #yocto09:27
*** wfailla <wfailla!~wfailla@> has joined #yocto09:34
*** maxin <maxin!~maxin@2001:998:22:0:a91b:4efe:a9f3:1e15> has quit IRC09:43
*** wfailla <wfailla!~wfailla@> has quit IRC09:43
*** jonathanmaw <jonathanmaw!> has joined #yocto09:53
*** Kakadu <Kakadu!4fad4e8c@gateway/web/freenode/ip.> has joined #yocto09:56
-YoctoAutoBuilder- build #707 of nightly-x86 is complete: Failure [failed BuildImages_2 Running ESDK Sanity Tests] Build details are at
*** joshuagl <joshuagl!joshuagl@nat/intel/x-meaifydlbujjlmip> has quit IRC09:56
*** N-a-N <N-a-N!uid149677@gateway/web/> has joined #yocto09:57
*** raykinsella78 <raykinsella78!rkinsell@nat/intel/x-xtpuowllhvedbkyk> has joined #yocto10:01
*** raykinsella78 <raykinsella78!rkinsell@nat/intel/x-xtpuowllhvedbkyk> has left #yocto10:01
*** wfailla <wfailla!~wfailla@2001:6f8:12d9:13:1208:b1ff:fee8:f733> has joined #yocto10:04
*** jmleo <jmleo!> has joined #yocto10:07
jmleohi !10:07
*** joshuagl <joshuagl!~joshuagl@> has joined #yocto10:09
*** jmleo <jmleo!> has left #yocto10:12
*** wfailla <wfailla!~wfailla@2001:6f8:12d9:13:1208:b1ff:fee8:f733> has quit IRC10:12
*** dv_ <dv_!> has quit IRC10:20
*** dv_ <dv_!> has joined #yocto10:22
*** wfailla <wfailla!~wfailla@> has joined #yocto10:27
boucman_workok, thx, one more question and I send my patch :P10:30
boucman_workmy patch modifies meta/recipes-core/initrdscripts/files/ but not the recipe itself... I would have expected to have to increment something... but there is no PR in the recipe, and the recipe has no upstream10:31
boucman_workshould I create a new file, create a new .bb with a new version in its name, or should I just push and assume prserv will handle it correctly ?10:31
rburtonbitbake sees that you've modified the file and rebuilds as required10:31
boucman_workrburton, yes it does, my question was more "do I need to increase the PV in my patch"10:32
rburtonas bitbake sees a file modification and rebuilds as required10:32
boucman_workok, cool, i'm good to go then10:32
*** _4urele_ <_4urele_!> has quit IRC10:36
boucman_workand sent... hopefully I got it right :)10:39
*** _4urele_ <_4urele_!> has joined #yocto10:39
*** LocutusOfBorg <LocutusOfBorg!~Gianfranc@ubuntu/member/locutusofborg> has joined #yocto10:40
*** dv_ <dv_!> has quit IRC10:42
*** mihai <mihai!mihai@nat/intel/x-onasgefnjvxwllmo> has joined #yocto10:42
*** dv_ <dv_!> has joined #yocto10:44
*** belen <belen!~Adium@> has quit IRC10:57
*** wfailla <wfailla!~wfailla@> has quit IRC10:58
*** zero_note <zero_note!~zero_note@> has joined #yocto11:03
*** john55 <john55!3cfa6ee2@gateway/web/freenode/ip.> has quit IRC11:14
*** pidge_ <pidge_!~pidge@2a02:8084:ac1:d80:e9f7:42f8:4fb:388f> has joined #yocto11:16
*** pidge_ <pidge_!~pidge@2a02:8084:ac1:d80:e9f7:42f8:4fb:388f> has quit IRC11:20
*** coolmouse <coolmouse!~coolmouse@> has joined #yocto11:21
*** wfailla <wfailla!> has joined #yocto11:24
*** JEEB <JEEB!~jeeb@unaffiliated/jeeb> has quit IRC11:30
*** berton <berton!~fabio@> has joined #yocto11:31
*** ka6sox is now known as zz_ka6sox11:31
*** JEEB <JEEB!~jeeb@unaffiliated/jeeb> has joined #yocto11:32
*** ant_work <ant_work!> has quit IRC11:39
*** cart_man <cart_man!29a03a62@gateway/web/freenode/ip.> has joined #yocto11:44
cart_manIS there a specific Cross compiler I need to be able to Compile on windows for my Yocto device?11:45
LetoThe2ndcart_man: i think the meta-mingw layer works on enabling the sdk generation for windows dev hosts, but.... there be dragons!11:47
cart_manLetoThe2nd: AWwww....11:48
cart_manLetoThe2nd: Ok soo do you think coding in normal GCC / G++ on Linux will work best?11:48
LetoThe2ndcart_man: s/work best/probably be the only thing that works close to reliable/11:48
cart_manLetoThe2nd: So I can just work on Ubuntu standard compiler not even need to use a crosscompiler ?11:51
LetoThe2ndcart_man: nope11:51
cart_manfuk soo need to use the meta-mingw... so where do I get this meta-mingw ?11:52
LetoThe2ndcart_man: given the correct arch, using your distros toolchain might work for very limited, statically linked use cases.11:52
LetoThe2ndcart_man: for anything else, use the sdk functionality provided by OE. its there for a reason.11:53
cart_manLetoThe2nd: Ok I am actually trying to get to the point where i can use exactly that which you are speaking of11:53
cart_manLetoThe2nd: But I am a bit lost11:53
cart_manI have my IMX6 board running Yocto at the moment AND its on the network soo I want to start building apps for it in C++ from my Desktop computer11:54
LetoThe2ndcart_man: the bottom line is: you have an OE based build process that generates your image. so then just use that very same build process to provide the fitting sdk.11:54
LetoThe2ndcart_man: for standard cases, this means only after doing "bitbake your-image", a "bitbake your-image -c populate_sdk"11:55
LetoThe2ndwhich will provide you with an installable sdk, that brings the toolchain matching your target system, as well as the available libraries and a setup script for your environment to use it.11:56
*** caiortp <caiortp!~inatel@> has joined #yocto11:57
cart_manLetoThe2nd: Ok so how does it work? Does the code gets transfered to your device and compiled on it or do you need to set up a compiler on your Host PC?11:59
LetoThe2ndcart_man: ermmm....11:59
*** JaMa <JaMa!> has joined #yocto11:59
LetoThe2nd12:56 < LetoThe2nd> which will provide you with an installable sdk, that brings the toolchain matching your target system,11:59
*** clopez <clopez!> has quit IRC12:00
cart_manLetoThe2nd: Ok soo I install that then onto my Desktop? Ughh im confused12:01
LetoThe2ndcart_man: you install it onto your development host. which is not necessarily a desktop computer ;-)12:01
LetoThe2ndcart_man: have a good look at
*** ant_work <ant_work!> has joined #yocto12:03
LetoThe2ndcart_man: or generally anything in
LetoThe2ndcart_man: the alternative is, try the populate_sdk comamnd and tinker around with it to see what it does and what you get out of it.12:04
LetoThe2ndor alternative #2: hire a consultant12:06
*** blueness <blueness!~blueness@gentoo/developer/blueness> has quit IRC12:06
*** clopez <clopez!> has joined #yocto12:06
cart_manLetoThe2nd: No I am just confused as to how Targeted compilations work12:08
LetoThe2ndyou probably mean "cross compilation"12:09
AnticomHow is network configuration done properly, when using systemd? currently we simply install a file to /etc/network/interfaces in a init-ifupdown.bbappend recipe that seems kind of wonky ot me12:11
cart_manLetoThe2nd: Well how to compile onto my target.. cross probably ues12:11
LetoThe2ndcart_man: *sigh*12:12
cart_manLetoThe2nd: : (12:12
LetoThe2ndcart_man: you really have to get the terms "toolchain" "compilation" "architecture" "target" and "host" straight first.12:12
*** wfailla <wfailla!> has quit IRC12:13
LetoThe2ndcart_man: otherwise you just will misinterpret about everything you see.12:13
Anticomthink in the mega manaual there was a step by step tutorial on some hello world recipe iirc12:13
Anticomcheck that one out cart_man12:13
LetoThe2ndAnticom: generally the application development section in the yocto docs is pretty exhaustive.12:14
AnticomLetoThe2nd: is that concerning my recommendation to cart_man or concerning my question?12:14
LetoThe2ndcart_man: this just isn't as simple as clicking the compile button in your favorite uC-IDE with predefined projects, sorry.12:15
LetoThe2ndAnticom: concerning the recommendation, yes.12:15
LetoThe2ndAnticom: concerning your own one, the problem is just that there is no systemd way of network configuration. its up to whatever network management engine you choose to accompany it.12:16
Anticomso no delicious abstractions for that yet?12:17
AnticomLetoThe2nd: How are you doing interface configuration in your projects?12:17
LetoThe2ndAnticom: well there ist systemd-networkd, but we told you about that already yesterday - so i implied by you not asking specifically about it that you decided against it.12:17
LetoThe2ndAnticom: we have some custom stuff in place12:17
AnticomLetoThe2nd: Checked back with my PM and he told me i should investigate further12:18
AnticomLetoThe2nd: i saw, that there was /etc/systemd/network or something where you can place your config when using systemd12:19
LetoThe2ndAnticom: um, so you just mentally erased what you learned yesterday and ask the same questions again to "investigate further?"12:19
Anticomiirc there was no exhaustive answer to that question12:19
LetoThe2ndAnticom: no. plain wrong. there is a specific place under etc where you you can place your config when using systemd_networkd12:19
LetoThe2ndsystemd by itself just does not do that. no matter how often you repeat it.12:20
AnticomSo in the end it also comes to installing config files to rootfs?12:21
LetoThe2ndAnticom: the exhaustive answer was "pick one of the alternatives, then one can discuss on how to use it."12:21
Anticomthat's what my question is more about12:21
LetoThe2ndAnticom: well as your configuration probably is meant to be persistent, it will always mean some file operation of one kind or the other. that holds true for networkd, connman, nm, everything i know.12:21
LetoThe2ndshouldn't you generally choose your solution by matching its features against your requests, instead of looking at the path where it wants his config files?12:22
AnticomLetoThe2nd: Well as i wrote yesterday already from what i know systemd is somewhat 100% compatible with sysvinit files. The idea we had was switching to systemd before we launch our product so we can port the things from sysvinit to systemd gradually when the product has already been launched12:24
LetoThe2ndAnticom: ... which i think is a really bad idea.12:24
AnticomBackground is, that systemd should improve our boot times since it starts services in parralel instead of sequencially12:25
LetoThe2ndsystemd is very, very invasive. and it is really not sysvinit compatible, at least not in terms of "i just install systemd, it makes everything magically faster while nothing breaks."12:25
AnticomLetoThe2nd: And now i'm curious what exactly did break and in turn how much efford it would take to fix it again12:26
*** wfailla <wfailla!~wfailla@> has joined #yocto12:27
AnticomLetoThe2nd: also why do they claim its compatible when it's really not?12:27
LetoThe2ndAnticom: its "enough compatible for the common desktop usecase."12:28
*** AndersD <AndersD!> has quit IRC12:31
LetoThe2ndAnticom: i really know that for most desktop linux distribution users systemd has the effect/impression of "hey we switched the init system and now everything boots magically faster". but under the hood that is just not true. it is not the reality.12:32
AnticomLetoThe2nd: it doesn't have to be 'magically' faster yet12:33
cart_manLetoThe2nd: Ok so this SDK Tool that you where talking about.. where does this get installed .. My Question is DOES bitbake Generate anything that you must use to "Prepare" the development system (My Desktop NOT the ImX6 board)12:33
AnticomThe idea is more about preparing our production image to enable making it faster int he future by providing the proper tools12:33
AnticomCurrently it only has to 'not break'12:34
LetoThe2ndAnticom: if your image is more than trivial (it has more than one binary that has to be kicked off during boot), switching to systemd will break stuff and eat your dev time.12:34
AnticomLetoThe2nd: Binary of what sort? custom or something from the oe layers?12:35
Anticomi mean ntp, syslogd, etc. seemed to be running just fine12:35
LetoThe2ndcart_man: really, this is all neatly documented, and however complicated it is not black magic. i feel that trying to explain those basics again through irc is not really a valuable use of time.12:35
LetoThe2ndcart_man: my suggestion would be, find somebody who has already done that once and have him/her show it to you in real life.12:36
LetoThe2ndAnticom: because those already have seen the proper dev work needed for the transition.12:36
*** blueness <blueness!~blueness@gentoo/developer/blueness> has joined #yocto12:36
AnticomLetoThe2nd: well then we actually do have only a single service that is brought up by us12:37
cart_manLetoThe2nd: My problem is I am stuck not remotely close to anybody know even knows Linux : /   ... I will try the docs12:37
LetoThe2ndAnticom: then write a proper systemd unit file and have it kicked off. sacrifice a chicken in the meanwhile and pray that nothing that you implicitly took for granted breaks.12:38
Anticomcart_man: 1st step: install linux, 2nd step: learn linux (/join #ubuntu etc.) 3rd step: get poky set up in such way you can at least build core-image-sato and run it in quemu, 4th step: come back here :)12:38
AnticomLetoThe2nd: Are goats instead of chicken alright too?12:38
AnticomChicken are out currently :/12:39
LetoThe2ndAnticom: it becomes really, really nasty if you have runtime monitoring of your service in terms of watchdogging it, restarting/rebooting12:39
cart_manAnticom: Lol well I at least got to installing my own Yocto build on my IMX6 so I am a bit clued up haha12:39
LetoThe2ndAnticom: i can only repeat my practical experience - if you are not in the very, very early stages in a project - do not ponder switching to systemd.12:40
AnticomLetoThe2nd: First of all i need to get my image to build again. Just installed lttng tools on my host and the image doesn't build anymore due to invalid kernel config ._.12:40
LetoThe2ndAnticom: usually you can gain a lot more of bootup spped by other means.12:40
AnticomLetoThe2nd: even if it's only a single executable that runs our system? I got about a month of time to get it working.12:42
LetoThe2ndAnticom: depends.12:42
LetoThe2ndAnticom: i cannot comment in a resonably sane way what will break for your specific application and usecase.12:42
AnticomSure there's no standard answer to this12:43
LetoThe2ndjust saw a *lot* breaking unexpected and differently fomr sysV here.12:43
AnticomBut back to the networking stuff. Googling arround for systemd_networkd yielded
AnticomI don't get how stuff like connman relate to this12:44
LetoThe2ndAnticom: why should connman realte to a systemd-networkd specific configuration file?12:44
Anticom<LetoThe2nd> Anticom: well as your configuration probably is meant to be persistent, it will always mean some file operation of one kind or the other. that holds true for networkd, connman, nm, everything i know.12:45
AnticomI was asking, whether the way to go was installing a config to /etc/systemd/network/ but you declined didn't you?12:46
*** AndersD <AndersD!> has joined #yocto12:46
AnticomI know i'm probably giving you a lot of *sigh*'s but i honnestly don't get it then :/12:46
*** wfailla <wfailla!~wfailla@> has quit IRC12:46
LetoThe2ndAnticom: read again.12:46
*** wfailla <wfailla!~wfailla@> has joined #yocto12:47
LetoThe2ndAnticom: i said that every one of those solutions will include some config file. i did not say that they all use the same.12:47
Anticom<Anticom> LetoThe2nd: i saw, that there was /etc/systemd/network or something where you can place your config when using systemd \\ <LetoThe2nd> Anticom: no. plain wrong. there is a specific place under etc where you you can place your config when using systemd_networkd12:47
LetoThe2ndAnticom: read again, one more time.12:48
AnticomSo basically installing files there is the way to go?12:48
LetoThe2ndAnticom: i pointed out that this is the place for *SYSTEMD_NETWORKD*12:48
LetoThe2ndAnticom: not for *SYSTEMD*12:48
Anticomis this a bb var or what are you refering to?12:48
LetoThe2ndAnticom: i am totally not referring to anything OE specific in the least. I am *only* pointing out how these things architecturally work.12:49
AnticomArch wiki any many other websites state stuff like: "All configurations in this section are stored as in /etc/systemd/network."12:50
AnticomSo what is wrong about my assumption?12:50
AnticomI just don't get it12:50
LetoThe2ndbottom line. if you have something that works, don't break it. if bootup speed is your concern, there's a lot more options you have besides systemd12:51
LetoThe2ndAnticom: they are just all referring to one specific network management software called systemd_networkd, which is part of the systemd source distribution. none of these places on the web applies to anything else.12:51
Anticomso yocto doesn't use systemd_networkd ?12:52
LetoThe2ndnow you got it.12:52
LetoThe2ndshall i get you the backlog line where we told you that exact fact already yesterday?12:52
AnticomLetoThe2nd: no need, i belive you12:53
AnticomSo for dummies: systemd_networkd is a networkmanager that talks systemd api?12:53
LetoThe2ndAnticom: yeah.12:53
Anticomand even in yocto i have multiple alternatives?12:54
Anticomlike e.g. connman?12:54
LetoThe2ndAnticom: and again, be precise. its not "yocto that uses". its "the poky distribution that uses by default"12:54
LetoThe2ndAnticom: exactly. pick whatever you want12:54
AnticomAny recommendations?12:54
Anticomor a good resource comparing them so i can pick one myself?12:55
LetoThe2ndAnticom: recommendation "match your requirement against the provided feature sets"12:55
Anticomrequirement: should work12:55
Anticomno special requirements12:56
LetoThe2ndAnticom: that also holds true for an ip= line in the kernel bootargs. please don't be ridiculous.12:56
Anticomso maybe small footprint and fast would be nice12:56
*** flihp_ <flihp_!> has quit IRC12:57
AnticomLetoThe2nd: we're not building an IOT device. So network connectivity has no special requirements really12:57
Anticomdidn't want to be offensive12:57
*** flihp <flihp!> has joined #yocto12:57
LetoThe2ndAnticom: i guess the requirement are just not qhat you think they are.12:57
LetoThe2ndAnticom: ask your user interface people how they are willing to provide configuration data, parse it, etc.12:57
Anticomno UI12:58
Anticombasically it's a logging device12:59
LetoThe2ndAnticom: ok, so they order the device from you with one single fixed network configuration?12:59
LetoThe2ndAnticom: then ask your manufacturing guys what they need.12:59
*** wfailla <wfailla!~wfailla@> has quit IRC12:59
Anticomjust another thought to ease porting from sysvinit. If systemd has a network manager what about sysvinit? is it integrated tight into sysvinit whereas systemd has it nice and modular or is there any for systemd that sysvinit also uses?13:00
LetoThe2ndthe other way round is, just include connman or networkmanager (who will probably 'jsut work') for trivial cases, and wait until it either goes unnoticed or blows up.13:01
AnticomLetoThe2nd: and how do i instruct bitbake to use either of them? is this sufficient?
LinuxMiceHi Everyone, i build java with this command: bitbake openjdk-7-jre and when i want to install this package on my arm board , i take an error : Bus error, wherem am i wrong ?13:03
AnticomLinuxMice: got some more verbose error information? 'bus error' isn't much of information13:04
LetoThe2ndLinuxMice: sounds like the architecture you built for doesn't match the package.... maybe.13:05
LinuxMiceVerbose of error is this: Bus error , no another thing13:05
LetoThe2ndAnticom: see
LetoThe2ndAnticom: it comes complete with systemd unit support13:06
*** wfailla <wfailla!~wfailla@> has joined #yocto13:06
LinuxMiceLetoThe2nd: I thing i take error Which is Bus error Because I have no Space for installing ?13:07
LetoThe2ndLinuxMice: that is something you can easily check, right?13:07
LinuxMiceYeap You are right this way, i boot on nand flash Now i boot on sd card :) Finally i have 1.6 gb available space :)13:10
*** eengie <eengie!> has joined #yocto13:15
eengieHi all.  Has anyone ever seen wic fail with an error like "exec_cmd: install -m 0644 -D <deploy path>/etc <image boot pat>/etc returned '1' instead of 0"??13:16
*** maxin <maxin!~maxin@> has joined #yocto13:16
eengie(I realize it's not really Yocto-related directly, but wic seems to be a pretty common way of packaging Yocto, so I was hoping someone has seen that error)13:19
*** bottazzini <bottazzini!~realBigfo@> has joined #yocto13:20
eengieI don't see a way to force a "verbose" output or determine where it's logging information at either.  But that error makes me wonder if the return value is simply saying the directory exists and shouldn't really be flagged as an "error"13:20
Crofton|workeengie, you might need to file a bug report, the wic devs tend not to hang out on irc13:23
*** freanux <freanux!~freanux@unaffiliated/freanux> has joined #yocto13:24
rburtoneengie: what happens if you run that command yourself?13:25
*** wfailla_ <wfailla_!~wfailla@> has joined #yocto13:25
*** wfailla <wfailla!~wfailla@> has quit IRC13:25
*** fledermaus <fledermaus!~vivek@> has joined #yocto13:27
eengieCroftonIwork: Thanks (and thanks again for the last week of helping me out too -- made loads of progress).  I may have just sniffed out the issue.  I think it's all related to that first question about how to deploy and link files over onto the SD card which ended up being a multi-part approach involving the deploy class (to move the files over to that folder), a pkg_postinst function to create the links after the files were insta13:28
eengierburton: same error as I get when it's in my script.13:28
eengieI think where I may have goofed is that I changed IMAGE_BOOT_FILES to simply say "etc" rather than specify explicitly all of the files...13:29
eengieThere doesn't seem to be a way to access that variable from recipes, unfortunately.13:29
*** leon-anavi <leon-anavi!~leon@> has joined #yocto13:29
rburtoneengie: i mean, run the install command13:30
*** wfailla <wfailla!~wfailla@2001:6f8:12d9:13:1208:b1ff:fee8:f733> has joined #yocto13:30
leon-anavirburton, thanks again for the help with nettle. I have just seen that the fix has been merged in the latest version of branch fido.13:31
eengierburton: sorry, not enough coffee yet...  It says omitting directory.13:31
rburtoneengie: there you go then :)13:32
eengierburton: yeah, I forgot it was one of the changes I made to that layer's conf file...trying to let the user simply deploy files into a couple of documented folders and have wic blindly pick up those whole directories and deploy them to the boot partition.13:32
*** wfailla_ <wfailla_!~wfailla@> has quit IRC13:33
*** wfailla <wfailla!~wfailla@2001:6f8:12d9:13:1208:b1ff:fee8:f733> has quit IRC13:36
*** belen <belen!~Adium@> has joined #yocto13:37
*** lamego <lamego!jose@nat/intel/x-nvczncdzjgiejyyx> has joined #yocto13:37
eengieWeird, according to the docs, the "glob pattern" should work.  So having a layer.conf with IMAGE_BOOT_FILES += "etc/*" should gather up everything in the deploy/..../etc directory.  Right?  (
Anticommaybe dumb question, but doesn't it have to be += "<space> etc/*" ?13:39
*** zero_note <zero_note!~zero_note@> has left #yocto13:40
eengieAnticom: not according to that link.  Then again that link is specifying with an equals, and I'm trying to append since my layer is tacking on extra things to the SD card.13:40
rburton+= adds whitespace13:44
eengieInteresting... I did an IMAGE_BOOT_FILES += "etc/*;etc/" (equivalent to what the link shows above for the glob format) and got an error that it was malformed.13:45
eengieThe trouble I've been having with how to add things to that variable is that the most important one, the top-level Xilinx BSP layer has a weak 'set' for the kernel and u-boot, etc.  Then the vendor's BSP sets it.  But if I specify it, the layer order overwrites the vendor's spec even if I set my layer priority to lower than theirs.13:46
eengieAnd touching the variable from a recipe does absolutely nothing.13:46
*** vdehors_ <vdehors_!> has joined #yocto13:48
*** ADM <ADM!~ADEM@> has joined #yocto13:50
eengierburton: is there a function I could insert into that variable that would recursively generate a list of directories and files from a certain point?  I think I've seen something like that in other recipes using things like bb.utils but I'm having trouble finding it.13:52
*** vdehors <vdehors!~vdehors@> has quit IRC13:52
*** ant_work <ant_work!> has quit IRC13:56
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:5f7f:f279:59ff:fe64:3a8> has joined #yocto13:57
*** kscherer <kscherer!~kscherer@> has joined #yocto14:01
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:5f7f:f279:59ff:fe64:3a8> has quit IRC14:03
*** Flinger <Flinger!d51670c2@gateway/web/freenode/ip.> has joined #yocto14:04
*** egavinc <egavinc!> has quit IRC14:05
*** JaMa <JaMa!> has quit IRC14:12
*** eengie <eengie!> has left #yocto14:12
*** IvanSB <IvanSB!> has joined #yocto14:16
*** nighty <nighty!> has joined #yocto14:17
*** zz_ka6sox is now known as ka6sox14:18
*** JaMa <JaMa!> has joined #yocto14:18
*** paulg_ <paulg_!> has joined #yocto14:24
tmcguire__I added PACKAGE_CLASSES = "package_ipk" to my local.conf, yet bitbake meta-toolchain tries to build nativesdk-rpm (which fails). Any idea how to completely get rid of RPM?14:24
*** sujith_h <sujith_h!~toaster@kde/developers/sujithh> has quit IRC14:28
rburtonwhy does that fail?14:31
JaMatmcguire__: rpm is used e.g. for debugedit tool even when building ipk packages14:32
frayrpm is often built because it has tools for handing debug info and other things..14:32
fraywhat is the error?14:32
frayand what version of rpm are you using?14:32
tmcguire__I'm trying to get Yocto dizzy to work.14:32
fraywow, that is pretty old14:32
fraywhy not try a newer version of the YP?14:33
tmcguire__yeah, but I need it to compare with some actual real project14:33
tmcguire__Missing or unbuildable dependency chain was: ['meta-toolchain', 'nativesdk-packagegroup-sdk-host', 'nativesdk-smartpm', 'nativesdk-rpm']14:33
tmcguire__Hmm, maybe I should just edit the packagegroup14:33
frayI don't believe dizzy supported nativesdk-rpm..  so I'm not sure why it would be in that list?14:33
tmcguire__FYI, error is "undefined reference to `db3Free'", but I'd rather exclude RPM than trying to fix that.14:34
frayare you mixing dizzy with newer recipes?14:34
*** boucman_work <boucman_work!~jrosen@wesnoth/developer/boucman> has quit IRC14:34
frayany comparison you do will be invalid w/ RPM availabel in the system as it's used to process various debugging and dependency information14:34
tmcguire__I don't believe I'm mixing anything, unless I did something wrong. FWIW, the actual image built fine.14:34
fraydb3Free comes from BerkleyDB14:34
tmcguire__well, rpm-native is used internally for dependency information, right? That actually builds fine. What doesn't build is nativesdk-rpm, is that really needed?14:35
*** cart_man <cart_man!29a03a62@gateway/web/freenode/ip.> has quit IRC14:35
* tmcguire__ tries to find the packagegroup thing now and look at it14:36
tmcguire__Ok, found, let's see in what interesting ways it will break when I remove nativesdk-smartpm from that package group...14:38
tmcguire__Btw, "bitbake -g -u depexp nativesdk-rpm" didn't show the dependency chain, only when i tried to blacklist rpm, I got the error message "dependency chain was: ['meta-toolchain', 'nativesdk-packagegroup-sdk-host', 'nativesdk-smartpm', 'nativesdk-rpm']"14:40
tmcguire__Is there another way to get the dependency chain, apart from blacklisting the package with "PNBLACKLIST"?14:41
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto14:41
*** zeechs_ <zeechs_!> has joined #yocto14:42
zeechs_Hi all, I'm trying to build a Yocto image with opencv installed. So I added meta-oe to have the recipe available, I added  opencv to IMAGE_INSTALL, opencv is building fine but is not on the image tar.bz2. I don't understand why? Other packages are installing without any problem.14:45
zeechs_I'm building core-image-base14:45
*** boucman_work <boucman_work!> has joined #yocto14:46
*** boucman_work <boucman_work!~jrosen@wesnoth/developer/boucman> has joined #yocto14:46
rburtonzeechs_: iirc opencv doesn't produce a package called "opencv"14:49
rburtonclearly i need to go and beat the opencv recipe with the work-properly stick14:50
rburtonzeechs_: assuming you have a fairly recent oe, "oe-pkgdata-util list-pkgs -p opencv" will list the packages that it actually created14:50
LinuxMiceHi Evertyone, Finally I installed open-jdk-7 on my device, and i installed tomcat7, JRE_HOME Path needed by is tomcat7, Where find JRE_HOME, Wehere am i installed java14:57
*** madisox <madisox!> has joined #yocto14:57
zeechs_rburton, thanks, it indeed lists all the packages built, which I can find under the "tmp/deploy/rpm/" directory. But how come these packages are not on my target rootfs?14:58
mborzeckiLinuxMice: wow, are you sure you have enough RAM to run tomcat? :)14:58
*** blueness <blueness!~blueness@gentoo/developer/blueness> has quit IRC14:59
boucman_workrburton, is there a more general command to do the recipe => package matching ? something based on PACKAGES or is that the best way ? (and is there a technicall reason or is it a case of "nobody implemente it")14:59
zeechs_rburton, do I have to add each package to the IMAGE_INSTALL variable ?14:59
LinuxMicemborzecki: Yeap i have 512 mb ram and i use yocto fido 1.8 its enough for tomcat7 ;_14:59
mborzeckiboucman_work: oe-pkgdata-util14:59
rburtonboucman_work: that is the general command.  reading the recipe is the alternative but the package list can often be determined at build time.  oe-pkgdata-util looks at what the recipe actually built.15:00
kergothIs anyone else seeing no documents listed at ?15:00
*** AndersD <AndersD!> has quit IRC15:00
rburtonzeechs_: you'd have to read the recipe, but unless there's a meta-package that depends on all the libraries then yes if you want all of opencv installed.15:01
rburtonpatches welcome it sounds like a lot of people get angry at opencv15:01
mborzeckikergoth: `If there are no results for this category, something is wrong. Please contact the site administrator via the Yocto bug tracker.`15:01
kergothyeah, but i have a bunch of extensions installed that occasionally break sites, so i don't trust that it's not on my end :)15:02
mborzeckialso might be a bit outdated15:02
kergothi.e. ublock origin, chameleon, referrer control15:02
kergothso wanted to make sure it was a problem in general, not just here15:02
zeechs_rburton, ok I get it. I now have a better understanding of how the IMAGE_INSTALL works. Thanks a lot!15:03
*** LocutusOfBorg <LocutusOfBorg!~Gianfranc@ubuntu/member/locutusofborg> has quit IRC15:12
*** pacopedraza2 <pacopedraza2!86868949@gateway/web/freenode/ip.> has joined #yocto15:15
AnticomIs BB_DANGLINGAPPENDS_WARNONLY disabled by default? Manual doesn't tell it **directly** but it reads like it's disabled if you don't activate it in your local.conf
*** joshuagl <joshuagl!~joshuagl@> has quit IRC15:20
*** LinuxMice <LinuxMice!~LinuxMice@> has quit IRC15:22
*** LocutusOfBorg <LocutusOfBorg!~Gianfranc@ubuntu/member/locutusofborg> has joined #yocto15:22
*** Ulfalizer <Ulfalizer!~ulf@> has joined #yocto15:22
*** joshuagl <joshuagl!~joshuagl@> has joined #yocto15:23
*** t0mmy <t0mmy!~tprrt@> has quit IRC15:25
*** t0mmy <t0mmy!~tprrt@> has joined #yocto15:27
*** vmeson <vmeson!> has joined #yocto15:30
*** vmesons <vmesons!> has quit IRC15:30
*** marek_ <marek_!> has quit IRC15:36
*** belen <belen!~Adium@> has quit IRC15:40
*** belen <belen!Adium@nat/intel/x-oxixkdpkasvywqdl> has joined #yocto15:40
*** townxelliot <townxelliot!~ell@> has quit IRC15:42
*** madisox <madisox!> has joined #yocto15:42
*** gatisp <gatisp!~gp@> has joined #yocto15:43
*** benjamirc <benjamirc!besquive@nat/intel/x-zembpwkzeepcvkrp> has joined #yocto15:44
gatispHello, I was wondering does yocto have an API for setting file/dir timestaps for all files in final sysroot?15:44
*** wfailla <wfailla!~wfailla@2001:6f8:12d9:13:1208:b1ff:fee8:f733> has joined #yocto15:46
*** T0mW <T0mW!~twalsh@> has joined #yocto15:47
*** wfailla <wfailla!~wfailla@2001:6f8:12d9:13:1208:b1ff:fee8:f733> has quit IRC15:49
*** townxelliot <townxelliot!~ell@> has joined #yocto15:49
T0mWThis has been driving me crazy for a few daze.  I'm trying to set a value into /etc/version in my image.  Currently the "DATE+TIME" is in there, we want "1.3" in /etc/version.  I've tried setting $DISTRO_VERSION, also grep'ed the OE tree + bitbake tree but cannot find anywhere which sets a value into /etc/version.15:50
T0mWThere is something in toolchain-scripts.bbclass which sets something like $versionfile?15:51
Crofton|workfrom #oe15:52
Crofton|work<joshuagl> Crofton|work: if you're still looking /etc/version gets written in lib/oe/rootfs.py15:52
* T0mW looks15:52
*** hamis_lt_u <hamis_lt_u!~irfan@> has quit IRC15:52
Crofton|workthere is also an /etc/timestamp15:52
Crofton|workjoshuagl> Crofton|work: meta/classes/rootfs-postcommands.bbclass15:53
T0mWCrofton, Thanks!  wonder why egrep doesn't like python? heh15:53
T0mWI started looking to append to something like do_populate_sysroot to change the file.15:55
T0mWthen figured "enough,  go ask"15:56
*** berton <berton!~fabio@> has quit IRC15:57
*** maxin <maxin!~maxin@> has quit IRC15:59
*** T0mW <T0mW!~twalsh@> has quit IRC16:01
*** T0mW <T0mW!~twalsh@> has joined #yocto16:02
T0mWCrofton, YAY, you da' man!16:04
* T0mW buys Crofton a pizza16:04
Crofton|worksomeone asked something similar on stackoverflow16:04
kergothAnticom: yes, it's disabled by default. normally dangling appends are fatal16:04
T0mWCrofton, yeah, google the crap outa' this one, tons of hits but not answers. Maybe I need to retake remdial-google-101 ?16:05
* zeddii is locked and loaded for ELC16:07
* fray will be there as well16:07
* zeddii has good memories of the last time it was in San Diego16:07
zeddiior I should say "hazy memories"16:07
*** gatisp <gatisp!~gp@> has quit IRC16:07
fraythis is more inland (by the real convention center) then the last one which was next to the airport in the marina..16:08
Anticomkergoth: thank's16:08
frayI've been to this area a lot at the San Diego Comic-Con...16:08
fraylots of stuff within walking distance16:08
*** Anticom <Anticom!~timo.m@> has quit IRC16:08
zeddiiCrofton|work. fray is convincing me to leave late enough to stay for the oedam.16:09
*** fl0v01 <fl0v01!> has quit IRC16:11
*** dv_ <dv_!> has quit IRC16:14
*** zero_note <zero_note!~zero_note@> has joined #yocto16:15
*** dv_ <dv_!> has joined #yocto16:15
*** pacopedraza2 <pacopedraza2!86868949@gateway/web/freenode/ip.> has quit IRC16:18
*** t0mmy <t0mmy!~tprrt@> has quit IRC16:19
*** t0mmy <t0mmy!~tprrt@> has joined #yocto16:19
*** edbart1 <edbart1!~ebartosh@> has joined #yocto16:21
*** edbart <edbart!ebartosh@nat/intel/x-bfandqbrkulfimch> has quit IRC16:22
*** edbart1 <edbart1!~ebartosh@> has quit IRC16:22
*** sameo <sameo!samuel@nat/intel/x-bmcsaizoqtsxuiuh> has quit IRC16:26
Crofton|workzeddii, aweso,e16:27
*** afxez0r <afxez0r!~afxez0r@> has quit IRC16:34
*** Aethenelle <Aethenelle!~Aethenell@> has joined #yocto16:36
*** dmoseley <dmoseley!> has joined #yocto16:40
*** YoctoAutoBuilder <YoctoAutoBuilder!> has quit IRC16:48
*** YoctoAutoBuilder <YoctoAutoBuilder!> has joined #yocto16:48
*** morphis <morphis!> has quit IRC16:52
*** IvanSB <IvanSB!> has quit IRC16:57
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:5f7f:f279:59ff:fe64:3a8> has joined #yocto17:01
*** joshuagl <joshuagl!~joshuagl@> has quit IRC17:02
*** boucman_work <boucman_work!~jrosen@wesnoth/developer/boucman> has quit IRC17:05
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:5f7f:f279:59ff:fe64:3a8> has quit IRC17:08
*** mckoan is now known as mckoan|away17:08
*** zeechs_ <zeechs_!> has quit IRC17:15
*** berton <berton!~fabio@> has joined #yocto17:19
*** pohly <pohly!> has quit IRC17:22
*** afxez0r <afxez0r!~afxez0r@> has joined #yocto17:24
*** berton <berton!~fabio@> has quit IRC17:25
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:5f7f:f279:59ff:fe64:3a8> has joined #yocto17:26
*** obsrwr_home <obsrwr_home!~obsrwr@> has joined #yocto17:26
*** afxez0r <afxez0r!~afxez0r@> has quit IRC17:34
*** yann|work <yann|work!> has quit IRC17:35
*** jbrianceau is now known as jbrianceau_away17:38
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:5f7f:f279:59ff:fe64:3a8> has quit IRC17:40
*** berton <berton!~fabio@> has joined #yocto17:42
*** afxez0r <afxez0r!~afxez0r@> has joined #yocto17:52
*** LocutusOfBorg <LocutusOfBorg!~Gianfranc@ubuntu/member/locutusofborg> has quit IRC17:52
*** coolmouse <coolmouse!~coolmouse@> has quit IRC17:52
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:5f7f:f279:59ff:fe64:3a8> has joined #yocto17:52
*** jonathanmaw <jonathanmaw!> has quit IRC17:52
*** Kakadu <Kakadu!4fad4e8c@gateway/web/freenode/ip.> has quit IRC17:57
*** ADM <ADM!~ADEM@> has quit IRC17:57
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:5f7f:f279:59ff:fe64:3a8> has quit IRC17:58
*** aehs291 <aehs291!~aehernan@> has quit IRC18:02
RPhalstead: I think we agreed the maintainance window was now. When you're done could you start a build of master-next please?18:03
*** aehs29 <aehs29!~aehernan@> has joined #yocto18:03
halsteadRP will do. Thank you.18:04
*** Flinger <Flinger!d51670c2@gateway/web/freenode/ip.> has quit IRC18:04
RPhalstead: thanks!18:04
*** roccof <roccof!> has quit IRC18:08
*** YoctoAutoBuilder <YoctoAutoBuilder!> has quit IRC18:12
*** YoctoAutoBuilder <YoctoAutoBuilder!> has joined #yocto18:13
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:5f7f:f279:59ff:fe64:3a8> has joined #yocto18:13
*** matteo <matteo!~matteo@openwrt/developer/matteo> has quit IRC18:13
*** fishey1 <fishey1!> has quit IRC18:16
*** benjamirc <benjamirc!besquive@nat/intel/x-zembpwkzeepcvkrp> has quit IRC18:17
*** toddw_ <toddw_!> has quit IRC18:18
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:5f7f:f279:59ff:fe64:3a8> has quit IRC18:20
*** pacopedraza2 <pacopedraza2!8686894b@gateway/web/freenode/ip.> has joined #yocto18:23
*** edbart <edbart!~ebartosh@> has joined #yocto18:29
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:5f7f:f279:59ff:fe64:3a8> has joined #yocto18:32
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has quit IRC18:32
*** belen <belen!Adium@nat/intel/x-oxixkdpkasvywqdl> has quit IRC18:35
*** bottazzini <bottazzini!~realBigfo@> has quit IRC18:35
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:5f7f:f279:59ff:fe64:3a8> has quit IRC18:38
*** fishey1 <fishey1!> has joined #yocto18:42
*** edbart <edbart!~ebartosh@> has quit IRC18:45
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:5f7f:f279:59ff:fe64:3a8> has joined #yocto18:48
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:5f7f:f279:59ff:fe64:3a8> has quit IRC18:55
kergothgrr, i'm really not happy with the shallow implementation, but i'm also having trouble finding any better way to do it18:59
*** townxelliot <townxelliot!~ell@> has quit IRC19:04
* kergoth grumbles19:05
*** Snert_ <Snert_!> has quit IRC19:05
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:5f7f:f279:59ff:fe64:3a8> has joined #yocto19:07
*** leon-anavi <leon-anavi!~leon@> has quit IRC19:08
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:5f7f:f279:59ff:fe64:3a8> has quit IRC19:14
*** mihai <mihai!mihai@nat/intel/x-onasgefnjvxwllmo> has quit IRC19:15
*** blueness <blueness!~blueness@gentoo/developer/blueness> has joined #yocto19:16
*** dmoseley <dmoseley!> has quit IRC19:19
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:5f7f:f279:59ff:fe64:3a8> has joined #yocto19:20
*** Saur <Saur!pkj@nat/axis/x-xqblanaxsxbiefxe> has quit IRC19:20
*** bottazzini <bottazzini!~realBigfo@> has joined #yocto19:25
*** TobSnyder <TobSnyder!> has quit IRC19:27
*** t0mmy <t0mmy!~tprrt@> has quit IRC19:30
*** Saur <Saur!pkj@nat/axis/x-ihkoibfumvkanvwn> has joined #yocto19:32
*** ftonello <ftonello!~felipe@> has quit IRC19:38
*** JaMa <JaMa!> has quit IRC19:45
*** vquicksilver_ <vquicksilver_!~nobody@gentoo/contributor/vquicksilver> has quit IRC19:46
*** vquicksilver <vquicksilver!~nobody@gentoo/contributor/vquicksilver> has joined #yocto19:46
*** jbrianceau_away <jbrianceau_away!uid10952@gateway/web/> has quit IRC19:48
*** alimon1 <alimon1!~alimon@> has quit IRC19:55
*** scottrif <scottrif!> has joined #yocto19:55
*** bottazzini <bottazzini!~realBigfo@> has quit IRC19:55
*** maxin <maxin!> has joined #yocto20:02
*** evanmeagher <evanmeagher!> has joined #yocto20:05
*** t0mmy <t0mmy!> has joined #yocto20:06
*** evanmeagher <evanmeagher!> has quit IRC20:19
*** maxin <maxin!> has left #yocto20:19
*** evanmeagher <evanmeagher!> has joined #yocto20:20
*** evanmeagher <evanmeagher!> has quit IRC20:22
*** sameo <sameo!~samuel@> has joined #yocto20:26
*** N-a-N <N-a-N!uid149677@gateway/web/> has quit IRC20:26
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:5f7f:f279:59ff:fe64:3a8> has quit IRC20:28
*** T0mW <T0mW!~twalsh@> has quit IRC20:40
*** lamego <lamego!jose@nat/intel/x-nvczncdzjgiejyyx> has quit IRC20:41
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:5f7f:f279:59ff:fe64:3a8> has joined #yocto20:42
*** alimon1 <alimon1!alimon@nat/intel/x-hmsbfifgyrglxfif> has joined #yocto20:44
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:5f7f:f279:59ff:fe64:3a8> has quit IRC20:48
*** dreyna4529 <dreyna4529!> has joined #yocto20:51
*** lamego <lamego!~jose@> has joined #yocto20:58
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:5f7f:f279:59ff:fe64:3a8> has joined #yocto21:00
*** pacopedraza2 <pacopedraza2!8686894b@gateway/web/freenode/ip.> has quit IRC21:01
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:5f7f:f279:59ff:fe64:3a8> has quit IRC21:06
*** fledermaus <fledermaus!~vivek@> has quit IRC21:10
*** yann|work <yann|work!> has joined #yocto21:14
*** scottrif <scottrif!> has left #yocto21:14
*** caiortp <caiortp!~inatel@> has quit IRC21:16
*** berton <berton!~fabio@> has quit IRC21:16
*** obsrwr_home <obsrwr_home!~obsrwr@> has quit IRC21:23
*** sameo <sameo!~samuel@> has quit IRC21:25
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:5f7f:f279:59ff:fe64:3a8> has joined #yocto21:27
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:5f7f:f279:59ff:fe64:3a8> has quit IRC21:33
*** pacopedraza <pacopedraza!86868b4e@gateway/web/freenode/ip.> has joined #yocto21:37
*** sjolley <sjolley!sjolley@nat/intel/x-gljtlmoiuhwftrgs> has quit IRC21:37
*** sjolley <sjolley!sjolley@nat/intel/x-vbxfsizxsjwdfauh> has joined #yocto21:39
*** scottrif <scottrif!> has joined #yocto21:42
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:5f7f:f279:59ff:fe64:3a8> has joined #yocto21:47
*** scottrif <scottrif!> has left #yocto21:50
*** bottazzini <bottazzini!~realBigfo@> has joined #yocto21:54
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:5f7f:f279:59ff:fe64:3a8> has quit IRC21:58
*** eraineri <eraineri!~eraineri@2605:6000:151e:814d:224:d7ff:febc:c3d0> has joined #yocto21:59
*** darknighte <darknighte!~darknight@pdpc/supporter/professional/darknighte> has joined #yocto22:07
*** lamego <lamego!~jose@> has quit IRC22:09
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:5f7f:f279:59ff:fe64:3a8> has joined #yocto22:12
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:5f7f:f279:59ff:fe64:3a8> has quit IRC22:17
*** lamego <lamego!jose@nat/intel/x-ckemwqjbbdailror> has joined #yocto22:23
*** toddw <toddw!> has joined #yocto22:28
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:5f7f:f279:59ff:fe64:3a8> has joined #yocto22:29
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:5f7f:f279:59ff:fe64:3a8> has quit IRC22:37
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:5f7f:f279:59ff:fe64:3a8> has joined #yocto22:38
*** ant_home <ant_home!> has joined #yocto22:39
*** zero_note <zero_note!~zero_note@> has quit IRC22:40
*** evanmeagher <evanmeagher!~evanmeagh@> has joined #yocto22:49
*** kscherer <kscherer!~kscherer@> has quit IRC22:51
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:5f7f:f279:59ff:fe64:3a8> has quit IRC22:54
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:5f7f:f279:59ff:fe64:3a8> has joined #yocto22:55
*** bfederau <bfederau!> has quit IRC23:01
*** fmeerkoetter <fmeerkoetter!> has quit IRC23:01
*** fmeerkoetter <fmeerkoetter!> has joined #yocto23:01
*** bfederau <bfederau!> has joined #yocto23:01
*** nighty <nighty!> has quit IRC23:02
*** ant_home <ant_home!> has quit IRC23:05
*** aehs29 <aehs29!~aehernan@> has quit IRC23:05
*** aehs29 <aehs29!~aehernan@> has joined #yocto23:06
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:5f7f:f279:59ff:fe64:3a8> has quit IRC23:08
*** evanmeagher <evanmeagher!~evanmeagh@> has quit IRC23:12
*** alimon1 <alimon1!alimon@nat/intel/x-hmsbfifgyrglxfif> has quit IRC23:12
*** toddw <toddw!> has quit IRC23:12
*** evanmeagher <evanmeagher!~evanmeagh@> has joined #yocto23:14
*** rburton <rburton!> has quit IRC23:20
*** lamego <lamego!jose@nat/intel/x-ckemwqjbbdailror> has quit IRC23:21
*** evanmeag_ <evanmeag_!~evanmeagh@> has joined #yocto23:28
*** evanmeagher <evanmeagher!~evanmeagh@> has quit IRC23:30
*** agust <agust!> has quit IRC23:45
-YoctoAutoBuilder- build #701 of nightly-fsl-ppc-lsb is complete: Success [build successful] Build details are at

Generated by 2.11.0 by Marius Gedminas - find it at!