Wednesday, 2015-01-07

RPotavio: not here it isn't :/00:00
RPotavio: version.h is a build artefact, it goes into the kernel build output directory00:00
otavioRP: even if you do: bitbake linux-imx; than bitbake imx-test00:01
otavioRP: it keeps failing00:01
RPotavio: I know what is wrong, working on a patch00:02
RPotavio: I updated fsl2.patch00:04
RPotavio: its more a proof of concept about what is wrong but it does fix the build00:04
-YoctoAutoBuilder- build #147 of nightly-fsl-arm is complete: Success [build successful] Build details are at
RPotavio: the other option is to add include/linux/version.h to the make command in do_make_scripts()00:06
otavioRP: testing00:07
otavioRP: works00:08
otavioRP: fsl2 works00:08
*** hramrach <hramrach!~hramrach@gateway/tor-sasl/hramrach> has joined #yocto00:12
*** Jefro <Jefro!> has joined #yocto00:13
*** nicktick <nicktick!~john@unaffiliated/nicktick> has joined #yocto00:21
*** nicktick1 <nicktick1!~john@> has joined #yocto00:26
*** nicktick <nicktick!~john@unaffiliated/nicktick> has quit IRC00:27
*** staylor <staylor!> has quit IRC00:28
*** nicktick <nicktick!~john@unaffiliated/nicktick> has joined #yocto00:30
*** nicktick1 <nicktick1!~john@> has quit IRC00:33
*** nrossi <nrossi!~nrossi@> has quit IRC00:45
*** nrossi <nrossi!~nrossi@> has joined #yocto00:51
*** melio_cc <melio_cc!> has joined #yocto00:51
*** Jefro <Jefro!> has quit IRC00:55
*** Nitin <Nitin!nakamble@nat/intel/x-egdvzjaownhtuxep> has joined #yocto01:04
*** Nitin2 <Nitin2!~nakamble@> has joined #yocto01:06
*** Nitin1 <Nitin1!~nakamble@> has quit IRC01:06
*** Nitin <Nitin!nakamble@nat/intel/x-egdvzjaownhtuxep> has quit IRC01:08
*** benjamirc <benjamirc!~besquive@> has quit IRC01:08
-YoctoAutoBuilder- build #150 of nightly-x86 is complete: Success [build successful] Build details are at
*** sjolley <sjolley!~sjolley@> has quit IRC01:16
*** vquicksilver <vquicksilver!~vquicksil@gentoo/contributor/vquicksilver> has quit IRC01:20
*** Xz <Xz!kmsywula@nat/intel/x-frgdahmgjxwbzmto> has joined #yocto01:31
Xzhi guys01:31
Xzhow does 'fakeroot' work in Yocto recipes? and what's its range? If I have fakeroot a() that calls b(), will b be embraced?01:32
Crofton|workfakeroot is replaced by pseudo01:41
Crofton|workI do not know much past that01:42
nrossiXz: anything that forks from the parent fakeroot/pseudo environment will be within the same fakeroot environment01:45
Crofton|workhi nrossi01:50
nrossiCrofton: hi :)01:50
Crofton|workwhat time is it there?01:51
Crofton|workI need to work out my calibration01:51
nrossiCrofton: its just before lunch :), 11:50am01:51
Crofton|work2051 here01:51
Crofton|workSoylentYellow, nrossi does meta-xilinx work01:52
*** ka6sox <ka6sox!ka6sox@nasadmin/ka6sox> has left #yocto02:04
*** sjolley <sjolley!~sjolley@> has joined #yocto02:05
*** Xz <Xz!kmsywula@nat/intel/x-frgdahmgjxwbzmto> has quit IRC02:21
*** behanw <behanw!~behanw@2001:470:b26c:0:1ce4:ea6b:1b97:50bf> has quit IRC02:29
*** nicktick <nicktick!~john@unaffiliated/nicktick> has quit IRC02:46
*** Aethenelle <Aethenelle!~Aethenell@> has joined #yocto03:06
*** ecdhe_ <ecdhe_!> has quit IRC03:14
*** Net147 <Net147!~Net147@unaffiliated/net147> has joined #yocto03:33
*** Nilesh_ <Nilesh_!~minda@> has joined #yocto03:35
*** cmking <cmking!~cmking@2601:8:ab80:623:bd96:1843:43b1:a198> has joined #yocto04:00
*** noisebleed <noisebleed!~quassel@gentoo/contributor/noisebleed> has quit IRC04:05
*** noisebleed <noisebleed!~quassel@gentoo/contributor/noisebleed> has joined #yocto04:06
*** staylor <staylor!~staylor@> has joined #yocto04:48
*** zerus <zerus!> has quit IRC04:50
*** Aethenelle <Aethenelle!~Aethenell@> has quit IRC04:58
*** Nitin <Nitin!~nakamble@> has joined #yocto05:10
*** Nitin2 <Nitin2!~nakamble@> has quit IRC05:13
*** Net147 <Net147!~Net147@unaffiliated/net147> has quit IRC05:27
*** zerus <zerus!> has joined #yocto05:28
*** mranostay <mranostay!~mranostay@pdpc/supporter/active/mranostay> has quit IRC05:28
*** pidge <pidge!eflanagan@nat/intel/x-hdvnwdrkppgbuusa> has quit IRC05:33
*** mranostay <mranostay!> has joined #yocto05:36
*** mranostay <mranostay!> has quit IRC05:36
*** mranostay <mranostay!~mranostay@pdpc/supporter/active/mranostay> has joined #yocto05:36
*** staylor <staylor!~staylor@> has quit IRC05:45
*** mranostay <mranostay!~mranostay@pdpc/supporter/active/mranostay> has quit IRC05:59
*** hamis <hamis!~irfan@> has joined #yocto06:02
*** zerus <zerus!> has quit IRC06:09
*** melio_cc <melio_cc!> has quit IRC06:11
*** tasslehoff <tasslehoff!~Tasslehof@> has joined #yocto06:29
*** zerus <zerus!~epetmab@> has joined #yocto06:36
*** Jefro <Jefro!> has joined #yocto06:51
*** [Sno] <[Sno]!~Sno]> has quit IRC06:55
*** Nitin1 <Nitin1!~nakamble@> has joined #yocto07:05
*** Nitin <Nitin!~nakamble@> has quit IRC07:05
*** mranostay <mranostay!~mranostay@pdpc/supporter/active/mranostay> has joined #yocto07:06
*** Nitin1 <Nitin1!~nakamble@> has quit IRC07:10
*** Jefro <Jefro!> has quit IRC07:17
*** nrossi <nrossi!~nrossi@> has quit IRC07:17
*** nrossi <nrossi!~nrossi@> has joined #yocto07:18
*** fusman <fusman!~fahad@> has joined #yocto07:21
*** rob_w <rob_w!~bob@unaffiliated/rob-w/x-1112029> has joined #yocto07:23
*** lyang0 <lyang0!~lyang001@> has quit IRC07:23
*** SorenHolm <SorenHolm!~quassel@> has joined #yocto07:23
*** Nitin <Nitin!~nakamble@> has joined #yocto07:28
*** fusman <fusman!~fahad@> has joined #yocto07:29
*** lyang0 <lyang0!~lyang001@> has joined #yocto07:34
*** sarahsharp <sarahsharp!sarah@nat/intel/x-qkzhrybkyyrsuazt> has quit IRC07:35
*** 17SABD3NH <17SABD3NH!> has joined #yocto07:38
*** 17SABD3NH <17SABD3NH!> has quit IRC07:39
*** kimo <kimo!> has joined #yocto07:40
*** patrickz <patrickz!~Thunderbi@> has joined #yocto07:41
*** volker_123456 <volker_123456!> has joined #yocto07:51
*** zerus <zerus!~epetmab@> has quit IRC07:57
*** fusman <fusman!~fahad@> has quit IRC07:58
*** fusman <fusman!~fahad@> has joined #yocto07:58
*** ddalex1 <ddalex1!~ddalex@> has joined #yocto08:05
*** kimo <kimo!> has quit IRC08:05
*** [Sno] <[Sno]!~Sno]> has joined #yocto08:06
*** shoragan <shoragan!~shoragan@debian/developer/shoragan> has joined #yocto08:08
*** agust <agust!> has joined #yocto08:10
*** jbrianceau_away <jbrianceau_away!uid10952@gateway/web/> has joined #yocto08:12
*** jbrianceau_away is now known as jbrianceau08:12
*** TobSnyder <TobSnyder!> has joined #yocto08:12
*** fusman <fusman!~fahad@> has quit IRC08:13
*** blitz00 <blitz00!stefans@nat/intel/x-zuwsmqulwzvgxxqv> has joined #yocto08:15
*** blitz00 <blitz00!stefans@unaffiliated/blitz00> has joined #yocto08:15
*** nicktick <nicktick!~john@unaffiliated/nicktick> has joined #yocto08:18
*** florian_kc <florian_kc!~fuchs@Maemo/community/contributor/florian> has joined #yocto08:21
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto08:21
*** florian_kc is now known as florian08:21
*** rob_w <rob_w!~bob@unaffiliated/rob-w/x-1112029> has quit IRC08:22
*** ant_work <ant_work!> has joined #yocto08:28
bluelightningmorning all08:37
*** soderstrom <soderstrom!~soderstro@> has joined #yocto08:40
*** mckoan_ is now known as mckoan08:40
mckoangood morning08:41
*** mago_ <mago_!> has joined #yocto08:41
*** mago_ <mago_!> has quit IRC08:45
*** lumo <lumo!> has joined #yocto09:10
*** luminita <luminita!> has quit IRC09:13
*** mago_ <mago_!> has joined #yocto09:17
*** pegu` <pegu`!> has joined #yocto09:17
*** e8johan <e8johan!> has joined #yocto09:17
*** pegu <pegu!> has quit IRC09:17
*** MickyMick <MickyMick!59fb345d@gateway/web/freenode/ip.> has joined #yocto09:18
*** Saur1 <Saur1!pkj@nat/axis/x-nqcvlruwayyqmkjs> has quit IRC09:18
*** Saur <Saur!pkj@nat/axis/x-eeqxaxmtanwydohx> has joined #yocto09:19
*** nicktick <nicktick!~john@unaffiliated/nicktick> has quit IRC09:19
*** ddalex1 <ddalex1!~ddalex@> has quit IRC09:23
*** LetoTheII is now known as letothe2nd09:26
*** ddalex1 <ddalex1!~ddalex@> has joined #yocto09:26
*** letothe2nd <letothe2nd!> has quit IRC09:26
*** letothe2nd <letothe2nd!~jd@unaffiliated/letothe2nd> has joined #yocto09:26
*** ddom <ddom!> has joined #yocto09:29
*** kimo <kimo!> has joined #yocto09:31
*** cmking <cmking!~cmking@2601:8:ab80:623:bd96:1843:43b1:a198> has quit IRC09:33
*** rburton <rburton!> has joined #yocto09:34
*** cmking1 <cmking1!> has joined #yocto09:36
*** slips <slips!> has joined #yocto09:45
*** slips <slips!> has joined #yocto09:47
*** lpapp <lpapp!~lpapp@kde/lpapp> has joined #yocto09:49
lpappgood morning09:49
*** e8johan <e8johan!> has quit IRC09:50
*** Metax <Metax!c3dc2512@gateway/web/freenode/ip.> has joined #yocto09:51
lpappis there a way to exclude a file from the FILES_* pattern?09:51
lpappI would like to exclude the .debug folders, otherwise it would be much more work to do it right.09:52
Metaxis there a list of the supported boards ?09:53
Metax(like raspberry pi, beaglebone, banana pi, etc.)09:53
letothe2ndMetax: as nobody is required to announce/list/certify his BSP, there is no such thing as a comprehensive list09:54
letothe2ndMetax: usually the board vendor says if yocto/oe support is available, or not09:54
lpappMetax: I think this is your best bet,
Metaxok, thx09:55
Metaxlpapp: this was the page I had09:55
lpapp(and google of course)09:55
Metaxbut the last doesn't seem complete09:55
Metax(no raspberry for example)09:56
letothe2ndMetax: of course, it never can be09:56
MetaxI understand09:56
letothe2ndMetax: like my company for example has a bunch of boards that we have layers for, but those are not publicly available, and we don't want them listed09:56
lpappMetax: those are mostly intel layers, whereas raspberry pi is not maintained by Intel.09:57
lpappso in that sense, it is "complete".09:57
Metaxok, thanks09:59
letothe2ndyou could also have an extended look at the metalayers hosted on git.yoctoproject.org09:59
Metaxwhat are the most used boards ?09:59
MetaxRaspberry I guess, probably beaglebone ?09:59
lpappMetax: who knows?09:59
letothe2ndand no, i think that its not an intel issue - its an issue of what vendor wants to publically show his stuff09:59
letothe2ndti for example has a well-maintained and extensive layer there too.10:00
lpappMetax: you are asking quite broad questions :)10:00
lpapp(hard to answer)10:00
MetaxI know :)10:00
MetaxI'm discovering yocto, and I'd like to know wich boards are ok with it10:01
MetaxAnd then, I'll buy it and test10:01
lpappout of curiosity: is there any practical use of knowing which layer is the most common? Are you thinking about launching a project and target the most used?10:01
*** ddalex1 <ddalex1!~ddalex@> has quit IRC10:01
*** jimBaxter <jimBaxter!> has joined #yocto10:01
lpappMetax: well, raspberrypi is cheap, but then again: you will get different answers from different people.10:02
Metaxpersonnally, i'm not fond of raspberry10:02
Metaxit's cheap, but there are better for a few more dollars10:02
Metax(banana pi, beaglebone black)10:03
lpapplike I said, these questions are primarily opinion based and broad10:03
MetaxI know :p10:03
Metaxit's just that I'd like to know if the banana pi (for example) is well supported before buying it10:04
*** letothe2nd is now known as LetoThe2nd10:04
lpappfor instance, you do not even need a board to experiment with Yocto.10:05
MetaxYeah, but it's funnier with one :p10:05
*** stryx`_ <stryx`_!~stryx@unaffiliated/stryx/x-3871776> has joined #yocto10:05
lpappwell, I would go the other way around, personally: what I am trying to achieve10:06
lpappand fit or not fit Yocto later10:06
*** stryx`__ <stryx`__!~stryx@> has quit IRC10:06
lpappYocto is not an end goal, just means :)10:06
bluelightninglpapp: re excluding .debug folders - no there is no exclusion mechanism; if you don't want them produced, perhaps set INHIBIT_PACKAGE_DEBUG_SPLIT = "1"10:07
lpapp(unless it is a theoretical project)10:07
lpappbluelightning: that will strip the debug files from the -dbg package.10:07
bluelightninglpapp: perhaps you could explain what you're trying to acheive10:08
lpappbluelightning: yeah, I think that would be beneficial, so my main issue is that I have tons of files for installation in /opt, include /etc/ configuration files, libs, executables, et c.10:08
lpappbluelightning: Yocto seems to generate .debug in there, which is fine since I have executables coming from us to there.10:09
lpappbluelightning: but I have another package for "static" things that come from the vendor and already stripped.10:09
lpappbluelightning: the 2-3 executables coming from us in the /opt tree would go into our own package and they need .debug into -dbg since that is our software10:09
lpappbluelightning: but there are many static files coming from the vendor into /opt and so I thought FILES_ would only catch /opt not to enumerate many files10:10
lpappbluelightning: but that will inherently catch the .debug things generated in /opt and will rightfully get an error from Yocto that it is not going into the -dbg package.10:11
lpappbluelightning: and in PACKAGES I would put our package prior to the static package so that /opt "catch-all" would catch the rest.10:11
lpappbluelightning: that is why I am claiming that excluding .debug would be easier than explicitly listing hundreds of files10:12
bluelightningwell, our packaging code does not support exclusions, the way this sort of thing is normally handled is by controlling the order of PACKAGES such that the appropriate package picks up the files first10:13
lpappok, so I would need to do pkg1 -dbg pkg2, where pkg2 is the /opt catch-all.10:14
bluelightningthat's what I'd recommend yes10:18
*** chankit1 <chankit1!~oneam@> has joined #yocto10:24
*** slips <slips!> has joined #yocto10:31
*** Metax <Metax!c3dc2512@gateway/web/freenode/ip.> has quit IRC10:32
*** hirata <hirata!> has quit IRC10:36
*** vquicksilver <vquicksilver!> has joined #yocto10:38
*** vquicksilver <vquicksilver!~vquicksil@gentoo/contributor/vquicksilver> has joined #yocto10:38
*** hirata <hirata!> has joined #yocto10:41
lpappbluelightning: do you know how I could debug why already-stripped does not work, given that the binaries in question are in the right packages-split directory? Perhaps, it was not functional in dylan?10:57
bluelightninglpapp: well, the code that implements the checks is in either package.bbclass or insane.bbclass (we did move all of it to insane.bbclass since then), so it would be a matter of adding print (or more effectively bb.warn() ) calls and figuring out why it's not taking effect10:59
*** hirata <hirata!> has quit IRC10:59
lpappbluelightning: ok, was it supposed to work in dylan to start with?11:00
bluelightningas far as I am aware, yes11:00
bluelightningwe may even have been using it actively in dylan, check the u-boot recipe11:00
*** kimo <kimo!> has quit IRC11:02
*** hirata <hirata!> has joined #yocto11:03
*** bboozzoo <bboozzoo!> has joined #yocto11:03
lpappbluelightning: empty output for 'grep -rn "stripped" ../meta/recipes-bsp/u-boot/'11:04
bluelightningI guess it was added to the recipe later in that case11:04
lpappwhat is the difference between disabling debug split and already-stripped for non-strip-mixed packages?11:12
lpappI mean difference as in difference for the end user, not implementation.11:13
*** slips is now known as slipss11:13
*** slips- <slips-!> has joined #yocto11:14
*** slips- is now known as slips11:15
bluelightningINHIBIT_PACKAGE_DEBUG_SPLIT will prevent debugging symbols from being split out at all11:21
bluelightningfor all files installed by the recipe11:21
lpappyeah, so the difference is only for mixed-strip-packages?11:22
lpappif you do not mix that, it is the same effect?11:22
bluelightningno, they aren't at all similar11:22
lpappwhy is that11:22
bluelightningINSANE_SKIP is telling the system to not produce a warning if the symbols aren't even present in the binary file11:23
lpappwell, if it is split, I would not assume a warning to be asserted11:24
bluelightningI'm not sure what that means11:24
lpappif you disable the debug things, I would not expect "already stripped" warnings.11:25
lpappsince I told the buildsystem to forget about debug things.11:25
bluelightningif you set INHIBIT_PACKAGE_STRIP then yes the warnings will not occur, because the code that checks for the symbols won't even be executed11:25
*** noisebleed <noisebleed!~quassel@gentoo/contributor/noisebleed> has quit IRC11:41
*** Nikhil_D <Nikhil_D!~quassel@nat/ti/x-ignxrhsgpaajdple> has joined #yocto11:58
*** ecdhe_ <ecdhe_!> has joined #yocto12:00
*** warthog9 <warthog9!~warthog9@> has quit IRC12:14
*** warthog9 <warthog9!~warthog9@> has joined #yocto12:16
*** cmking1 <cmking1!> has quit IRC12:16
*** Nilesh_ <Nilesh_!~minda@> has left #yocto12:19
*** bboozzoo <bboozzoo!> has quit IRC12:20
*** tmpsantos <tmpsantos!~tmpsantos@> has joined #yocto12:31
*** warthog9 <warthog9!~warthog9@> has quit IRC12:37
*** warthog9 <warthog9!~warthog9@> has joined #yocto12:38
*** mranostay <mranostay!~mranostay@pdpc/supporter/active/mranostay> has quit IRC12:38
Crofton|workzeddii, you awake yet?12:44
*** e8johan <e8johan!> has joined #yocto12:51
lpappbluelightning: how do I use INHIBIT_PACKAGE_STRIP for a particular package in a recipe?12:53
*** kimo <kimo!> has joined #yocto12:54
lpappsimilarly as FILES_* ?12:54
*** warthog9 <warthog9!~warthog9@> has quit IRC12:54
*** warthog9 <warthog9!~warthog9@> has joined #yocto12:56
*** kimo <kimo!> has quit IRC13:10
*** kimo <kimo!> has joined #yocto13:10
*** jmpdelos__ <jmpdelos__!> has quit IRC13:12
*** jmdelos_ <jmdelos_!> has joined #yocto13:12
bluelightninglpapp: you can't I'm afraid13:12
lpappbluelightning: ok, well, then I still need to find a solution for the already-stripped issue. It looked like a workaround.13:13
*** bboozzoo <bboozzoo!> has joined #yocto13:16
*** bboozzoo is now known as bboozzoo_away13:16
*** Nikhil_D <Nikhil_D!~quassel@nat/ti/x-ignxrhsgpaajdple> has quit IRC13:17
*** sarahsharp <sarahsharp!~sarah@> has joined #yocto13:19
*** Nikhil_D <Nikhil_D!~quassel@nat/ti/x-hirkqkrhmfbnokus> has joined #yocto13:19
*** sarahsharp <sarahsharp!~sarah@> has quit IRC13:28
*** Nikhil_D <Nikhil_D!~quassel@nat/ti/x-hirkqkrhmfbnokus> has quit IRC13:32
*** mranostay <mranostay!~mranostay@pdpc/supporter/active/mranostay> has joined #yocto13:39
-YoctoAutoBuilder- build #150 of nightly-x32 is complete: Failure [failed BuildImages Running Sanity Tests_1] Build details are at
*** __karthik <__karthik!~karthik@nat/ti/x-czjvhubrxlbklqfs> has joined #yocto13:45
*** Nikhil_D <Nikhil_D!~quassel@nat/ti/x-dpqwbiokkuwhbecn> has joined #yocto13:48
*** mranostay <mranostay!~mranostay@pdpc/supporter/active/mranostay> has quit IRC13:48
*** marka <marka!~marka@> has joined #yocto13:51
*** mranostay <mranostay!~mranostay@pdpc/supporter/active/mranostay> has joined #yocto13:55
zeddiiCrofton|work, I'm awake now!14:02
Crofton|workhacking around, found one issue on my end14:07
Crofton|workthis kernel stuff is "fragile"14:08
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto14:08
* zeddii understands.14:08
Crofton|workdamn it14:08
zeddiiI'd rm -rf * and start over if I could14:08
Crofton|workdid the add "CONFIG_INPUT" without the =y and no error14:09
zeddiiCrofton|work. what's the hot issue ? are the patches not applying ?14:09
Crofton|worknot sure14:09
Crofton|workI backed oe-core up14:09
zeddiik. I'll start my sanity tests on patches and configs again, and see if anything pops out.14:10
Crofton|worktrying to reduce the set of things I am tryin gto fix, when I see something build here, I will go forward14:10
zeddiisounds sane. I'll see what I can find out in the mean time.14:10
Crofton|workI think I will start filng nuisnace bugs about cases where it would really help to refuse to build14:10
zeddiiCrofton|work. tag me on them, and I'll take care of the ones that make sense. I have an open bug to make the auditing and sanity more visible (again .. I was asked to hide it years ago), so I can group them together.14:11
Crofton|workit is really hard to figure out what is going when kernels build even though your cfg bits are nonsense14:12
*** melio_cc <melio_cc!> has joined #yocto14:13
zeddiiCrofton|work. I'll dig up the bugzilla I was talking about. you can toss flames and comments in it.14:13
yoctiBug 6943: enhancement, Medium+, 1.8 M2, bruce.ashfield, IN PROGRESS IMPLEMENTATION , kernel-dev: make Kconfig audit output visible14:14
Crofton|workok got a .o for the driver I am trying to add14:23
Crofton|worknow trying against master14:23
Crofton|workzeddii, to be clear, the audit would tell me about options I am tryin gto set, that do not get set in final config?14:24
zeddiiand optionally, halt the build (via a flag)14:26
zeddiiI'm getting my env setup to test now. I'm running out of builders with all the bugs in progress.14:26
Crofton|workok, I do not have an issue with master, just overall crappiness of kernel stuff :)14:27
zeddiiI have the same issue! :P14:28
Crofton|workI'll add some fuel to the fire on the bug14:28
zeddiiwe'll have a beer and commiserate14:28
Crofton|worknow I down to wic being broken in oe-core/dizzy14:28
*** noisebleed <noisebleed!> has joined #yocto14:30
*** noisebleed <noisebleed!~quassel@gentoo/contributor/noisebleed> has joined #yocto14:30
*** darknighte <darknighte!~darknight@pdpc/supporter/professional/darknighte> has joined #yocto14:30
Crofton|workupdated, and I did some SHOUTING even14:32
*** [Sno] <[Sno]!~Sno]> has quit IRC14:32
*** mranostay <mranostay!~mranostay@pdpc/supporter/active/mranostay> has quit IRC14:33
*** luminita <luminita!> has joined #yocto14:33
*** adams_ <adams_!67f855e1@gateway/web/freenode/ip.> has joined #yocto14:34
adams_Can anyone help me in integrating megacity window manager with poky-dizzy14:34
Crofton|workRP, you are off the hook wrt to me and the kernel, just crappy kernel tooling :)14:35
*** lumo <lumo!> has quit IRC14:35
Crofton|workI added my isue to the existing bug14:35
Crofton|workand will drink beer with zeddii14:35
RPCrofton|work: great, I'm pleased I'm off the hook on something for a change! :)14:38
zeddiiCrofton|work, I like the shouting :P14:38
zeddiinow back to the pile14:39
*** lpapp <lpapp!~lpapp@kde/lpapp> has left #yocto14:39
RPzeddii: we should probably make the config "warnings" unconditionally fatal and be done with it14:39
RPzeddii: its where we're heading with other areas like packaging14:39
rburtonadams_: metacity?  it's in meta-gnome.14:39
zeddiiRP: agreed. I can do that under the time allocated for my bug. and it has a side benefit of forcing certain people to keep the kernel configs always clean an up to date14:40
* zeddii whistles innocently14:40
RPzeddii: ;-)14:40
Crofton|workheh, the comment about not alarming the user or breaking the build when doing that would have led to to the solution quickly annoyed me14:40
zeddiiCrofton|work. opinions have shifted. at one point .. we didn't want to alarm everyone. but now .. game on! :P14:41
Crofton|workI can't see why someone would not want to know the kconfig does not have options they are asking for14:42
* zeddii nods. 14:42
zeddiiand the tools will even tell you if it is invalid for a number of reasons .. which would have caught yours and pointed it out.14:43
* zeddii wonders if he'll go 0 for 4 on ECL* talks. I failed all of 2014 to get one accepted.14:43
zeddiiELC even.14:44
zeddii*sigh* back to hacking14:44
*** paulg_ <paulg_!> has joined #yocto14:48
JaMaRP: thanks for super fast merge of last 2 patches14:52
*** Aethenelle <Aethenelle!~Aethenell@> has joined #yocto14:52
JaMarburton: RP: any progress on merging libav-9 and REQUIRED_DISTRO_FEATURES changes? They are on ML for months14:52
rburtonJaMa: now i had a problem with the av series…  distro features one is still on my todo list :/14:53
RPJaMa: np, the kernel one is obviously causing issues in particular14:53
JaMawith the patches growing in my jansa/master branches, the world builds will be less and less relevant to the state of current master14:53
rburtonJaMa: good news is that my personal inbox says <200 threads, before xmas it was almost 400!14:53
JaMacool, my says 4659 messages just for oe-core.. I need some smarter way of filtering them :)14:54
* rburton drops the pcmanfm upgrade series, it's broken14:54
rburtonJaMa: i've now finally got a small script to move messages in imap based on git logs, as per everyone else14:55
rburtonits like a rite of passage - writing the tool to do that14:55
RPrburton: I think that is just you and I isn't it? :)14:55
RPJaMa: that sounds more like my inbox :/14:55
JaMarburton: so it moves patches to different folder after they are merged to some branch?14:56
RPJaMa: yes, that is what mine does, using simplistic matching on the subject lines and git commit first line entries14:56
adams_<rburton> How i can replace matchbox with metacity14:57
JaMalooks useful, maybe we should improve the git hook to use the same matching14:57
rburtonJaMa: i use gmail so oe-core mails get tagged, and get archived on merge14:57
RPJaMa: I think it would make patchwork much nicer14:57
JaMabecause the currently used digest didn't match with any patchwork change for months :/14:57
JaMayes trying to keep 3 places (branches, patchwork, imap) consistent is boring and takes a lot of time, more scripting would be nice14:59
*** dgm816 <dgm816!~dgm816@unaffiliated/orkim> has quit IRC15:02
*** SorenHolm <SorenHolm!~quassel@> has quit IRC15:02
RPJaMa: I agree, I've been wondering about some custom tooling15:07
*** hamis <hamis!~irfan@> has quit IRC15:07
*** jkridner|work <jkridner|work!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto15:07
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has quit IRC15:08
*** nicktick <nicktick!~john@unaffiliated/nicktick> has joined #yocto15:08
*** florian <florian!~fuchs@Maemo/community/contributor/florian> has quit IRC15:10
*** ant_work <ant_work!> has quit IRC15:10
*** rwoolley <rwoolley!~rwoolley@> has joined #yocto15:11
*** hitlin37 <hitlin37!uid16371@gateway/web/> has joined #yocto15:13
hitlin37i have a baytrail based board and thinking to try yocto on it. is yocto supported on baytrail?15:14
rburtonhitlin37: yes, the intel-corei7-64 BSP in meta-intel supports that15:17
JaMaRP: gerrit maintains all 3 in one place, but I know you don't like it :)15:19
*** sarahsharp <sarahsharp!sarah@nat/intel/x-rovsietwploleaet> has joined #yocto15:19
Aethenellei'm having all kinds of issues getting openjdk-7 or openjdk-8 to build on any platform. I know jdk-8 only works on aarch64 and i've tried several platforms (currently working through the qemu* images as a test but i've tried wandboard-quad, t4240rdb-64b, edgerouter and aarch64). is there a known combination that currently works?15:20
AethenelleI'm working from yocto/master15:20
RPJaMa: "don't like" is an understatement :/15:20
RPI don't think I've found a web interface I hate more :/15:21
AethenelleRP: i haven't seen the one you're looking at but i assure you, there are worse.15:21
JaMaok, fair enough.. just had to mention it as we agreed that we need some custom tooling just to be able to deal with incomming patches and review and that's exactly what gerrit does15:23
JaMahonestly current patchwork isn't much help15:23
JaMait mostly acts as shared imap folder, biggest advantage for me is that pwam can reach pw's http easier than git am my gmail inbox15:24
-YoctoAutoBuilder- build #149 of nightly-qa-systemd is complete: Failure [failed Running Sanity Tests Running Sanity Tests_1 Running Sanity Tests_2] Build details are at
*** benjamirc <benjamirc!besquive@nat/intel/x-shqbrgixunxymuae> has joined #yocto15:29
*** tmpsantos <tmpsantos!~tmpsantos@> has quit IRC15:29
RPrburton: when is someone going to fix the systemd failure?15:31
kergothcould check out reviewboard as an alternative to gerritt. haven't played with eitehr much, myself, though i know the reviewboard devs15:32
* kergoth yawns15:32
*** sarahsharp <sarahsharp!sarah@nat/intel/x-rovsietwploleaet> has quit IRC15:35
JaMawe were trying reviewboard + stash and found tight integration of git repo and review in gerrit easier to use15:35
JaMaphabricator also looks nice (as UI), but too different to what I'm used to (so I cannot objectively compare)15:36
*** benjamirc <benjamirc!besquive@nat/intel/x-shqbrgixunxymuae> has quit IRC15:39
*** tasslehoff <tasslehoff!~Tasslehof@> has quit IRC15:39
*** benjamirc <benjamirc!besquive@nat/intel/x-fljspkjexlsvuarj> has joined #yocto15:39
*** jimBaxter <jimBaxter!> has quit IRC15:46
*** fusman <fusman!~fahad@> has joined #yocto15:48
*** tmpsantos <tmpsantos!~tmpsantos@> has joined #yocto15:53
hitlin37rburton: thanks for the reply. the one i have here is intel atom E382515:54
*** sarahsharp <sarahsharp!sarah@nat/intel/x-jqbwwegkvzvqmfwb> has joined #yocto15:54
*** jimBaxter <jimBaxter!> has joined #yocto15:54
hitlin37ah, i think that one is also there in dual core version of minnowboard15:55
hitlin37so may be it has support from yocto15:55
* hitlin37 checks minnowboard project15:56
*** sarahsharp <sarahsharp!sarah@nat/intel/x-jqbwwegkvzvqmfwb> has quit IRC15:58
rburtonif you have a baytrail board you want meta-intel15:58
*** sarahsharp <sarahsharp!sarah@nat/intel/x-gwunpqimzosdcbzs> has joined #yocto15:58
rburtonmeta-minnowboard is for the original minnowboard which wasn't baytrail15:58
*** sarahsharp <sarahsharp!sarah@nat/intel/x-gwunpqimzosdcbzs> has quit IRC16:00
*** sarahsharp <sarahsharp!sarah@nat/intel/x-engozsxqnvpxsuua> has joined #yocto16:00
bluelightninghitlin37: FYI:
hitlin37thanks bluelightning16:05
hitlin37rburton: yup. i mean the newer version of minnowboard.
hitlin37that one has the same atom as i have here on my board. atom e382516:06
hitlin37i actually managed to flash Lubuntu 14.04 on its emmc and it boots fine. but consumes most of the space out of its 4gb16:06
hitlin37i like it that i can touch it and its not heated at all16:09
*** tmpsantos <tmpsantos!~tmpsantos@> has quit IRC16:11
*** tmpsantos <tmpsantos!~tmpsantos@> has joined #yocto16:11
-YoctoAutoBuilder- build #152 of nightly-multilib is complete: Failure [failed BuildImages_2 Running Sanity Tests_2 BuildImages_3 Running Sanity Tests_3 BuildImages_4] Build details are at
hitlin37bluelightning: the boards i have here has BIOS on it. do you think i can try with yocto provided image and make it boot from usb to it? asking this question as i don't know how yocto plays with BIOS.16:15
* hitlin37 starts to fetch the meta-intel tree16:16
hitlin37should i fetch daisy or the newer release dizzy16:17
* hitlin37 wonders why all the yocto releases starts with d16:18
*** slips_ <slips_!~slips@> has joined #yocto16:19
*** bachp <bachp!> has joined #yocto16:22
*** lpapp <lpapp!~lpapp@kde/lpapp> has joined #yocto16:23
*** sarahsharp <sarahsharp!sarah@nat/intel/x-engozsxqnvpxsuua> has quit IRC16:23
*** sarahsharp <sarahsharp!~sarah@> has joined #yocto16:23
lpappbluelightning: I think I will create two recipes for the two packages then if strip cannot be set per on a package basis.16:23
lpappusing an .inc from both with require.16:24
*** slips_ <slips_!~slips@> has quit IRC16:24
lpappit would be nice to support this from within one recipe in the future though.16:24
*** slips_ <slips_!~slips@> has joined #yocto16:26
lpappbluelightning: ha! grep -rn "already-stripped" ../meta/ -> empty output16:27
hitlin37if i understand, yocto do a common release across both intel and arm. or it diffeers for each arch.16:27
bluelightninglpapp: ah, right... I guess my memory was faulty, in dylan there was no way to turn off that warning16:28
*** slips_ <slips_!~slips@> has quit IRC16:28
*** staylor <staylor!~staylor@> has joined #yocto16:29
lpappbluelightning: :O16:32
*** staylor <staylor!~staylor@> has quit IRC16:32
lpappbluelightning: so you also recommend two separate recipes or there is still a nicer way?16:32
lpapp(we cannot update dylan now as we need to focus on the release)16:32
bluelightningyou could patch in the ability to disable the warning, if you are happy to carry that patch16:33
bluelightningthat's probably the only way other than the solutions already discussed16:33
bluelightningother than just ignoring the warning16:33
lpappbluelightning: I am also getting an error due to this, remember.16:34
bluelightningok, so maybe I missed that, can you remind me of the error as opposed to the warning?16:34
lpappbluelightning: it is trying to split already stripped binaries16:35
lpappERROR: QA Issue: non debug package contains .debug directory: ...16:35
lpapp(sorry, split = create .debug)16:36
bluelightninglpapp: we talked about that, the solution is to reorder PACKAGES - have you tried that?16:37
otaviozeddii: Are your patches somewhere?16:38
otaviozeddii: I'd like to check what is there and what is still pending16:39
hitlin37bluelightning: i tried the steps from the wiki for simple 32 bit image but got this error on first run of . IOError: file $HOME/source/meta-intel/conf/layer.conf not found in /home/test/source/poky/meta-yocto:/home/test/source/poky/build:/home/test/source/poky/meta:/home/test/source/poky/meta-yocto-bsp16:39
hitlin37i mean first run of bitbake core-image-minimal16:40
*** sarahsharp <sarahsharp!~sarah@> has quit IRC16:40
bluelightninghitlin37: you can't use $HOME in there I'm afraid, it needs to be a proper path16:41
lpappbluelightning: I do not wish to have .debug for already stripped binaries since it feels pointless, no?16:46
*** slips_ <slips_!~slips@> has joined #yocto16:46
lpappso basically I wished to split and I was told that already-stripped would also split.16:47
bluelightninglpapp: I'm afraid we don't currently offer anything to explicitly handle that mixed setup, certainly not in dylan16:48
hitlin37bluelightning: thanks. that worked! building now16:49
lpappbluelightning: two recipes or backport that is?16:50
*** sarahsharp <sarahsharp!~sarah@> has joined #yocto16:56
*** mckoan is now known as mckoan|away16:56
*** slips__ <slips__!~slips@> has joined #yocto16:59
*** slips_ <slips_!~slips@> has quit IRC16:59
bluelightninglpapp: I'm not understanding the question - sorry can you rephrase?17:00
*** slips__ <slips__!~slips@> has quit IRC17:01
*** benjamirc <benjamirc!besquive@nat/intel/x-fljspkjexlsvuarj> has quit IRC17:02
*** kimo <kimo!> has quit IRC17:02
*** alimon_ <alimon_!c713fb17@gateway/web/freenode/ip.> has joined #yocto17:03
*** [Sno] <[Sno]!~Sno]> has joined #yocto17:04
*** alimon_ <alimon_!c713fb17@gateway/web/freenode/ip.> has quit IRC17:09
*** mago_ <mago_!> has quit IRC17:12
lpappbluelightning: I see two solutions: 1) Backporting the already-stripped feature 2) Create two recipes and I can explicitly split in the "static" recipe in which the files are already stripped.17:12
*** benjamirc <benjamirc!~besquive@> has joined #yocto17:12
-YoctoAutoBuilder- build #154 of nightly-world is complete: Failure [failed BuildImages] Build details are at
*** TobSnyder <TobSnyder!> has quit IRC17:15
*** ddom <ddom!> has quit IRC17:17
bluelightninglpapp: right, yes17:18
*** e8johan <e8johan!> has quit IRC17:19
*** mranostay <mranostay!~mranostay@pdpc/supporter/active/mranostay> has joined #yocto17:25
*** mranostay <mranostay!~mranostay@pdpc/supporter/active/mranostay> has quit IRC17:26
*** mranostay <mranostay!~mranostay@pdpc/supporter/active/mranostay> has joined #yocto17:26
*** SorenHolm <SorenHolm!> has joined #yocto17:28
*** Jefro <Jefro!> has joined #yocto17:30
*** nicktick <nicktick!~john@unaffiliated/nicktick> has quit IRC17:30
-YoctoAutoBuilder- build #152 of nightly-x86-64-lsb is complete: Failure [failed BuildImages] Build details are at
*** benjamirc <benjamirc!~besquive@> has quit IRC17:34
*** benjamirc1 <benjamirc1!~besquive@> has joined #yocto17:34
*** behanw <behanw!~behanw@2001:470:b26c:0:a432:81b2:875a:97fb> has joined #yocto17:38
*** blitz00 <blitz00!stefans@unaffiliated/blitz00> has quit IRC17:41
*** Jefro <Jefro!> has quit IRC17:48
*** jkridner|work <jkridner|work!~jkridner@pdpc/supporter/active/jkridner> has quit IRC17:49
otavioWe are living under edge now rburton17:51
otaviowhat is building now, may fail in 3min17:51
*** dgm816 <dgm816!> has joined #yocto17:53
*** dgm816 <dgm816!~dgm816@unaffiliated/orkim> has joined #yocto17:53
*** SorenHolm <SorenHolm!> has quit IRC17:53
*** jbrianceau is now known as jbrianceau_away17:54
*** sjolley <sjolley!~sjolley@> has quit IRC18:01
*** SorenHolm <SorenHolm!> has joined #yocto18:05
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has joined #yocto18:06
*** benjamirc1 <benjamirc1!~besquive@> has quit IRC18:08
*** Jefro <Jefro!> has joined #yocto18:11
*** benjamirc <benjamirc!besquive@nat/intel/x-jqetbrleytciitcx> has joined #yocto18:14
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC18:20
*** benjamirc <benjamirc!besquive@nat/intel/x-jqetbrleytciitcx> has quit IRC18:21
*** bluelightning <bluelightning!~paul@> has joined #yocto18:22
*** bluelightning <bluelightning!~paul@> has quit IRC18:22
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto18:22
*** staylor <staylor!> has joined #yocto18:25
lpappbluelightning: would it be difficult to backport already-stripped or just the matter of a couple lines?18:25
bluelightninglpapp: AFAIR it was part of a refactoring effort so you may find it easier to implement that one thing from scratch, but it would probably be worth double-checking18:26
*** sarahsharp <sarahsharp!~sarah@> has quit IRC18:28
*** sjolley <sjolley!sjolley@nat/intel/x-vagopnjbbkzwbyxu> has joined #yocto18:28
*** sarahsharp <sarahsharp!~sarah@> has joined #yocto18:28
*** benjamirc <benjamirc!besquive@nat/intel/x-mofobssefvpegftr> has joined #yocto18:38
*** sarahsharp <sarahsharp!~sarah@> has quit IRC18:40
*** dmoseley <dmoseley!> has quit IRC18:50
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC18:52
*** dgm816 <dgm816!~dgm816@unaffiliated/orkim> has quit IRC18:53
*** benjamirc <benjamirc!besquive@nat/intel/x-mofobssefvpegftr> has quit IRC18:53
*** dgm816 <dgm816!> has joined #yocto18:53
*** dgm816 <dgm816!~dgm816@unaffiliated/orkim> has joined #yocto18:53
*** phragment <phragment!> has quit IRC18:58
*** phragment <phragment!> has joined #yocto18:59
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto19:00
*** lpapp <lpapp!~lpapp@kde/lpapp> has quit IRC19:03
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has quit IRC19:05
*** Jefro1 <Jefro1!> has joined #yocto19:07
*** Jefro <Jefro!> has quit IRC19:09
*** Aethenelle <Aethenelle!~Aethenell@> has quit IRC19:11
*** kroon <kroon!> has joined #yocto19:11
*** bluelightning <bluelightning!~paul@> has joined #yocto19:16
*** bluelightning <bluelightning!~paul@> has quit IRC19:16
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto19:16
*** Jefro <Jefro!> has joined #yocto19:20
*** Jefro1 <Jefro1!> has quit IRC19:22
*** ddalex1 <ddalex1!~ddalex@> has joined #yocto19:25
*** tmpsantos <tmpsantos!~tmpsantos@> has quit IRC19:25
*** ddalex1 <ddalex1!~ddalex@> has quit IRC19:31
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC19:32
*** ddalex1 <ddalex1!~ddalex@> has joined #yocto19:33
*** Aethenelle <Aethenelle!> has joined #yocto19:34
*** fusman <fusman!~fahad@> has quit IRC19:36
*** tmpsantos <tmpsantos!~tmpsantos@> has joined #yocto19:38
*** Nikhil_D <Nikhil_D!~quassel@nat/ti/x-eqfnzbtqhnjrgssk> has joined #yocto19:48
*** e8johan <e8johan!> has joined #yocto19:49
*** dgm816 <dgm816!~dgm816@unaffiliated/orkim> has quit IRC19:58
*** dgm816 <dgm816!> has joined #yocto19:59
*** dgm816 <dgm816!~dgm816@unaffiliated/orkim> has joined #yocto19:59
*** jbrianceau_away <jbrianceau_away!uid10952@gateway/web/> has quit IRC20:07
*** Nikhil_D <Nikhil_D!~quassel@nat/ti/x-eqfnzbtqhnjrgssk> has quit IRC20:27
*** SorenHolm <SorenHolm!> has quit IRC20:29
*** SorenHolm <SorenHolm!> has joined #yocto20:30
*** Aethenelle_ <Aethenelle_!> has joined #yocto20:37
*** Aethenelle <Aethenelle!> has quit IRC20:37
*** Aethenelle_ is now known as Aethenelle20:37
*** rtollert <rtollert!~rtollert@> has quit IRC20:44
*** benjamirc <benjamirc!~besquive@> has joined #yocto20:58
*** mranostay <mranostay!~mranostay@pdpc/supporter/active/mranostay> has quit IRC21:01
*** mranostay <mranostay!~mranostay@pdpc/supporter/active/mranostay> has joined #yocto21:02
*** dmoseley <dmoseley!> has joined #yocto21:12
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has quit IRC21:19
*** rtollert <rtollert!~rtollert@> has joined #yocto21:20
*** rwoolley <rwoolley!~rwoolley@> has quit IRC21:25
*** ylouise <ylouise!~yalouise@> has quit IRC21:36
*** marka <marka!~marka@> has quit IRC21:37
*** Aethenelle <Aethenelle!> has quit IRC21:37
*** ylouise <ylouise!yalouise@nat/intel/x-pylymdvluupkpdzw> has joined #yocto21:37
*** Aethenelle <Aethenelle!> has joined #yocto21:39
*** SorenHolm <SorenHolm!> has quit IRC21:40
*** arcomivi <arcomivi!5b08b219@gateway/web/freenode/ip.> has joined #yocto21:42
arcomivihello:) i would like to ask you for help. 1) I created bitbake core-image-sato 2) deployed .hddimg to USB using USB-ZIP method 3) booted Atom PC from usb -> "ramdisk not found". so i figured out  that /dev/ram0 does not exist in rootfs and also i found out a thread that says CONFIG_BLK_DEV_RAM has to be set in .config file in poky linux-yocto. However, still when bitbaking core-image-sato there is no /dev/ram0 under rootfs. maybe there21:43
arcomivito set CONFIG_BLK_DEV_RAM in?21:43
*** ynezz <ynezz!> has quit IRC21:44
*** challinan <challinan!> has quit IRC21:49
*** jimBaxter <jimBaxter!> has quit IRC21:53
kroonarcomivi, so you set  CONFIG_BLK_DEV_RAM in an additional kernel fragment file ?22:02
kroonarcomivi, it's better to use a fragment file than modifying files under tmp/work/22:05
kroonarcomivi, those changes will be lost when you bitbake clean/rebuild22:06
kroonarcomivi, dunno about linux-yocto kernel, but you might wanna double-check that you have devtmpfs enabled in the kernel by the sounds of it22:06
*** ynezz <ynezz!> has joined #yocto22:08
*** challinan <challinan!> has joined #yocto22:09
arcomivi<kroon> no, i do not have a fragment config/kernel file. I am using standard from linux-yocto build, at least i think this is used.22:10
arcomividevtmpfs - did not look into this again. At least i would not know that this is enabled.22:11
arcomiviCONFIG_DEVTMPFS is enabled under .config in linux-yocto22:12
*** e8johan <e8johan!> has quit IRC22:13
arcomiviso what would be the best way to create a fragment file? an bbappend under poky/meta/recipes-kernel/linux ?22:14
kroonarcomivi, yeah, via a .bbappend file, in preferrably in a layer that you create yourself22:16
kroonarcomivi, "2.2.3. Changing the Configuration"22:16
arcomivi<kroon> yep, already saw this, but actually did not want to use this. I thought a standard would work, but no problem, i will try this option. Is anything else known not working straight forward when booting from USB?22:17
kroonarcomivi, I don't use the Atom, so I'm of no help there22:18
arcomivi<kroon> ok, thank you anyways, i will try to proceed ;)22:19
kroonarcomivi, no problem, good luck22:20
arcomivikroon, thank you! i will need it22:22
*** bluelightning <bluelightning!~paul@2001:8b0:258:7d7a:2ad2:44ff:fe40:9209> has joined #yocto22:23
*** bluelightning <bluelightning!~paul@2001:8b0:258:7d7a:2ad2:44ff:fe40:9209> has quit IRC22:23
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto22:23
*** demonimin_ <demonimin_!~demonimin@unaffiliated/demonimin> has joined #yocto22:29
*** demonimin <demonimin!~demonimin@unaffiliated/demonimin> has quit IRC22:31
*** rec <rec!> has joined #yocto22:34
*** Jefro <Jefro!> has quit IRC22:35
*** rec <rec!> has left #yocto22:36
*** bcochran <bcochran!> has joined #yocto22:37
*** Jefro <Jefro!> has joined #yocto22:38
*** Aethenelle <Aethenelle!> has quit IRC22:39
*** bfederau <bfederau!> has quit IRC23:01
*** bfederau <bfederau!> has joined #yocto23:01
*** zeddii_home <zeddii_home!> has joined #yocto23:02
*** melio_cc <melio_cc!> has quit IRC23:03
*** rburton <rburton!> has quit IRC23:04
*** benjamirc <benjamirc!~besquive@> has quit IRC23:05
*** noisebleed <noisebleed!~quassel@gentoo/contributor/noisebleed> has quit IRC23:23
*** hirata <hirata!> has quit IRC23:26
*** jbrianceau_away <jbrianceau_away!uid10952@gateway/web/> has joined #yocto23:28
*** noisebleed <noisebleed!~quassel@gentoo/contributor/noisebleed> has joined #yocto23:28
*** hirata <hirata!> has joined #yocto23:28
*** arcomivi <arcomivi!5b08b219@gateway/web/freenode/ip.> has quit IRC23:29
*** chankit1 <chankit1!~oneam@> has quit IRC23:34
*** hirata <hirata!> has quit IRC23:40
*** mranostay <mranostay!~mranostay@pdpc/supporter/active/mranostay> has quit IRC23:40
*** mranostay <mranostay!~mranostay@pdpc/supporter/active/mranostay> has joined #yocto23:41
*** hirata <hirata!> has joined #yocto23:41

Generated by 2.11.0 by Marius Gedminas - find it at!