Thursday, 2016-07-07

*** paulg <paulg!~paulg@> has quit IRC00:10
*** nighty <nighty!> has joined #yocto00:18
*** paulg <paulg!> has joined #yocto00:34
*** dreyna <dreyna!> has quit IRC00:34
*** tjamison <tjamison!~tjamison@> has left #yocto00:57
*** evanmeagher <evanmeagher!> has quit IRC01:02
*** billr <billr!~wcrandle@> has quit IRC01:08
*** Jefro <Jefro!> has quit IRC01:24
wrmrxquestion - is there an easy way to add a repository that isn't available on git to a toaster configuration? i've tried editing toasterconf.json but i'm not sure where in the file it goes01:40
wrmrxi have some board support files from NXP that i need to be made available to bitbake but i'm not sure how to add it via the administrator interface nor through editing the json file, since both seem to want to be linked to a git repository01:41
*** crankslider <crankslider!~slidercra@unaffiliated/slidercrank> has quit IRC01:42
khemwrmrx:what kind of files are these01:45
khemit could be better that you write a recipe for it and hold these files together in a tarball somewhere in your n/w01:45
wrmrxit's a layer with some machine definitions and some patches01:46
bluelightningas far as metadata goes, if you want to use local layers with Toaster you use the "import layer" function01:46
*** god <god!> has quit IRC01:47
wrmrxfrom the toaster ui? doesn't that ask you for a remote repo name?01:47
khemfile:///path/to/local/fs might work too01:50
wrmrxas vcs_url?01:50
*** paulg <paulg!> has quit IRC01:50
wrmrxalso - currently, i'm putting the entry for the repo on the same level under "layers": [] listed here:
wrmrxis that correct or should it be a separate layer source?01:51
wrmrxi'm assuming it should be okay because i put my non-tracked layer in the same folder as meta-yocto and meta-yocto-bsp01:52
bluelightningthe actual location on disk is not important (or it shouldn't be...)01:52
wrmrxas long as it's within the scope of "../../" ?01:53
wrmrx(as described by "apiurl" on the top level)01:53
*** blueness <blueness!~blueness@gentoo/developer/blueness> has quit IRC01:55
wrmrxi mean, isn't a local layer the procedure through which people might want to work on patches and build through toaster?01:58
*** evanmeagher <evanmeagher!> has joined #yocto02:02
bluelightningAFAIK, layers should be specified using an absolute path, that means they can be anywhere02:05
wrmrxah, okay02:05
bluelightningbtw if you have Toaster-related questions that you don't get answers to, you might get more informed responses by posting to the toaster mailing list02:06
wrmrxthen, in the example toasterconf.json, why is it that the default apiurl is "../../" and all the layers on that source are relative to that?02:06
wrmrxthanks, i'll keep that in mind02:06
bluelightningI'm not sure I'm afraid02:07
wrmrxi may just return to doin it by hand, i'm not sure toaster actually offers too much that i don't already have besides possibly a visual frontend02:07
bluelightningit may be worth keeping in mind that toasterconf.json is just what gets used to create the database, once it's created you should use the Toaster main UI and/or the Toaster admin interface to configure it02:08
wrmrxah, okay02:08
bluelightningbeing able to examine the build output through Toaster is useful, but then you don't need to actually start your builds through Toaster for that (there's another mode where it just collects data for a command-line build)02:09
wrmrxyep, that's where you launch it with source, correct?02:12
*** cference <cference!> has quit IRC02:14
wrmrxalso -- quick last question -- thanks so much for helping me thus far -- i'm trying to compile yocto with kernel dynamic debug messages turned on, and i've tried a few different things02:15
wrmrxas per this file ( i see that i'm supposed to enable a flag in the kernel config file, which as i understand it gets built up from many config files throughout the layers02:16
wrmrxso what's the easiest way to just set one flag? i tried writing a patch to add a config fragment, but it didn't seem to work; and the only kernel flag that i can set with bitbake -c menuconfig doesn't give me the level of logging that i want02:16
armpitmmm, toast02:19
*** evanmeagher <evanmeagher!> has quit IRC02:21
bluelightningwrmrx: by "the only kernel flag you could set" do you mean CONFIG_DYNAMIC_DEBUG ?02:22
bluelightningwrmrx: which other ones are there?02:22
wrmrxthe one listed in menuconfig is just DYNAMIC_DEBUG02:24
bluelightningright, the same thing then02:24
wrmrxso that should work?02:24
bluelightningit should, I don't see any others listed in that document02:24
bluelightningI don't have any knowledge of dynamic debugging in the kernel though02:25
wrmrxi'll give it another shot02:25
bluelightningjust going by what I read in that text file02:25
bluelightningnote that just turning that option on isn't enough according to that, it looks like you actually need to tell it to turn on debug output for individual files at runtime02:25
wrmrxi haven't gotten it to the point where anything is visible at /sys/kernel/debug/dynamic_debug02:26
wrmrxit mounts debugfs ok but the dynamic_debug directory isn't there02:26
bluelightningyou may need to talk to someone with actual kernel experience then I'm afraid02:27
bluelightningI can certainly tell you how to determine if that option is really on for the kernel you built though02:27
wrmrxah that is very useful02:29
wrmrxyes p&ty02:29
wrmrxesp. given that i've been calling menuconfig with the target virtual/kernel and im' not 100% on whether that actually applies to my target, which is for a specific SCM02:31
bluelightningfirst run bitbake -e virtual/kernel | grep ^STAGING_KERNEL_BUILDDIR=02:44
bluelightningthen grep CONFIG_DYNAMIC_DEBUG on the .config file in the directory that reports02:44
*** wrmrx <wrmrx!0cc9f26a@gateway/web/freenode/ip.> has quit IRC02:49
*** evanmeagher <evanmeagher!> has joined #yocto02:52
*** blueness <blueness!~blueness@gentoo/developer/blueness> has joined #yocto03:25
*** moto-timo <moto-timo!~ttorling@> has joined #yocto03:52
*** moto-timo <moto-timo!~ttorling@fsf/member/moto-timo> has joined #yocto03:52
*** yann|work <yann|work!> has quit IRC04:00
*** marquiz_ <marquiz_!~marquiz@> has quit IRC04:03
*** ulf^ <ulf^!> has joined #yocto04:13
*** yann|work <yann|work!> has joined #yocto04:15
*** _stephan <_stephan!~stephan@> has joined #yocto04:15
*** blueness <blueness!~blueness@gentoo/developer/blueness> has quit IRC04:29
*** ulf^ <ulf^!> has quit IRC04:40
*** gtristan <gtristan!~tristanva@> has quit IRC05:02
*** AndersD <AndersD!> has joined #yocto05:10
*** AndersD <AndersD!> has quit IRC05:13
*** AndersD <AndersD!> has joined #yocto05:13
*** evanmeagher <evanmeagher!> has quit IRC05:15
*** evanmeagher <evanmeagher!> has joined #yocto05:16
*** aehs29 <aehs29!~aehernan@> has left #yocto05:18
*** evanmeagher <evanmeagher!> has quit IRC05:21
*** evanmeagher <evanmeagher!> has joined #yocto05:29
*** Nilesh_ <Nilesh_!uid116340@gateway/web/> has joined #yocto05:31
*** evanmeagher <evanmeagher!> has quit IRC05:33
*** wenzong <wenzong!~wfan@> has quit IRC05:42
*** wenzong <wenzong!~wfan@> has joined #yocto05:43
*** gtristan <gtristan!~tristanva@> has joined #yocto05:49
*** mwarning <mwarning!~mwarning@2001:a60:a07d:1:f1a7:7fd5:cd33:a84c> has joined #yocto05:56
*** dreyna <dreyna!> has joined #yocto06:09
*** frsc <frsc!~frsc@> has joined #yocto06:10
*** sujith_h <sujith_h!~toaster@kde/developers/sujithh> has joined #yocto06:11
*** pohly <pohly!> has joined #yocto06:12
*** TobSnyder <TobSnyder!> has joined #yocto06:15
*** toanju <toanju!~toanju@> has joined #yocto06:15
*** demonimin <demonimin!~demonimin@unaffiliated/demonimin> has quit IRC06:16
*** WarheadsSE <WarheadsSE!> has quit IRC06:22
*** agust <agust!> has joined #yocto06:23
*** WarheadsSE <WarheadsSE!> has joined #yocto06:23
*** ziggo <ziggo!~ziggo@> has quit IRC06:39
*** ziggo <ziggo!~ziggo@> has joined #yocto06:39
*** obsrwr <obsrwr!~otp-amois@> has joined #yocto06:52
-YoctoAutoBuilder- build #928 of nightly is complete: Success [build successful] Build details are at
*** jbrianceau <jbrianceau!uid10952@gateway/web/> has joined #yocto06:54
*** sambaran <sambaran!~sambaran@> has joined #yocto06:55
*** t0mmy <t0mmy!~tprrt@> has joined #yocto06:56
sambaranguys is toaster working with the master branch?06:56
sambaranfor me it shows error06:56
*** townxelliot <townxelliot!~ell@> has joined #yocto06:59
*** oan <oan!> has quit IRC07:00
*** townxelliot <townxelliot!~ell@> has joined #yocto07:01
*** csanchezdll <csanchezdll!> has joined #yocto07:04
*** fredcadete <fredcadete!d4a63893@gateway/web/freenode/ip.> has left #yocto07:06
*** fredcadete <fredcadete!d4a63893@gateway/web/freenode/ip.> has joined #yocto07:06
*** phatina <phatina!> has quit IRC07:08
*** phatina <phatina!> has joined #yocto07:08
*** bachp <bachp!~bachp@> has joined #yocto07:09
*** fl0v0 <fl0v0!> has joined #yocto07:13
*** rajm <rajm!> has joined #yocto07:13
*** florian <florian!~fuchs@Maemo/community/contributor/florian> has joined #yocto07:26
*** boucman_work <boucman_work!> has joined #yocto07:28
*** jku <jku!jku@nat/intel/x-kgomgpmfcpiipylj> has joined #yocto07:30
*** mathieu1 <mathieu1!> has joined #yocto07:33
*** sno <sno!> has quit IRC07:33
*** joshuagl <joshuagl!joshuagl@nat/intel/x-ipbdcjqjpwitatci> has joined #yocto07:33
*** vdehors_ <vdehors_!> has joined #yocto07:44
*** josep <josep!> has quit IRC07:44
*** vdehors <vdehors!~vdehors@> has quit IRC07:48
*** edbart <edbart!ebartosh@nat/intel/x-phmcznotkstaegrr> has joined #yocto07:51
*** rburton <rburton!> has joined #yocto07:53
*** toscalix <toscalix!~toscalix@> has joined #yocto07:53
*** crankslider <crankslider!~slidercra@unaffiliated/slidercrank> has joined #yocto07:56
*** blueness <blueness!~blueness@gentoo/developer/blueness> has joined #yocto07:57
*** rubdos <rubdos!> has joined #yocto08:00
*** CoLa|work <CoLa|work!~cordlandw@> has joined #yocto08:06
*** fredcadete <fredcadete!d4a63893@gateway/web/freenode/ip.> has quit IRC08:09
*** fredcadete <fredcadete!d4a63893@gateway/web/freenode/ip.> has joined #yocto08:13
*** dreyna <dreyna!> has quit IRC08:16
*** maxin <maxin!> has joined #yocto08:18
*** Biliogadafr <Biliogadafr!> has joined #yocto08:21
*** oan <oan!> has joined #yocto08:40
*** sno <sno!~sno@> has joined #yocto08:43
*** belen <belen!Adium@nat/intel/x-jkvvzilzvysqiruy> has joined #yocto08:49
*** belen <belen!Adium@nat/intel/x-jkvvzilzvysqiruy> has quit IRC08:51
*** belen <belen!~Adium@> has joined #yocto08:51
*** sameo_ <sameo_!~samuel@> has joined #yocto08:54
*** belen <belen!~Adium@> has quit IRC08:55
*** sgw_ <sgw_!~sgw_@> has quit IRC08:59
*** belen <belen!~Adium@> has joined #yocto08:59
*** sgw_ <sgw_!~sgw_@> has joined #yocto09:00
*** crankslider <crankslider!~slidercra@unaffiliated/slidercrank> has quit IRC09:00
*** RzR <RzR!~RzR@> has quit IRC09:03
*** RzR <RzR!~RzR@unaffiliated/rzr> has joined #yocto09:03
*** t0mmy <t0mmy!~tprrt@> has quit IRC09:13
*** t0mmy <t0mmy!~tprrt@> has joined #yocto09:14
*** mathieu_la <mathieu_la!> has joined #yocto09:14
*** Jefro <Jefro!> has joined #yocto09:16
*** gaurang <gaurang!74c5b80b@gateway/web/freenode/ip.> has joined #yocto09:21
gauranghi developers09:26
*** grma <grma!~gruberm@> has joined #yocto09:26
gauranghow can we maintain linux kernel continuous development out of the yocto tree, still having some dependent recipes (like perf) inside yocto layer09:27
gaurangany suggestion09:27
boucman_workdo you need to modify perf or just recompile it with your modified kernel ?09:28
boucman_work(I am not sure how tools like perf are built, yocto-wise)09:28
gaurangthere are even some kernel dependent recipes as well09:29
boucman_workgaurang: and how do you develop your kernel ? do you use devtool (I think devtool can be used on kernels) externalsrc ? or do you just compile out of yocto and then replace the kernel on the generate images ?09:29
gaurangcurrently it is inside yocto only09:30
gaurangbut like for continous development environment09:30
gauranglike shall i build full yocto everytime when kernel developer commit their changes in git ??09:31
-YoctoAutoBuilder- build #929 of nightly is complete: Failure [failed] Build details are at
boucman_workok, so your devs work on their own git, then push to a repo and your CI infrastructure pulls from that repo, right ?09:32
gaurangwe have seperate kernel developers, who will keep committing their changes in git09:32
*** evanmeagher <evanmeagher!> has joined #yocto09:32
gaurangyes kernel recipe is pointing to private repo09:33
gaurangso for each commit, is it OK to build Yocto everytime? I don't think this is good idea09:33
gaurangand I also need to take care kernel dependent other recipes09:34
gaurangso confused like what is the best way to maintain always TOT of kernel ?09:34
boucman_workgaurang: i am not sure I understand your question... it depends on the capacity of your CI, it's not really a yocto question09:34
gaurangso you mean to say, per kernel commit, one yocto build ??09:35
boucman_workI personnaly would rebuild nightly rather than on every commit, but that's really a question for you to answer...09:35
boucman_workyocto is good at building "only what is needed" but when the kernel is changed, "what is needed" can be quite large09:36
gaurangyes correct09:36
*** evanmeagher <evanmeagher!> has quit IRC09:37
gaurangbecause not i need to maintain kernel build, dependent recipe should also be built when there is a kernel change09:38
gaurangso that is a big problem09:38
fredcadetegaurang: are there that many recipes dependent on the *kernel*? considering that linux-libc-headers are separate09:40
gaurangi would say for me its 8-9 recipes09:41
boucman_workthat's not many, you can probably rebuild at every commit...09:41
*** chatter <chatter!> has joined #yocto09:42
*** chatter is now known as mathieu_la09:42
*** mathieu1 <mathieu1!> has quit IRC09:44
*** mathieu_la <mathieu_la!> has joined #yocto09:44
*** nighty <nighty!> has quit IRC09:47
*** mathieu_la <mathieu_la!> has quit IRC09:53
*** lewiatan_ <lewiatan_!> has joined #yocto09:54
fredcadetegaurang: maybe I'm not understanding your cost of "build full Yocto". Consider as well that if you reuse sstate, only the kernel+dependent recipes are built for that use case09:55
*** mathieu_la <mathieu_la!> has joined #yocto09:55
gaurangyes cost is not much, but i would like to understand what is the best practise available and yocto developers are using09:57
lewiatan_Hi. What will happen if I set do_configure_prepend() in my *.bbappend but such task is already in *.bb? I'm asking because I need to prepend something to existing prepend without changing original recipe.09:58
fredcadetegaurang: ack. I'd also like to know of a better way if there is one09:59
*** Jefro <Jefro!> has quit IRC10:04
*** armpit <armpit!~akuster@2601:202:4001:9ea0:ddc0:e30a:8ba7:370c> has quit IRC10:05
rburtonlewiatan_: you can have multiple _prepends or _appends and they all apply10:06
lewiatan_Great. Thank you rburton (and sorry to others for getting in the middle of conversation)10:07
*** armpit <armpit!~akuster@2601:202:4001:9ea0:ddc0:e30a:8ba7:370c> has joined #yocto10:08
*** maxin <maxin!> has quit IRC10:09
*** mathieu_la <mathieu_la!> has quit IRC10:13
-YoctoAutoBuilder- build #240 of nightly-checkuri is complete: Success [build successful] Build details are at
*** mathieu_ <mathieu_!> has joined #yocto10:17
*** RzR <RzR!~RzR@unaffiliated/rzr> has left #yocto10:22
*** maxin <maxin!~maxin@2001:998:22:0:a9ed:7d21:23f1:b8d7> has joined #yocto10:29
*** clopez <clopez!> has quit IRC10:29
*** clopez <clopez!> has joined #yocto10:33
*** t0mmy <t0mmy!~tprrt@> has quit IRC10:33
*** gaurang <gaurang!74c5b80b@gateway/web/freenode/ip.> has quit IRC10:43
*** fl0v01 <fl0v01!> has joined #yocto10:48
*** fl0v0 <fl0v0!> has quit IRC10:50
*** gtristan <gtristan!~tristanva@> has quit IRC10:51
*** learning_yocto <learning_yocto!d997f20f@gateway/web/freenode/ip.> has joined #yocto10:51
learning_yoctoHi! Is there any yocto variable with the absolute path of the layer in which your recipe is?10:51
*** belen <belen!~Adium@> has quit IRC10:52
*** present <present!~present@> has joined #yocto10:55
*** belen <belen!~Adium@> has joined #yocto10:56
-YoctoAutoBuilder- build #395 of nightly-wic is complete: Failure [failed BuildImages_3 CreateWicImages_2 CreateWicImages_3 CreateWicImages_4] Build details are at
*** t0mmy <t0mmy!~tprrt@> has joined #yocto11:02
rburtonlearning_yocto: THISDIR?11:11
learning_yoctoThat points to the recipe dir... I guess  could do ../../.. from there11:12
learning_yoctobut it would be nice if there was a varaible for the layer paht11:12
*** nighty <nighty!> has joined #yocto11:12
fredcadetelearning_yocto: LAYERDIR?11:13
fredcadeteoops it's only for layer.conf11:13
*** frsc <frsc!~frsc@> has quit IRC11:17
boucman_worklearning_yocto: out of curiosity, why do you need that ?11:29
*** maxin1 <maxin1!> has joined #yocto11:30
*** maxin <maxin!~maxin@2001:998:22:0:a9ed:7d21:23f1:b8d7> has quit IRC11:31
*** townxelliot <townxelliot!~ell@> has quit IRC11:35
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC11:42
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto11:45
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC11:46
*** frsc <frsc!~frsc@> has joined #yocto11:47
*** phatina <phatina!> has quit IRC11:47
*** phatina <phatina!> has joined #yocto11:49
learning_yoctofredcadete: Yes.. I wish that was available from the recipies too....11:50
learning_yoctoboucman_work: because I have some scripts in a "scripts" folder under the layer. some packages need to call these scripts, so I need the path11:50
rburtonset a variable in the layer.conf11:51
*** frsc <frsc!~frsc@> has quit IRC11:52
*** frsc <frsc!~frsc@> has joined #yocto11:54
*** ziggo <ziggo!~ziggo@> has quit IRC11:55
learning_yoctoUmh, I will try that11:58
learning_yoctoBTW, is there a variable with the name of the workspace?11:59
learning_yoctowith the path *11:59
boucman_workwhat do you mean by workspace ? $TOPDIR ?12:00
*** florian <florian!~fuchs@Maemo/community/contributor/florian> has quit IRC12:03
learning_yoctoYes! thanks12:14
*** obsrwr <obsrwr!~otp-amois@> has quit IRC12:19
*** lamego <lamego!~jose@> has joined #yocto12:23
*** mago__ <mago__!~mago@unaffiliated/blastur> has quit IRC12:24
*** fledermaus <fledermaus!~vivek@2a00:1098:5:0:49b6:6ca:be5e:7b6c> has joined #yocto12:24
*** berton <berton!~fabio@> has joined #yocto12:34
*** _stephan <_stephan!~stephan@> has quit IRC12:42
learning_yoctoI am trying to make a recipe for some binaries which are needed on the development machine. They should also be included ni the sdk12:46
*** jku <jku!jku@nat/intel/x-kgomgpmfcpiipylj> has quit IRC12:46
learning_yoctoI have used BBCLASSEXTEND = "native nativesdk" and I have added "DEPENDS += " mypackage-native" in those packages which need them12:46
boucman_workDEPENDS is a recipe name, not a package name IIRC12:47
learning_yoctoNot sure how to implement the do_install() on the recipe for the native packages... The do_compile() generates several binaries in different paths. How should I implement the do_install method in order to have the binaries I need copieed?12:47
boucman_workor am I confused...12:47
*** WarheadsSE <WarheadsSE!> has left #yocto12:47
rburtoneveryone is confused!12:49
rburtonthe recipe should use bbclassextend to be buildable for native and nativesdk12:49
learning_yoctoYep, I have done that12:49
rburtonwhat do_install does is up to how the source builds, but generally speaking a do_install should work for all instances12:49
rburtonthen a recipe which needs foo-native to build should depend on foo-native, as you say12:50
learning_yoctoyeah, so my source is a little bit special12:50
learning_yoctoIn the do_compile several bianries are created12:50
*** ziggo <ziggo!> has joined #yocto12:50
learning_yoctonow I think in the do_install I need to copy them to some folder (${D}${bindir} ... ?) in order to be able to use them from any recipe12:50
learning_yoctooh, so is ${D}${bindir} the right folder?12:51
learning_yoctodo I also need to create any symbolic link?12:51
rburtonyes, and only if you want to make symlinks12:51
rburtonyou don't need to12:51
rburtonif you want nativesdk-foo in your SDK too - so you can run the binaries whilst using the sdk - then you need a variable i can't recall the name of12:52
learning_yoctoyes, I also need that12:52
learning_yoctotoo bad you can recall that number =(12:52
learning_yoctothat name *12:52
learning_yoctothat name *12:53
learning_yoctooh, i see what you mean12:55
learning_yoctook, i will look for that variable12:55
rburtonyeah maybe append SDK_RDEPENDS in your image recipe with nativesdk-foo12:56
rburtonclearly this bit needs better documentation12:56
learning_yoctoshouldn't it be SDK_DEPENDS rather than SDK_RDEPENDS?12:57
learning_yoctothese are compile time dependencies12:57
*** igor2 <igor2!~igor@> has joined #yocto13:00
rburtonSDK_DEPENDS is stuff that you need to build the sdk with13:01
*** ntl <ntl!> has joined #yocto13:01
rburtonyou want RDEPENDS, things you want in the SDK13:01
rburton(I think)13:01
learning_yoctothanks again13:01
*** paulg <paulg!> has joined #yocto13:02
*** Nilesh_ <Nilesh_!uid116340@gateway/web/> has quit IRC13:17
*** gtristan <gtristan!~tristanva@> has joined #yocto13:23
*** edbart <edbart!ebartosh@nat/intel/x-phmcznotkstaegrr> has quit IRC13:25
*** blueness <blueness!~blueness@gentoo/developer/blueness> has quit IRC13:30
*** edbart <edbart!ebartosh@nat/intel/x-yhoeaksmhpffbxzg> has joined #yocto13:30
*** evanmeagher <evanmeagher!> has joined #yocto13:33
*** agust <agust!> has quit IRC13:35
*** evanmeagher <evanmeagher!> has quit IRC13:38
*** blueness <blueness!~blueness@gentoo/developer/blueness> has joined #yocto13:55
*** nisha <nisha!~nisha@> has joined #yocto13:56
*** blueness <blueness!~blueness@gentoo/developer/blueness> has quit IRC13:56
*** nisha is now known as Guest5401713:56
*** Guest54017 <Guest54017!~nisha@> has quit IRC13:57
*** nish <nish!~nisha@> has joined #yocto13:57
*** nish is now known as nisha13:58
*** AndersD <AndersD!> has quit IRC13:58
*** madisox <madisox!~madison@> has joined #yocto14:03
*** tjamison <tjamison!~tjamison@> has joined #yocto14:06
*** agust <agust!> has joined #yocto14:07
*** sambaran <sambaran!~sambaran@> has quit IRC14:11
*** blueness <blueness!~blueness@gentoo/developer/blueness> has joined #yocto14:12
*** jku <jku!> has joined #yocto14:13
*** mathieu_la <mathieu_la!> has joined #yocto14:16
*** mathieu_ <mathieu_!> has quit IRC14:16
*** moto-timo <moto-timo!~ttorling@fsf/member/moto-timo> has quit IRC14:16
*** abelloni_ is now known as abelloni14:26
*** belen <belen!~Adium@> has quit IRC14:29
*** belen <belen!~Adium@> has joined #yocto14:29
*** csanchezdll <csanchezdll!> has left #yocto14:29
*** billr <billr!> has joined #yocto14:33
*** igor2 <igor2!~igor@> has quit IRC14:33
*** igor2 <igor2!~igor@> has joined #yocto14:33
*** aehs29 <aehs29!~aehernan@> has joined #yocto14:42
*** TobSnyder <TobSnyder!> has quit IRC14:43
*** yann|work <yann|work!> has quit IRC14:48
*** dreyna <dreyna!> has joined #yocto14:48
*** bachp <bachp!~bachp@> has quit IRC14:59
*** yann|work <yann|work!> has joined #yocto15:03
*** ziggo <ziggo!> has quit IRC15:03
*** Nilesh_ <Nilesh_!uid116340@gateway/web/> has joined #yocto15:08
joshuaglvmeson: could you CC me, or let me know the # here, when you file the createrepo bug?15:09
*** frsc <frsc!~frsc@> has quit IRC15:12
*** toanju <toanju!~toanju@> has quit IRC15:13
*** ntl <ntl!> has quit IRC15:17
*** maxin1 <maxin1!> has quit IRC15:18
*** fredcadete <fredcadete!d4a63893@gateway/web/freenode/ip.> has quit IRC15:22
*** benjamirc <benjamirc!~besquive@> has joined #yocto15:24
*** lpapp <lpapp!~lpapp@kde/lpapp> has joined #yocto15:24
lpapphey, why cannot opkg overwrite symlinks if some nasty colleague replaces symlinks manually in /usr/lib?15:24
lpappif I say opkg install mylib.15:24
*** billr <billr!> has quit IRC15:26
*** paulg <paulg!> has quit IRC15:27
*** lewiatan_ <lewiatan_!> has left #yocto15:28
*** sgw_ <sgw_!~sgw_@> has quit IRC15:32
*** sgw_ <sgw_!~sgw_@> has joined #yocto15:32
*** t0mmy <t0mmy!~tprrt@> has quit IRC15:37
*** rajm <rajm!> has quit IRC15:42
*** boucman_work <boucman_work!> has quit IRC15:51
*** florin <florin!~florin@> has joined #yocto15:53
florinhi guys15:53
*** mwarning <mwarning!~mwarning@2001:a60:a07d:1:f1a7:7fd5:cd33:a84c> has quit IRC15:53
*** florin is now known as Guest8079315:54
Guest80793how can one know which version of bitbake works with a certain branch of openembedded?15:54
Guest80793hi all15:54
Guest80793more specifically, I need to know which version of bitbake works with the krogoth branch of openembedded15:54
Guest80793openembedded-core that is15:55
*** present <present!~present@> has quit IRC15:55
rburtonGuest80793:, second table15:55
*** ntl <ntl!> has joined #yocto15:57
*** joshuagl <joshuagl!joshuagl@nat/intel/x-ipbdcjqjpwitatci> has quit IRC15:57
Guest80793rburton, I tried that, using bitbake 1.30 and openembedded-core krogoth but I get this error15:58
Guest80793whereas this does not happen if using master of bitbake15:58
Guest80793so I thought I did not get the correct matching between bitbake and openembedded-core but apparently there is a problem there15:59
*** jku <jku!> has quit IRC15:59
*** evanmeagher <evanmeagher!> has joined #yocto16:04
*** billr <billr!~wcrandle@> has joined #yocto16:05
*** belen <belen!~Adium@> has quit IRC16:09
*** belen <belen!~Adium@> has joined #yocto16:10
*** maxin <maxin!> has joined #yocto16:16
*** maxin <maxin!> has quit IRC16:22
*** anselmolsm <anselmolsm!~anselmols@> has joined #yocto16:28
*** edbart <edbart!ebartosh@nat/intel/x-yhoeaksmhpffbxzg> has quit IRC16:32
*** obsrwr_home <obsrwr_home!~obsrwr@> has joined #yocto16:32
*** edbart <edbart!ebartosh@nat/intel/x-izxxzpdahgpgrssr> has joined #yocto16:33
*** edbart1 <edbart1!ebartosh@nat/intel/x-eqsgmevywehonugv> has joined #yocto16:35
*** edbart <edbart!ebartosh@nat/intel/x-izxxzpdahgpgrssr> has quit IRC16:39
*** edbart1 <edbart1!ebartosh@nat/intel/x-eqsgmevywehonugv> has quit IRC16:40
*** sa2ajj <sa2ajj!> has joined #yocto16:52
*** sno <sno!~sno@> has quit IRC16:55
*** yann|work <yann|work!> has quit IRC16:58
*** grma <grma!~gruberm@> has quit IRC16:59
*** fl0v01 <fl0v01!> has quit IRC17:08
*** aehs29 <aehs29!~aehernan@> has left #yocto17:10
*** jbrianceau is now known as jbrianceau_away17:18
*** belen <belen!~Adium@> has quit IRC17:25
*** obsrwr_6 <obsrwr_6!~obsrwr@> has joined #yocto17:29
*** obsrwr_home <obsrwr_home!~obsrwr@> has quit IRC17:29
-YoctoAutoBuilder- build #396 of nightly-wic is complete: Success [build successful] Build details are at
*** benjamirc1 <benjamirc1!~besquive@> has joined #yocto17:31
*** benjamirc <benjamirc!~besquive@> has quit IRC17:31
-YoctoAutoBuilder- build #875 of nightly-x86-64 is complete: Failure [failed Running Sanity Tests] Build details are at
*** paulg <paulg!> has joined #yocto17:34
*** benjamirc1 <benjamirc1!~besquive@> has quit IRC17:36
*** fredcadete_ <fredcadete_!51f356a0@gateway/web/freenode/ip.> has quit IRC17:49
*** belen <belen!~Adium@> has joined #yocto17:54
khemlpapp: opkg by default will not override however it does have options to do so17:55
khemand if you are overriting files from different package its going to land you in trouble later when you update the original package.17:56
khemso its better to resolve the namesapce issue beforehand17:56
*** obsrwr_home <obsrwr_home!~obsrwr@> has joined #yocto17:58
lpappkhem: it did not seem to overwrite with the overwrite options, either.17:58
*** obsrwr_6 <obsrwr_6!~obsrwr@> has quit IRC17:59
khemdid you use --force-overwrite17:59
lpappkhem: I tried --force-overwrite and --force-reinstall17:59
kheminteresting. here it has worked18:00
khemwhenever tried18:00
*** lpapp <lpapp!~lpapp@kde/lpapp> has quit IRC18:00
*** fester <fester!~fester@rhlug/fester> has joined #yocto18:08
festerso i have a device that boots an image that i think was built from yocto, how can i tell which target image it has?18:10
festerlike core-image-full-cmdline or core-image-lsb-sdk ?18:11
khemfester: I dont think we have a standard way to denote that, however you may ask your device vendor if they have a version info file embedded into your rootfs18:13
festeris there a typical location where that info might be found?18:16
festerkhem: thanks, by the way18:17
*** aehs29 <aehs29!~aehernan@> has joined #yocto18:19
*** DriverCoder <DriverCoder!~mdrustad@> has joined #yocto18:21
*** sameo_ <sameo_!~samuel@> has quit IRC18:22
-YoctoAutoBuilder- build #580 of nightly-oe-selftest is complete: Failure [failed Running oe-selftest] Build details are at
*** toscalix <toscalix!~toscalix@> has quit IRC18:31
*** evanmeagher <evanmeagher!> has quit IRC18:32
*** billr <billr!~wcrandle@> has quit IRC18:32
*** dreyna <dreyna!> has quit IRC18:37
*** toanju <toanju!> has joined #yocto18:39
*** bluelightning <bluelightning!> has joined #yocto18:49
*** bluelightning <bluelightning!> has quit IRC18:49
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto18:49
*** evanmeagher <evanmeagher!> has joined #yocto18:52
*** Nilesh_ <Nilesh_!uid116340@gateway/web/> has quit IRC19:07
*** dmoseley <dmoseley!> has joined #yocto19:11
*** toanju <toanju!> has quit IRC19:14
*** crankslider <crankslider!~slidercra@unaffiliated/slidercrank> has joined #yocto19:17
*** sno <sno!> has joined #yocto19:22
*** benjamirc <benjamirc!~besquive@> has joined #yocto19:24
khemfester: if the image has a package management tool like rpm or opkg on it then you may see what all packages are installed and deduce from that19:26
*** jbrianceau_away <jbrianceau_away!uid10952@gateway/web/> has quit IRC19:29
*** dreyna <dreyna!> has joined #yocto19:42
*** jku <jku!> has joined #yocto19:46
*** maxin <maxin!> has joined #yocto19:47
*** ecdhe_ <ecdhe_!> has quit IRC19:52
*** ecdhe <ecdhe!> has quit IRC19:52
*** belen <belen!~Adium@> has quit IRC19:52
*** yann|work <yann|work!> has joined #yocto20:04
*** fledermaus <fledermaus!~vivek@2a00:1098:5:0:49b6:6ca:be5e:7b6c> has quit IRC20:04
*** moto-timo <moto-timo!~ttorling@> has joined #yocto20:05
*** moto-timo <moto-timo!~ttorling@> has quit IRC20:05
*** moto-timo <moto-timo!~ttorling@fsf/member/moto-timo> has joined #yocto20:05
*** jku <jku!> has quit IRC20:13
*** yann|work <yann|work!> has quit IRC20:14
*** psadro <psadro!~Thunderbi@> has quit IRC20:15
*** DriverCoder <DriverCoder!~mdrustad@> has quit IRC20:20
*** dmoseley <dmoseley!> has quit IRC20:21
*** tripzero <tripzero!~tripzero@> has quit IRC20:28
*** ntl <ntl!> has quit IRC20:29
*** psadro <psadro!~Thunderbi@> has joined #yocto20:31
*** tripzero <tripzero!~tripzero@> has joined #yocto20:36
-YoctoAutoBuilder- build #876 of nightly-x86-64 is complete: Success [build successful] Build details are at
*** __karthik <__karthik!~karthik@> has quit IRC20:44
*** __karthik <__karthik!~karthik@> has joined #yocto20:44
*** sgw_ <sgw_!~sgw_@> has quit IRC20:48
*** pohly <pohly!> has quit IRC20:56
*** khem <khem!~khem@unaffiliated/khem> has quit IRC21:03
*** maxin <maxin!> has quit IRC21:06
*** sgw_ <sgw_!~sgw_@> has joined #yocto21:07
*** Guest80793 is now known as florin_21:08
*** florin_ is now known as florin21:08
*** florin is now known as flor__21:08
flor__rburton, any clue about the rror I posted above?21:08
*** lamego <lamego!~jose@> has quit IRC21:09
*** obsrwr_home <obsrwr_home!~obsrwr@> has quit IRC21:09
*** aehs29 <aehs29!~aehernan@> has left #yocto21:10
RPflor__: it looks like you're trying to run bitbake master with python2 ?21:16
RPflor__: either use oe-core master with bitbake master, or use the 1.30 branch of bitbake with the krogoth branch of oe-core. Master uses python3, the older 1.30 uses python221:17
flor__that error above is with oe-core krogoth and bitbake 1.30, Richard21:18
flor__using oe-core krogoth and master bitbake works21:19
*** berton <berton!~fabio@> has quit IRC21:23
*** khem <khem!~khem@unaffiliated/khem> has joined #yocto21:24
kergothbluelightning, RP: I notice dthe sstate mirror object availability progress bar replaces the preceding initializing tasks progress bar. I think there'd be value in keeping the previous one with its final completion time in the output. Would just need a newline on completion, I expect.21:27
bluelightningkergoth: hmm perhaps yes - I think probably the issue is not calling finish() on the progressbar21:28
kergothah, that'd make sense21:28
*** rubdos <rubdos!> has quit IRC21:38
RPflor__: it is not oe-core krogoth branch there. This is the code in the oe-core krogoth branch: and the get_callable_args() function does not have an inspect.signature() call.21:40
*** maxin <maxin!> has joined #yocto21:40
*** maxin <maxin!> has left #yocto21:40
*** blueness <blueness!~blueness@gentoo/developer/blueness> has quit IRC21:40
RPwell, but its the same code21:41
*** yann|work <yann|work!> has joined #yocto21:51
*** yann|work is now known as yann21:52
*** fester <fester!~fester@rhlug/fester> has left #yocto21:52
*** blueness <blueness!~blueness@gentoo/developer/blueness> has joined #yocto21:55
*** fmeerkoetter <fmeerkoetter!> has quit IRC22:01
*** bfederau <bfederau!> has quit IRC22:01
*** fmeerkoetter <fmeerkoetter!> has joined #yocto22:01
*** bfederau <bfederau!> has joined #yocto22:01
*** gtristan <gtristan!~tristanva@> has quit IRC22:02
*** anselmolsm <anselmolsm!~anselmols@> has quit IRC22:03
*** Crofton|work <Crofton|work!> has quit IRC22:06
*** rburton <rburton!> has quit IRC22:12
*** tjamison <tjamison!~tjamison@> has left #yocto22:28
*** igor2 <igor2!~igor@> has quit IRC22:44
*** benjamirc <benjamirc!~besquive@> has quit IRC22:46
*** evanmeagher <evanmeagher!> has quit IRC22:50
*** agust <agust!> has quit IRC22:54
*** blueness <blueness!~blueness@gentoo/developer/blueness> has joined #yocto23:01
*** sujith_h <sujith_h!~toaster@kde/developers/sujithh> has quit IRC23:16
*** nisha <nisha!~nisha@> has quit IRC23:17
*** evanmeagher <evanmeagher!> has joined #yocto23:17
*** mattsm <mattsm!uid128834@gateway/web/> has joined #yocto23:20
*** nighty <nighty!> has quit IRC23:46
*** dreyna <dreyna!> has quit IRC23:49
*** RP <RP!> has quit IRC23:55
*** paulg <paulg!> has quit IRC23:59

Generated by 2.11.0 by Marius Gedminas - find it at!