Monday, 2015-04-20

*** mchehab <mchehab!~mchehab@187-53-4-119.3g.brasiltelecom.net.br> has quit IRC00:25
*** melio_cc <melio_cc!~melio_cc@c-75-67-202-137.hsd1.ma.comcast.net> has joined #yocto00:28
*** mchehab <mchehab!~mchehab@187-53-4-119.3g.brasiltelecom.net.br> has joined #yocto01:08
*** chankit <chankit!chankitx@nat/intel/x-mzizlmmkoofkvdnu> has joined #yocto01:30
*** neur0Fuzzy <neur0Fuzzy!~neur0Fuzz@p239.net182021249.tokai.or.jp> has joined #yocto02:12
*** nrossi_ is now known as nrossi02:20
*** pidge <pidge!~pidge@2a02:8084:0:3000:c159:c7f5:95d9:42ff> has joined #yocto02:34
*** behanw <behanw!~behanw@12.10.73.130> has joined #yocto02:37
*** GunsNRose <GunsNRose!~GunsNRose@110.184.147.224> has joined #yocto02:53
*** manuel__ <manuel__!~manuel@c-24-61-40-209.hsd1.ma.comcast.net> has quit IRC03:00
*** manuel__ <manuel__!~manuel@c-24-61-40-209.hsd1.ma.comcast.net> has joined #yocto03:01
*** manuel__ <manuel__!~manuel@c-24-61-40-209.hsd1.ma.comcast.net> has quit IRC03:03
*** mchehab <mchehab!~mchehab@187-53-4-119.3g.brasiltelecom.net.br> has quit IRC03:04
*** mchehab1 <mchehab1!~mchehab@179.204.230.206> has joined #yocto03:04
*** mchehab1 is now known as mchehab03:04
*** mchehab is now known as Guest2723803:05
*** OutOfNoWhere <OutOfNoWhere!~rpb@199.68.195.102> has quit IRC03:07
*** dholland_ <dholland_!~quassel@vpn.pelagicore.de> has quit IRC03:08
*** dholland <dholland!~quassel@vpn.pelagicore.de> has joined #yocto03:08
*** Guest27238 <Guest27238!~mchehab@179.204.230.206> has quit IRC03:35
*** melio_cc <melio_cc!~melio_cc@c-75-67-202-137.hsd1.ma.comcast.net> has quit IRC03:55
*** melio_cc <melio_cc!~melio_cc@c-75-67-202-137.hsd1.ma.comcast.net> has joined #yocto03:56
*** melio_cc <melio_cc!~melio_cc@c-75-67-202-137.hsd1.ma.comcast.net> has quit IRC03:59
*** flihp <flihp!~flihp@c-50-185-54-102.hsd1.ca.comcast.net> has quit IRC04:04
*** flihp <flihp!~flihp@c-50-185-54-102.hsd1.ca.comcast.net> has joined #yocto04:21
*** e8johan <e8johan!~quassel@83.218.80.242> has joined #yocto04:21
*** miandonmenmian <miandonmenmian!~miandonme@210.22.153.182> has joined #yocto04:29
*** redengin <redengin!~redengin@c-73-193-21-136.hsd1.wa.comcast.net> has joined #yocto04:49
*** SorenHolm <SorenHolm!~quassel@5634f191.rev.stofanet.dk> has joined #yocto04:52
*** e8johan <e8johan!~quassel@83.218.80.242> has quit IRC04:56
*** e8johan <e8johan!~quassel@83.218.80.242> has joined #yocto04:57
*** imrehg <imrehg!~greg@122.147.15.218> has joined #yocto05:10
*** AndersD <AndersD!~anders@213-64-219-84-no126.business.telia.com> has joined #yocto05:15
*** AndersD <AndersD!~anders@213-64-219-84-no126.business.telia.com> has quit IRC05:19
*** agust <agust!~agust@pD9E2FADF.dip0.t-ipconnect.de> has joined #yocto05:31
*** AndersD <AndersD!~anders@213-64-219-84-no126.business.telia.com> has joined #yocto05:34
*** SorenHolm <SorenHolm!~quassel@5634f191.rev.stofanet.dk> has quit IRC05:39
miandonmenmianhow can i get detailed info from a recipe using bitbake? or i need bitbake-layers?05:59
*** grma <grma!~gruberm@chello213047201250.tirol.surfer.at> has joined #yocto06:07
*** hamis <hamis!~irfan@110.93.212.98> has joined #yocto06:09
*** agust <agust!~agust@pD9E2FADF.dip0.t-ipconnect.de> has quit IRC06:10
AndersDmiandonmenmian, what are you looking for? Does `bitbkae -e <recipe-name>`shou what you need?06:11
*** wadim_ <wadim_!~egorov@mail.phycard.de> has joined #yocto06:18
*** DatGizmo <DatGizmo!~mogwai@ip1886d814.dynamic.kabel-deutschland.de> has quit IRC06:23
*** SorenHolm <SorenHolm!~quassel@93.165.148.186> has joined #yocto06:25
*** loggerbox <loggerbox!todor@nat/intel/x-jwyucbpdghbtblld> has quit IRC06:28
*** loggerbox <loggerbox!todor@nat/intel/x-ntexnkbwqgnhpzbn> has joined #yocto06:29
*** shoragan <shoragan!~shoragan@debian/developer/shoragan> has joined #yocto06:33
miandonmenmianAndersD: wow, thanks. i suppose somewhere there has to be. I'm trying to locate the .bb file and location for the python stack. would like to add some more dependencies to python and want to see how the current ones are done06:45
*** volker_123456 <volker_123456!~quassel@host-188-174-253-51.customer.m-online.net> has joined #yocto06:47
*** ant_work <ant_work!~ant__@host222-188-static.61-79-b.business.telecomitalia.it> has joined #yocto06:50
*** imrehg <imrehg!~greg@122.147.15.218> has quit IRC06:52
*** cristianiorga <cristianiorga!~cristiani@134.134.139.76> has quit IRC07:01
*** vquicksilver_ <vquicksilver_!~nobody@gentoo/contributor/vquicksilver> has quit IRC07:10
*** vquicksilver <vquicksilver!~nobody@gentoo/contributor/vquicksilver> has joined #yocto07:11
*** florian <florian!~fuchs@Maemo/community/contributor/florian> has joined #yocto07:14
AndersDWell, usually I end up being lazy and run find to locate the bb-file (or look at the history in git to find the path).07:25
*** mckoan|away is now known as mckoan07:31
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto07:31
mckoangood morning07:31
*** TobSnyder <TobSnyder!~schneider@ip92341b76.dynamic.kabel-deutschland.de> has joined #yocto07:35
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has quit IRC07:36
*** patrickz <patrickz!~Thunderbi@212.118.209.82> has joined #yocto07:41
*** patrickz <patrickz!~Thunderbi@212.118.209.82> has joined #yocto07:45
*** SorenHolm <SorenHolm!~quassel@93.165.148.186> has quit IRC07:57
*** SorenHolm <SorenHolm!~quassel@93.165.148.186> has joined #yocto07:58
*** LocutusOfBorg1 <LocutusOfBorg1!~Gianfranc@93-33-58-76.ip43.fastwebnet.it> has joined #yocto08:00
*** jimBaxter <jimBaxter!~jbaxter@jimbax.plus.com> has joined #yocto08:03
*** jku <jku!jku@nat/intel/x-iggsybbkmhbifxaa> has joined #yocto08:04
*** behanw <behanw!~behanw@12.10.73.130> has quit IRC08:05
*** smustafa <smustafa!~mustafa@110.93.212.98> has joined #yocto08:06
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto08:11
*** _4urele_ <_4urele_!~aurele@srvmail.castel.fr> has quit IRC08:11
bluelightningmorning all08:12
*** GunsNRose <GunsNRose!~GunsNRose@110.184.147.224> has quit IRC08:15
*** diego_r <diego_r!~diego@host65-246-static.10-188-b.business.telecomitalia.it> has joined #yocto08:42
*** maxin <maxin!~majo@sestofw01.enea.se> has joined #yocto08:42
*** _4urele_ <_4urele_!~aurele@srvmail.castel.fr> has joined #yocto08:58
jaz303hello08:59
jaz303how would I go about creating an SD card image that includes a UBI image?09:00
jaz303at the moment I'm flashing the SD card myself and then mounting the rootfs and copying in the UBI image + all the supporting scripts09:01
jaz303i have a dive through the python oe.image module but was a bit out of my depth09:02
jaz303*had09:02
*** jimBaxter__ <jimBaxter__!~jbaxter@jimbax.plus.com> has joined #yocto09:02
*** jimBaxter <jimBaxter!~jbaxter@jimbax.plus.com> has quit IRC09:03
ant_workjaz303: why would you use UBI on an SD?09:05
diego_rHi everybody. Can anybody help me understand what variable FEED_DEPLOYDIR_BASE_URI is supposed to do? I'm using ipk package format and opkg package manager. I expected to find an additional conf file under /etc/opkg/ but no additional file has been placed there after bitbaking09:05
ant_workjaz303: is it to be flashed on nand/nor ?09:05
jaz303ant_work: i want my users to be able to boot from the SD and if they like it they can flash it, yes09:05
*** belen <belen!~Adium@192.198.151.44> has joined #yocto09:05
ant_workah, ok, thne I se09:07
ant_workargh..09:07
ant_workah, ok, then I see09:07
ant_workiirc there are some layers handling complex SD images, if I'm not wrong meta-fsl-arm09:12
*** dv__ is now known as dv_09:18
*** tsramos <tsramos!tsramos@nat/intel/x-nzllwgsmkmwlxvod> has joined #yocto09:22
*** tsramos <tsramos!tsramos@nat/intel/x-nzllwgsmkmwlxvod> has quit IRC09:33
*** tsramos <tsramos!~tsramos@192.55.55.37> has joined #yocto09:34
*** pidge <pidge!~pidge@2a02:8084:0:3000:c159:c7f5:95d9:42ff> has quit IRC09:37
*** pidge <pidge!~pidge@2a02:8084:0:3000:79ad:e357:68a1:683> has joined #yocto09:38
*** tsramos <tsramos!~tsramos@192.55.55.37> has quit IRC09:39
*** hsychla <hsychla!~hsychla@pd95c9392.dip0.t-ipconnect.de> has joined #yocto09:42
*** nighty-_ <nighty-_!~nighty@hokuriku.rural-networks.com> has joined #yocto09:48
*** pidge <pidge!~pidge@2a02:8084:0:3000:79ad:e357:68a1:683> has quit IRC09:51
*** JaMa <JaMa!~martin@ip-86-49-34-37.net.upcbroadband.cz> has joined #yocto09:52
*** AndersD <AndersD!~anders@213-64-219-84-no126.business.telia.com> has quit IRC10:06
*** arfoll_ <arfoll_!arfoll@nat/intel/x-mtaeynkovbgtmnhv> has joined #yocto10:07
*** kanavin__ <kanavin__!~ak@192.55.54.40> has joined #yocto10:07
*** belen1 <belen1!Adium@nat/intel/x-mtlcxwyhjojhsoxf> has joined #yocto10:08
*** blitz00__ <blitz00__!stefans@nat/intel/x-txnhdxpptiuuqnjq> has joined #yocto10:08
*** AndersD <AndersD!~anders@213-64-219-84-no126.business.telia.com> has joined #yocto10:08
*** blitz00_ <blitz00_!stefans@nat/intel/x-xtgasgulsyiwpepu> has quit IRC10:09
*** arfoll <arfoll!arfoll@nat/intel/x-khidkfxjyaujgydr> has quit IRC10:09
*** kanavin_ <kanavin_!ak@nat/intel/x-smiipwrvvfawubza> has quit IRC10:09
*** jku <jku!jku@nat/intel/x-iggsybbkmhbifxaa> has quit IRC10:09
*** belen <belen!~Adium@192.198.151.44> has quit IRC10:10
*** lpapp <lpapp!~lpapp@kde/lpapp> has joined #yocto10:24
lpappgood morning10:24
lpappwhen migrating to Daisy from Dylan, I can see this, but nothing in the migration guide: WARNING: Building libpam but 'pam' isn't in DISTRO_FEATURES, PAM won't work correctly10:24
lpappthis is the only entry in the migration guide: libpam: Deny all services for the OTHER entries.10:24
*** ddom <ddom!~ddom@p4FFD96BC.dip0.t-ipconnect.de> has joined #yocto10:26
bluelightninglpapp: somewhere a dependency on libpam exists that is not conditional on pam being in DISTRO_FEATURES; you should find it and eliminate it10:29
lpappit is probably our software, but pam is not option for that.10:30
bluelightningif by that you mean it's required, then you should add pam to your DISTRO_FEATURES value10:31
joshuaglwk10:31
mckoanI've a couple of questions about 'dizzy'10:36
mckoanthe command 'hystory' is no longer available on generated fs, what's missing?10:36
mckoanthe 'opkg-target' command is no longer generated in minimal-image, what's missing?10:37
lpappbluelightning: ok, thanks; interesting that this transition step is not documented.10:39
lpappor I may be missing something.10:39
bluelightninglpapp: it's not that we added a new requirement, we probably just added a check, the issue was probably always there10:40
lpappstill, it could have been put in there.10:41
lpappso this will do it? DISTRO_FEATURES_append = " largefile --disable-zlib pam"10:42
*** nerdboy <nerdboy!~sarnold@gentoo/developer/nerdboy> has quit IRC10:42
diego_rsorry if I ask again, but maybe not everybody read. Can anybody help me understand what variable FEED_DEPLOYDIR_BASE_URI is supposed to do? I'm using ipk package format and opkg package manager. I expected to find an additional conf file under /etc/opkg/ but no additional file has been placed there after bitbaking my image10:44
mckoanI mean, are those removed features in 'dizzy' ?10:45
bluelightninglpapp: er, --disable-zlib doesn't belong in there10:50
bluelightninglpapp: otherwise, yes10:50
lpappwhy?10:50
bluelightningbecause nothing will check for that?10:50
lpappso why is it in there?10:50
bluelightningI'm not sure, it's your line that's adding it10:50
bluelightningcould be that somewhere a check was added for it in your custom metadata, but I wouldn't have thought so10:51
*** miandonmenmian <miandonmenmian!~miandonme@210.22.153.182> has quit IRC10:52
*** miandonmenmian <miandonmenmian!~miandonme@140.206.114.194> has joined #yocto10:57
*** nerdboy <nerdboy!~sarnold@gatekeeper.gentoogeek.org> has joined #yocto10:57
lpappbluelightning: hmm, it was not used even at the denzil era?11:11
bluelightninglpapp: no, we wouldn't use that syntax in DISTRO_FEATURES11:12
*** mchehab <mchehab!~mchehab@201-67-29-182.bsace703.dsl.brasiltelecom.net.br> has joined #yocto11:14
lpappok :)11:14
lpappthanks.11:14
*** ionte_ <ionte_!uid48103@gateway/web/irccloud.com/x-lrxgnsrfigtcrocc> has joined #yocto11:17
*** JYDawg <JYDawg!~jydawg@jydawg.xs4all.nl> has joined #yocto11:25
JYDawghullo11:25
*** chankit1 <chankit1!~oneam@203.106.195.178> has joined #yocto11:25
*** neur0Fuzzy <neur0Fuzzy!~neur0Fuzz@p239.net182021249.tokai.or.jp> has quit IRC11:26
*** jku <jku!jku@nat/intel/x-jkvfzqavtnijonxq> has joined #yocto11:27
JYDawgis there a parser for bitbake recipes that allows me e.g. to get the dump as a dictionary in python?11:28
JYDawgor the entire layer for that matter11:28
LetoThe2ndJYDawg: hm, the information you're looking for might already be contained in bitbake -e11:33
rink_you can try 'bitbake -e <receipe>'11:33
LetoThe2ndcan be spammy, though :)11:33
JYDawgoke11:33
JYDawglessee11:34
rink_but it depends on what you need11:34
JYDawgwe have several developers in the same layers and I'd like to be able to make sure they increase the package versions where needed. The other issue is that I'd like to be able to make package patches from builds but thats another item.11:37
* rink_ never increments package versions when adding patches and stuff... it's amazing how well the dependency tracking in bitbake works11:39
*** manuel__ <manuel__!~manuel@c-24-61-40-209.hsd1.ma.comcast.net> has joined #yocto11:41
JYDawgbuildserver has a load of 55. This may take a while11:44
JYDawgdoes bitbake have a python lib backend or sumsuch?11:45
*** varibull <varibull!~varibull@ta.tainstruments.com> has joined #yocto11:47
*** vmeson <vmeson!~rmacleod@24-212-184-107.cable.teksavvy.com> has quit IRC11:54
*** jku <jku!jku@nat/intel/x-jkvfzqavtnijonxq> has quit IRC11:57
*** jku <jku!jku@nat/intel/x-vhejwllyffsthwvx> has joined #yocto11:57
*** jku <jku!jku@nat/intel/x-vhejwllyffsthwvx> has quit IRC12:02
RPJaMa: thanks for the reminder about the fontconfig patch. I want to talk to rburton about it and check his concern was addressed but will merge as soon as I can to do (or give feedback)12:03
* RP really needs to get a better process around this...12:04
bluelightningJYDawg: there is "tinfoil" that allows accessing some of the internals e.g. parsing12:07
bluelightningJYDawg: here's an example of using it: https://gist.github.com/bluelightning/613898012:09
*** jku <jku!jku@nat/intel/x-mdpbsestgbepihzw> has joined #yocto12:15
miandonmenmiani've got a layer working, where can i set distro params on my layer to override current default ones?12:17
bluelightningmiandonmenmian: add a conf/distro/yourdistroname.conf with the settings you want, and then set DISTRO = "yourdistroname" in conf/local.conf12:20
bluelightningmiandonmenmian: http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#creating-your-own-distribution12:20
miandonmenmianbluelightning: thanks a bunch. i've also had some trouble setting maintainer on per package basis. isnt it suposed to be MAINTAINER= " " on the .bb ?12:21
*** pidge <pidge!~pidge@2a02:8084:0:3000:79ad:e357:68a1:683> has joined #yocto12:22
bluelightningmiandonmenmian: where are you expecting the MAINTAINER value to show up?12:23
miandonmenmianon opkg12:23
lpappbluelightning:  ELF binary '<file>' has relocations in .text [textrel] from here: http://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html -> What would be the solution suggested? -fPIC/-fpic or something else?12:26
bluelightningmiandonmenmian: well, near as I can tell, setting it in the recipe should affect any packages produced; it may be that just changing MAINTAINER doesn't trigger do_package to re-execute though, I'm not sure12:26
bluelightninglpapp: I believe so yes12:27
lpappbluelightning: could be put into the document as a hint, no?12:28
bluelightninglpapp: http://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#qa-issue-textrel could be extended yes12:29
*** vmeson <vmeson!~rmacleod@128.224.252.2> has joined #yocto12:30
lpappok, thanks12:32
JaMaRP: thanks12:34
bluelightninglpapp: thanks for filing, i can remove that from my todo list now ;)12:35
JaMaRP: this one is only 1 week old, but also didn't get any feedback (nor is in master-next) http://lists.openembedded.org/pipermail/openembedded-core/2015-April/103684.html12:35
lpappbluelightning: :D np.12:41
*** tsramos <tsramos!~tsramos@134.134.137.75> has joined #yocto12:47
*** nighty^ <nighty^!~nighty@static-68-179-124-161.ptr.terago.net> has joined #yocto12:52
*** kscherer <kscherer!~kscherer@128.224.252.2> has joined #yocto12:53
JYDawgbluelightning: nice, starting to look a lot like what I need.12:53
lpappbluelightning: I am getting some strange warnings, https://paste.kde.org/proplo3gj12:55
RPJaMa: didn't see that one for some reason. Have replied suggesting a minor tweak to the naming12:56
bluelightninglpapp: there was a regression a while ago where we now expect everything added to ROOTFS_POSTPROCESS_COMMAND to be a function rather than a plain command12:56
*** jku <jku!jku@nat/intel/x-mdpbsestgbepihzw> has quit IRC12:57
miandonmenmianbluelightning: followed the process, seems the layer is found alltogether with packages, that individually do well. however, image is not. set the distro as per the guide link you shared didnt work for me. do i need to refresh the cache for the distro to appear?12:57
bluelightninglpapp: I suppose we should probably fix it, but then again using functions is generally a better way to structure things there12:57
bluelightningmiandonmenmian: what exactly is failing? I'm not quite following...12:59
miandonmenmianbitbake mydistro does not exist12:59
bluelightningmiandonmenmian: that isn't generally expected to work13:00
lpappbluelightning: should probably also be documented in the migration guide?13:00
miandonmenmiannot expected to work as in will have problems? or as in nothing will happen?13:00
bluelightningmiandonmenmian: a distro is a set of configuration values that you can select through DISTRO, it's not a target you can build13:00
bluelightningmiandonmenmian: what I suspect you want in addition is to define a custom image recipe containing the packages you want13:01
bluelightninglpapp: well, not if it's a bug that we should fix, no13:01
*** SorenHolm <SorenHolm!~quassel@93.165.148.186> has quit IRC13:02
miandonmenmianbluelightning: BBFILE_COLLECTIONS ?13:02
*** manuel__ <manuel__!~manuel@c-24-61-40-209.hsd1.ma.comcast.net> has quit IRC13:03
miandonmenmiandoes that refer to the set of configuration for the distro? or i need to look for this inside the distro.conf file?13:03
miandonmenmianbluelightning: ok, i will take a look at your second suggestion, seems like that is exactly what i need13:04
bluelightningmiandonmenmian: if you haven't already seen it - http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#usingpoky-extend-customimage13:04
lpappbluelightning: is it a bug or feature? ^_^13:05
lpappeither way, report is neded for either? Is there one already to fix this regression?13:06
bluelightninglpapp: it seems like a regression to me, if you could file a bug that would be great13:07
*** melio_cc <melio_cc!~melio_cc@static-194-113-26-69.axsne.net> has joined #yocto13:10
*** melio_cc <melio_cc!~melio_cc@static-194-113-26-69.axsne.net> has quit IRC13:11
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto13:12
*** melio_cc <melio_cc!~melio_cc@static-194-113-26-69.axsne.net> has joined #yocto13:12
*** ntl <ntl!~ntl@99-127-51-4.lightspeed.austtx.sbcglobal.net> has quit IRC13:14
*** melio_cc_ <melio_cc_!~melio_cc@static-194-113-26-69.axsne.net> has joined #yocto13:14
*** melio_cc <melio_cc!~melio_cc@static-194-113-26-69.axsne.net> has quit IRC13:14
*** smustafa <smustafa!~mustafa@110.93.212.98> has quit IRC13:16
*** tasslehoff <tasslehoff!~Tasslehof@82.147.55.166> has joined #yocto13:17
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has quit IRC13:17
*** realBigfoot <realBigfoot!~realBigfo@134.191.220.74> has joined #yocto13:18
lpappbluelightning: submitted, thanks.13:25
*** ntl <ntl!~ntl@99-127-51-4.lightspeed.austtx.sbcglobal.net> has joined #yocto13:25
*** LongQi <LongQi!9b45e1ae@gateway/web/freenode/ip.155.69.225.174> has joined #yocto13:26
LongQican the target Runtime Package Management install .deb or .rpm from existed distribution repository?13:30
LongQiif they have same CPU architecture.13:31
LongQior we must build our own repository?13:31
*** realBigfoot <realBigfoot!~realBigfo@134.191.220.74> has quit IRC13:35
mckoanthe history command is still present but the list of commands is not persistent, how can I enable it?13:36
*** realBigfoot <realBigfoot!~realBigfo@134.191.220.74> has joined #yocto13:38
*** fray <fray!~mhatle@192.40.192.95> has joined #yocto13:39
*** ionte_ <ionte_!uid48103@gateway/web/irccloud.com/x-lrxgnsrfigtcrocc> has quit IRC13:40
*** lexano <lexano!~lexano@CPEa021b7ac59c9-CMbcc81006f6ee.cpe.net.cable.rogers.com> has joined #yocto13:41
*** manuel__ <manuel__!~manuel@209.6.175.242> has joined #yocto13:43
*** e8johan <e8johan!~quassel@83.218.80.242> has quit IRC13:44
miandonmenmiani'm building a package that installs a file, without do_compile. the file is located on the recipe/files and im calling it with SRC_URI = "file://myfile"13:46
miandonmenmianinstall -m 644 ${WORKDIR}/myfile ${D}/usr/lib/myDestinationFolder13:47
miandonmenmianis this wrong? my package is built empty13:47
lpappbluelightning: it does not matter whether it is a python or bash function?13:47
*** kapare <kapare!~kapare@mail.rogue-research.com> has joined #yocto13:48
*** timsche <timsche!~quassel@port-92-192-16-94.dynamic.qsc.de> has joined #yocto13:53
*** mchehab <mchehab!~mchehab@201-67-29-182.bsace703.dsl.brasiltelecom.net.br> has quit IRC13:59
bluelightninglpapp: that is one of the things we gained in exchange for the regression, yes14:00
*** AndersD <AndersD!~anders@213-64-219-84-no126.business.telia.com> has quit IRC14:01
lpappbluelightning: how can I assign a function to a variable?14:02
lpappis there an example somewhere?14:02
lpappjust pass the function name along?14:02
bluelightningmiandonmenmian: you will need to add that path to FILES_${PN} i.e. FILES_${PN} += "${libdir}/myDestinationFolder" (and use ${libdir} rather than /usr/lib in your install command14:02
bluelightninglpapp: ROOTFS_POSTPROCESS_COMMAND is still semicolon-separated, that hasn't changed14:03
*** LongQi <LongQi!9b45e1ae@gateway/web/freenode/ip.155.69.225.174> has quit IRC14:03
lpappso the function names separated by semicolon?14:03
bluelightningyes14:04
lpappthank you very much14:04
*** mchehab <mchehab!~mchehab@201-67-29-182.bsace703.dsl.brasiltelecom.net.br> has joined #yocto14:05
*** tasslehoff <tasslehoff!~Tasslehof@82.147.55.166> has quit IRC14:08
miandonmenmianbluelightning: add the file to path for the do_install function ?14:10
bluelightningmiandonmenmian: no, outside of it14:10
bluelightningmiandonmenmian: assuming you were asking where to put this FILES_${PN} line14:12
*** tsramos <tsramos!tsramos@nat/intel/x-euduksnzoydgkkwp> has joined #yocto14:12
miandonmenmianyes, that is right, sorry. However, i am not sure I understand it:14:13
miandonmenmianthe source SRC_URI += "file://myfile" assumes the recipe folder?14:13
*** wadim_ <wadim_!~egorov@mail.phycard.de> has quit IRC14:14
miandonmenmiani was worried the file was lost on {WORKDIR} since there are no other sources. perhaps the line should be SRC_URI =14:14
bluelightningmiandonmenmian: myfile should be placed in a directory next to the recipe, named either the same as the recipe, or "files"14:14
miandonmenmianbluelightning: ok, well, at least got that right :S14:14
*** tomz <tomz!trz@nat/intel/x-nhzxkkmesqxlbjdu> has left #yocto14:15
miandonmenmiansomehow, on verbose, bitbake is still looking for sstate folder sources14:17
miandonmenmianpackage is built empty14:18
bluelightningmiandonmenmian: something is still wrong with your FILES line then, it's not matching up14:19
bluelightningmiandonmenmian: just checking, are you using Toaster or oe-init-build-env-memres?14:20
*** kapare <kapare!~kapare@mail.rogue-research.com> has quit IRC14:20
miandonmenmianoe-init-build-env14:20
bluelightningmiandonmenmian: would you be prepared to pastebin your recipe?14:21
miandonmenmianshould've done that before. sorry. give me a sec14:21
*** madisox <madisox!~madison@64-71-1-115.static.wiline.com> has joined #yocto14:22
*** hamis <hamis!~irfan@110.93.212.98> has quit IRC14:23
miandonmenmianbluelightning: http://apaste.info/4mh14:25
*** lexano <lexano!~lexano@CPEa021b7ac59c9-CMbcc81006f6ee.cpe.net.cable.rogers.com> has quit IRC14:26
*** geheimnis` <geheimnis`!~geheimnis@23.226.237.192> has quit IRC14:26
*** lexano <lexano!~lexano@CPEa021b7ac59c9-CMbcc81006f6ee.cpe.net.cable.rogers.com> has joined #yocto14:28
*** geheimnis` <geheimnis`!~geheimnis@23.226.237.192> has joined #yocto14:28
bluelightningmiandonmenmian: you need an install -d command to create the ${D}${libdir}/python-2.7 directory14:31
*** shinobi <shinobi!~shinobi@78.176.131.144> has joined #yocto14:31
bluelightningmiandonmenmian: also you should be doing FILES_${PN} += not = (although that won't make much difference in this case, but it's good practice)14:31
miandonmenmianbluelightning: tried that as well. however, another package should be bcreating this directory14:31
*** shinobi <shinobi!~shinobi@78.176.131.144> has left #yocto14:31
bluelightningmiandonmenmian: doesn't matter, this recipe builds in isolation as far as the install step is concerned14:32
miandonmenmiani'm reading another doc that adds the asterisk at the end for the FILES line.  ${libdir}/lib*.so.* \   does the myfile have to be included here? or just the path ?14:32
bluelightningmiandonmenmian: the path is sufficient14:32
bluelightningmiandonmenmian: you shouldn't be inheriting autotools or gettext for this recipe either14:33
miandonmenmianah, that is a very good point14:33
bluelightningyou do have a closing } at the end of do_install as well right?14:34
miandonmenmianoh, brother...14:35
miandonmenmianthanks a bunch bluelightning, that was probably it14:36
bluelightningit's curious that that didn't trigger an error14:36
miandonmenmiani was wondering as well. but i'm pretty certain i have not seen any with regards to the do install or brackets14:37
*** lamego <lamego!jalamego@nat/intel/x-jblcerybigxewevt> has joined #yocto14:41
*** TuTizz <TuTizz!~TuTizz@unaffiliated/tutizz> has joined #yocto14:48
*** florian <florian!~fuchs@Maemo/community/contributor/florian> has quit IRC14:48
*** tsramos <tsramos!tsramos@nat/intel/x-euduksnzoydgkkwp> has quit IRC14:49
*** tsramos <tsramos!~tsramos@134.134.137.75> has joined #yocto14:49
*** tsramos <tsramos!~tsramos@134.134.137.75> has quit IRC14:51
*** tsramos <tsramos!tsramos@nat/intel/x-ethbkbbbdrqqgdmq> has joined #yocto14:51
bluelightningafter reproducing the lack of error I filed a bug: https://bugzilla.yoctoproject.org/show_bug.cgi?id=763314:52
yoctiBug 7633: normal, Undecided, ---, richard.purdie, NEW , Parser does not error out on unclosed function14:52
timschehey guys, i'm trying to build yocto for rpi with qt5. so i'm using poky master, meta-qt5 master, meta-raspberrypi master and meta-openembedded master.14:55
timschemy bblayers.conf goes like http://apaste.info/pI0 , while my local.conf goes like http://apaste.info/qcU .14:55
timscheqtbase fails to compile - the error log goes here http://apaste.info/DIT .14:55
timschedid anyone of you succeed in building this configuration? any opinions?14:55
timscheand i forgot to mention that i've edited qtbase.inc to use gles2 instead of desktop gl14:57
*** mario-goulart <mario-goulart!~user@email.parenteses.org> has quit IRC14:58
*** mchehab <mchehab!~mchehab@201-67-29-182.bsace703.dsl.brasiltelecom.net.br> has quit IRC15:15
*** Aethenelle <Aethenelle!~Aethenell@199.15.128.78> has joined #yocto15:19
*** SorenHolm <SorenHolm!~quassel@5634f191.rev.stofanet.dk> has joined #yocto15:25
lpappbluelightning: I am getting this, WARNING: libstdc++-4.8.2 was registered as shlib provider for libstdc++.so.6, changing it to foo-0.1 because it was built later15:26
lpappI wonder hwy15:26
lpappwhy*15:26
*** behanw <behanw!~behanw@167.220.23.56> has joined #yocto15:26
bluelightninglpapp: is foo-0.1 is installing its own libstdc++.so.6?15:26
lpappnot as far as I am aware of.15:27
bluelightningthe warning would suggest that it is15:27
lpappoh, wow, it does15:27
lpapphow nasty15:27
lpappthis is not what I agreed with my colleague :P15:28
*** behanw <behanw!~behanw@167.220.23.56> has quit IRC15:33
*** SorenHolm <SorenHolm!~quassel@5634f191.rev.stofanet.dk> has quit IRC15:33
*** behanw <behanw!~behanw@167.220.23.56> has joined #yocto15:34
*** tsramos <tsramos!tsramos@nat/intel/x-ethbkbbbdrqqgdmq> has quit IRC15:39
*** tsramos <tsramos!tsramos@nat/intel/x-qpweyulhaqwzcymf> has joined #yocto15:40
*** SorenHolm <SorenHolm!~quassel@5634f191.rev.stofanet.dk> has joined #yocto15:40
*** tsramos <tsramos!tsramos@nat/intel/x-qpweyulhaqwzcymf> has quit IRC15:44
*** TobSnyder <TobSnyder!~schneider@ip92341b76.dynamic.kabel-deutschland.de> has quit IRC15:46
ericbuttershi. i simply want to build my linux kernel. i use an external toolchain. i only do: bitbake virtual/kernel -- and that works. but why there are 457 tasks installing i.e binutils-native, so *-native* packages? is this really needed to just compile my kernel? how to remove unused stuff? can i blacklist this?15:48
*** aehs29 <aehs29!~aehernan@134.134.139.72> has joined #yocto15:53
*** SorenHolm <SorenHolm!~quassel@5634f191.rev.stofanet.dk> has quit IRC15:57
*** sameo <sameo!samuel@nat/intel/x-zldxmzcqhunvsssq> has joined #yocto15:57
*** mckoan is now known as mckoan|away15:57
-YoctoAutoBuilder- build #266 of nightly-ppc-lsb is complete: Failure [failed] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-ppc-lsb/builds/26615:57
*** fitzsim` <fitzsim`!~user@2001:420:284a:1300:21c:c4ff:fe73:2d74> has quit IRC15:58
-YoctoAutoBuilder- build #266 of nightly-fsl-ppc is complete: Failure [failed BuildImages Building Toolchain Images Building Toolchain Images_1] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-fsl-ppc/builds/26615:59
-YoctoAutoBuilder- build #270 of nightly-fsl-ppc-lsb is complete: Failure [failed BuildImages] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-fsl-ppc-lsb/builds/27015:59
*** sameo <sameo!samuel@nat/intel/x-zldxmzcqhunvsssq> has quit IRC16:06
*** lamego <lamego!jalamego@nat/intel/x-jblcerybigxewevt> has quit IRC16:09
*** lamego <lamego!jalamego@nat/intel/x-gkzxxvorfboehlve> has joined #yocto16:13
*** smustafa <smustafa!~mustafa@39.42.58.142> has joined #yocto16:23
*** sarahsharp <sarahsharp!~sarah@134.134.139.72> has joined #yocto16:25
*** jku <jku!~jku@212-149-207-214.bb.dnainternet.fi> has joined #yocto16:26
*** jku <jku!~jku@212-149-207-214.bb.dnainternet.fi> has joined #yocto16:27
*** sjolley <sjolley!~sjolley@134.134.137.75> has quit IRC16:28
*** ddom <ddom!~ddom@p4FFD96BC.dip0.t-ipconnect.de> has quit IRC16:29
*** aehs29 <aehs29!~aehernan@134.134.139.72> has quit IRC16:31
*** SoylentYellow <SoylentYellow!~SoylentYe@209-234-137-234.static.twtelecom.net> has joined #yocto16:33
*** todor <todor!todor@nat/intel/x-rgvspybrsetgteow> has joined #yocto16:33
*** sarahsharp <sarahsharp!~sarah@134.134.139.72> has quit IRC16:35
*** varibull <varibull!~varibull@ta.tainstruments.com> has quit IRC16:36
*** varibull <varibull!~varibull@ta.tainstruments.com> has joined #yocto16:36
lpapphmm, renaming yocto based repositories with ain't fun.16:39
lpappsadly, git will not do renaming of a directory with more than 4K files without further trouble and it seems the poky repository has far more than that file amount.16:39
lpappbluelightning: so is it ok to use PRIVATE_LIBS then?16:51
lpappit would be less work for me now than refactoring the system with testing.16:51
bluelightningyou probably should yes16:52
bluelightningthough it probably won't change the behaviour since it appears to have acknowledged your "custom" version of the lib16:52
lpappyes, that is fine, I just want to get rid of the warning.16:53
kergothericbutters: i'd say use bitbake -g, possibly with depexp, to explore the dependency graph to determine that. e.g. bitbake -g -u depexp virtual/kernel16:54
*** anselmolsm <anselmolsm!~anselmols@192.55.55.37> has joined #yocto16:56
*** belen1 <belen1!Adium@nat/intel/x-mtlcxwyhjojhsoxf> has quit IRC16:56
*** dmoseley <dmoseley!~dmoseley@cpe-174-96-222-251.carolina.res.rr.com> has quit IRC16:57
*** belen1 <belen1!Adium@nat/intel/x-wxttlqosgcltthpr> has joined #yocto16:59
*** sjolley <sjolley!~sjolley@134.134.139.70> has joined #yocto16:59
*** anselmolsm <anselmolsm!~anselmols@192.55.55.37> has quit IRC17:02
*** anselmolsm <anselmolsm!anselmolsm@nat/intel/x-iymgjfpguamvokva> has joined #yocto17:02
*** AndersD <AndersD!~anders@c-89-160-69-55.cust.bredband2.com> has joined #yocto17:05
*** belen1 <belen1!Adium@nat/intel/x-wxttlqosgcltthpr> has quit IRC17:06
*** AndersD <AndersD!~anders@c-89-160-69-55.cust.bredband2.com> has quit IRC17:10
*** AndersD <AndersD!~anders@213-64-219-84-no126.business.telia.com> has joined #yocto17:10
*** sarahsharp <sarahsharp!sarah@nat/intel/x-fwjmndlhwainjcid> has joined #yocto17:11
lpappbluelightning: if you had not seen it, https://bugzilla.yoctoproject.org/show_bug.cgi?id=763217:26
yoctiBug 7632: normal, Undecided, ---, scott.m.rifenbark, NEW , ROOTFS_POSTPROCESS_COMMAND no longer accepts raw commands, just functions17:26
lpappbluelightning: which file shall I put into PRIVATE_LIBS, the library with the symlinks, too?17:27
lpappthere are two symlinks created by the recipe to the library.17:27
bluelightningjust the library I believe17:27
*** diego_r <diego_r!~diego@host65-246-static.10-188-b.business.telecomitalia.it> has quit IRC17:27
lpappso libstdc++.so -> libstdc++.so.6 -> libstdc++.so.6.0.1017:27
lpappbluelightning: so in my case libstdc++.so.6.0.10 or libstdc++.so?17:29
lpapphttp://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#var-PRIVATE_LIBS -> this seems to use the .so files.17:30
lpappnot the versioned ones.17:30
lpappI wonder if that is intentional or just coincidence.17:30
bluelightningnot sure, sorry17:30
lpappok, I will keep trying until the warning is gone.17:31
*** aehs29 <aehs29!aehernan@nat/intel/x-bztibpgckhchdipv> has joined #yocto17:33
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC17:34
*** timsche <timsche!~quassel@port-92-192-16-94.dynamic.qsc.de> has quit IRC17:38
*** Aethenelle <Aethenelle!~Aethenell@199.15.128.78> has quit IRC17:48
*** AndersD <AndersD!~anders@213-64-219-84-no126.business.telia.com> has quit IRC18:04
*** ddom <ddom!~ddom@ip-37-24-103-185.hsi14.unitymediagroup.de> has joined #yocto18:09
*** SoylentYellow <SoylentYellow!~SoylentYe@209-234-137-234.static.twtelecom.net> has quit IRC18:13
*** trip0 <trip0!~tripzero@134.134.139.72> has joined #yocto18:22
trip0what is the status of fido?  Is it too late to pull in the latest bluez (5.30)?18:23
*** SoylentYellow <SoylentYellow!~SoylentYe@209-234-137-234.static.twtelecom.net> has joined #yocto18:30
lpappdoes the Yocto build bail out with failure if a patch cannot be applied?18:31
kergothif a patch can't be applied, the do_patch task will fail. bitbake will then cleanly shut down, letting the other currently running tasks finish, and then exit non-zero, unless you run with bitbake -k, in which case it will continue running as many tasks as it's possible to run given the task that failed, and will then exit non-zero18:32
kergoththe -k argument came from gnu make, which has similar behavior18:33
lpappok, thanks.18:38
lpappI updated from dylan to daisy and the build succeeds, but my kernel will no longer boot18:39
lpappit hungs up at the state of "Uncompressing Linux... done, booting the kernel."18:39
lpappwe have our own kernel recipe, not sharing it with Yocto18:39
lpappand after the upgrade, we did not change that, so I am surprised that it is broken.18:39
kergothpossibly a toolchain version problem, assuming the kenrel hasn't changed18:40
lpappperhaps the kernel was created properly, but the image not?18:40
kergoththere have definitely been issues with certain gcc versions and the kernel18:40
lpappI guess I would need to look into the the log.*?18:40
*** jimBaxter__ <jimBaxter__!~jbaxter@jimbax.plus.com> has quit IRC18:40
kergoththat's a possibility too, but if it stops that early, i doubt it got far enough to run init in the rootfs18:40
lpapphmm, I would not know how to proceed from there as I am not the kernel developer in here.18:40
kergothunless you're passing quiet in the cmdline18:40
kergothin which case you should remove that so you can see more of what's going on18:41
lpappoh, kernelopts=rw rootwait quiet18:41
lpappuboot has that, indeed18:41
lpappgood idea :)18:41
lpapp(to check it)18:41
*** sarahsharp <sarahsharp!sarah@nat/intel/x-fwjmndlhwainjcid> has quit IRC18:41
kergoth:)18:41
lpappthe bootlog seems to be the same without that, too :( https://paste.kde.org/pktk6fov518:42
lpappI wonder how to proceed from here. I wish I had more low-level Linux kernel experience.18:43
lpappthere must be some command line option to turn more logging on18:43
kergothmy *guess* would be a possibly miscompiled kernel, assuming you're using an internal toolchain18:43
kergothyeah, should be able to crank up console printk log level18:43
kergothi don't recall the exact syntax offhand, though18:43
lpappI am using the toolchain that Yocto generates.18:44
lpappbut I can double check the log.do_compile file for the kernel18:44
lpapphmm, sadly not built with VERBOSE=118:45
lpappNOTE: make -j 8 uImage CC=arm-foo-linux-gnueabi-gcc  -mno-thumb-interwork -marm LD=arm-foo-linux-gnueabi-ld.bfd18:45
lpappthis is the best I can get out of it.18:46
kergothnot sure if that'll change anything, usually such bugs will just be a bad interaction between gcc and the kernel resulting in something ending up miscompiled, but no indication of such in the gcc output. i don't know of any specific bugs like that offhand, but i've seen them before. usually the kernel will end up with a fix to adjust for it later on. could check the kernel log for after your version, i suppose18:46
lpappthere is this in the compilation log, but I am not sure if it can be ignored: WARNING: modpost: Found 1 section mismatch(es).18:46
kergothalso don't know what version of gcc was used in your previous poky version vs current18:46
*** SoylentYellow <SoylentYellow!~SoylentYe@209-234-137-234.static.twtelecom.net> has quit IRC18:46
lpappme neither, I would need to look it up, but it was a dylan to daisy change18:47
kergothno idea, unfortunately. been long enough since i've done any kernel development that those skills are all atrophied and out of date :)18:47
kergothmight be something else, this was all that came to mind as a possibility18:47
* kergoth shrugs18:47
lpappok, thank you18:48
lpappI will probably ask this in #kernelnewbies, too18:48
lpappthey might be less rusty than us :P18:48
*** bluelightning <bluelightning!~paul@2001:8b0:258:7d7a:2ad2:44ff:fe40:9209> has joined #yocto18:53
*** bluelightning <bluelightning!~paul@2001:8b0:258:7d7a:2ad2:44ff:fe40:9209> has quit IRC18:53
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto18:53
*** nerdboy <nerdboy!~sarnold@gatekeeper.gentoogeek.org> has quit IRC18:57
*** nerdboy <nerdboy!~sarnold@gentoo/developer/nerdboy> has joined #yocto18:57
*** SoylentYellow <SoylentYellow!~SoylentYe@209-234-137-234.static.twtelecom.net> has joined #yocto19:00
*** vmeson <vmeson!~rmacleod@128.224.252.2> has quit IRC19:10
*** lpapp <lpapp!~lpapp@kde/lpapp> has quit IRC19:11
*** vmeson <vmeson!~rmacleod@128.224.252.2> has joined #yocto19:13
*** ddalex1 <ddalex1!~ddalex@154.58.102.3> has joined #yocto19:27
*** jku <jku!~jku@212-149-207-214.bb.dnainternet.fi> has quit IRC19:30
-YoctoAutoBuilder- build #268 of nightly-qa-logrotate is complete: Failure [failed Running Sanity Tests] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-qa-logrotate/builds/26819:37
kergothHmm, I should propose adding 'd' to event handlers, the way it's available elsewhere and via e.data, just as a convenience19:40
*** sarahsharp <sarahsharp!sarah@nat/intel/x-bekzunrshhzvojdm> has joined #yocto19:41
*** smustafa <smustafa!~mustafa@39.42.58.142> has quit IRC19:42
kergothshould also propose including the cooker's expanded_data in the ConfigParsed event19:46
*** evanp_ <evanp_!evan@nat/intel/x-ffatingvmvuhlpps> has quit IRC19:46
kergothboth would simplify some event handlers somewhat19:47
* kergoth adds todo19:47
*** sarahsharp <sarahsharp!sarah@nat/intel/x-bekzunrshhzvojdm> has quit IRC19:49
*** SorenHolm <SorenHolm!~quassel@5634f191.rev.stofanet.dk> has joined #yocto19:53
*** madisox <madisox!~madison@64-71-1-115.static.wiline.com> has quit IRC20:03
*** ionte_ <ionte_!uid48103@gateway/web/irccloud.com/x-kigfngfzopwwhnxk> has joined #yocto20:05
*** sarahsharp <sarahsharp!sarah@nat/intel/x-tyhbfsuqkrhgvjbm> has joined #yocto20:20
*** madisox <madisox!~madison@64-71-1-114.static.wiline.com> has joined #yocto20:21
*** vmeson <vmeson!~rmacleod@128.224.252.2> has quit IRC20:27
* kergoth moves the meta-sourcery sanity checks from BuildStarted to TreeDataPreparationStarted20:29
*** ddom <ddom!~ddom@ip-37-24-103-185.hsi14.unitymediagroup.de> has quit IRC20:37
*** Aethenelle <Aethenelle!~Aethenell@199.15.128.78> has joined #yocto20:40
*** madisox <madisox!~madison@64-71-1-114.static.wiline.com> has quit IRC20:50
*** ant_home <ant_home!~ant__@host231-254-dynamic.11-79-r.retail.telecomitalia.it> has joined #yocto20:58
*** varibull <varibull!~varibull@ta.tainstruments.com> has quit IRC21:01
*** varibull <varibull!~varibull@ta.tainstruments.com> has joined #yocto21:01
*** madisox <madisox!~madison@64-71-1-115.static.wiline.com> has joined #yocto21:07
*** sarahsharp <sarahsharp!sarah@nat/intel/x-tyhbfsuqkrhgvjbm> has quit IRC21:07
*** khem` <khem`!~khem@unaffiliated/khem> has joined #yocto21:12
*** _dv_ <_dv_!~quassel@chello062178118086.5.14.vie.surfer.at> has joined #yocto21:22
*** dv_ <dv_!~quassel@chello062178118086.5.14.vie.surfer.at> has quit IRC21:22
*** anselmolsm <anselmolsm!anselmolsm@nat/intel/x-iymgjfpguamvokva> has quit IRC21:25
*** anselmolsm <anselmolsm!~anselmols@192.55.54.36> has joined #yocto21:26
khem`Can we generate a rootfs tar with symbols and debug info and then strip it for final image ?21:29
khem`current tarball is as much stripped as any other image fs type21:30
kergothnot that i know of, but work has been done on generating a separate filesystem with just the -dbg packages installed, so you can point gdb at that. not sure if that was ever merged, however21:40
khem`do you have links21:40
kergothchecking for it now21:40
khem`it should be like21:40
khem`IMAGE_FSTYPES21:41
kergothfs types just control archival of the fs, that's too late to change their content21:41
*** Aethenelle <Aethenelle!~Aethenell@199.15.128.78> has quit IRC21:41
khem`I meant from usability POV21:42
khem`underneath I agree21:42
*** dmoseley <dmoseley!~dmoseley@cpe-174-96-222-251.carolina.res.rr.com> has joined #yocto21:42
kergothyou can alwyas add dbg-pkgs to IMAGE_FEATURES< but of course that affects every output of the image21:42
kergothth enice thing about a separate debug fs is you can e.g. put it on a usb stick, or just extrac tit to point gdb at when you connect to gdbserver21:43
kergothlooking for the patch/branch now21:43
khem`exactly21:43
khem`I want the images to be stripped but corresponding debug rootfs image in tarball21:44
khem`so folks can use it to debug the crash by booting from USB and so on21:44
kergothwe rolled our own version of it in meta-mentor a while ago, but the pending one sent to the list is cleaner, if i can track the damn thing down21:45
kergothi need to start jotting down pending branches / patch series that interest me so i can monitor their status21:45
kergothheh21:45
*** sjolley <sjolley!~sjolley@134.134.139.70> has quit IRC21:46
kergothkhem`: see poky-contrib, mhatle/debugfs21:46
kergothalso went to oe-core, "image.bbclass: Add a method for creating a companion debug filesystem"21:47
khem`ok21:48
khem`hope it will work with 1.6 too21:48
kergothdepends on whether 1.6 was before image construction got converted to python, i don't remember when that happened :)21:49
-YoctoAutoBuilder- build #269 of nightly-qa-logrotate is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-qa-logrotate/builds/26921:50
khem`ls ../lib/oe/package.py21:51
khem`../lib/oe/package.py21:51
khem`so yes it was :)21:51
kergothnice21:51
*** Crofton|work <Crofton|work!~balister@pool-71-171-14-122.ronkva.east.verizon.net> has quit IRC21:51
khem`let me try it21:51
khem`I dont see it in OE-core21:55
khem`do you have a  SHA21:55
kergothit went to the oe-core *list*, but wasn't merged21:55
kergothstill pending, no one merged it21:55
kergothshould be in patchwork, i'd expect21:56
kergothshould reply with a reminder in case it fell off the radar21:56
kergothi'm sick of having overridden image.bbclass in meta-mentor-staging :)21:56
khem`ah I see21:57
khem`http://patchwork.openembedded.org/patch/83519/21:58
khem`you acked it21:58
khem`thats good but no heed21:58
kergothyeah, i'm guessing it probably fell off richard/saul's radar and mhatle and i never followed up21:59
kergothit happens21:59
khem`right21:59
khem`so resurrect it21:59
khem`thats why pw is so useful22:00
khem`we dont use it as effectively for oe-core as we do for other layer s22:00
*** bfederau <bfederau!~quassel@service.basyskom.com> has quit IRC22:01
kergothreplied22:01
kergothagreed22:01
-YoctoAutoBuilder- build #268 of nightly-qa-systemd is complete: Failure [failed Running Sanity Tests SendErrorReport Running Sanity Tests_2] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-qa-systemd/builds/26822:01
*** SorenHolm <SorenHolm!~quassel@5634f191.rev.stofanet.dk> has quit IRC22:03
*** Crofton|work <Crofton|work!~balister@108.44.119.236> has joined #yocto22:04
RPkergoth: its intended for master FWIW, just never see the patch at the right time :/22:07
khem`RP: its has  become a bit stale22:12
*** Crofton|work <Crofton|work!~balister@108.44.119.236> has quit IRC22:12
RPkhem`: I think fray said he'd repost it22:13
khem`cool22:13
khem`its worth for 1.8 too22:14
*** mario-goulart <mario-goulart!~user@email.parenteses.org> has joined #yocto22:16
kergothcool22:18
kergothlooks like the rejects are pretty straightforward to resolve, it seems, just did it here when applying it to meta-mentor-staging as a temporary measure.22:18
*** sjolley <sjolley!~sjolley@134.134.137.75> has joined #yocto22:23
*** Crofton|work <Crofton|work!~balister@pool-108-44-115-55.ronkva.east.verizon.net> has joined #yocto22:25
*** OutOfNoWhere <OutOfNoWhere!~rpb@199.68.195.102> has joined #yocto22:25
*** sjolley <sjolley!~sjolley@134.134.137.75> has quit IRC22:26
*** JaMa <JaMa!~martin@ip-86-49-34-37.net.upcbroadband.cz> has quit IRC22:30
*** nighty-_ <nighty-_!~nighty@hokuriku.rural-networks.com> has quit IRC22:37
*** anselmolsm_ <anselmolsm_!~anselmols@177.194.87.135> has joined #yocto22:40
*** trip0 <trip0!~tripzero@134.134.139.72> has quit IRC22:40
*** anselmolsm <anselmolsm!~anselmols@192.55.54.36> has quit IRC22:40
*** vmeson <vmeson!~rmacleod@24-212-184-107.cable.teksavvy.com> has joined #yocto22:41
*** paulg_ <paulg_!~paulg@72.1.195.9> has joined #yocto22:43
*** ant_home <ant_home!~ant__@host231-254-dynamic.11-79-r.retail.telecomitalia.it> has quit IRC22:44
*** sjolley <sjolley!~sjolley@134.134.137.75> has joined #yocto22:46
khem`kergoth: can you post the updated patch somewhere ?22:49
*** lamego <lamego!jalamego@nat/intel/x-gkzxxvorfboehlve> has quit IRC22:51
kergothkhem`: https://gist.github.com/5412df1791f59663069622:53
kergothcurl https://gist.githubusercontent.com/kergoth/5412df1791f596630696/raw/81780886483d195d3f84aae091646987347534a3/- | git am22:53
kergothonly limited testing done22:54
kergothbut should be fine22:54
kergothstuck waiting on a rebuild mostly from scratch after updating our upstream layers22:54
* kergoth taps foot22:54
khem`heh22:55
kergothsstate is nice and all, but still feels awfully brittle, doesn't take much to end up rebuilding the world from scratch22:56
kergothneed to think about how to implement task output checksumming.. would likely be non-trivial, though, would require adjusting the runqueue more on the fly22:57
*** manuel__ <manuel__!~manuel@209.6.175.242> has quit IRC23:00
*** anselmolsm <anselmolsm!~anselmols@192.55.55.41> has joined #yocto23:10
*** anselmolsm_ <anselmolsm_!~anselmols@177.194.87.135> has quit IRC23:10
*** anselmolsm <anselmolsm!~anselmols@192.55.55.41> has quit IRC23:10
*** ddalex1 <ddalex1!~ddalex@154.58.102.3> has quit IRC23:11
khem`kergoth: Yeah i am getting lot of fire for it23:18
kergotheven output checksumming wouldn't be perfect, given we'd have to figure out how to limit the scope by path potentially, or capture the api of the output, or fix builds to be more reproducible, less encoding of timestamps and whatnot.. probably a combination of all of them23:19
*** ionte_ <ionte_!uid48103@gateway/web/irccloud.com/x-kigfngfzopwwhnxk> has quit IRC23:20
kergoththere's also the possibility of having file-level task-dependencies coupled with the output checksumming, e.g. we only depend on these files, only if they change should we rebuild, but others might depend on something else23:20
kergothhmm, bitbake chokes if TMPDIR is g+s.. we should improve it so it just does a chmod g-s when TMPDIR is created in the first place, if possible23:23
kergothif we know what's wrong, and what's wrong is in our output, we should just fix it23:24
kergothit's quite reasonable for COREBASE & friends to be g+s for sharing will colleagues23:24
kergothso if you create build dirs in ${COREBASE}/.., bitbake gets unhappy23:24
*** chankit1 <chankit1!~oneam@203.106.195.178> has quit IRC23:25
*** madisox <madisox!~madison@64-71-1-115.static.wiline.com> has quit IRC23:36
*** nighty-_ <nighty-_!~nighty@hokuriku.rural-networks.com> has joined #yocto23:38
*** nighty-_ <nighty-_!~nighty@hokuriku.rural-networks.com> has quit IRC23:41
*** manuel__ <manuel__!~manuel@c-24-61-40-209.hsd1.ma.comcast.net> has joined #yocto23:42
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC23:58

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