**** BEGIN LOGGING AT Wed Jun 11 02:59:59 2014 Jun 11 07:05:39 http://www.draisberghof.de/usb_modeswitch/usb-modeswitch-2.0.1.tar.bz2 Jun 11 07:05:39 http://www.draisberghof.de/usb_modeswitch/usb-modeswitch-2.2.0.tar.bz2 Jun 11 07:34:13 good morning Jun 11 07:48:42 gm Jun 11 07:51:23 howdy Jun 11 08:04:32 meta-oe recipy usb-modeswitch needs a SRCURI update ;) Jun 11 08:04:42 they deleted the old tarball Jun 11 08:30:01 morning ! Jun 11 08:42:08 pompomJuice send patch Jun 11 08:42:19 ok Jun 11 08:42:47 ive been wanting to contribute... just I never have time I am always behind at work Jun 11 08:42:57 I have juicy mono recipies to contruibute Jun 11 09:01:49 morning all Jun 11 09:08:39 morning Jun 11 09:09:54 hi bl and kroon Jun 11 09:12:46 hi kroon, woglinde Jun 11 13:45:41 first ever pull request... take it slow. Jun 11 13:45:57 hehe Jun 11 13:46:09 will be ignored Jun 11 13:46:11 *g* Jun 11 13:46:14 not really Jun 11 13:51:12 hehe Jun 11 13:51:19 we will see Jun 11 13:51:27 I say ship it Jun 11 13:53:19 Next level would be a build server that takes in one pull request at a time and report on whether it builds cleanly... that could save loads of time? Jun 11 13:55:09 nope Jun 11 13:55:18 to many configurations Jun 11 13:55:20 previous level? Jun 11 13:55:29 hectic Jun 11 13:55:35 so how do you test them? Jun 11 13:55:40 who does that work? Jun 11 13:55:46 hm btw. where did you send the patch? Jun 11 13:55:52 intel does Jun 11 13:56:01 or the yocto guys Jun 11 13:56:02 https://github.com/openembedded/meta-openembedded/pull/3 Jun 11 13:56:07 lol Jun 11 13:56:10 wrong Jun 11 13:56:15 damn Jun 11 13:56:26 but gitbub did all the thinking I just said go go Jun 11 13:56:27 did you not wonder why it is 3? Jun 11 13:56:30 yea I did Jun 11 13:56:34 where are the other 2? Jun 11 13:57:24 subscribe to oe@mailinglist not oe-core (but you should in case of sending patches for oe-core) Jun 11 13:57:37 so no pull requests? Jun 11 13:57:39 patches only? Jun 11 13:57:42 than send patches via git send-email Jun 11 13:57:43 yes Jun 11 13:57:50 they end up in patchwork Jun 11 13:57:55 why not pull requests it seems to work? Jun 11 13:58:12 topic [meta-oe] when it is for meta-oe Jun 11 13:58:17 aah ok Jun 11 13:58:41 http://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded Jun 11 13:59:02 thanks... let me get this figured out Jun 11 13:59:03 no hiding behind github account *g* Jun 11 13:59:43 makes sense Jun 11 13:59:49 I had this awesome avatar Jun 11 13:59:59 instant pull request acceptor avatar Jun 11 14:00:10 id accept it Jun 11 14:00:34 ah may bad I searched for scripts/create-pull-request did not know how it was called Jun 11 14:00:54 and did all the stuff by hand Jun 11 14:01:24 say again? Jun 11 14:03:05 no only reminder for me Jun 11 14:03:15 when I ship the next pull request Jun 11 14:04:21 where is that file Jun 11 14:04:22 create-pull-request Jun 11 14:05:04 under scripts somewhere in oe-core Jun 11 14:05:10 not meta-oe Jun 11 14:05:12 bah found it Jun 11 14:05:40 do not forgot meta-oe patches goes to oe ml, oe-core patches goes to oe-core ml Jun 11 14:06:25 step 2 says: Create a branch for your changes if you haven't already. Other than backports from master or fixing bugs that only occur in an older branch, this should be on top of the master branch. Jun 11 14:06:37 will try to keep track of that Jun 11 14:06:52 what does that mean: "ontop of master branch". Jun 11 14:06:59 This patch is for branch daisy Jun 11 14:07:20 the branch I made came from daisy not master... is that a problem? Jun 11 14:08:59 yes Jun 11 14:09:07 first for master than for daisy Jun 11 14:09:18 or if it is already in master Jun 11 14:09:33 than you can send it directly for daisy inclusion Jun 11 14:09:56 ok Jun 11 14:10:01 jo Jun 11 14:10:06 you are welcome Jun 11 14:10:30 will probably have more questions later... for now im gonna try and use those scripts to do the work Jun 11 14:11:07 yes I am heading home Jun 11 14:11:10 till later maybe Jun 11 14:13:36 kk Jun 11 14:13:37 thanks Jun 11 14:13:39 bye Jun 11 14:29:23 koen: we are cleaning things up in the AMD layer and I have a note from you about DISTRO vars Jun 11 14:31:16 create-pull-request -u fork -p "meta-oe][PATCH" Jun 11 14:31:20 does that look correct? Jun 11 14:32:08 I get weird warnings: Unrecognized remote URL: https://github.com/pompomJuice/meta-openembedded.git Jun 11 14:33:10 pompomJuice: for private repos, I usually use ssh, fwiw Jun 11 14:33:35 not really a private repo Jun 11 14:33:54 ssh fwiw? Jun 11 14:34:13 pompomJuice: fwiw = for what it's worth Jun 11 14:34:47 aah Jun 11 14:34:48 ok Jun 11 14:35:03 pompomJuice: hmm, I thought the -p in the create-pull-request script indicates a private github repo Jun 11 14:35:09 aah I see Jun 11 14:35:35 the instructions say I must add that if I want to make a contribution to meta-oe since meta-oe is actually just a front end for many layers? Jun 11 14:35:50 kinda confusing Jun 11 14:36:18 all the meta-oe oe-meta openembeded-meta meta-openembedded good god why all the renames? Jun 11 14:36:34 :) Jun 11 14:36:44 I have to read everything 5 times Jun 11 14:36:48 :P Jun 11 14:37:07 pompomJuice: ahhh, different script param then Jun 11 14:37:15 hehehe.. what's in a name?! Jun 11 14:37:37 yes Jun 11 14:38:02 is it that one or that one or the other one that is actually the first one inside the second one layer just add more layers this is to easy to understand Jun 11 14:38:52 http://layers.openembedded.org/ has a search function Jun 11 14:39:11 checking... Jun 11 14:39:22 bookmarked Jun 11 14:39:26 that helps... a mapping Jun 11 14:42:21 I dunno when the search function was added actually ... I discovered it quite recently Jun 11 14:57:33 hi, im trying to crossbuild a framework (with provided configure and makefiles) on my debian 32bits for arm (colibrit20), i was told to make an openembedded build, can you tell me how to proceed? Jun 11 14:58:51 rick_ => http://www.yoctoproject.org/docs/1.5/dev-manual/dev-manual.html#using-bbappend-files Jun 11 14:59:31 http://www.angstrom-distribution.org/ Jun 11 15:24:32 I made a change to meta-oe, but for some bizarre reason bitbake is stuck on old recipy MD5 checksums Jun 11 15:24:35 totally bizarre Jun 11 15:26:07 some caching has gone wrong again Jun 11 15:30:20 pompomJuice: that stuff is not read from the cache, so it's not a caching issue Jun 11 15:30:31 this is bizarre Jun 11 15:30:37 since it's not rocket science to check Jun 11 15:30:49 this is basics Jun 11 15:31:04 but let me check again Jun 11 15:31:27 the weird thing is Jun 11 15:31:34 the change was a version bump Jun 11 15:31:38 I'm not sure I understand the problem you are having ... could you explain it? Jun 11 15:32:11 version bump -> change filename with new PV and update checksums... right? Wrong... bitbake detects the new recipy PV but somehow holds on to the old recipe's checksums Jun 11 15:32:29 further more Jun 11 15:32:37 it works on my dev box Jun 11 15:32:53 when I injected the changes onto our prod build server it breaks Jun 11 15:33:07 saying I must add these two lines to the recipy... but the lines are the same! Jun 11 15:33:28 so I went onto the build agent Jun 11 15:33:32 and maually did a cleansstate Jun 11 15:33:34 no effect Jun 11 15:33:53 oh wait Jun 11 15:34:15 omg Jun 11 15:34:17 nm Jun 11 15:34:21 version control issue Jun 11 15:34:35 I had a bbappend with old checksums in Jun 11 15:37:24 * kergoth chuckles Jun 11 15:37:27 right Jun 11 15:37:52 my only advice is "try to work out if what you think happening is what is actually happening" Jun 11 16:20:16 is it possible to "disable" a recipe for a given machine ? Jun 11 16:21:00 that's what COMPATIBLE_MACHINE is for, but it's the other way around — make it buildable only fro the specified machines Jun 11 16:21:11 that's perfect Jun 11 16:21:22 thanks Jun 11 16:22:28 np Jun 11 16:25:30 maybe i could use a better technique, i defined SRC_URI with file://defconfig in every linux kernel recipe with a .inc. Then only some versions of those kernels are compatible with some machines. Is it ok ? Jun 11 16:27:24 COMPATIBLE_MACHINE is indeed the best wayt o handle the kernel and bootloader recipes for a bsp Jun 11 16:27:45 good Jun 11 16:32:36 strangely it's using linux-dummy now :( something went wrong Jun 11 16:33:28 note that COMPATIBLE_MACHINE is a regex Jun 11 16:33:34 lol ok Jun 11 16:33:38 i understand now Jun 11 16:34:04 that's strange Jun 11 18:21:13 Hmm, http://onethingwell.org/post/561436185/ranger looks interesting Jun 11 18:21:31 * kergoth wonders if bluelightning found what he needed in the oe history Jun 11 21:45:32 halstead: what would be involved with replacing google auth for the helios voting server? Jun 11 21:48:34 darknighte, It needs to be pointed an OATH provider. It doesn't have to be Google. I think the Linux Foundation runs one. It does mean running your own copy instead of using the hosted service. Jun 11 21:49:33 darknighte, The hosted service auths against yahoo, facebook, or google. A user only needs an account at one of them. Jun 11 21:49:39 not sure we will get all the members to go for oauth Jun 11 21:50:00 how secure would you say oauth is for us to use? Jun 11 21:51:40 darknighte, I don't see any security issues with it. It's probably safer than any method short of issuing certificates to the browser. Jun 11 21:52:16 hmmm, my lack of knowledge about how oauth works makes me leery, but I defer to your judgement there. Jun 11 21:52:52 So, other than some icky interface issues, it should work for us. Jun 11 21:53:40 darknighte, And if I remember correctly only the user creating the ballot needs to authenticate. The people voting are e-mailed login links with id/pass combos. Jun 11 21:56:55 hmmm, let me double check that then. Jun 11 21:57:19 halstead: ^ Jun 11 22:00:13 darknighte, Sure. Let me know if you need anything else. Jun 11 22:02:06 hmmm, you appear to be correct. so, realistically, we don't need to host it ourselves, unless we want to control the UI a bit more. Jun 11 22:02:11 halstead: ^ Jun 11 22:19:36 darknighte, Yeah. And then we will need someone to keep updates going and such. Jun 11 22:37:23 halstead: does the outbound email work for the helios server you setup? Jun 11 22:38:07 darknighte, I'm not sure at the moment. It certainly did when we were testing last. Jun 11 22:38:22 darknighte, Do you need me to check? Jun 11 23:37:07 halstead: no. thank you. I think I'm going to recommend that we go with the public solution. Jun 11 23:42:50 darknighte, I think that's best. **** ENDING LOGGING AT Thu Jun 12 02:59:59 2014