Tuesday, 2015-08-25

*** likewise <likewise!~likewise@178-85-26-82.dynamic.upc.nl> has quit IRC00:00
*** afxez0r <afxez0r!~afxez0r@> has quit IRC00:03
*** ant_home <ant_home!~ant__@host167-191-dynamic.52-82-r.retail.telecomitalia.it> has quit IRC00:09
kergothkhem: keep meaning to try it, but haven't had the time, have you played with it?00:10
*** khem` <khem`!~khem@unaffiliated/khem> has joined #yocto00:12
khemkergoth: yes I have, its very fast00:14
khemand has java'ism00:15
khembut if you are able to ignore it. its pretty decent00:15
khem`I am getting python tracebacks from bitbake starting today00:57
seebswell, broken pipe usually means the thing on the other side exited unexpectedly.01:08
*** sameo_ <sameo_!samuel@nat/intel/x-txmmqtrdwrfidbvw> has quit IRC01:11
*** sjolley <sjolley!~sjolley@> has joined #yocto01:18
*** robert__ <robert__!~lyang1@> has quit IRC01:35
*** robert__ <robert__!~lyang1@> has joined #yocto01:35
-YoctoAutoBuilder- build #451 of build-appliance is complete: Failure [failed BuildImages] Build details are at http://autobuilder.yoctoproject.org/main/builders/build-appliance/builds/45101:42
*** Jefro <Jefro!~jefro@50-0-152-82.dedicated.static.sonic.net> has quit IRC01:44
*** dhirc <dhirc!~dhirc@unaffiliated/dhirc> has joined #yocto02:01
dhircI'm new to yocto. I am building a vanilla Fido image for the Beagle Bone Black. It builds alsa-lib-1.0.28 by default, but I need alsa-lib-1.0.29. How do I go about specifying this?02:04
*** jkridner|work <jkridner|work!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto02:19
*** libv <libv!~libv@ppp-188-174-137-67.dynamic.mnet-online.de> has quit IRC02:21
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has quit IRC02:21
parrot1dhirc: you can check out stuffs from http://git.yoctoproject.org/cgit.cgi/poky/plain/meta/recipes-multimedia/alsa/ which contain alsa-lib 1.0.2902:23
*** libv <libv!~libv@ppp-188-174-129-11.dynamic.mnet-online.de> has joined #yocto02:27
dhircparrot1: thanks, where is the 'best' place to put the .bb recipes and how do I add them to my local.conf?02:30
parrot1hmm.....not really sure if you can work with just alsa-lib being 1.0.29 while the rest is 1.0.2902:30
parrot1I would suggest creating a new meta layer and dump the new recipes there02:31
nerdboygholms: that's the plan...  (sjl noticed too ;)02:37
*** simmel80_ <simmel80_!~quassel@p5797EEAA.dip0.t-ipconnect.de> has joined #yocto02:44
*** 7GHAA056D <7GHAA056D!~quassel@p5797ED67.dip0.t-ipconnect.de> has quit IRC02:48
*** joshuagl <joshuagl!~joshuagl@host86-186-99-213.range86-186.btcentralplus.com> has quit IRC03:18
*** joshuagl <joshuagl!~joshuagl@host31-54-70-65.range31-54.btcentralplus.com> has joined #yocto03:19
*** Cardoe <Cardoe!~Cardoe@gentoo/developer/Cardoe> has joined #yocto03:35
*** Jefro <Jefro!~jefro@50-0-152-82.dedicated.static.sonic.net> has joined #yocto03:36
*** thaytan <thaytan!~thaytan@> has quit IRC04:04
*** thaytan <thaytan!~thaytan@> has joined #yocto04:10
*** Guest80885 is now known as ka6sox-farfarawa04:12
-YoctoAutoBuilder- build #180 of nightly-world-lsb is complete: Failure [failed BuildImages] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-world-lsb/builds/18004:39
*** hamis <hamis!~irfan@> has joined #yocto04:48
kergothHmm, what was Darren Hart's nick again?05:23
*** zecke <zecke!~ich@ip5b41fb99.dynamic.kabel-deutschland.de> has joined #yocto05:28
-YoctoAutoBuilder- build #462 of nightly-world is complete: Failure [failed BuildImages] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-world/builds/46205:45
*** frsc <frsc!~frsc@> has joined #yocto05:46
*** grma <grma!~gruberm@HSI-KBW-46-237-193-133.hsi.kabel-badenwuerttemberg.de> has joined #yocto05:48
*** frsc <frsc!~frsc@> has quit IRC05:50
*** frsc <frsc!~frsc@> has joined #yocto05:51
*** sjolley <sjolley!~sjolley@> has quit IRC06:04
*** sjolley <sjolley!sjolley@nat/intel/x-tvsolcxogoynjhvk> has joined #yocto06:07
*** onoffon <onoffon!~khem@unaffiliated/khem> has joined #yocto06:11
*** TobSnyder <TobSnyder!~schneider@ip923450f2.dynamic.kabel-deutschland.de> has joined #yocto06:12
*** khem` <khem`!~khem@unaffiliated/khem> has quit IRC06:13
*** armpit <armpit!~akuster@2601:202:4000:1239:e17c:4679:6483:8991> has quit IRC06:13
*** fitzsim <fitzsim!~user@2001:420:284a:1300:6e0b:84ff:fe09:4e9f> has quit IRC06:13
*** fitzsim <fitzsim!~user@2001:420:284a:1300:6e0b:84ff:fe09:4e9f> has joined #yocto06:14
*** armpit <armpit!~akuster@2601:202:4000:1239:596f:bbca:6faf:af6> has joined #yocto06:18
*** pohly <pohly!~pohly@p57A57DEF.dip0.t-ipconnect.de> has joined #yocto06:24
*** pohly1 <pohly1!~pohly@p57A57DEF.dip0.t-ipconnect.de> has joined #yocto06:30
*** pohly <pohly!~pohly@p57A57DEF.dip0.t-ipconnect.de> has quit IRC06:30
*** opennandra <opennandra!~marek@> has joined #yocto06:41
*** jbrianceau_away <jbrianceau_away!uid10952@gateway/web/irccloud.com/x-mfgjybcfjoimlevz> has joined #yocto06:52
*** jbrianceau_away is now known as jbrianceau06:52
*** sameo_ <sameo_!samuel@nat/intel/x-jgohojbxnvwxoloq> has joined #yocto06:57
*** fredcadete <fredcadete!d4a63893@gateway/web/freenode/ip.> has joined #yocto06:59
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has joined #yocto07:00
*** [Sno] <[Sno]!~sno@p578b540c.dip0.t-ipconnect.de> has quit IRC07:04
-YoctoAutoBuilder- build #153 of nightly-oe-selftest is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-oe-selftest/builds/15307:06
*** [Sno] <[Sno]!~sno@p578b540c.dip0.t-ipconnect.de> has joined #yocto07:06
*** dreyna4529 <dreyna4529!~dreyna@c-24-5-28-247.hsd1.ca.comcast.net> has joined #yocto07:14
-YoctoAutoBuilder- build #443 of nightly-deb is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-deb/builds/44307:14
*** ant_work <ant_work!~ant__@host222-188-static.61-79-b.business.telecomitalia.it> has joined #yocto07:18
*** florian <florian!~fuchs@Maemo/community/contributor/florian> has joined #yocto07:23
*** aehs29 <aehs29!~aehernan@> has quit IRC07:26
*** dcyrille18 <dcyrille18!59fb345d@gateway/web/freenode/ip.> has quit IRC07:30
*** roccof <roccof!~rocco@93-51-177-218.ip268.fastwebnet.it> has joined #yocto07:37
*** psnsilva <psnsilva!~psnsilva@193-126-29-154.net.novis.pt> has joined #yocto07:46
*** hitlin37 <hitlin37!uid16371@gateway/web/irccloud.com/x-xrimorbbkzjqcmjg> has joined #yocto07:52
-YoctoAutoBuilder- build #463 of nightly-fsl-ppc-lsb is complete: Failure [failed UploadToasterEventlog] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-fsl-ppc-lsb/builds/46307:56
-YoctoAutoBuilder- build #119 of nightly-deb-non-deb is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-deb-non-deb/builds/11908:06
*** jimBaxter <jimBaxter!~jbaxter@jimbax.plus.com> has joined #yocto08:09
*** armpit <armpit!~akuster@2601:202:4000:1239:596f:bbca:6faf:af6> has quit IRC08:17
*** likewise <likewise!~likewise@178-85-26-82.dynamic.upc.nl> has joined #yocto08:18
*** gunnarx <gunnarx!~gan@c-5eeaaab7-74736162.cust.telenor.se> has joined #yocto08:23
*** sno <sno!~sno@p578b540c.dip0.t-ipconnect.de> has joined #yocto08:25
*** [Sno] <[Sno]!~sno@p578b540c.dip0.t-ipconnect.de> has quit IRC08:26
gunnarxWhen I do a bitbake -c fetchall, it runs a bunch of compile jobs too.  Is that normal?08:26
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has quit IRC08:27
*** psnsilva <psnsilva!~psnsilva@193-126-29-154.net.novis.pt> has quit IRC08:27
gunnarxor is there some better way to do only the source download08:29
*** Jefro <Jefro!~jefro@50-0-152-82.dedicated.static.sonic.net> has quit IRC08:29
LetoThe2ndgunnarx: without taking a closer look, it probably builds the stuff needed for getting. (curl, git, whatever)08:32
*** likewise <likewise!~likewise@178-85-26-82.dynamic.upc.nl> has quit IRC08:33
gunnarxLetoThe2nd: Oh, ok, I thought those tools were taken from the host system.  They are built first?08:34
LetoThe2ndgunnarx: as little as possible is taken from the host system, so i'm relatively sure these are built first.08:34
LetoThe2ndgunnarx: or at least some of them08:34
gunnarxLetoThe2nd:  You're right, they are all -native components.  And since the tools have lots of dependencies themselves it was more than I had expected.08:43
*** jonathanmaw <jonathanmaw!~jonathanm@82-70-136-246.dsl.in-addr.zen.co.uk> has joined #yocto08:45
*** belen <belen!Adium@nat/intel/x-jtecdvvooxivccfg> has joined #yocto08:47
*** onoffon <onoffon!~khem@unaffiliated/khem> has quit IRC08:52
*** rburton <rburton!~Adium@> has joined #yocto08:54
*** raykinsella78 <raykinsella78!rkinsell@nat/intel/x-kagghayxmnkupwpn> has joined #yocto08:55
*** dreyna4529 <dreyna4529!~dreyna@c-24-5-28-247.hsd1.ca.comcast.net> has quit IRC08:56
*** LocutusOfBorg1 <LocutusOfBorg1!~Gianfranc@93-33-57-140.ip43.fastwebnet.it> has quit IRC08:56
*** raykinsella78 <raykinsella78!rkinsell@nat/intel/x-kagghayxmnkupwpn> has left #yocto08:57
*** gunnarx <gunnarx!~gan@c-5eeaaab7-74736162.cust.telenor.se> has quit IRC08:57
*** gunnarx <gunnarx!~gan@> has joined #yocto08:57
*** raykinsella78 <raykinsella78!rkinsell@nat/intel/x-hnjeetpcglcyshqi> has joined #yocto08:58
-YoctoAutoBuilder- build #466 of nightly-x86-64 is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-x86-64/builds/46609:01
*** nighty^ <nighty^!~nighty@hokuriku.rural-networks.com> has joined #yocto09:02
*** gunnarx <gunnarx!~gan@> has quit IRC09:07
*** gunnarx <gunnarx!~gan@> has joined #yocto09:07
*** raykinsella78 <raykinsella78!rkinsell@nat/intel/x-hnjeetpcglcyshqi> has left #yocto09:10
*** likewise <likewise!~likewise@178-85-26-82.dynamic.upc.nl> has joined #yocto09:10
*** gunnarx <gunnarx!~gan@> has quit IRC09:12
*** gunnarx <gunnarx!~gan@> has joined #yocto09:12
*** LocutusOfBorg1 <LocutusOfBorg1!~Gianfranc@93-33-57-140.ip43.fastwebnet.it> has joined #yocto09:12
*** gunnarx <gunnarx!~gan@> has quit IRC09:18
*** zecke <zecke!~ich@ip5b41fb99.dynamic.kabel-deutschland.de> has quit IRC09:19
*** gunnarx <gunnarx!~gan@> has joined #yocto09:19
*** Crofton <Crofton!~balister@> has joined #yocto09:27
*** JaMa <JaMa!~martin@ip-86-49-34-37.net.upcbroadband.cz> has joined #yocto09:28
*** gunnarx <gunnarx!~gan@> has quit IRC09:34
*** parrot1 <parrot1!~chankitx@> has quit IRC09:35
*** gunnarx <gunnarx!~gan@> has joined #yocto09:41
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto09:43
bluelightningmorning all09:44
Croftonbluelightning, any word on atlas/csipy?09:45
*** armpit <armpit!~akuster@2601:202:4000:1239:596f:bbca:6faf:af6> has joined #yocto09:48
*** YoctoAutoBuilder <YoctoAutoBuilder!~YoctoAuto@yocto-www.yoctoproject.org> has quit IRC09:49
*** YoctoAutoBuilder <YoctoAutoBuilder!~YoctoAuto@yocto-www.yoctoproject.org> has joined #yocto09:50
*** tasslehoff <tasslehoff!~Tasslehof@> has joined #yocto09:52
*** gunnarx <gunnarx!~gan@> has quit IRC09:54
*** gunnarx <gunnarx!~gan@> has joined #yocto09:55
bluelightningCrofton: I think Alejandro had it basically building after bashing on it for some time, but he only got it to build for x86 so far unfortunately10:04
bluelightningI suggested he talk to you about getting some help to fix the remaining issues10:04
bluelightninghas he been in touch?10:04
-YoctoAutoBuilder- build #444 of nightly-deb is complete: Failure [failed BuildImages Running Sanity Tests Running Sanity Tests_1 Running Sanity Tests_2 SendErrorReport] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-deb/builds/44410:08
*** zecke <zecke!~ich@ip5b41fb99.dynamic.kabel-deutschland.de> has joined #yocto10:15
*** hitlin37 <hitlin37!uid16371@gateway/web/irccloud.com/x-xrimorbbkzjqcmjg> has quit IRC10:22
*** gunnarx <gunnarx!~gan@> has quit IRC10:28
*** florian_kc <florian_kc!~fuchs@Maemo/community/contributor/florian> has joined #yocto10:31
*** dv__ <dv__!~quassel@chello062178118086.5.14.vie.surfer.at> has joined #yocto10:32
*** dv_ <dv_!~quassel@chello062178118086.5.14.vie.surfer.at> has quit IRC10:33
*** florian <florian!~fuchs@Maemo/community/contributor/florian> has quit IRC10:33
*** uggedal <uggedal!~uggedal@titanium.uggedal.com> has joined #yocto10:55
*** Crofton <Crofton!~balister@> has quit IRC11:04
*** hitlin37 <hitlin37!uid16371@gateway/web/irccloud.com/x-zafbyhtqxuchkbmh> has joined #yocto11:11
*** blitz00 <blitz00!stefans@unaffiliated/blitz00> has quit IRC11:21
*** blitz00 <blitz00!stefans@unaffiliated/blitz00> has joined #yocto11:22
*** Ox4 <Ox4!~user@unaffiliated/zloy> has joined #yocto11:25
Ox4hey guys11:25
Ox4I've written a script to fully automate building process for jenkins. It is executed on my local host perfectly, but if I run it on a jenkins host it fails with the following message: http://dpaste.com/37JK0MX11:27
Ox4how to resolve this?11:27
JaMaUse a umask which allows a+rx and u+rwx11:28
JaMae.g. 002211:28
Ox4JaMa: for bitbake script?11:30
JaMano, in your operating system11:32
fredcadeteI agree the message is a bit cryptic11:38
*** Ox4 <Ox4!~user@unaffiliated/zloy> has quit IRC11:40
jeremiahIt looks like a bunch of perl modules exist in poky/OE: http://cgit.openembedded.org/cgit.cgi/meta-openembedded/tree/meta-perl/recipes-perl/libtest/libtest-harness-perl_3.30.bb?h=master11:55
jeremiahhow do I access them from perl scripts?11:55
jeremiahthe usual 'use foo::bar' doesn't seem to work11:55
fredcadeteare you trying to use that from the target or the build environment?12:00
jeremiahOn the target machine12:03
fredcadeteI'd suggest checking if the package is installed to the rootfs and where12:04
jeremiahfredcadete: It don't see it anywhere on a 'find' of the rootfs12:04
fredcadetein your build system, do you see it in the work directory?12:05
fredcadetels build/tmp/worl/<machine>/libtest-harness-perl12:05
fredcadeteor something like that12:05
fredcadetethen you can see it in the "package" directory12:05
jeremiahI'll check12:07
jeremiahwhich leads me to believe it ought to be on the "image" under /usr/lib/12:07
jeremiahOr am I misunderstanding things?12:07
fredcadeteI'm not sure, that "image" is tripping me up12:08
fredcadeteI was expecting "package"12:08
jeremiahI think I have things in 'package' as well12:08
*** ntl <ntl!~ntl@99-127-51-4.lightspeed.austtx.sbcglobal.net> has quit IRC12:09
fredcadeteunder packages-split you don't have a package that includes TAP/Parser.pm?12:09
jeremiahon the image?12:13
jeremiahOr is it just on the build machine?12:13
jeremiahHoly crap, there's a ton of perl modules there.12:15
jeremiahthanks fredcadete12:15
jeremiahI guess I can just move'm over12:15
fredcadetethe right thing would be to add the corresponding package to your image12:16
jeremiahOkay, I'll do that.12:17
*** gunnarx <gunnarx!~gan@c-5eeaaab7-74736162.cust.telenor.se> has joined #yocto12:18
*** ntl <ntl!~ntl@99-127-51-4.lightspeed.austtx.sbcglobal.net> has joined #yocto12:23
jeremiahfredcadete: It appears that meta-perl was not listed in my bb.layers file12:29
jeremiahI've added that now.12:29
jeremiahdo I need to bitbake clean?12:29
gunnarxbitbake -c clean rarely works for me to get a failed state back into working mode.  Just saying.12:30
gunnarxIt's a small step to bitbake clean only the offending packages, but as I said it's not guaranteed to work (in my experience)12:31
gunnarxyou know that -c cleanall will remove also the downloaded source right?  Rarely needed but worth trying if all else fails.12:31
bluelightningjeremiah: no, no need to clean12:32
jeremiahbluelightning: thanks, and thanks gunnarx12:33
bluelightninggunnarx: -c clean isn't meant to be an unbreak-everything type of tool though, in fact almost always there's some underlying problem that cleaning and rebuilding is not going to help fix12:33
gunnarxbluelightning: Yeah I don't know what it's meant to do, but I am just noting that it rarely helps in the type of problems I run into, despite that the build itself is in some sense OK because if I wipe all state it is typically successful12:36
gunnarxbut that means some hours of repeated build time.12:36
bluelightninggunnarx: I would strongly urge you to try to get those problems fixed by reporting them, or we'll never be able to fix them12:37
bluelightningif you wipe your TMPDIR any information that might be used to track down the issue is gone12:37
gunnarxbluelightning:  Of course I would if I can identify the yocto problem.  But if a system definition builds find from clean I suspect that yocto/bitbake is considered OK.12:38
gunnarxFor example, I've had this computer that shuts down due to heat in the middle of the build12:38
bluelightninggunnarx: ah well, that's a problem we cannot fix, no ;)12:38
gunnarxUsually the build will not continue cleanly, there are errors.12:38
bluelightningI guess it's fair to say we do assume the hardware on which we're running can be relied upon12:39
gunnarx(after rebooting).  So all I am looking to do is to understand how to make it all a bit less brittle if there are any problems along the way.12:39
bluelightningthere could be a lot of factors at work under those circumstances... did the writes that the system thought succeeded actually succeed?12:40
gunnarxTheoretically it would be possible to recognize that the previous step was not cleanly done, and backtrack to a stable state, I'm just assuming...12:40
gunnarxMany tasks running in parallel is of course a factor12:40
bluelightningwell, we kind of already do that - we only write a stamp for a task (i.e. mark it as done) if it really did run successfully to completion12:40
gunnarxbluelightning:  I know and that's why I'm often surprised at the level of difficulty to restart things cleanly when it is done half way like this.12:41
gunnarxOf course the build scripts could be unclean too.  They only work when run in the right order, undisturbed and so on.12:41
bluelightningnow, if internally that task writes some state that is bad and it's unable to recover from that, then there might be a problem - but cleaning that particular recipe should solve that kind of problem12:41
gunnarx"should" which brings us full circle :-)12:42
*** pohmelie <pohmelie!bca24113@gateway/web/freenode/ip.> has joined #yocto12:42
bluelightningI can't see how it couldn't though12:42
gunnarxI'm not here only to complain, just sharing and discussing...12:42
bluelightningif it doesn't, there is something else happening - e.g., writes that you thought got back to disk actually did not12:42
bluelightningor, files that were written OK got corrupted after the fact12:43
gunnarxmakes sense what you're saying.  I've had this idea to dump out all tasks and run them one by one, storing the state that is created by each one.12:43
gunnarxBut that means serializing the build so I'm changing the parameters then.12:43
gunnarxstoring state = in git/git-annex for example12:43
*** diego_r <diego_r!~diego@host65-246-static.10-188-b.business.telecomitalia.it> has joined #yocto12:43
bluelightningI'm certainly all for trying to mitigate failures if we practically can, at the moment without actual details I'm not sure as to the actual cause of the problem12:44
pohmelieHi, everyone! Is there simple method to add some tree of files and directories to image? I mean some configuration files, soft links, etc…12:44
gunnarxnp, I'm not expecting anything more from you atm12:44
gunnarxthanks for the chat12:44
gunnarxpohmelie: Seems like you could just follow any recipe definition tutorial for this.  Your recipe is just to copy files that you can either keep in your layer, or alternatively unpack a tarball with them.12:49
gunnarx I'm about to ask a question on this file:  http://tinyurl.com/qb89s5q  So why don't you look there.  You can see weston.ini stored in the layer, and you can see it being installed with install.  Of course "cp" is an alternative.12:50
*** lamego <lamego!lamego@nat/intel/x-uomrifqauzlivbwy> has joined #yocto12:51
gunnarxSpecific question:  http://tinyurl.com/qb89s5q   What's an idiomatic way to select one or another file (weston.ini in this case) based on the value of $MACHINE?12:51
gunnarxCould the value of MACHINE just be appended to the filename maybe...12:51
gunnarxI have no idea if that's considered a clean way to do it or not though...12:52
gunnarx(i'm talking about line 33)12:52
*** florian_kc is now known as florian12:52
pohmeliegunnarx: yeah, that's what I'm talking about. If I have two files, recipe is ok, but when I need to copy hundreds? I think about archive, but maybe there is more elegant solution?12:53
pohmelieor not…12:53
bluelightninggunnarx: you should just be able to put the file into a MACHINE-named subdirectory/subdirectories and it should just work12:53
gunnarxI would think about that as source code and provide a tarball that you fetch from somewhere.12:54
gunnarxThat $MACHINE dir goes in same dir as the bb file?12:54
pohmeliegunnarx: hm, interesting, thanks12:54
bluelightninggunnarx: no, under a directory next to it that's the same name as the name part of the recipe, or "files"12:55
bluelightningnormally you'd just put the files in that directory itself, but to make them specific to a machine or architecture you can put them under a subdirectory under that with the machine/arch name12:56
gunnarxLike wayland/<MACHINE name> in this example?12:56
gunnarxNo actually wayland/weston/<MACHINE> I suppose...12:57
gunnarxbluelightning,I think I got it. thanks.12:59
*** raykinsella78 <raykinsella78!rkinsell@nat/intel/x-hnjeetpcglcyshqi> has joined #yocto13:03
raykinsella78having trouble setting up authenication to push to poky contributions - can anyone help?13:03
*** sameo_ <sameo_!samuel@nat/intel/x-jgohojbxnvwxoloq> has quit IRC13:04
*** bellma <bellma!uid109430@gateway/web/irccloud.com/x-dzkoxcyrhwrgpjdf> has joined #yocto13:05
bluelightningraykinsella78: I can try - what seems to be the problem?13:06
*** Cardoe <Cardoe!~Cardoe@gentoo/developer/Cardoe> has joined #yocto13:06
raykinsella78well I asked to send a public key to Michael Halstead 13:12
raykinsella78which I did ...13:12
*** ljose <ljose!~user@> has joined #yocto13:13
*** khem` <khem`!~khem@unaffiliated/khem> has joined #yocto13:13
raykinsella78so now I setting up ssh to clone from poky-contrib ... and something is going wrong.13:13
raykinsella78Cloning into 'poky-contrib'...13:15
raykinsella78Permission denied (publickey).13:15
raykinsella78fatal: Could not read from remote repository.13:15
raykinsella78Please make sure you have the correct access rights13:15
raykinsella78and the repository exists.13:15
ljoseDoes any body know if 'backtrace' is supported with Fido ARM builds? I getting some bogust stack traces in my libray, not sure if it could be related to ARM  limitations13:15
raykinsella78in my .ssh I specifically set the private key for the public key I sent Michael.13:15
raykinsella78So I am definitely doing something wrong.13:15
*** Aethenelle <Aethenelle!~Aethenell@> has joined #yocto13:19
*** Aethenelle <Aethenelle!~Aethenell@> has joined #yocto13:19
zeddiiraykinsella78. can you pm the line you are using for the clone ?13:19
*** Ox4 <Ox4!~user@unaffiliated/zloy> has joined #yocto13:22
*** khem` <khem`!~khem@unaffiliated/khem> has quit IRC13:22
Ox4I've executed script from jenkins workspace and it is executed successfully. But if I trigger a job from the jenkins web interface I receive sanity check misconfiguration :-(13:23
bluelightningOx4: is this the same umask issue you pasted above?13:29
Ox4bluelightning: yes, it is13:29
bluelightningOx4: did you follow JaMa's advice?13:29
Ox4I executed chmod a+rw -R in the jenkins workspace but it didn't help13:30
bluelightningthat's not umask13:31
bluelightningumask is about files you create from that point on13:31
bluelightningumask is set with the "umask" command13:31
Ox4hold on13:32
Ox4the same13:33
bluelightningit's also about what umask is set to within the jenkins environment, not outside of it13:34
*** tsramos <tsramos!~tsramos@> has joined #yocto13:35
Ox4bluelightning: do I have to do umask all jenkins workspace?13:36
Ox4to all*13:36
bluelightningOx4: I'd imagine you could set it in the build script just before running bitbake13:37
mcfriskOx4: a general note, Jenkins is not a build system. bitbake and yocto are a build system. Jenkins needs a lot of hand holding to execute jobs in a sane way, e.g. builds should be isolated from each other, start with clean workspace (or git clean -f -f -x -v && git reset --hard), stop properly without leaking processes... I suggest running these in all of your jenkins job shell scripts: env && set -euxo pipefail && bash. It might be the jenkins is not running thing13:38
* mcfrisk has a lov.. mostly hate relationship with jenkins13:39
*** ftonello <ftonello!~quassel@> has joined #yocto13:40
*** ftonello <ftonello!~quassel@> has joined #yocto13:40
*** ftonello <ftonello!~quassel@> has joined #yocto13:41
Ox4bluelightning: for poky directory?13:41
Ox4ok I will try13:41
bluelightningOx4: it's not for a directory - umask is associated with your shell session13:41
*** raykinsella78 <raykinsella78!rkinsell@nat/intel/x-hnjeetpcglcyshqi> has left #yocto13:42
*** gunnarx <gunnarx!~gan@c-5eeaaab7-74736162.cust.telenor.se> has quit IRC13:44
*** khem` <khem`!~khem@unaffiliated/khem> has joined #yocto13:44
Ox4umask 022, right?13:45
*** gunnarx <gunnarx!~gan@> has joined #yocto13:45
bluelightningOx4: 022 should be fine I think yes13:46
Ox4it works13:47
Ox4thank you bluelightning and mcfrisk13:47
*** khem` <khem`!~khem@unaffiliated/khem> has quit IRC13:47
*** dmoseley <dmoseley!~dmoseley@cpe-75-181-75-239.carolina.res.rr.com> has joined #yocto13:51
*** gunnarx <gunnarx!~gan@> has quit IRC13:53
*** khem` <khem`!~khem@unaffiliated/khem> has joined #yocto13:53
*** gunnarx <gunnarx!~gan@c-5eeaaab7-74736162.cust.telenor.se> has joined #yocto13:54
*** belen2 <belen2!Adium@nat/intel/x-gznxwpwwivpvairr> has joined #yocto13:58
*** belen <belen!Adium@nat/intel/x-jtecdvvooxivccfg> has quit IRC13:58
*** tsramos_ <tsramos_!~tsramos@> has joined #yocto13:59
*** ftonello <ftonello!~quassel@> has quit IRC13:59
*** ftonello <ftonello!~quassel@> has joined #yocto14:00
*** tasslehoff <tasslehoff!~Tasslehof@> has quit IRC14:01
*** tsramos <tsramos!~tsramos@> has quit IRC14:01
*** gunnarx <gunnarx!~gan@c-5eeaaab7-74736162.cust.telenor.se> has quit IRC14:01
*** gunnarx <gunnarx!~gan@> has joined #yocto14:02
*** tanuk_ is now known as tanuk14:03
*** Ox4 <Ox4!~user@unaffiliated/zloy> has quit IRC14:05
*** gunnarx <gunnarx!~gan@> has quit IRC14:09
*** gunnarx <gunnarx!~gan@c-5eeaaab7-74736162.cust.telenor.se> has joined #yocto14:09
*** khem` <khem`!~khem@unaffiliated/khem> has quit IRC14:11
*** khem` <khem`!~khem@unaffiliated/khem> has joined #yocto14:12
*** gunnarx <gunnarx!~gan@c-5eeaaab7-74736162.cust.telenor.se> has quit IRC14:19
realBigfootI am stuck in "Waiting for root device /dev/mmcblkp2" when starting yocto14:19
realBigfootdoes anyone know what this is ?14:19
*** gunnarx <gunnarx!~gan@c-5eeaaab7-74736162.cust.telenor.se> has joined #yocto14:19
*** paulg_ <paulg_!~paulg@> has joined #yocto14:21
*** florian <florian!~fuchs@Maemo/community/contributor/florian> has quit IRC14:22
paulg_someone changed some gnome pkgs from bz2 to xz and it seems not all mirrors have the xz (yet?)   :(14:22
paulg_causing an obvious fetcher failure.14:23
rburtonpatches!  there's a patch on the list for libnotify14:23
rburtonthe fetcher needs a way of doing a HEAD to sanity check URLs without downloading the entire file14:24
*** gunnarx <gunnarx!~gan@c-5eeaaab7-74736162.cust.telenor.se> has quit IRC14:24
*** gunnarx <gunnarx!~gan@c-5eeaaab7-74736162.cust.telenor.se> has joined #yocto14:24
*** hamis <hamis!~irfan@> has quit IRC14:25
kergoththe fetcher can and does check urls before it downloads the entire file, that's what the checkstatus() method in the fetchers is14:27
kergothnot entirely sure where all it's used offhand, though, i haven't had my coffee14:27
* kergoth yawns14:27
kergoththough, maybe you meant checking more than whether its a 404 :)14:28
*** sjolley <sjolley!sjolley@nat/intel/x-tvsolcxogoynjhvk> has quit IRC14:30
*** pohmelie <pohmelie!bca24113@gateway/web/freenode/ip.> has quit IRC14:31
* kergoth mulls over what tests need writing for the git fetcher14:32
*** Aethenelle <Aethenelle!~Aethenell@> has quit IRC14:32
*** gunnarx <gunnarx!~gan@c-5eeaaab7-74736162.cust.telenor.se> has quit IRC14:33
*** gunnarx <gunnarx!~gan@> has joined #yocto14:33
*** belen2 <belen2!Adium@nat/intel/x-gznxwpwwivpvairr> has quit IRC14:33
*** tsramos_ <tsramos_!~tsramos@> has quit IRC14:34
*** tsramos <tsramos!~tsramos@> has joined #yocto14:34
*** sjolley <sjolley!sjolley@nat/intel/x-zegdkyctfkmbqika> has joined #yocto14:35
*** belen <belen!Adium@nat/intel/x-rwcpqjtssicmnwhq> has joined #yocto14:38
JaMapaulg_: even if they have it, it will fail because different checksums14:40
*** aehs29 <aehs29!aehernan@nat/intel/x-wnydlalgvnxbvxnx> has joined #yocto14:41
RPkergoth: its used in the recipe reporting system to figure out various things about recipe upgrades amongst other places14:44
kergothah, cool14:44
RPkergoth: think there is a checkstatus task like do_fetch too, or there was...14:44
ljoseHi, how can I install all python-XXX packages in my image?14:44
RPljose: install python-modules ?14:44
kergothyep, checkuri/checkuriall from utility-tasks.bbclass. cool, that sounds useful14:45
rburtonkergoth: checking for 404 would help14:47
aehs29ljose: I think this might be what you're looking for http://www.yoctoproject.org/docs/1.8/ref-manual/ref-manual.html#var-CORE_IMAGE_EXTRA_INSTALL14:47
rburtonah, neat14:47
aehs29ljose: plus, check the python-manifest file to see what modules you want in specific14:47
paulg_yeah, I'm getting 404s by the handful.14:48
paulg_(well, at least four...)14:49
*** raykinsella78 <raykinsella78!rkinsell@nat/intel/x-hnjeetpcglcyshqi> has joined #yocto14:53
*** belen <belen!Adium@nat/intel/x-rwcpqjtssicmnwhq> has quit IRC14:59
*** opennandra <opennandra!~marek@> has quit IRC14:59
*** Ox4 <Ox4!~user@unaffiliated/zloy> has joined #yocto15:02
Ox4guys, I have one more question15:02
*** belen <belen!Adium@nat/intel/x-cqgzafhbjjipfvjd> has joined #yocto15:03
Ox4| cc1: error: unrecognized command line option "-fuse-ld=bfd"15:03
Ox4in the meta/classes/kernel-arch.bbclass I see this option: KERNEL_CC = "${CCACHE}${HOST_PREFIX}gcc ${HOST_CC_KERNEL_ARCH} -fuse-ld=bfd"15:03
Ox4can I remove this?15:03
*** afxez0r <afxez0r!~afxez0r@> has joined #yocto15:11
*** frsc <frsc!~frsc@> has quit IRC15:14
RPseebs: around?15:14
*** frsc <frsc!~frsc@> has joined #yocto15:15
RPseebs: we're seeing oddness like https://autobuilder.yoctoproject.org/main/builders/nightly-ipk/builds/451/steps/BuildImages/logs/stdio, the pseudo upgrade was in there and I'm wondering if its related15:16
RPseebs: no proof as yet mind :/15:16
*** frsc <frsc!~frsc@> has quit IRC15:16
paulg_0x4 - you using a non-default toolchain?   Otherwise I'd expect others to be seeing that error too....15:17
Ox4paulg_: yes, I am using sourcery gcc-4.5.115:18
paulg_0x4 probably easiest to just bbappend that option out of existence in your custom layer then.15:19
kergoththat'll be a pain, you'd have to do it for every kernel recipe for every bsp. I'd use KERNEL_CC_remove in config metadata15:20
kergothi'll probably add that to meta-sourcery15:20
*** gunnarx <gunnarx!~gan@> has quit IRC15:21
*** gunnarx <gunnarx!~gan@c-5eeaaab7-74736162.cust.telenor.se> has joined #yocto15:21
Ox4kergoth: I just set KERNEL_CC in my linux-yocto-custom.bb file15:22
* kergoth nods15:22
*** khem` <khem`!~khem@unaffiliated/khem> has quit IRC15:26
*** khem` <khem`!~khem@unaffiliated/khem> has joined #yocto15:27
*** likewise <likewise!~likewise@178-85-26-82.dynamic.upc.nl> has quit IRC15:27
*** Crofton <Crofton!~balister@> has joined #yocto15:27
*** cference <cference!~cference@> has joined #yocto15:28
*** Jefro <Jefro!~jefro@50-0-152-82.dedicated.static.sonic.net> has joined #yocto15:28
*** belen <belen!Adium@nat/intel/x-cqgzafhbjjipfvjd> has quit IRC15:30
*** fredcadete <fredcadete!d4a63893@gateway/web/freenode/ip.> has quit IRC15:35
*** gunnarx <gunnarx!~gan@c-5eeaaab7-74736162.cust.telenor.se> has quit IRC15:35
*** gunnarx <gunnarx!~gan@c-5eeaaab7-74736162.cust.telenor.se> has joined #yocto15:36
*** belen <belen!Adium@nat/intel/x-hwbgeenzaphaigzg> has joined #yocto15:36
*** raykinsella78 <raykinsella78!rkinsell@nat/intel/x-hnjeetpcglcyshqi> has left #yocto15:38
*** belen <belen!Adium@nat/intel/x-hwbgeenzaphaigzg> has quit IRC15:42
*** likewise <likewise!~likewise@178-85-26-82.dynamic.upc.nl> has joined #yocto15:43
*** sameo_ <sameo_!~samuel@> has joined #yocto15:45
*** staylor <staylor!~staylor@mail.au-zone.com> has joined #yocto15:51
staylorIs there a way to better manage the SDK installer generated by -c populate_sdk?  Specifically we need to ship that out to various developers and it would be nice if the contents could be broken down so we can have packages for the various pieces.15:52
ntl0x4, kergoth: -fuse-ld was added in gcc 4.8, so yeah, a 4.5-based toolchain won't know it15:52
*** ka6sox-farfarawa is now known as zz_ka6sox-farfar15:54
*** gunnarx <gunnarx!~gan@c-5eeaaab7-74736162.cust.telenor.se> has quit IRC16:01
*** likewise <likewise!~likewise@178-85-26-82.dynamic.upc.nl> has quit IRC16:02
*** sameo_ <sameo_!~samuel@> has quit IRC16:05
*** zecke <zecke!~ich@ip5b41fb99.dynamic.kabel-deutschland.de> has quit IRC16:07
frayI'm running a command (. ./oe-init-env bitbake -e | grep ...) and when it returns my console is all messed up16:14
frayis there a way to get bitbake stop stop screwing with the console?16:14
frayI just need the value of a specific variable so I can do some setup16:14
*** nerdboy <nerdboy!~sarnold@gentoo/developer/nerdboy> has quit IRC16:16
fray(it's odd, I can't always replicate the failure mode with the console either.. :P16:17
kergothRP: can you explain why the fetcher removes the entire clone when an update of it fails? I have a commit changing this, but figured I'd run it by you to see what the purpose behind that behavior was. was it to deal with repository corruption? if it's a transitory network failure, ir eally don't want to have to re-clone my entire kernel repo16:17
kergothfray: heh, yeah, seem slike bitbake -e is pretty useless when piped nowadays. not sure when that changed16:17
fraykergoth, I thought it was due to non-fast forward git trees16:18
frayok.. good so it's NOT just me..16:18
kergothgit can fetch non-fast-forward branches just fine..16:18
kergothit's the repo in DL_DIR i'm talking about, not the clone in WORKDIR16:18
kergoththe latter would be more of a factor, since it has checkouts of the branches16:18
frayis there a simple way to get a variable out of bitbake then (better then bitbake -e | grep ...?)  (I need the value of bblayers16:19
*** nerdboy <nerdboy!~sarnold@gatekeeper.gentoogeek.org> has joined #yocto16:19
*** nerdboy <nerdboy!~sarnold@gentoo/developer/nerdboy> has joined #yocto16:19
kergothbb would work for now, as a workaround. https://github.com/kergoth/bb - bb show BBLAYERS16:20
* kergoth hasn't touched bb in ages, but still uses it from time to time16:21
RPkergoth: I think it was just being paranoid16:22
* nerdboy wakes up with buddy guy and a stray kitty...16:22
frayso bb-show is actually using bitbake itself/16:22
kergothfray: it uses tinfoil and other bitbake modules, yes16:22
*** picolcd <picolcd!~synapt@p5B1255FE.dip0.t-ipconnect.de> has joined #yocto16:23
frayI wish I could figure out what is triggering the console going nuts.. sometimes it does, sometimes it doesn't..16:25
bluelightningfray: any idea when it started doing that?16:26
fraysometime between 1.7 and master.... (it definitely did NOT go it in 1.7.. I didn't use 1.8 enough to notice.. and it's been doing it for some time in 1.9...16:27
kergothRP: I'm wondering about the case where we already have a git mirror tarball, e.g. from the original fetch, the repo was successfully updated in the past, but there's a transitory network failure causing the update to fail, then try_mirrors() is run on MIRRORS, which runs try_mirror_uri, which eventually re-runs the origud.download() again, but in this case both the tarball and the clone exist, so that second call of the original fetcher download method16:27
kergoth won't actually do the expected unpack of the mirror tarball, it'll try again to update the clone, and it could keep doing this through all the applicable MIRRORS16:27
frayI THOUGHT it went away, but it came back.. and like I said, I'm not getting consistent 'corruption'16:27
kergothRP: unless I'm missing something, this is a theoretical case in my head from reading the code16:27
frayI have to do a 'reset' to get it back..  (basically it hides the cursor and never restores it)16:27
* nerdboy enjoys occasionally harassing the uni IT people on the SIG-UCCS mailing list...16:27
frayblind typing sucks.. ;)16:28
kergothRP: although, previously the clone would have been cleaned, then the first mirror would have re-unpacked the tarball, and then it would have tried to update the newly unpacked clone and failed, anyway, so i guess it's no worse16:28
* kergoth scratches head16:28
RPfray: it sounds like there is an uncaught exception path in knotty16:28
fraythats what i was wondering if somehow it's dropping out without resetting the cursor mode(s)16:28
RPkergoth: I think I've looked at this before and decided not to worry too much about it. I agree it could do with being improved16:28
frayany suggestions on what I can do to try to nail it down?16:28
RPfray: try and spot the pattern to start with?16:29
fray(it wouldn't surprise me at all if it was an artifact of bitbake -e and something failing to expand)16:29
*** tsramos_ <tsramos_!~tsramos@> has joined #yocto16:29
frayRP, I rarely have it happen with a poky checkout..16:29
frayI almost always have it happen with a complex set of layers16:29
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has joined #yocto16:29
kergothRP: Long term, I'd like to see the case where the mirror fetcher is different than the main fetcher be handled more explicitly, rather than re-running the origud.download(). e.g. have a new method for it, or at least pass the mirror ud into the download method so we can tell in what case we're being called16:29
* nerdboy would tie a string to kergoth and send him down the rabbit-hole...16:30
* kergoth ponders16:30
RPkergoth: that would seem reasonable16:30
kergothRP: these crazy possible cases are hurting my head, we need more fetch unit tests :)16:30
RPfray: I wonder why that would be? Unless its extra parse time which opens up some kind of window16:31
frayit's odd if I run it from the command line it works.. but if I run it from a script it's not.. (still trying for a more reliable reproducer)16:31
RPkergoth: this is why I started them last time...16:31
nerdboywait, i thought you were immune to that stuff...16:31
*** tsramos <tsramos!~tsramos@> has quit IRC16:31
* kergoth nods16:31
RPnerdboy: have you looked at the fetcher code? ;-)16:31
nerdboyyeah, but then i sat back down and forgot about it16:31
kergothevery time i touch this code i cringe worrying that i might have broken some corner case i didnt' think about16:32
RPnerdboy: probably good from the nightmare perspective ;-)16:32
RPkergoth: I know the feeling16:32
nerdboyit was probably at least a year ago...16:32
RPkergoth: I dread patches on the list for it too16:32
nerdboyare we okay with python3 constructs?16:33
picolcdHi all, I am get some weird error messages, when my bitbake build fails:  "log_check: Matched keyword: [E:] ERROR: E: //; p }', as for example on libexpat-dev when running bitbake for the meta-raspberrypi. Does anyone have a clue? Thanks.16:33
nerdboyor does it need to conform with 2.716:33
* kergoth is working on simplifying and splitting up the git shallow mirror tarball support to try to make it less painful to pull in16:33
kergothnerdboy: the latter, we're not ready to move to 3 yet16:34
nerdboytoo bad, could use that kind of refactoring...16:34
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has quit IRC16:34
nerdboy3.4 is stable now i think?16:34
bluelightningpicolcd: hmm, that looks ugly :(16:34
nerdboywhatever that means on gentoo...16:35
kergothnerdboy: i think it's mainly the unicode bits that are holding us up, i don't think anyone has even started on that16:35
* nerdboy is not yet thinking in python316:35
bluelightningpicolcd: log_check only runs when building an image though - so is it the image that's failing to build?16:35
nerdboykergoth: don't suppose anyone is jumping up and down to hack at it?16:36
kergoththere has been some work on it already, moving to more portable constructs and whatnot16:36
kergothi did some ages ago, and others more recently16:36
kergothbut there's still work to be done16:36
nerdboyis that in a branch somewhere?16:36
picolcdthat is correct, actually it always fails on do_rootfs16:36
kergothnerdboy: thus far all the work being done works in both 2 and 3, so hasn't needed a long lived branch16:37
kergothafaik anyway16:37
picolcdbluelightning: that is correct, actually it always fails on do_rootfs16:37
-YoctoAutoBuilder- build #452 of nightly-intel-gpl is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-intel-gpl/builds/45216:38
bluelightningpicolcd: ok, can you pastebin your log.do_rootfs ?16:38
kergothRP: https://github.com/openembedded/bitbake/commit/76d57e1 is one that worries me a little. It *seems* like it should work fine, but I worry I'm missing something16:39
kergothhttps://github.com/kergoth/bitbake/commit/76d57e1 rather16:39
RPkergoth: I agree it should in principle but I know what you mean...16:41
*** jbrianceau is now known as jbrianceau_away16:41
*** tsramos_ <tsramos_!~tsramos@> has quit IRC16:43
*** tsramos <tsramos!tsramos@nat/intel/x-jqpxsekxskznpokc> has joined #yocto16:43
*** roccof <roccof!~rocco@93-51-177-218.ip268.fastwebnet.it> has quit IRC16:44
*** jonathanmaw <jonathanmaw!~jonathanm@82-70-136-246.dsl.in-addr.zen.co.uk> has quit IRC16:44
*** sjolley <sjolley!sjolley@nat/intel/x-zegdkyctfkmbqika> has quit IRC16:45
*** diego_r <diego_r!~diego@host65-246-static.10-188-b.business.telecomitalia.it> has quit IRC16:48
picolcdbluelightning:  http://pastebin.com/wThud9Ti ... had to trim it a little, please tell me if you need more.16:49
*** TobSnyder <TobSnyder!~schneider@ip923450f2.dynamic.kabel-deutschland.de> has quit IRC16:49
bluelightningpicolcd: it looks like set -x is on, which is rather ugly...16:54
*** Aethenelle <Aethenelle!~Aethenell@> has joined #yocto16:57
picolcdbluelightning: do you think that it would help if I do "set +x" before running bitbake again?17:00
*** AndersD <AndersD!~anders@h-198-190.a137.corp.bahnhof.se> has joined #yocto17:05
*** ftonello <ftonello!~quassel@> has quit IRC17:07
kergothHas anyone looked into adding a general 'if this package is in the sdk, then add these other specific packages to it' logic to populate_sdk? Somewhat similar to complementary packages, but a one-off with specific package names, not extending with a suffix. I think that's what we need for qt5 to be handled cleanly, but not sure if anyone has started on adding that to the core classes or if they're just punting and using separate sdk recipes or manual17:10
fraywe've always setup dynamic packagegroup packages based on whatever logic is reasonable..17:12
fraythen included them..17:12
fraybut we've avoided trying to look at what packages are 'installed'17:12
kergothHmm, fair enough17:12
fraybut doing a post-process "install more based on what we did" isn't that hard.. preprocess is nearly impossible to get right17:12
fraywe've also done this with the RRECOMMENDS and enabling/disabling them in variable installs..17:13
*** ant_work <ant_work!~ant__@host222-188-static.61-79-b.business.telecomitalia.it> has quit IRC17:36
*** dfaught <dfaught!~dfaught@cpe-70-119-105-90.tx.res.rr.com> has joined #yocto17:38
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC17:41
*** belen1 <belen1!~Adium@> has joined #yocto17:47
*** armpit <armpit!~akuster@2601:202:4000:1239:596f:bbca:6faf:af6> has quit IRC17:58
*** picolcd <picolcd!~synapt@p5B1255FE.dip0.t-ipconnect.de> has quit IRC18:00
kergothokay, cleaned up and split -- https://github.com/kergoth/bitbake/compare/master...kergoth:fetch-bugfixes and https://github.com/kergoth/bitbake/compare/fetch-bugfixes...kergoth:simplified-shallow-git .. will re-submit as PATCH & RFC, respectively, later today18:00
*** likewise <likewise!~likewise@178-85-26-82.dynamic.upc.nl> has joined #yocto18:03
*** likewise <likewise!~likewise@178-85-26-82.dynamic.upc.nl> has quit IRC18:07
*** hitlin37 <hitlin37!uid16371@gateway/web/irccloud.com/x-zafbyhtqxuchkbmh> has quit IRC18:15
*** deception <deception!~deception@unaffiliated/deception> has quit IRC18:15
*** AndersD <AndersD!~anders@h-198-190.a137.corp.bahnhof.se> has quit IRC18:17
*** deception <deception!~deception@unaffiliated/deception> has joined #yocto18:18
*** hitlin37 <hitlin37!uid16371@gateway/web/irccloud.com/x-cknyklqhshaourhe> has joined #yocto18:19
*** paulg <paulg!~paulg@> has joined #yocto18:24
*** dfaught <dfaught!~dfaught@cpe-70-119-105-90.tx.res.rr.com> has quit IRC18:25
*** likewise <likewise!~likewise@178-85-26-82.dynamic.upc.nl> has joined #yocto18:26
*** jimBaxter__ <jimBaxter__!~jbaxter@jimbax.plus.com> has joined #yocto18:31
*** jimBaxter__ <jimBaxter__!~jbaxter@jimbax.plus.com> has quit IRC18:31
*** hitlin37 <hitlin37!uid16371@gateway/web/irccloud.com/x-cknyklqhshaourhe> has quit IRC18:32
*** likewise <likewise!~likewise@178-85-26-82.dynamic.upc.nl> has quit IRC18:33
*** zz_ka6sox-farfar is now known as ka6sox18:35
*** sjolley <sjolley!sjolley@nat/intel/x-wyualzcjncpqsayk> has joined #yocto18:46
*** jbrianceau_away <jbrianceau_away!uid10952@gateway/web/irccloud.com/x-mfgjybcfjoimlevz> has quit IRC18:56
*** sno <sno!~sno@p578b540c.dip0.t-ipconnect.de> has quit IRC19:05
*** [Sno] <[Sno]!~sno@p578b540c.dip0.t-ipconnect.de> has joined #yocto19:07
*** berton <berton!~fabio@> has joined #yocto19:07
*** [Sno] <[Sno]!~sno@p578b540c.dip0.t-ipconnect.de> has quit IRC19:16
*** [Sno] <[Sno]!~sno@p578b540c.dip0.t-ipconnect.de> has joined #yocto19:19
ljoseHi trying to install python pip, installed a bunch of python packages, but is failing because plistlib is not found, any ideas if there is a package for this?19:19
*** grma <grma!~gruberm@HSI-KBW-46-237-193-133.hsi.kabel-badenwuerttemberg.de> has quit IRC19:20
*** belen1 <belen1!~Adium@> has quit IRC19:21
topikjust throw in python-modules19:23
*** dreyna4529 <dreyna4529!~dreyna@unknown-216-200.windriver.com> has joined #yocto19:23
topikoff the bat i would guess it's included in the python-setuptools (if i remember the packagename coreectly)19:24
fmeerkoetteri'd like to create an SDK for a qt5 based image. i don't want to build the meta-qt5-toolchain target but rather go the populate_sdk route so my SDK contains all things i need  based on what i already have in the image.  the problem is that the resulting SDK can't be used for qt5 development19:25
fmeerkoetteri was told that my image should contain this line: "inherit core-image populate_sdk_qt5"19:25
fmeerkoetterwhen i now do a "bitbake myimage -c populate_sdk" i get an SDK that is missing important bits and pieces19:26
fmeerkoetterlike the mkspecs or qt.conf19:26
*** [Sno] <[Sno]!~sno@p578b540c.dip0.t-ipconnect.de> has quit IRC19:27
fmeerkoetterkergoth: we chatted about that topic a while ago. based on that i've added TOOLCHAIN_HOST_TASK_append = " nativesdk-packagegroup-qt5-toolchain-host" to my local.conf19:27
fmeerkoetterwith some limited success19:28
fmeerkoetternow i have at least qmake and friends in my sdk19:28
fmeerkoetterbut none of the mkspecs19:28
*** [Sno] <[Sno]!~sno@p578b540c.dip0.t-ipconnect.de> has joined #yocto19:28
kergothpretty sure the example i gave you included the specs.19:30
* kergoth shrugs19:30
*** sjolley <sjolley!sjolley@nat/intel/x-wyualzcjncpqsayk> has quit IRC19:30
fmeerkoetterkergoth: you are right19:39
*** bluelightning <bluelightning!~paul@> has joined #yocto19:40
*** bluelightning <bluelightning!~paul@> has quit IRC19:40
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto19:40
fmeerkoetterkergoth: but the names weren't exect matches. for the tools i managed to find the right name19:40
fmeerkoetterbut for the mkspecs i am not sure19:41
fmeerkoetteri have to re-test19:41
fmeerkoetterkergoth: can I add packagegroup-qt5-toolchain-target to my  TOOLCHAIN_HOST_TASK_append (in addition to nativesdk-packagegroup-qt5-toolchain-host)? it contains a dependency to qtbase-mkspecs19:44
seebsRP: That does look like a bug that would typically be pseudo-related, except that it's also the sort of bug pseudo has been (historically) pretty good at avoiding. Were you using the xattrdb feature?19:44
kergothfmeerkoetter: no, that wouldn't make much sense. target and host are completely different. host is stuff that runs on your machine, target ist arget. the sdk has two sysroots, they're indpenedent, with independent package install lists (TOOLCHAIN_HOST_TASK, TOOLCHAIN_TARGET_TASK), you can't install one in the other19:48
fmeerkoetterkergoth: should that approach of having an image inherit from populate_sdk_qt5 work?19:49
kergothno idea, not familiar with populate_sdk_qt5. presumably it's supposed to handle this for ou19:50
fmeerkoetteryeah. it also does  TOOLCHAIN_HOST_TASK_append = " nativesdk-packagegroup-qt5-toolchain-host"19:50
*** Crofton <Crofton!~balister@> has quit IRC20:01
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC20:04
*** ant_home <ant_home!~ant__@host167-191-dynamic.52-82-r.retail.telecomitalia.it> has joined #yocto20:06
*** pohly1 <pohly1!~pohly@p57A57DEF.dip0.t-ipconnect.de> has quit IRC20:13
*** pohly <pohly!~pohly@p57A57DEF.dip0.t-ipconnect.de> has joined #yocto20:13
*** pohly <pohly!~pohly@p57A57DEF.dip0.t-ipconnect.de> has quit IRC20:18
*** belen1 <belen1!~Adium@> has joined #yocto20:18
*** belen1 <belen1!~Adium@> has quit IRC20:21
*** bluelightning <bluelightning!~paul@2001:8b0:258:7d7a:2ad2:44ff:fe40:9209> has joined #yocto20:25
*** bluelightning <bluelightning!~paul@2001:8b0:258:7d7a:2ad2:44ff:fe40:9209> has quit IRC20:25
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto20:25
*** lamego <lamego!lamego@nat/intel/x-uomrifqauzlivbwy> has quit IRC20:27
*** lamego <lamego!lamego@nat/intel/x-qmimbglsztevbvee> has joined #yocto20:27
RPseebs: no, we wouldn't be using that20:28
seebsOkay. In that case, I can't immediately think of anything that ought to be able to cause that. If you can get a reproducer, or point me at a failed build, I can have a look?20:29
RPseebs: well, we backed out the pseudo change and those kinds of failures stopped happening20:30
RPseebs: so I'm pretty sure it is pseudo. Have you run builds where its built an rpm package feed and constructed a rootfs from it?20:30
ljosetopik: I add python-modules but still get the same failure no module name plistlib20:31
kergothplistlib sounds like something mac-specific, or a third party module20:31
*** jmpdelos <jmpdelos!~polk@delos.delosent.com> has quit IRC20:32
ljoseI don't think so as install pip requires it20:33
*** jmpdelos <jmpdelos!~polk@delos.delosent.com> has joined #yocto20:33
ljose*** lamego (lamego@nat/intel/x-qmimbglsztevbvee) has joined channel #yocto20:35
ljose<RP> seebs: no, we wouldn't be using that  [22:28]20:35
ljose<seebs> Okay. In that case, I can't immediately think of anything that ought20:35
ljose        to be able to cause that. If you can get a reproducer, or point me at20:35
ljose        a failed build, I can have a look?  [22:29]20:35
ljose<RP> seebs: well, we backed out the pseudo change and those kinds of failures20:35
ljose     stopped happening  [22:30]20:35
ljose<RP> seebs: so I'm pretty sure it is pseudo. Have you run builds where its20:35
ljose     built an rpm package feed and constructed a rootfs from it?20:35
ljose<ljose> topik: I add python-modules but still get the same failure no module20:35
*** challinan <challinan!~chris@173-10-226-189-BusName-WestFlorida.hfc.comcastbusiness.net> has quit IRC20:35
ljose        name plistlib  [22:31]20:35
ljose<kergoth> plistlib sounds like something mac-specific, or a third party module20:35
ljose*** jmpdelos (~polk@delos.delosent.com) has quit: Quit: Leaving  [22:32]20:35
ljose<ljose> I don't think so as install pip requires it  [22:33]20:35
ljose*** jmpdelos (~polk@delos.delosent.com) has joined channel #yocto20:35
ljoseERC> Changed in version 2.6: This module was previously only available in the Mac-specific library, it is now available for all platforms.20:35
*** Crofton <Crofton!~balister@> has joined #yocto20:42
*** anselmolsm <anselmolsm!~anselmols@> has quit IRC20:46
*** berton <berton!~fabio@> has quit IRC20:46
*** anselmolsm <anselmolsm!~anselmols@> has joined #yocto20:47
*** sjolley <sjolley!sjolley@nat/intel/x-qncymduhfqaglvzt> has joined #yocto20:48
seebsI believe that's how the build I did worked, but I may have missed some step.20:48
ljoseast module seems is also missing https://docs.python.org/2/library/ast.html20:50
*** anselmolsm_ <anselmolsm_!~anselmols@> has joined #yocto20:58
*** anselmolsm <anselmolsm!~anselmols@> has quit IRC20:58
*** phantoxeD <phantoxeD!destroy@a89-152-21-144.cpe.netcabo.pt> has joined #yocto21:03
RPhalstead: have you touched the SendErrorReport part of the autobuilder at all?21:05
RPhalstead: anything that might have resulted in https://autobuilder.yoctoproject.org/main/builders/poky-tiny/builds/470 ?21:06
*** cference <cference!~cference@> has quit IRC21:06
halsteadRP, No but I have been troubleshooting the yocto-builds list not receiving e-mail.21:06
halsteadRP, No code changes on my part. Could this be related?21:07
*** phantoneD <phantoneD!destroy@a89-152-21-144.cpe.netcabo.pt> has quit IRC21:07
RPhalstead: not sure what is going on right now. Its unlikely I guess21:08
RPhalstead: I did merge  a couple of emergency fixes into the autobuilder code but I didn't touch this area :/21:08
RPhalstead: (top two commits of yocto-autobuilder master)21:08
halsteadRP, What I'm fixing stopped working in July. :(21:09
RPhalstead: we appear to have multiple issues :(21:09
RPhalstead: just wanted to check it wasn't something related to what you were looking at, thanks21:09
RPhalstead: will try a master build and see where we are21:10
ljoseLooking at my python2.7 build I see tmp/sysroots/beaglebone/usr/lib/python2.7/plistlib.py and tmp/sysroots/beaglebone/usr/lib/python2.7/ast.py but those files are not being installed by python-modules21:10
ljosecould this be a problem with python recipe?21:10
halsteadRP, Thank you. I'll message if I think any changes will help.21:10
*** jimBaxter <jimBaxter!~jbaxter@jimbax.plus.com> has quit IRC21:15
*** JaMa <JaMa!~martin@ip-86-49-34-37.net.upcbroadband.cz> has quit IRC21:22
*** ka6sox is now known as zz_ka6sox21:28
*** zz_ka6sox is now known as Guest2169821:29
*** Crofton <Crofton!~balister@> has quit IRC21:33
ljoseSo any ideas on getting the other modules installed, should I look into patch python2.7-manifest?21:37
*** paulg <paulg!~paulg@> has quit IRC21:38
*** darknighte <darknighte!~darknight@pdpc/supporter/professional/darknighte> has joined #yocto21:41
*** Aethenelle <Aethenelle!~Aethenell@> has quit IRC21:41
*** darknighte <darknighte!~darknight@pdpc/supporter/professional/darknighte> has quit IRC21:42
*** ftonello <ftonello!~quassel@82-71-26-47.dsl.in-addr.zen.co.uk> has joined #yocto21:44
*** darknighte <darknighte!~darknight@pdpc/supporter/professional/darknighte> has joined #yocto21:44
*** pepone <pepone!~user@> has joined #yocto21:45
*** tsramos_ <tsramos_!~tsramos@> has joined #yocto21:48
*** tsramos <tsramos!tsramos@nat/intel/x-jqpxsekxskznpokc> has quit IRC21:50
*** tsramos_ <tsramos_!~tsramos@> has quit IRC21:52
*** ant_home <ant_home!~ant__@host167-191-dynamic.52-82-r.retail.telecomitalia.it> has quit IRC21:58
*** bfederau <bfederau!~quassel@service.basyskom.com> has quit IRC22:01
*** fmeerkoetter <fmeerkoetter!~quassel@service.basyskom.com> has quit IRC22:01
*** bfederau <bfederau!~quassel@service.basyskom.com> has joined #yocto22:01
*** fmeerkoetter <fmeerkoetter!~quassel@service.basyskom.com> has joined #yocto22:01
*** anselmolsm_ <anselmolsm_!~anselmols@> has quit IRC22:03
*** phantoneD <phantoneD!destroy@a89-152-21-144.cpe.netcabo.pt> has joined #yocto22:03
*** rburton <rburton!~Adium@> has quit IRC22:04
*** phantoxeD <phantoxeD!destroy@a89-152-21-144.cpe.netcabo.pt> has quit IRC22:07
*** phantoneD <phantoneD!destroy@a89-152-21-144.cpe.netcabo.pt> has quit IRC22:07
*** Cardoe <Cardoe!~Cardoe@gentoo/developer/Cardoe> has quit IRC22:16
*** pepone <pepone!~user@> has quit IRC22:17
*** paulg <paulg!~paulg@71-19-175-186.dedicated.allstream.net> has joined #yocto22:17
*** MiskaX <MiskaX!~jussi@rankki.sonarnerd.net> has quit IRC22:18
*** YoctoAutoBuilder <YoctoAutoBuilder!~YoctoAuto@yocto-www.yoctoproject.org> has quit IRC22:19
*** YoctoAutoBuilder <YoctoAutoBuilder!~YoctoAuto@yocto-www.yoctoproject.org> has joined #yocto22:19
*** lamego <lamego!lamego@nat/intel/x-qmimbglsztevbvee> has quit IRC22:37
*** MiskaX <MiskaX!~jussi@rankki.sonarnerd.net> has joined #yocto22:38
*** alimon <alimon!~alimon@> has quit IRC22:38
*** Aethenelle <Aethenelle!~Aethenell@> has joined #yocto22:55
*** aehs29 <aehs29!aehernan@nat/intel/x-wnydlalgvnxbvxnx> has quit IRC23:00
*** aehs29 <aehs29!aehernan@nat/intel/x-vxjqhycxxvgirbab> has joined #yocto23:02
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC23:20
*** sjolley <sjolley!sjolley@nat/intel/x-qncymduhfqaglvzt> has quit IRC23:23
*** nighty^ <nighty^!~nighty@hokuriku.rural-networks.com> has quit IRC23:23
*** Aethenelle <Aethenelle!~Aethenell@> has quit IRC23:25
*** aehs29 <aehs29!aehernan@nat/intel/x-vxjqhycxxvgirbab> has left #yocto23:31
*** khem` <khem`!~khem@unaffiliated/khem> has quit IRC23:31
*** ftonello <ftonello!~quassel@82-71-26-47.dsl.in-addr.zen.co.uk> has quit IRC23:33
*** phantoxeD <phantoxeD!destroy@a89-152-21-144.cpe.netcabo.pt> has joined #yocto23:35
*** slips <slips!~slips@> has quit IRC23:50
aj_cim getting to add  a group into the a proyect, but im getting a awful error "ERROR: useradd not found in the base feeds (qemux86 i586 x86 noarch any all).23:50
aj_cacl-2.2.52-r0@" using as template /meta-skeleton/recipes-skeleton/useradd/useradd-example.bb23:50
aj_cif i used the full template it works fine but, as soon y remove useraddPARAM and do_install it sent that error23:51
aj_ci just want to create some new groups for other time use23:52
*** staylor <staylor!~staylor@mail.au-zone.com> has quit IRC23:53
*** slips <slips!~slips@> has joined #yocto23:54

Generated by irclog2html.py 2.11.0 by Marius Gedminas - find it at mg.pov.lt!