Tuesday, 2013-07-30

*** mulhern <mulhern!~mulhern@c-24-128-153-12.hsd1.ma.comcast.net> has quit IRC00:00
*** smartin <smartin!~smartin@20-87-190-109.dsl.ovh.fr> has quit IRC00:04
*** smartin <smartin!~smartin@20-87-190-109.dsl.ovh.fr> has joined #yocto00:08
*** mulhern <mulhern!~mulhern@c-24-128-153-12.hsd1.ma.comcast.net> has joined #yocto00:20
*** lpapp <lpapp!~lpapp@kde/lpapp> has quit IRC00:20
*** Jefro <Jefro!~jefro@50-0-152-82.dedicated.static.sonic.net> has joined #yocto00:24
*** lpapp <lpapp!~lpapp@kde/lpapp> has joined #yocto00:35
*** Rootert <Rootert!~Rootert@54694E34.cm-12-2b.dynamic.ziggo.nl> has quit IRC00:37
*** RagBal <RagBal!~RagBal@54694E34.cm-12-2b.dynamic.ziggo.nl> has quit IRC00:38
*** arky <arky!~arky@113.22.49.207> has quit IRC00:39
*** seebs <seebs!~seebs@home.seebs.net> has joined #yocto00:41
*** Rootert <Rootert!~Rootert@54694E34.cm-12-2b.dynamic.ziggo.nl> has joined #yocto00:42
*** RagBal <RagBal!~RagBal@54694E34.cm-12-2b.dynamic.ziggo.nl> has joined #yocto00:43
*** _julian_ <_julian_!~quassel@x2f14bd1.dyn.telefonica.de> has joined #yocto00:51
*** Jefro <Jefro!~jefro@50-0-152-82.dedicated.static.sonic.net> has quit IRC00:52
*** davest <davest!Adium@nat/intel/x-qtgwgvziozdoiddj> has quit IRC00:53
*** _julian <_julian!~quassel@x2f00932.dyn.telefonica.de> has quit IRC00:55
*** sameo <sameo!~samuel@192.55.54.40> has quit IRC00:59
*** munch <munch!~mark@c-67-184-166-69.hsd1.il.comcast.net> has quit IRC01:01
*** phdeswer_ <phdeswer_!~phdeswer@a88-113-104-180.elisa-laajakaista.fi> has quit IRC01:19
*** rogerzhou <rogerzhou!~rogerzhou@1.202.252.122> has joined #yocto01:25
*** joeythesaint <joeythesaint!~jjm@198-84-238-35.cpe.teksavvy.com> has quit IRC01:43
*** mulhern <mulhern!~mulhern@c-24-128-153-12.hsd1.ma.comcast.net> has quit IRC01:44
*** jchonig <jchonig!~jch@24.114.85.61> has quit IRC01:45
*** mitz <mitz!~mitz@KHP222227247006.ppp-bb.dion.ne.jp> has quit IRC02:04
*** mitz <mitz!~mitz@KHP222227247006.ppp-bb.dion.ne.jp> has joined #yocto02:07
*** silviof1 <silviof1!~silviof@ppp-93-104-14-226.dynamic.mnet-online.de> has joined #yocto02:07
*** silviof <silviof!~silviof@host-188-174-208-204.customer.m-online.net> has quit IRC02:10
*** Jefro <Jefro!~jefro@50-0-152-82.dedicated.static.sonic.net> has joined #yocto02:37
*** halfhalo <halfhalo!halfhalo@nasadmin/webteam/halfhalo> has quit IRC02:55
*** lpapp <lpapp!~lpapp@kde/lpapp> has quit IRC02:55
*** halfhalo <halfhalo!halfhalo@nasadmin/webteam/halfhalo> has joined #yocto02:59
*** andyross <andyross!~andy@c-67-171-188-207.hsd1.or.comcast.net> has joined #yocto03:10
*** Jefro <Jefro!~jefro@50-0-152-82.dedicated.static.sonic.net> has joined #yocto04:24
*** Jefro <Jefro!~jefro@50-0-152-82.dedicated.static.sonic.net> has quit IRC04:26
*** lpapp <lpapp!~lpapp@cpc11-cmbg15-2-0-cust30.5-4.cable.virginmedia.com> has joined #yocto04:26
*** lpapp <lpapp!~lpapp@kde/lpapp> has joined #yocto04:26
*** nerdboy <nerdboy!~sarnold@gentoo/developer/nerdboy> has left #yocto04:40
*** nerdboy <nerdboy!~sarnold@gentoo/developer/nerdboy> has joined #yocto04:40
*** Jefro <Jefro!~jefro@50-0-152-82.dedicated.static.sonic.net> has joined #yocto04:41
*** behanw <behanw!~behanw@216-58-123-51.cpe.distributel.net> has quit IRC04:51
*** Jefro <Jefro!~jefro@50-0-152-82.dedicated.static.sonic.net> has quit IRC04:57
*** ericben <ericben!~ebenard@pac33-3-88-170-243-169.fbx.proxad.net> has quit IRC05:04
*** ericben <ericben!~ebenard@pac33-3-88-170-243-169.fbx.proxad.net> has joined #yocto05:06
*** andyross <andyross!~andy@c-67-171-188-207.hsd1.or.comcast.net> has quit IRC05:08
*** Jefro <Jefro!~jefro@50-0-152-82.dedicated.static.sonic.net> has joined #yocto05:12
*** zecke <zecke!~ich@91-65-247-193-dynip.superkabel.de> has joined #yocto05:21
*** mihai <mihai!~mihai@80.97.15.150> has joined #yocto05:23
*** zeeblex <zeeblex!apalalax@nat/intel/x-vzwsmxfqhtfxwcce> has joined #yocto05:25
*** agust <agust!~agust@p4FDE7118.dip0.t-ipconnect.de> has joined #yocto05:46
*** Jefro <Jefro!~jefro@50-0-152-82.dedicated.static.sonic.net> has quit IRC05:49
*** tasslehoff <tasslehoff!~tasslehof@77.40.182.98> has joined #yocto05:51
*** tor <tor!~tor@c-ef66e655.125-1-64736c10.cust.bredbandsbolaget.se> has joined #yocto05:53
*** Jefro <Jefro!~jefro@50-0-152-82.dedicated.static.sonic.net> has joined #yocto06:11
*** B4gder <B4gder!~daniel@sestofw01.enea.se> has joined #yocto06:31
*** silviof1 is now known as silviof06:32
*** smartin <smartin!~smartin@20-87-190-109.dsl.ovh.fr> has quit IRC06:34
*** rogerzhou <rogerzhou!~rogerzhou@1.202.252.122> has quit IRC06:35
*** smartin <smartin!~smartin@20-87-190-109.dsl.ovh.fr> has joined #yocto06:36
*** eballetbo <eballetbo!~eballetbo@43.Red-2-139-180.staticIP.rima-tde.net> has joined #yocto06:57
*** elmi82 <elmi82!~timo@mail.bmw-carit.de> has joined #yocto07:02
*** melonipoika <melonipoika!~quassel@ip050-115.seclan.com> has quit IRC07:10
*** gmacario <gmacario!~gmacario@maxlab.polito.it> has joined #yocto07:10
*** _frank_ <_frank_!~frank@1.202.252.122> has joined #yocto07:12
*** TuTizz <TuTizz!~TuTizz@unaffiliated/tutizz> has quit IRC07:12
*** melonipoika <melonipoika!~quassel@ip050-115.seclan.com> has joined #yocto07:15
*** tbn <tbn!~tbn@mad27-1-88-172-46-29.fbx.proxad.net> has joined #yocto07:22
*** tbn is now known as Guest2685507:23
*** TuTizz <TuTizz!~TuTizz@46.18.96.158> has joined #yocto07:26
*** darknighd <darknighd!~darknight@nat-wv.mentorg.com> has joined #yocto07:26
*** TuTizz <TuTizz!~TuTizz@46.18.96.158> has quit IRC07:26
*** TuTizz <TuTizz!~TuTizz@unaffiliated/tutizz> has joined #yocto07:26
*** darknighd is now known as darknighte07:26
*** darknighte <darknighte!~darknight@pdpc/supporter/professional/darknighte> has joined #yocto07:26
*** darknighte_znc <darknighte_znc!~darknight@pdpc/supporter/professional/darknighte> has quit IRC07:26
*** fgretief <fgretief!~chatzilla@41.0.38.138> has joined #yocto07:35
*** slaine <slaine!~slaine@84.203.137.218> has joined #yocto07:39
*** sveinse <sveinse!~chatzilla@81.166.90.189> has quit IRC07:42
*** calin <calin!86bfdc49@gateway/web/freenode/ip.134.191.220.73> has joined #yocto07:44
*** ant_work <ant_work!~ant@host54-128-static.10-188-b.business.telecomitalia.it> has joined #yocto07:45
*** calin is now known as Guest6277107:45
*** panda84kde <panda84kde!~diego@static-217-133-170-65.clienti.tiscali.it> has joined #yocto07:47
*** Guest62771 <Guest62771!86bfdc49@gateway/web/freenode/ip.134.191.220.73> has quit IRC07:49
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto07:54
dzoeHi, is there any way to set PREFERRED_VERSION_udev in image's .bb file or the only way is to use local.conf (or some other .conf)?07:54
bluelightningmorning all07:57
bluelightningdzoe: no, it has to be at the configuration level07:58
dzoebluelightning: and for example at meta layer configuration level?07:58
bluelightningdzoe: it would typically be in your custom distro configuration07:58
_frank_morning, bluelightning~ In yocto, many places used "d" variable, like "packages = d.getVar('PACKAGES', True)".08:00
_frank_Then, where is "d" defined ? and when is it cleared ?08:00
bluelightning_frank_: indeed08:00
bluelightning_frank_: it's normally passed into most python functions, either implicitly (for python xyz() { }) or explicitly (def funcname(arg1, arg2, d): ...)08:01
bluelightning_frank_: you can find the class declaration for it in bitbake/lib/bb/data_smart.py08:02
_frank_bluelightning: yeah, thanks for help !08:03
*** sameo <sameo!~samuel@192.55.54.40> has joined #yocto08:05
-YoctoAutoBuilder- build #230 of nightly-ppc-lsb is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org:8011/builders/nightly-ppc-lsb/builds/23008:07
dzoeAh, so basically I just add distro policy in meta-mylayer/conf/distro - that's easy.08:10
dzoebluelightning: thank you08:10
*** Jefro <Jefro!~jefro@50-0-152-82.dedicated.static.sonic.net> has quit IRC08:13
*** florian_kc <florian_kc!~fuchs@Maemo/community/contributor/florian> has joined #yocto08:15
*** florian_kc is now known as florian08:17
-YoctoAutoBuilder- build #231 of nightly-mips is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org:8011/builders/nightly-mips/builds/23108:27
*** honschu <honschu!~honschu@p549EBAF1.dip0.t-ipconnect.de> has joined #yocto08:27
*** honschu <honschu!~honschu@shackspace/j4fun> has joined #yocto08:27
-YoctoAutoBuilder- build #242 of nightly-mips-lsb is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org:8011/builders/nightly-mips-lsb/builds/24208:29
*** ChanServ sets mode: +o yocti08:30
*** honschu_ <honschu_!~honschu@shackspace/j4fun> has quit IRC08:31
*** belen <belen!Adium@nat/intel/x-froxmgvcpkdfhfww> has joined #yocto08:41
*** lpapp <lpapp!~lpapp@kde/lpapp> has quit IRC08:43
*** g0hl1n <g0hl1n!5be602f4@gateway/web/freenode/ip.91.230.2.244> has quit IRC08:46
*** phdeswer_ <phdeswer_!~phdeswer@a88-113-104-180.elisa-laajakaista.fi> has joined #yocto08:46
_frank_What does PACKAGE_INSTALL_ATTEMPTONLY mean ? attemptonly ??08:48
*** JimBaxter <JimBaxter!~jbaxter@jimbax.plus.com> has joined #yocto08:57
*** blitz00 <blitz00!~stefans@unaffiliated/blitz00> has joined #yocto08:58
*** eren <eren!~eren@unaffiliated/eren> has joined #yocto09:01
*** rogerzhou <rogerzhou!~rogerzhou@1.202.252.122> has joined #yocto09:04
-YoctoAutoBuilder- build #233 of nightly-x86 is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org:8011/builders/nightly-x86/builds/23309:07
erenhi all09:26
erentoday, I guess I will test the first hambedded linux image in ALIX board. I hope I will succeed in getting KISS modem working :)09:27
bluelightning_frank_: it's a mechanism for attempting to install recipes that are not hard requirements where installing them might not always be possible (due to unsatisfied dependencies or conflicts)09:34
bluelightninger, s/recipes/packages/09:34
_frank_bluelightning: Then, RRECOMMENDS_{PN} will be interpreted  to this kind attempting packages ?09:42
bluelightning_frank_: no, that is handled separately by the package manager09:42
-YoctoAutoBuilder- build #228 of nightly-world is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org:8011/builders/nightly-world/builds/22809:42
bluelightning_frank_: although in past versions for RPM I think recommends might have gone into there09:43
*** mckoan|away is now known as mckoan09:44
_frank_bluelightning: I wonder what will result in PACKAGE_INSTALL_ATTEMPTONLY ?09:44
-YoctoAutoBuilder- build #201 of nightly-fsl-arm-lsb is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org:8011/builders/nightly-fsl-arm-lsb/builds/20109:44
mckoangood morning09:45
_frank_As we know, IMAGE_INSTALL + "xxx" will go to PACKAGE_INSTALL09:45
bluelightning_frank_: "git grep PACKAGE_INSTALL_ATTEMPTONLY" is your friend ;)09:46
-YoctoAutoBuilder- build #227 of nightly-x86-64 is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org:8011/builders/nightly-x86-64/builds/22709:47
*** Corneliu <Corneliu!c0c69724@gateway/web/freenode/ip.192.198.151.36> has joined #yocto09:47
_frank_bluelightning: Thanks!09:51
*** rburton <rburton!~rburton@35.106.2.81.in-addr.arpa> has joined #yocto09:58
*** melonipoika <melonipoika!~quassel@ip050-115.seclan.com> has quit IRC10:17
*** lpapp <lpapp!~lpapp@kde/lpapp> has joined #yocto10:17
*** melonipoika <melonipoika!~quassel@ip050-115.seclan.com> has joined #yocto10:38
*** rogerzhou <rogerzhou!~rogerzhou@1.202.252.122> has quit IRC10:44
*** swex__ <swex__!~swex@217.197.245.213> has joined #yocto11:04
*** JaMa|Off <JaMa|Off!~martin@ip-62-24-80-145.net.upcbroadband.cz> has quit IRC11:04
*** joseppc <joseppc!~Josep@sestofw01.enea.se> has joined #yocto11:05
*** JaMa|Off <JaMa|Off!~martin@ip-62-24-80-145.net.upcbroadband.cz> has joined #yocto11:06
*** swex_ <swex_!~swex@178.17.193.168> has quit IRC11:07
-YoctoAutoBuilder- build #233 of nightly-arm-lsb is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org:8011/builders/nightly-arm-lsb/builds/23311:10
-YoctoAutoBuilder- build #233 of nightly-x86-lsb is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org:8011/builders/nightly-x86-lsb/builds/23311:15
-YoctoAutoBuilder- build #229 of nightly-arm is complete: Failure [failed Running Sanity Tests Building Images_1 Building Toolchain Images Building Toolchain Images_1 Publishing Artifacts] Build details are at http://autobuilder.yoctoproject.org:8011/builders/nightly-arm/builds/22911:31
*** slaine <slaine!~slaine@84.203.137.218> has quit IRC11:35
*** mulhern <mulhern!~mulhern@c-24-128-153-12.hsd1.ma.comcast.net> has joined #yocto11:35
*** joeythesaint <joeythesaint!~jjm@128.224.252.2> has joined #yocto11:55
*** ScriptRipper <ScriptRipper!~ScriptRip@opensuse/member/MartinMohring> has joined #yocto11:55
*** tasslehoff <tasslehoff!~tasslehof@77.40.182.98> has quit IRC12:04
*** behanw <behanw!~behanw@216-58-123-51.cpe.distributel.net> has joined #yocto12:16
*** walters <walters!~walters@c-66-31-18-51.hsd1.ma.comcast.net> has joined #yocto12:31
*** jchonig <jchonig!~jch@128.224.252.2> has joined #yocto12:31
*** calin <calin!86bfdd48@gateway/web/freenode/ip.134.191.221.72> has joined #yocto12:49
*** calin is now known as Guest976212:50
*** silviof1 <silviof1!~silviof@ppp-188-174-179-148.dynamic.mnet-online.de> has joined #yocto12:52
*** silviof <silviof!~silviof@ppp-93-104-14-226.dynamic.mnet-online.de> has quit IRC12:55
*** silviof2 <silviof2!~silviof@ppp-188-174-147-50.dynamic.mnet-online.de> has joined #yocto12:57
*** silviof1 <silviof1!~silviof@ppp-188-174-179-148.dynamic.mnet-online.de> has quit IRC12:57
*** silviof3 <silviof3!~silviof@ppp-93-104-168-44.dynamic.mnet-online.de> has joined #yocto13:01
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto13:03
*** silviof2 <silviof2!~silviof@ppp-188-174-147-50.dynamic.mnet-online.de> has quit IRC13:04
*** silviof4 <silviof4!~silviof@ppp-93-104-162-97.dynamic.mnet-online.de> has joined #yocto13:08
*** silviof <silviof!~silviof@ppp-93-104-184-172.dynamic.mnet-online.de> has joined #yocto13:10
*** silviof3 <silviof3!~silviof@ppp-93-104-168-44.dynamic.mnet-online.de> has quit IRC13:10
*** silviof4 <silviof4!~silviof@ppp-93-104-162-97.dynamic.mnet-online.de> has quit IRC13:13
*** Guest9762 <Guest9762!86bfdd48@gateway/web/freenode/ip.134.191.221.72> has quit IRC13:13
*** B4gder <B4gder!~daniel@sestofw01.enea.se> has quit IRC13:13
*** B4gder <B4gder!~daniel@rockbox/developer/bagder> has joined #yocto13:13
*** silviof <silviof!~silviof@ppp-93-104-184-172.dynamic.mnet-online.de> has quit IRC13:14
*** mihai <mihai!~mihai@80.97.15.150> has quit IRC13:16
*** tomz <tomz!~trz@c-68-53-177-94.hsd1.in.comcast.net> has joined #yocto13:18
*** tomz is now known as Guest2577813:18
*** mihai <mihai!~mihai@80.97.15.150> has joined #yocto13:23
*** lpapp <lpapp!~lpapp@kde/lpapp> has quit IRC13:23
*** davest <davest!Adium@nat/intel/x-dfynalpalbvmlore> has joined #yocto13:26
*** sameo <sameo!~samuel@192.55.54.40> has quit IRC13:27
panda84kdehi bluelightning: you can close this one: https://bugzilla.yoctoproject.org/show_bug.cgi?id=443913:27
yoctiBug 4439: normal, Medium, 1.5, kergoth, ACCEPTED , devshell fails to open a new tmux session13:27
*** Garibaldi|work <Garibaldi|work!~andydalt@nat/cisco/x-zifrgcfjvcdrukoz> has joined #yocto13:28
bluelightningpanda84kde: will do13:28
*** silviof <silviof!~silviof@ppp-188-174-129-34.dynamic.mnet-online.de> has joined #yocto13:29
panda84kdebluelightning: thanks for fixing it! :)13:29
bluelightningpanda84kde: thank the patch submitter, I just tried it out :)13:29
panda84kderight...13:30
*** belen2 <belen2!Adium@nat/intel/x-scpqxauxzhikegql> has joined #yocto13:36
*** belen <belen!Adium@nat/intel/x-froxmgvcpkdfhfww> has quit IRC13:37
*** Stygia <Stygia!~gmpsaifi@0904ds6-noe.0.fullrate.dk> has joined #yocto13:42
erenah, I need to try that as well13:46
erenI applied the workaround before13:46
erenlet's see :)13:46
*** ant_work <ant_work!~ant@host54-128-static.10-188-b.business.telecomitalia.it> has quit IRC13:47
erenbluelightning: there is another workaround for it, have you looked at it?13:50
erencml1.bbclass13:50
*** lpapp <lpapp!~lpapp@kde/lpapp> has joined #yocto13:50
erenI am wondering why it was not committed13:50
*** ScriptRipper <ScriptRipper!~ScriptRip@opensuse/member/MartinMohring> has quit IRC13:55
*** Garibaldi|work <Garibaldi|work!~andydalt@nat/cisco/x-zifrgcfjvcdrukoz> has quit IRC13:56
*** Garibaldi|work <Garibaldi|work!~andydalt@nat/cisco/x-jhfndhpvnttoyauy> has joined #yocto13:59
*** ScriptRipper <ScriptRipper!~ScriptRip@opensuse/member/MartinMohring> has joined #yocto13:59
bluelightningeren: I have, but that changes the behaviour for all terminals; this is a tmux-specific problem and should be fixed by the patch I've pointed to14:02
erenoh ok14:03
erenI guess we can close the bug after 2 confirmation14:03
bluelightningeren: did the patch I pointed to work for you?14:03
erenbluelightning: yes14:03
bluelightninggreat :)14:03
erenI guess we will see it included in the next release cycle?14:03
bluelightningyes, I'll add it to paule/dylan-next now for testing14:04
erenokkie14:04
bluelightning(poky-contrib branch that is)14:04
erenbluelightning: is there a problem with git.yoctoproject.org btw?14:05
erenit's really slow for me14:06
bluelightningeren: hmm yes it does seem a bit slow for me too14:06
erenhttp://dpaste.com/1323160/14:07
erenit seems that the bottleneck is level314:07
erenat least for me14:07
erenyeah, definitely there is a problem with level314:09
bluelightningeren: the 100% loss items are a bit of a concern...14:09
erenbluelightning: yeah, the output is from Turkey, our ISP's behind-the-wall filtering/spying device I guess :)14:10
erenI've tried from UK, linode: http://dpaste.com/1323165/14:10
bluelightningeren: that's OK, in recent months we've discovered (to not much surprise) that most countries have pretty intensive "spying" programmes :)14:11
erenyeah :)14:11
bluelightninghalstead: are you aware of any current problems affecting access to git.yoctoproject.org?14:12
erenbluelightning: it seems that it is throttling the bw14:14
*** munch <munch!~mark@67.184.166.69> has joined #yocto14:15
erenI get linux-yocto around 400 - 500 KB/s14:15
erenfrom UK / Linode14:15
erens/get/clone/14:17
*** mulhern <mulhern!~mulhern@c-24-128-153-12.hsd1.ma.comcast.net> has quit IRC14:20
*** mulhern <mulhern!~mulhern@c-24-128-153-12.hsd1.ma.comcast.net> has joined #yocto14:23
lpapphttp://pastebin.com/EgU1s9Vt -> this is another regression in dylan?14:27
*** fitzsim <fitzsim!~user@nat/cisco/x-nqiwhwcjhtvyaazt> has joined #yocto14:27
lpappI did not get such error messages with denzil.14:27
rburtonlpapp: no aware of any fetcher checksum changes, but i'm not paying attention there.  if you name your tarballs you need to use the names in the checksums, like the lines it gave you.14:29
lpappthe meta/recipes-kernel/... does not do that though.14:29
rburtonlinux-yocto uses git so that isn't checksumed14:31
*** Crofton|work <Crofton|work!~balister@pool-108-44-87-78.ronkva.east.verizon.net> has quit IRC14:32
lpappI see. OK, this was not a problem with denzil though.14:32
rburtonmaybe denzil didn't mandate the name, dunno.14:32
lpappsorry?14:33
rburtonmaybe denzil fell back to the non-named checksum14:33
lpappyou mean, it did not mandate the presence of the checksum?14:33
rburtonif you had a tarball you'd need a checksum14:33
lpappas I said, it was not a problem for denzil.14:34
lpappso it is likely a new "intrusive action".14:34
rburtonwell, it's more correct this way14:34
rburtonanyway, easy to fix and naming the checksums is more expressive/accurate when you have multiple files14:35
rburton(if you don't, no need to name them generally)14:35
lpappwell, you usually have patches for the kernel in a bsp layer ...14:36
*** zeeblex <zeeblex!apalalax@nat/intel/x-vzwsmxfqhtfxwcce> has left #yocto14:36
lpappseems the error does not go away if I manually insert those two lines into the kernel recipe.14:37
rburtontrue14:37
rburtonthen something Very Odd is happening, pastebin?14:37
lpappthe same error?14:37
lpappperhaps I should delete the tarball before retry14:38
rburtonno14:39
rburtonpastebin the recipe please14:39
*** Crofton|work <Crofton|work!~balister@pool-108-44-87-78.ronkva.east.verizon.net> has joined #yocto14:39
lpappactually, deleting the tarball helped.14:40
rburtoni can't see any reason for that14:40
rburtonbut i'm not going to argue it! :)14:40
lpappweird, it came up again, just much later.14:42
rburtonit was probably downloading the tarball14:42
rburtonit will do many things in parallel14:42
rburtonpastebin the latest error and your recipe14:42
rburton(with a dep chain of a->b->c, whilst a is still building bitbake will extract and patch b and c)14:43
lpapphttp://pastebin.com/N9Z0pAh314:43
lpappno, it was not.14:43
lpappaccording to bitbake, that went fine ("fetch").14:44
lpappand it was doing some other jobs.14:44
rburtoncan you pastebin the recipe too?14:45
lpapphmm, so kernel.md5sum != tarball.md5sum14:45
lpappsorry, no.14:45
rburtoncorrect14:45
rburtonyour SRC_URI has name=kernel14:46
lpappI do not think it should be this complicated.14:46
rburtonso you need a checksum called kernel.md5sum14:46
lpappit does not matter whether it is the kernel or something else.14:46
rburtonthis is generic bitbake checksumming14:46
lpappthe checksum should be standardized how it is expressed in bitbake.14:46
rburtonit is14:46
lpappmight be generic, but whether it is good.14:46
lpappthat is questionable.14:46
lpapphere is the example at hand.14:46
rburtonSRC_URI[optional-name.md5sum]14:46
rburtonyou may have multiple tarballs, so you need a way to identify them14:47
rburtonthe naming is entirely up to you14:47
lpapptoo much flexibility for no apparent gain.14:47
lpappmost people will not change the order, so that could be the common denominator.14:48
lpapp1: gcc-cross-4.7.2-r20 do_compile (pid 10855)14:48
lpapp???14:48
lpappwhy is it building that?14:49
lpappI explicitly have an external toolchain!14:49
rburtondidn't you have that problem earlier?  some dependency the external toolchain wasn't providing, iirc.14:49
lpappno, I did not.14:50
rburton"bitbake -g -u depexp" should let you see what is pulling it in14:50
rburtonthen you can work out why14:50
*** andyross <andyross!~andy@c-67-171-188-207.hsd1.or.comcast.net> has joined #yocto14:52
lpappWARNING: linux-foo: No generic license file exists for: GPL in any provider14:52
lpappthat seems to be a new change with dylan as well...14:53
lpappnot sure I understand the warning.14:53
rburtonyou need to version "GPL"14:54
rburtonie "GPLv2"14:54
rburtonthere wasn't a "GPL" in denzil either from what I can tell14:55
*** Garibaldi|work <Garibaldi|work!~andydalt@nat/cisco/x-jhfndhpvnttoyauy> has quit IRC14:56
lpappnot sure what that means.14:57
*** B4gder <B4gder!~daniel@rockbox/developer/bagder> has quit IRC14:57
*** Garibaldi|work <Garibaldi|work!~andydalt@nat/cisco/x-bsnfyrjwesfrivtd> has joined #yocto14:57
rburtonusing License="GPL" in denzil was likely to produce a warning, from what i can see14:58
*** BSDCat <BSDCat!unique@calvin.idempot.net> has joined #yocto14:58
rburtonthe kernel is v2, so you need to say GPLv214:58
*** scottrif <scottrif!~scott-len@b482.ip17.netikka.fi> has joined #yocto14:58
rburtonvery important as i'm sure you're aware, you don't want to accidently use any GPLv3 code if that concerns you14:59
*** Song <Song!c037362a@gateway/web/freenode/ip.192.55.54.42> has joined #yocto14:59
*** Song is now known as Song_Liu14:59
scottrifYPTM: Scott Rifenbark is on the call15:00
*** hollisb <hollisb!~hollisb@192.94.38.34> has joined #yocto15:00
lpapphttp://pastebin.com/FkAz7uik -> yet another dylan warning/error?15:00
*** belen2 <belen2!Adium@nat/intel/x-scpqxauxzhikegql> has quit IRC15:00
*** Guest25778 is now known as tomz215:01
Song_LiuYPTM: Welcome to the tech team meeting, please let me know who's on the bridge. Thanks!15:01
tomz2YPTM: Tom Z on15:01
bluelightningYPTM: Paul Eggleton joined15:01
*** jzhang-laptop <jzhang-laptop!~jzhang16@134.134.139.70> has joined #yocto15:01
jzhang-laptopYPTM: jzhang's on the call15:01
*** dvhart <dvhart!~dvhart@static-50-53-108-147.bvtn.or.frontiernet.net> has joined #yocto15:01
frayYPTM: I'm here15:01
dvhartYPTM: Darren is on15:01
rburtonlpapp: does the stock busybox build? might be your recipe using internal functions that got removed.15:02
darknighteYPTM: Song, Sean is here.15:02
* darknighte waves15:02
rburtonYPTM: ross here15:02
nitinkYPTM: Nitin is on the bridge15:02
*** zenlinux <zenlinux!~sgarman@c-50-139-96-211.hsd1.or.comcast.net> has quit IRC15:03
sgw_YPTM: Dial-in number: 1.972.995.7777 / Participant passcode:   4200107815:03
sgw_YPTM: Saul is on15:03
Song_LiuYPTM: Any opens?15:03
*** belen <belen!Adium@nat/intel/x-ijaprfmhxlsnezzn> has joined #yocto15:03
laurYPTM: LaurentiuP joined15:03
halsteadYPTM: Michael here.15:04
darknighteYPTM: Song_Liu: a reminder: there is a OE project IRC discussion in the next hour.15:04
erenoh15:04
*** cristiana <cristiana!86bfdc47@gateway/web/freenode/ip.134.191.220.71> has joined #yocto15:04
*** Garibaldi|work <Garibaldi|work!~andydalt@nat/cisco/x-bsnfyrjwesfrivtd> has quit IRC15:04
* eren connecting15:04
*** slaine <slaine!~slaine@84.203.137.218> has joined #yocto15:04
cristianiorgaYPTM: Cristian is present15:05
zeddiiYPTM: Bruce Ashfield in on.15:06
*** pidge <pidge!~pidge@c-24-21-207-18.hsd1.or.comcast.net> has joined #yocto15:06
*** Garibaldi|work <Garibaldi|work!~andydalt@nat/cisco/x-gthaenozcpibqzwr> has joined #yocto15:06
erenYPTM: Eren is present15:06
halsteadbluelightning, Is git.yp.org still slow for you?15:06
BSDCatYPTM: Matthew Weigel just joined15:06
pidgeYPTM: Beth joined15:07
bluelightninghalstead: a little bit, but eren was having some more serious difficulties15:07
*** Jefro <Jefro!~jefro@50-0-152-82.dedicated.static.sonic.net> has joined #yocto15:07
*** AlexG <AlexG!86bfdd48@gateway/web/freenode/ip.134.191.221.72> has joined #yocto15:07
*** fgretief <fgretief!~chatzilla@41.0.38.138> has quit IRC15:07
erenhalstead: yeah, I cloned linux-yocto at the rate of ~400 KB/s15:08
erenI cloned, no problem for me but I'm wondering why it was that slow15:09
*** ndec is now known as ndec|vacations15:09
halsteaderen, We have been near our bandwidth cap (60mbps) recently. http://is.gd/aSumhe15:10
erenhalstead: oh, assuming that that's a bw problem then?15:11
rburtonhalstead: whoa, what was that spike? :)15:11
halsteadrburton, The large spike going over the cap at 20:00 is a backup to a network peer. That's why it can go so high.15:12
rburtonah15:12
halsteadrburton, That transit really should be excluded from the graph but it isn't.15:13
rburtoni need me some of that capacity here15:13
halsteadThat would be nice. :)15:13
erenhalstead: do you use munin for network graph?15:14
erensorry for off-topic question :)15:14
*** zenlinux <zenlinux!~sgarman@c-24-20-145-95.hsd1.or.comcast.net> has joined #yocto15:14
erenany link for "making of?"15:16
halsteaderen, No. Just using our ISP's graphs right now.15:16
erenhalstead: okkie, thanks.15:16
AlexGis Beth around?15:17
sgw_AlexG: beth is pidge15:17
darknightedvhart: woot on getting so much into the maintainer trees.15:17
AlexGsgw_: tnx15:17
halsteaderen, Link to "making of" https://www.youtube.com/watch?v=Qbr9QYFmzrU&feature=player_embedded15:17
erenhalstead: thanks15:19
*** scottrif <scottrif!~scott-len@b482.ip17.netikka.fi> has left #yocto15:20
darknightehalstead: vacation!?!  who authorized that?15:20
zeddii+115:20
*** tinti <tinti!~tinti@pdpc/supporter/student/tinti> has joined #yocto15:20
halsteaddarknighte, Some crazy LF person.15:21
darknightehalstead: Hope you have a great time and manage to forget about work (for the most part) for a while.15:22
halsteaddarknighte, Thanks. I'll go out on southern Oregon whitewater for a bit and then see a play or three in Ashland OR. Should be fun.15:24
erengithub.com/eren/meta-hamradio15:24
darknighteSounds fun.15:24
sgw_halstead: I am jealous about whitewater!15:24
darknightehalstead: sgw_: I have never gone on whitewater.15:25
*** AlexG <AlexG!86bfdd48@gateway/web/freenode/ip.134.191.221.72> has quit IRC15:25
darknightehalstead: aren't there different levels?15:25
pidgeeren: I need to get my station back up soon :) Then I can start testing!15:25
erenpidge: oh okkie! :)15:26
erenthanks15:26
pidgeeren: antenna mast collapsed15:26
darknighteit sounds like pidge likes to brutalize her keyboard…15:27
erenpidge: oh :/ sad.15:27
erenpidge: only aprs support is there, btw.15:27
halsteaddarknighte, Each series of rapids is rated 1-6. I've done up to 4. (http://en.wikipedia.org/wiki/Rafting#Grades_of_white_water)15:27
*** walters <walters!~walters@c-66-31-18-51.hsd1.ma.comcast.net> has quit IRC15:27
erenI'm also working on ALIX 3D3 support, so it will be a little complicated :)15:28
erenI will see if it boots and try to interface it with KISS modem15:28
pidgeeren: I had grig support working a while back.15:28
Song_LiuYPTM: thank you all for joining the meeting, have nice day or evening!15:29
pidgedarknighte: my keyboard is loud15:29
pidgebrb15:29
darknightehalstead: so, going for a grade 6?15:29
sgw_khem, did you disappear the 2.18 eglibc tarball, do we need to recreate that on the downloads.yp.org?15:29
darknightehalstead: I like the description on wikipedia...15:29
kergothdamn. i was hoping to use this native systemd-tmpfiles to prepopulate tmpfiles.d, but it can't e built on rhel5/centos5, which is where we still do most of our builds15:30
* kergoth grumbles15:30
darknightehalstead: "Skill level: successful completion of a Class 6 rapid without serious injury or death is widely considered to be a matter of great luck or extreme skill and is considered by some as a suicidal venture"15:30
halsteaddarknighte, I'll probably stick with the easy ones as I'm a bit rusty.15:30
sgw_halstead: the rouge? on your own or with a guide?15:31
darknightehalstead: that sounds prudent to me.  it sounds like great fun no matter what class.15:31
erenhehe, these boards are literally "cooked" (minnowboard)15:33
halsteadsgw_, With a guide company. Probably a half day on the upper klamath and a full day on the rogue.15:34
sgw_halstead: nice, we did a family trip a couple of years ago on the rogue, was blast, I actually kayaked a bunch of it (but not the bigger stuff)15:37
dvhartdarknighte, thanks :)15:39
halsteadsgw_, When I was 19 I did a five day trip on the rogue with a paddle boat, an oar boat for gear, and two IKs. It was a good trip with a lot of downtime.15:39
*** dvhart <dvhart!~dvhart@static-50-53-108-147.bvtn.or.frontiernet.net> has quit IRC15:44
*** jzhang-laptop <jzhang-laptop!~jzhang16@134.134.139.70> has quit IRC15:46
sgw_bluelightning: do you have the external-sourcery patch in your dylan queue?15:48
bluelightningsgw_: I can add it definitely15:49
sgw_bluelightning: do you want me to leave bug 4908 open for dylan now, probably should take that, I will mark you owner also.15:49
yoctiBug https://bugzilla.yoctoproject.org/show_bug.cgi?id=4908 normal, Medium+, 1.5 M3, saul.wold, IN PROGRESS REVIEW , External toolchain does not work with poky dylan15:49
bluelightningsgw_: yes let's keep it open until the patch is merged in dylan15:50
*** Corneliu <Corneliu!c0c69724@gateway/web/freenode/ip.192.198.151.36> has quit IRC15:50
lpappkergoth: ^15:51
*** blitz00 <blitz00!~stefans@unaffiliated/blitz00> has quit IRC15:53
*** sameo <sameo!samuel@nat/intel/x-vdyobtfhzwdamhbs> has joined #yocto15:54
*** eballetbo <eballetbo!~eballetbo@43.Red-2-139-180.staticIP.rima-tde.net> has quit IRC15:58
*** cristiana <cristiana!86bfdc47@gateway/web/freenode/ip.134.191.220.71> has quit IRC16:02
*** TuTizz <TuTizz!~TuTizz@unaffiliated/tutizz> has quit IRC16:02
lpapprburton: I have the busybox version from danny16:04
lpappwhich is not working with dylan apparently ...16:04
*** fray <fray!U2FsdGVkX1@gate.crashing.org> has left #yocto16:04
lpappthis change  broke it from RP: http://bpaste.net/show/118688/16:04
rburtonlpapp: why are you using danny's busybox with dylan?16:04
lpapprburton: because dylan's busybox does not work.16:05
lpappalso, we have custom patches16:05
rburtonit does work, what's your specific problem?  i recommend applying your patches in a bbappend instead of taking a recipe from another version and amending that.16:06
lpappis there a way for sending patches to the mailing list without subscriving and moderation?16:06
lpappit is getting tedious.16:06
rburtonyou can subscribe and turn off mail delivery16:06
rburtonthen you don't get moderated but you don't get list mail16:06
lpapprburton: no no16:06
lpapprburton: our busybox is quite different.16:07
lpappwith changes, very unlikely for upstreaming.16:07
lpappand they are intrusive.16:07
lpapp.bbappend will not help you there.16:07
rburtonfine, so fork the one native to your release16:07
lpapprburton: that leaves me stale in a few years.16:08
lpappon many mailing lists, then... i.e. not a preferred option.16:08
lpapprburton: it was already forked back then.16:08
lpappso, can anyone explian RP's change?16:08
lpappI do not quite get it from the commit message.16:09
lpappnor that, what I am supposed to do afterwards ...16:09
*** belen <belen!Adium@nat/intel/x-ijaprfmhxlsnezzn> has quit IRC16:10
lpappso basically, Yocto does not provide API guarantee.16:10
lpappsource code interface can break at any moment.16:11
lpappso basically forking is an unpleasure experience then ...16:11
lpappbecause the Yocto API is inherently unstable.16:12
lpappno guarantees.16:12
*** mr_science <mr_science!~sarnold@net-cf9a4e91.cst.impulse.net> has joined #yocto16:12
*** mr_science <mr_science!~sarnold@gentoo/developer/nerdboy> has joined #yocto16:12
*** belen <belen!Adium@nat/intel/x-sqedhxsyoxzcdtql> has joined #yocto16:12
rburtonlpapp: that commit make the file deps handling be threaded, and it shouldn't have broken your recipe16:13
lpapprburton: process_deps is not available anymore after that commit ...16:14
lpappas you can see it was moved around ...16:14
*** Guest26855 <Guest26855!~tbn@mad27-1-88-172-46-29.fbx.proxad.net> has quit IRC16:14
lpappsounds like a bugzilla entry for documenting the no api compatibility promise.16:15
lpappNameError: global name 'process_deps' is not defined16:15
rburtonlpapp: i still recommend forking the busybox recipe in the version of your distro, instead of attempting to use one from an older release16:15
lpappafter that particular change ...16:15
lpapprburton: you are not real.16:16
lpapprburton: causing extra work for us is not wished.16:16
lpapprebase all the stuff, test all the utils thoroughly, etc.16:16
rburtonlpapp: if you pastebin the recipe i may be able to help you solve your parsing problems16:16
lpapprburton: recipe was already pasted.16:16
rburtonor if you just have patches, use a bbappend.16:16
lpappbut it upstream danny, really.16:16
rburtonlpapp: sorry i'm also in meetings and trying to do work, must have missed it16:17
lpappas I said before, .bbappend is a complete no go16:17
lpappplease read back why I claimed that.16:17
rburtoni did, and i don't understand16:17
lpappread harder. :)16:18
lpappalso, after the mailing list incident about fixing a serious regression, I do not wish to do any upgrade to busybox16:18
lpappit is fully broken, and should not be used for my project16:18
lpappyou will have more work in the end with the support than accepting, but I was trying to be clear about it.16:19
lpappI have to maintain old stuff, you need to support more.16:19
lpappit is a lost/lost for everyone involved except a very few people, if any!16:19
lpapphttps://bugzilla.yoctoproject.org/show_bug.cgi?id=495816:23
yoctiBug 4958: normal, Undecided, ---, scott.m.rifenbark, NEW , No documentation about source compatibility16:23
*** zenlinux <zenlinux!~sgarman@c-24-20-145-95.hsd1.or.comcast.net> has quit IRC16:23
bluelightninglpapp: help harder...16:24
lpappbluelightning: ?16:24
*** jzhang-laptop <jzhang-laptop!jzhang16@nat/intel/x-bawmletxexbkfqiw> has joined #yocto16:25
bluelightningyou want rburton to help you, so help him to do so by explaining yourself clearly16:25
bluelightningplease16:25
lpappbluelightning: what to explain, please?16:25
lpappthere are more specific questions than "I do not understand".16:26
*** jzhang-laptop <jzhang-laptop!jzhang16@nat/intel/x-bawmletxexbkfqiw> has left #yocto16:27
bluelightninglpapp: please explain why a bbappend won't work for you because that is the mechanism we recommend for adding a few patches/supplying a different config to a recipe such as busybox16:27
lpappI already did16:27
lpappbesides, no, you have actually suggested a *fork* for patches that will not be upstreamed.16:28
bluelightningnothing about bbappends mandates sending patches upstream16:28
lpappand even .bbappend would not fly really, as it does not solve the main problem at hand: avoid the additional rebase and relevant works because someone thought it is good to break source compatibility.16:29
rburtonthat's exactly what a bbappend is designed to solve16:29
lpappnot really, no.16:29
lpappit needs *manual* work to rebase changes, a lot, like this discussion.16:29
* lpapp wonders why he needs to fight for trivial things, like so many others fork packages out there, and now being pointed as evil16:30
lpappit is the same as the defense of the almost non-existing rfkill users.16:30
lpappI am bored with fighting for trivial stuff.16:30
rburtonwe're not stopping you fork, but it's your problem when the fork needs rebasing16:31
rburtonwhich is what bbappend is designed to do, you can change sources/add patches/add functions and not care when the "real" recipe is updated16:31
*** elmi82 <elmi82!~timo@mail.bmw-carit.de> has quit IRC16:31
lpappthe fork does not need any rebasing.16:31
lpappthat is the whole point of the fork.16:31
lpappthe upstream source version can be retained easily.16:32
lpappI am coming here for help, not to get more work on my shoulder.16:33
lpappRP: you broke the stuff, any clue what to change in the fork?16:33
bluelightninglpapp: this is a rare instance where a recipe was broken because it called internal functions in package.bbclass, this is not a common case16:33
davestlpapp: the community is happy to offer advice, but remember we all have work to do. You need to do work too. :-)16:34
bluelightninglpapp: if you prefer not to use a bbappend and rebase your patches each release, I'd suggest to resolve this particular issue, just use the current inc file16:34
lpappdavest: ?16:34
lpappI have been doing simple yocto stuff for two weeks soon16:34
lpappto get something basic done?16:34
lpappin full time16:34
lpappwith an already well-innovated system into Yocto.16:34
*** zenlinux <zenlinux!~sgarman@c-50-139-96-211.hsd1.or.comcast.net> has joined #yocto16:35
lpappbluelightning: that might bring new dependencies in, not present in other places...16:35
lpappbluelightning: which can launch an avalanche.16:35
bluelightninglpapp: what would you like us to do, then?16:35
lpappI would rather wait for an expert feedback, basically RP who broke it.16:35
bluelightningRP is on holiday, you may be waiting some time16:36
davestlpapp: perhaps you might be better served by someone like Wind River or Mentor who you can get paid support from.16:36
lpappand no one else knows why he broke it?16:36
lpapplike reviewers who approved?16:36
*** challinan <challinan!~challinan@173-10-226-189-BusName-WestFlorida.hfc.comcastbusiness.net> has quit IRC16:36
lpappdavest: oh, yeah, that is so cheap16:36
lpappbut if you pay, well, why not? :)16:36
bluelightninglpapp: at the time he made the change, FYI, the inc file no longer had a reference to the function16:36
*** challinan <challinan!~challinan@173-10-226-189-BusName-WestFlorida.hfc.comcastbusiness.net> has joined #yocto16:36
davestlpapp: I observe a definite fatigue factor on the community's part16:37
lpappbluelightning: yes, I checked.16:37
lpappbluelightning: but that does not mean, he did not break the API16:37
rburtonlpapp: you're assuming it was stable API to begin with.  i'm not sure where that was documented.16:37
lpappdavest: well, if Yocto is fatigue, that might be right. :)16:37
lpappdavest: we are all here to improve it to be less tiring.16:38
lpappi.e. proper errors, etc16:38
rburtonlpapp: so the change was good, as busybox was fixed before the change was made.16:38
lpapprburton: as I wrote just a few lines above, it broke the API for other people.16:38
*** joseppc <joseppc!~Josep@sestofw01.enea.se> has quit IRC16:38
lpapprburton: yes, of course, I assumed Yocto provides stable stuff16:38
lpapppardon me.16:38
lpappsee my bugreport for action points.16:38
*** mihai <mihai!~mihai@80.97.15.150> has quit IRC16:39
lpappis the busybox.inc supposed to work with older busybox releases as is?16:40
rburtonit's not designed to be generic for all time, no16:41
lpapp:'(16:41
rburtonbut if you've a compatible busybox its a big fragment you can include and then tweak from your .bb16:41
lpappso basically if you are coming from one older release (~6 month), you might be screwed.16:42
rburtonthere's a spectrum of ways to change a package16:42
rburtonfork the .bb / use a common .inc / use a bbappend16:43
lpappsounds like a call for a public discussion16:43
lpappto actually deprecate stuff maximum, but not break.16:43
rburtondeprecate implies remove16:43
davestlpapp: I think what you are suggesting would be impossible to validate16:43
lpapprburton: in the future. So?16:44
lpappdavest: no idea what you are saying.16:44
davest"is the busybox.inc supposed to work with older busybox releases as is?"16:44
davestThat would be impossible to validate16:44
lpappsure, it would be possible.16:45
davestNot with bounded resources of an open source project16:45
lpappgo back a few releases, but at least two (~1 year)16:45
davestremember, you are not paying money for this work16:45
lpappdavest: it really has nothing to do with that.16:45
lpappit could be all automated, really.16:45
lpappit is a machine work, not human.16:45
davestAgain, takes work to do that16:45
Jefrofor every supported board?16:45
davestdo you want to volunteer to do it?16:46
lpappJefro: of course no, just the supported toolchains etc ... which are still undocumented...16:46
lpappsee my bugreport for details.16:46
lpapplet us see who approved that break.16:47
lpappso, it could be that one release (~6 months) back is verified against the change with the supported combinations, and then the information could also be used for writing the porting guide.16:49
lpappif something breaks, at least a porting guide could help.16:49
*** sameo <sameo!samuel@nat/intel/x-vdyobtfhzwdamhbs> has quit IRC16:50
rburtonthe release notes have an upgrading section, but sadly humans are involved so stuff gets missed16:50
lpapprburton: how would you know something breaks if you do not have CI?16:51
lpappyou would have much less power to know.16:51
lpappso, I think the first step ahead could be testing one version back with CI16:51
lpappand that could also give some continuity between releases.16:51
lpappso one person coming from 2 or 3 versions back can still follow the progress.16:52
lpappnote, even if I decided to upgrade to the latest busybox, dylan would still be broken16:52
*** dvhart <dvhart!dvhart@nat/intel/x-wkyqcdmqvlkmbekr> has joined #yocto16:52
lpappas my change was rejected16:52
lpappso I do not even bother to get twice more work.16:52
davestlpapp: believe this does go beyond what we're able to do, unless you feel inspired to volunteer.16:52
davestlpapp: as I said, you can always work with an OSV16:53
lpappwell, it is not my problem, only.16:53
lpappit is also your, and your users' problem.16:53
lpappit would be a generic quality and documentation gate.16:54
davestlpapp: we try to be responsive if there is a strong demand16:54
davestlpapp: but remember, it's still free software16:54
JefroI think the issue is that lpapp is trying to do things outside of what we normally test for. We can only build & test for a finite number of combinations of things, so we try to meet as many combinations as we can. I can also see his point, that there are things that "should" work - while we welcome contributions to help get those things working, there is only so much one team can do.16:55
lpappit is not possible to search on patchwork for an sha? o_O16:55
lpappJefro: no no16:56
Jefronot correct?16:56
lpappJefro: it would be equivalently broken for any supported combination with one release back.16:56
lpappregardless toolchain, machine, distro, whatsoever.16:56
lpappa python function got moved around. It is platform agnostic stuff.16:56
lpappJefro: I do not think you will give CI access for me.16:57
lpappso inherently, I cannot help.16:57
davestlpapp: if you are suggesting we validate one version back for all recipes to make sure they still function, that is not sensible16:57
davestlpapp: excuse me16:57
davestlpapp: I meant to say16:57
davestlpapp: creating a working operating system is a tricky thing16:58
davestlpapp: you need to get everything just right to make it work16:58
davestlpapp: it's not easy, believe me16:58
*** mulhern <mulhern!~mulhern@c-24-128-153-12.hsd1.ma.comcast.net> has quit IRC16:58
lpappdavest: easy or not, it would make a lot of sense IMO... ;-)16:58
davestlpapp: and YP is so flexible and the universe of possible combinations so large16:59
davestlpapp: I just don't see how an open source community project could do better16:59
lpappwell, you will not give access for me to the CI, will you16:59
davestlpapp: but we really do try to do better, all the time16:59
lpappif you do not, you cannot say, I should help because I am physically unable. :)17:00
davestlpapp: well, anything is possible17:00
lpappyeah, right ... :)17:01
davestlpapp: honestly though, I would want to meet with you first17:01
*** fgretief <fgretief!~chatzilla@196-215-192-74.dynamic.isadsl.co.za> has joined #yocto17:01
lpapphttps://bugzilla.yoctoproject.org/show_bug.cgi?id=4958 -> anyway, this can be a starting step, and probably not hard to resolve.17:01
yoctiBug 4958: normal, Undecided, ---, scott.m.rifenbark, NEW , No documentation about source compatibility17:01
lpapp"it can eat babies, period"17:01
lpappand then I will try to do my best to avoid forks.17:02
lpappI would not mind updating my busybox to dylan if my patch had got approved, and hence had had one less pain.17:04
lpappbut that is just a hindsight.17:04
lpappand I even made the contribution there. ;)17:04
lpappwhy are white space changes allowed? :O17:06
lpappI mean 4 or 8 spaces.17:06
*** JimBaxter <JimBaxter!~jbaxter@jimbax.plus.com> has quit IRC17:06
lpappdoes it really matter?17:06
lpappI see a lot of noise like that in dylan.17:06
davestlpapp: there is something about Python compatibility17:06
lpappdavest: elaborate?17:06
davestlpapp: can't, I have never programmed in Python before17:07
davestlpapp: are you a Python expert?17:07
lpappno17:07
davestlpapp: just take my word for it17:08
lpappbut surely, python accepts both...17:08
lpappso modifying it for no real gain is bad.17:08
lpappsince it causes a lot of noise.17:08
davestlpapp: possibly, but please don't call me shirley17:08
lpappheh, fun, and actually these are even tabs!17:08
lpappI thought dylan would have eliminated tabs?17:09
hollisblpapp: http://python3porting.com/differences.html#indentation17:09
lpappdavest: will not as I do not even know what a shirley is. ;)17:09
lpapphollisb: what are you trying to represent17:10
*** belen <belen!Adium@nat/intel/x-sqedhxsyoxzcdtql> has quit IRC17:10
lpapppresent*17:10
*** sameo <sameo!~samuel@192.55.54.38> has joined #yocto17:10
*** JimBaxter <JimBaxter!~jbaxter@jimbax.plus.com> has joined #yocto17:10
hollisblpapp: I'm trying to answer your question about whitespace changes and why it matters17:11
bluelightninglpapp: a mix of tabs and spaces makes it hard to match things up between bbclasses, recipes that inherit from them, and bbappends17:11
lpapphollisb: that does not answer it though.17:11
lpapphollisb: the style is already mixed.17:11
hollisbok then, carry on17:11
lpapphollisb: and dylan was previously complaining about tabs when coming from denzil.17:11
bluelightninglpapp: and python mandates that you match them up from line to line within the same function, which in our system may be split across multiple files17:12
lpappbut what I see in meta/recipes-core/busybox/busybox.inc is the introduction of tabs17:12
bluelightninglpapp: in a python function or a shell function?17:13
*** mulhern <mulhern!~mulhern@c-24-128-153-12.hsd1.ma.comcast.net> has joined #yocto17:14
lpappbluelightning: busybox.inc17:14
lpapppython17:14
lpappand also shell.17:14
lpappjust compare from danny to dylan17:14
lpappit is a LOT of noise.17:15
lpappit can hardly integrate them because of the noise.17:15
lpappI can*17:15
lpappmaybe you have some whitespace ignoring diff program, but that is about vimdiff.17:15
*** el_robin <el_robin!~el_robin@2a01:e0b:1:124:ed70:49dd:bf2e:cfce> has quit IRC17:16
lpapp-> install: cannot stat `/home/lpapp/Projects/Yocto/poky-dylan-9.0.1/build/tmp/work/armv5te-foo-linux-gnueabi/busybox/1.20.2-r0/busybox-cron': No such file or directory17:18
lpappafter copying the new busybox.inc over.17:18
*** slaine <slaine!~slaine@84.203.137.218> has quit IRC17:19
*** mulhern <mulhern!~mulhern@c-24-128-153-12.hsd1.ma.comcast.net> has left #yocto17:21
*** mckoan is now known as mckoan|away17:22
lpapphow can I fix that?17:22
*** el_robin <el_robin!~el_robin@2a01:e0b:1:124:75f7:d043:bc6d:cf4c> has joined #yocto17:23
bluelightninglpapp: probably, you'll need to adapt it to things that are not present in the version of busybox that you are building17:24
*** Stygia <Stygia!~gmpsaifi@0904ds6-noe.0.fullrate.dk> has quit IRC17:25
lpappthat is a lot of work, yeah.17:25
bluelightningI wouldn't have thought it to be that much17:26
* bluelightning needs to head off, back later17:26
lpappwell, you cannot solve it with clean vanilla.17:27
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC17:27
*** seebs <seebs!~seebs@home.seebs.net> has quit IRC17:28
lpappis there a version freeze period for packages to be updated?17:29
lpappi.e. can I just go ahead and submit u-boot, busybox, etc upgrades I made locally to oe-core?17:29
davestlpapp: there is a cycle for these things, yes17:30
davestlpapp: stick on the technical call and you will get a sense for how it works17:30
davestlpapp: you can submit patches of course but depending on the time frame it might not get applied to Master until after the release17:31
davestWe're finishing up M3 now, so there is still a window17:32
lpappI do not know anything about a technical call17:32
lpappi.e. I even opened a bugreport about that to be more open.17:32
lpappbut I might be off there.17:32
sgw_davest: lpapp: window for M3 is closed, M4 and beyond is open17:32
davestlpapp: ?17:32
*** seebs <seebs!~seebs@home.seebs.net> has joined #yocto17:32
davestlpapp: the call is announced on yocto@yoctoproject.org17:32
lpappdavest: well, it seems to be regular.17:33
lpappother projects document the time, place, etc on the webpage.17:33
lpappnot on a mailing list out of the many.17:33
sgw_lpapp: the number is also posted in the chat room.17:33
davestlpapp: this is the way we do it17:33
lpappdavest: which I suggest to change.17:33
lpapplast time when it started, I had no idea what was going on.17:34
lpappand I did not wanna chim in because it seemed something official.17:34
lpappI thought I would look for it on the website, but found noting.17:34
davestlpapp: it can take time to get used to the way a community works.17:34
lpappnothing*17:34
lpappso I had no any clue when I can start talking again, etc.17:34
davestlpapp: give it time, you'll figure it out17:34
lpappdavest: I do not wanna give time to everyone17:35
lpappI wanna people getting involved as easily as possible.17:35
lpappsee other projects, how smoothly they managed.17:35
davestlpapp: suggest you join the mailing list. there is an agenda posted there17:36
davestlpapp: This is the way it works for us and has worked pretty smoothly17:37
lpappdavest: I just mentioned why it does not work smooth17:37
lpappsee, this is what I do not like here. :)17:37
davestlpapp: and I understand17:37
lpapptrying to improve stuff, and I have to fight17:37
davestlpapp: don't fight, just be cool17:37
lpappfor factors, like better readable error messages for end users, easier to get into the circles, etc.17:37
lpappI would rather not fight ...17:38
Jefrolpapp the website is my jurisdiction. Do you have a specific suggestion?17:38
lpappbut people are reluctant to improving stuff... not sure why, really.17:38
hollisbdavest++17:38
lpappJefro: there could be a meetings section17:40
lpappeither main site, or wiki.17:40
lpappI prefer main because I dislike wikis.17:40
JefroThere is one public meeting. I think perhaps a page rather than an entire section.17:41
*** sameo <sameo!~samuel@192.55.54.38> has quit IRC17:41
JefroI can add a page under the Community section (see Tools & Resources)17:41
dvhartSomething in tools and resources makes sense to me17:41
lpappJefro: in that case, you could add it beside the irc channal name.17:41
lpappas an additional note.17:42
lpappperhaps it could even be in the topic.17:42
lpappin the topic at least when the meeting starts, that is.17:42
lpappor not topic, but announcement17:42
lpappnot that YPTM: foo joined17:42
lpappusually meeting bots starts with the topic.17:42
lpappstart*17:42
lpappand where to look for information, wiki to the agenda, etc.17:43
dvhartlpapp, what do you mean "not that YPTM: foo joined"?17:43
*** simar <simar!~simar@128.224.252.2> has joined #yocto17:43
lpappJefro: https://www.yoctoproject.org/tools-resources/community/irc17:43
lpappyou could add the info in ther.17:43
lpappthere*17:43
Jefroyes, although the call is actually a telephone call in addition to IRC. It can be linked in more than one place.17:44
sgw_lpapp: I did post the callin info at the start of the meeting17:44
lpapphttps://bugzilla.yoctoproject.org/show_bug.cgi?id=495917:44
yoctiBug 4959: normal, Undecided, ---, jeffrey.osier-mixon, NEW , Add some information about YPTM17:44
lpappsgw_: don't you think one needs to get info before calling something? :)17:45
Jefrolpapp thanks for the bug17:45
lpappat least, I will not make semi-random calls. :)17:46
lpappJefro: thanks for taking care.17:46
*** florian <florian!~fuchs@Maemo/community/contributor/florian> has quit IRC17:47
*** BSDCat <BSDCat!unique@calvin.idempot.net> has left #yocto17:51
lpappcan I tell bitbake on the command line which version to build?17:52
lpappfor instance "... bitbake u-boot ..."17:52
sgw_lpapp, you can use the -b option with the path to your recipe (not just the recipe name)17:56
*** Garibaldi|work <Garibaldi|work!~andydalt@nat/cisco/x-gthaenozcpibqzwr> has quit IRC17:57
lpappk, ty.17:57
*** lpapp <lpapp!~lpapp@kde/lpapp> has quit IRC17:58
*** Garibaldi|work <Garibaldi|work!~andydalt@nat/cisco/x-xjsvoqdjwkrdterm> has joined #yocto17:59
*** Garibaldi|work <Garibaldi|work!~andydalt@nat/cisco/x-xjsvoqdjwkrdterm> has quit IRC18:03
*** Garibaldi|work <Garibaldi|work!~andydalt@nat/cisco/x-ikxkhoipbmizrfri> has joined #yocto18:06
*** panda84kde <panda84kde!~diego@static-217-133-170-65.clienti.tiscali.it> has quit IRC18:14
*** davest <davest!Adium@nat/intel/x-dfynalpalbvmlore> has quit IRC18:18
*** acidfu <acidfu!~nib@unaffiliated/acidmen> has quit IRC18:19
*** Song_Liu <Song_Liu!c037362a@gateway/web/freenode/ip.192.55.54.42> has quit IRC18:20
*** lpapp <lpapp!~lpapp@kde/lpapp> has joined #yocto18:21
rburtonlpapp: you asked earlier about schedule and stuff: https://wiki.yoctoproject.org/wiki/Yocto_1.5_Schedule18:26
*** Jefro <Jefro!~jefro@50-0-152-82.dedicated.static.sonic.net> has quit IRC18:29
*** Jefro <Jefro!~jefro@50-0-152-82.dedicated.static.sonic.net> has joined #yocto18:29
mr_sciencelpapp: note the -b option disables dep resolution and a couple of other things18:35
mr_scienceuse PREFERRED_VERSION_foo = "X.X"18:36
mr_scienceunless it's just a one-off build of version X.X...18:37
sgw_mr_science: right, I should have mentioned that, thank you.  The PREFERRED_VERSION_foo should be set in a configure file, like a distro config or local.conf.18:37
sgw_khem: did you see my note about the 2.18 eglibc tarball being missing, we should probably get it up on download.yoctoproject.org18:40
* kergoth looks into creating a systemd service for chen qi's r/o script(s) to try using those bits on a systemd image18:41
kergothI wish I had known that contrib branch existed before we pursued a different approach, heh18:42
mr_sciencesgw_: hard to keep track of all the stuff winging at lpapp these days...   ;)18:47
sgw_kergoth: he just started working on it this last week.  Hopefully not too much duplicated work.18:55
kergothnot too much, only part of it covers the same area (how the read-only specific volatiles are handled). i still think we need to consolidate volatiles / tmpfiles handling if for no other reason than to reduce differentiation between sysvinit and systemd and to avoid recipe maintenance headaches18:56
kergothI'd like to see improved systemd support all around in the 1.5 timeframe18:56
kergothheh18:56
* mr_science votes for reduced recipe maintenance too19:00
*** mulhern <mulhern!~mulhern@c-24-128-153-12.hsd1.ma.comcast.net> has joined #yocto19:04
sgw_kergoth: yes that would be great, I think we between chen's work and your work, we can get a good patch set. I am not sure if he comes up on IRC or not.19:04
*** mulhern <mulhern!~mulhern@c-24-128-153-12.hsd1.ma.comcast.net> has quit IRC19:04
kergothgood god, i forgot what a from scratch build looks like19:05
* kergoth populating a new sstate cache on a new build VM19:05
sgw_kergoth: why not use SSTATE_MIRROR from an older build?19:06
sgw_kergoth: unless you want a pristine sstate cache19:06
*** Garibaldi|work <Garibaldi|work!~andydalt@nat/cisco/x-ikxkhoipbmizrfri> has quit IRC19:06
rburtonkergoth: the first 500 tasks hurt, don't they19:06
kergothsgw_: old vm went kaput on me, couldn't get back into it anymore, stopped booting19:07
kergothheh19:07
kergothrburton: indeed19:07
kergotheven using an external toolchain it's just painful19:07
rburtonsstate ftw.19:08
kergothyeah, as brittle as it can be, at least the rebuilds are only a subset of what there is, and the natives dont' get rebuilt much19:09
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto19:09
kergothits that up front build of all the native stuff thats the worst :)19:09
* kergoth wishes he could shove all his sstate into nfs to share amongst his vms, but the performance just isn't there, nor is the disk space, end up storing it locally instead19:10
kergothwould be nice if we had a virtual backing store for the sstate cache, which the build could both pull from and push to, transparently, not just locally19:10
rburtonkergoth: isn't that called NFS or CIFS? :)19:11
kergothwell yeah, if they didn't suck horribly19:11
kergoth:)19:11
rburtonfilesystems are hard etc ;)19:12
rburtonanyway there's an oven on downstairs that doesn't have any dinner in, i best resolve that19:12
rburtontata19:12
kergothindeed, later19:12
*** zecke_ <zecke_!~ich@91-65-247-193-dynip.superkabel.de> has joined #yocto19:12
*** smartin_ <smartin_!~smartin@ivr94-4-82-229-165-48.fbx.proxad.net> has joined #yocto19:14
*** zecke <zecke!~ich@91-65-247-193-dynip.superkabel.de> has quit IRC19:14
mr_sciencesamba mounts an nfs are about the same on GigE19:15
mr_science*and19:15
mr_sciencemaybe 11 MB/sec max19:16
*** lpapp <lpapp!~lpapp@kde/lpapp> has quit IRC19:16
*** eren <eren!~eren@unaffiliated/eren> has quit IRC19:22
mr_scienceat least on my local corp network...19:24
*** Garibaldi|work <Garibaldi|work!~andydalt@nat/cisco/x-sononkjandqfhvow> has joined #yocto19:26
*** davest <davest!Adium@nat/intel/x-adjourgrgcafacby> has joined #yocto19:31
*** tor <tor!~tor@c-ef66e655.125-1-64736c10.cust.bredbandsbolaget.se> has quit IRC20:16
*** fgretief <fgretief!~chatzilla@196-215-192-74.dynamic.isadsl.co.za> has quit IRC20:19
*** mulhern <mulhern!~mulhern@c-24-128-153-12.hsd1.ma.comcast.net> has joined #yocto20:19
*** joeythesaint <joeythesaint!~jjm@128.224.252.2> has quit IRC20:24
*** fenrig <fenrig!5bb5340c@gateway/web/freenode/ip.91.181.52.12> has joined #yocto20:37
fenrigHi20:37
fenrigbitbake doesn't want to reparse conf/bblayers.conf20:37
fenrigI always get: "NOTE: Your conf/bblayers.conf has been automatically updated. Please re-run bitbake."20:37
fenrigHow do i get rid of it (rerunning bitbake doesn't fix anything)20:37
fenrigfor instance how does bitbake know if it changed20:38
*** zecke_ <zecke_!~ich@91-65-247-193-dynip.superkabel.de> has quit IRC20:38
*** fray <fray!U2FsdGVkX1@gate.crashing.org> has joined #yocto20:40
kergoththere's a version number in it. compare it to the one in meta/conf/ and meta-yocto/conf/20:40
fenrigkergoth: okay that fixed it kinda :D20:45
*** fenrig <fenrig!5bb5340c@gateway/web/freenode/ip.91.181.52.12> has quit IRC20:48
*** lpapp <lpapp!~lpapp@kde/lpapp> has joined #yocto20:54
martiertI have a problem with my kernel defconfig. I have a linux-yocto_3.4.bbappend which specifies a sha sum and adds file://defconfig to SRC_URI21:01
martiertwith this, the defconfig is not copied into .config, and I can fix that by adding a cp ${WORKDIR}/defconfig ${S}/.config in a do_configure_prepend, but then do_kernel_configcheck fails21:02
martiertany ideas on what I can do to fix this?21:02
bluelightningzeddii: ^21:05
*** JimBaxter <JimBaxter!~jbaxter@jimbax.plus.com> has quit IRC21:17
*** darknighte is now known as darknighte_znc21:27
*** jchonig <jchonig!~jch@128.224.252.2> has quit IRC21:32
*** W1N9Zr0 <W1N9Zr0!~W1N9Zr0@24-246-93-30.cable.teksavvy.com> has quit IRC21:43
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has quit IRC21:43
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto21:44
*** zenlinux <zenlinux!~sgarman@c-50-139-96-211.hsd1.or.comcast.net> has quit IRC21:46
*** zenlinux <zenlinux!~sgarman@c-50-139-96-211.hsd1.or.comcast.net> has joined #yocto21:47
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has quit IRC21:48
*** W1N9Zr0 <W1N9Zr0!~W1N9Zr0@24-246-93-30.cable.teksavvy.com> has joined #yocto21:49
*** davest1 <davest1!Adium@nat/intel/x-pnedhmvzkfbutozq> has joined #yocto21:49
*** davest <davest!Adium@nat/intel/x-adjourgrgcafacby> has quit IRC21:53
*** mulhern <mulhern!~mulhern@c-24-128-153-12.hsd1.ma.comcast.net> has quit IRC21:55
fray'k21:59
frayoops21:59
*** agust <agust!~agust@p4FDE7118.dip0.t-ipconnect.de> has quit IRC22:02
*** mulhern <mulhern!~mulhern@c-24-128-153-12.hsd1.ma.comcast.net> has joined #yocto22:04
bluelightningmartiert: hmm, I guess he's not around; I'd suggest sending the same thing to the mailing list and CC Bruce22:05
bluelightningmartiert: sorry I know you've been struggling with this for a couple of days22:05
*** ant_home <ant_home!~andrea@host218-250-dynamic.17-79-r.retail.telecomitalia.it> has joined #yocto22:09
*** sameo <sameo!~samuel@192.55.54.40> has joined #yocto22:17
*** b1gtuna <b1gtuna!~adam@206.116.3.18> has quit IRC22:22
*** Garibaldi|work <Garibaldi|work!~andydalt@nat/cisco/x-sononkjandqfhvow> has quit IRC22:23
*** davest1 <davest1!Adium@nat/intel/x-pnedhmvzkfbutozq> has quit IRC22:27
*** Jefro <Jefro!~jefro@50-0-152-82.dedicated.static.sonic.net> has quit IRC22:29
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto22:30
*** YoctoAutoBuilder <YoctoAutoBuilder!~YoctoAuto@autobuilder.yoctoproject.org> has quit IRC22:32
*** jkridner|work <jkridner|work!~jkridner@nat/ti/x-djissblsvblyvvxy> has joined #yocto22:34
*** YoctoAutoBuilder <YoctoAutoBuilder!~YoctoAuto@autobuilder.yoctoproject.org> has joined #yocto22:34
*** YoctoAutoBuilder <YoctoAutoBuilder!~YoctoAuto@autobuilder.yoctoproject.org> has quit IRC22:35
*** YoctoAutoBuilder <YoctoAutoBuilder!~YoctoAuto@autobuilder.yoctoproject.org> has joined #yocto22:35
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has quit IRC22:36
*** behanw <behanw!~behanw@216-58-123-51.cpe.distributel.net> has quit IRC22:51
*** mulhern <mulhern!~mulhern@c-24-128-153-12.hsd1.ma.comcast.net> has quit IRC22:53
*** tinti <tinti!~tinti@pdpc/supporter/student/tinti> has quit IRC23:00
*** smartin_ <smartin_!~smartin@ivr94-4-82-229-165-48.fbx.proxad.net> has quit IRC23:00
*** dvhart <dvhart!dvhart@nat/intel/x-wkyqcdmqvlkmbekr> has quit IRC23:06
*** jkridner|work <jkridner|work!~jkridner@nat/ti/x-djissblsvblyvvxy> has quit IRC23:21
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC23:32
*** hollisb <hollisb!~hollisb@192.94.38.34> has quit IRC23:32
*** khem <khem!~khem@99-57-140-209.lightspeed.sntcca.sbcglobal.net> has quit IRC23:33
*** Jefro <Jefro!~jefro@50-0-152-82.dedicated.static.sonic.net> has joined #yocto23:55
*** andyross <andyross!~andy@c-67-171-188-207.hsd1.or.comcast.net> has quit IRC23:55
*** Jefro <Jefro!~jefro@50-0-152-82.dedicated.static.sonic.net> has quit IRC23:59

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