**** BEGIN LOGGING AT Fri May 30 03:00:00 2014
May 30 03:54:19 <Kashyap1> hello
May 30 07:11:05 <mckoan> good morning
May 30 12:21:35 <Crofton|work> zeddii, this new line at the end of cfg frags is annoying
May 30 13:03:49 <zeddii> Crofton|work, I aim to squash annoyances. have details to shoot my way ?
May 30 13:04:15 <Crofton|work> you are familiar with the issue ?
May 30 13:04:44 <Crofton|work> if there is no new line at the end of a cfg file, the first option set in the next one disappears
May 30 13:04:46 <Crofton|work> silently
May 30 13:05:16 <zeddii> hah. wow. I've never seen that. I can fix it. want to lob a bugzilla my way ?
May 30 13:05:38 <Crofton|work> we've been falling over it in meta-xilinx
May 30 13:06:42 <zeddii> nasty. I can do something right away, not good at all.
May 30 13:07:46 <Crofton|work> https://github.com/Xilinx/meta-xilinx/commit/17d55a1acd9391a3c4f4abf2803289ef801445bd
May 30 13:12:56 <Crofton|work> I can't be entirely certain it isn't something caused by meta-xilinx
May 30 13:14:22 <Crofton|work> zeddii, https://lists.yoctoproject.org/pipermail/meta-xilinx/2014-May/000654.html
May 30 13:14:43 <Crofton|work> I can make an entry in bugzilla referencing that email
May 30 13:24:32 <droy> bluelightning hello
May 30 13:27:53 * zeddii reappears
May 30 13:28:18 <Crofton|work> open the curtains, reveal zeddii
May 30 13:28:55 <zeddii> Crofton|work,  the email is enough for me. I'll start a build.
May 30 13:29:09 <Crofton|work> k
May 30 13:29:30 * zeddii isn't religious about "paper work" ;)
May 30 13:29:32 <bluelightning> hi droy
May 30 13:29:47 <Crofton|work> I wasn't sure if you got bonuses for fixing bugs in bugzilla
May 30 13:30:57 <zecke> hehe
May 30 13:32:36 <RP> kergoth: around?
May 30 13:33:04 <zeddii> ;)
May 30 13:33:08 <RP> Crofton|work: I wish we did
May 30 13:33:19 <Crofton|work> :)
May 30 13:34:16 <RP> Crofton|work: just looking at your MACHINE unset bug as it happens...
May 30 13:34:29 <Crofton|work> duping it OK?
May 30 13:34:55 <Crofton|work> sorry about complaining about this sort of thing :)
May 30 13:35:21 <RP> Crofton|work: yes, its lovely and reproducible and needs fixes in about three places
May 30 13:35:27 <Crofton|work> awesome
May 30 13:35:30 <RP> Crofton|work: don't be sorry, that error sucks
May 30 13:35:33 <Crofton|work> I like bugs like that
May 30 13:35:37 <Crofton|work> yep
May 30 13:35:53 <Crofton|work> easy to dupe and clealy must be fixed
May 30 13:37:07 <droy> which all boards by texas instruments are supported by yocto project?
May 30 13:38:06 <Crofton|work> Be sure to read all the way
May 30 13:38:08 <Crofton|work> http://blogs.cisco.com/sp/why-were-joining-the-linaro-digital-home-group
May 30 13:41:59 <RP> kergoth: I've sent mail to bitbake-devel
May 30 13:43:53 <bluelightning> droy: within the core, only beaglebone; but TI / beagleboard.org provide layers to add additional board support
May 30 13:46:16 <droy> ok
May 30 13:53:36 <RP> Crofton|work: nice :)
May 30 13:55:36 <Crofton|work> (The “Yocto Project” is the open source development environment for Linaro, and, by proxy, LHG.)
May 30 14:00:19 <rburton> Crofton|work: ooo
May 30 14:58:39 <RP> Crofton|work: if you're subbed to the bitbake list you'll see the more I poke at this, the more patches I end up writing :/
May 30 14:58:53 <Crofton|work> bummer
May 30 14:59:02 <Crofton|work> I'm not, but I might take a peek
May 30 14:59:47 <RP> Crofton|work: we can paper over it with one change to OE-Core but it does change the fact our exception handling in bitbake sucks :/
May 30 14:59:55 <Crofton|work> yeah
May 30 15:00:04 <Crofton|work> I was wondering why it would be so hard
May 30 15:00:12 <Crofton|work> just check for MACHINE early and bail
May 30 15:00:34 <RP> Crofton|work: the sanity checker does do that in an event handler
May 30 15:00:48 <RP> Crofton|work: but what is "bail"?
May 30 15:00:52 <RP> SystemExit?
May 30 15:00:55 <Crofton|work> yes
May 30 15:00:57 <Crofton|work> bail out
May 30 15:01:12 <Crofton|work> jump from the crashing plane in a controlled fashion
May 30 15:01:42 <RP> Crofton|work: we're having trouble with the control problem, particularly when you think of bitbake as a server which shouldn't in fact exit
May 30 15:02:04 <Crofton|work> should systemd implement bitbake then?
May 30 15:02:33 <JaMa> :)
May 30 15:02:40 <RP> Crofton|work: I knew there was a solution I was overlooking...
May 30 15:03:08 <RP> Personally, it should be a kernel module, avoid context switching
May 30 15:03:24 <RP> we've need to add python to the kernel but that is a technical detail...
May 30 15:04:17 <Crofton|work> prepare a patch adding python to the kernel for next April
May 30 15:07:43 <ant_work> Crofton|work: and FaceBook too
May 30 15:19:30 <zecke> RP: I love the "reduce" context switch arguments. :)
May 30 15:19:47 <zecke> RP: which exception handling do you talk about? the one to catch errors in bbclass?
May 30 15:20:13 <zecke> RP: s,bbclass,any python method/snippet executed by bitbake,?
May 30 15:21:07 <scottrif> halstead: ping
May 30 15:22:28 <RP> zecke: its the event handlers in bitbake that are causing problems
May 30 15:22:52 <RP> zecke: we also have some broken code catching exceptions by name rather than class :/
May 30 17:07:30 <jtoomey> hi folks, anyone alive?
May 30 17:08:39 <bluelightning> jtoomey: hey
May 30 17:09:14 <jtoomey> bluelightning: hey - how are you?
May 30 17:09:21 <bluelightning> great thanks, and you?
May 30 17:10:10 <jtoomey> i would be better if i wasnt here - its a bank holiday and im stuck trying to get an rc out the door :S
May 30 17:10:31 <bluelightning> doh
May 30 17:10:35 <bluelightning> anything I can help with?
May 30 17:10:46 <jtoomey> i hope so!!
May 30 17:11:20 <jtoomey> the yocto build is failing because it depends on a file which doesnt seem to be there any more. http://sources.openembedded.org/git2_git.videolan.org.x264.git.tar.gz
May 30 17:11:50 <bluelightning> jtoomey: ah yes... upstream removed the revision we were fetching :/
May 30 17:11:57 <jtoomey> apparently we are still using Dylan so i guess the default response is PFO
May 30 17:12:11 <bluelightning> well, I think we'd still fix this
May 30 17:12:20 <bluelightning> I have a patch for newer branches, let me do a quick backport
May 30 17:12:54 <jtoomey>  cool!
May 30 17:22:28 <bluelightning> jtoomey: so actually I realised this recipe wasn't in the core in dylan, and we were building a different revision there than master
May 30 17:23:00 <bluelightning> however, I'm fairly sure you should be able to change SRCREV to bfed708c5358a2b4ef65923fb0683cefa9184e6f  which is apparently the new equivalent for the old revision upstream
May 30 17:23:12 <bluelightning> why they changed it I don't know...
May 30 17:24:47 <bluelightning> jtoomey_: did you get my last message re the new revision?
May 30 17:25:09 <bluelightning> hmm
May 30 17:25:34 <bluelightning> jtoomey: did you get my last message about the new revision?
May 30 17:25:55 <jtoomey> no - sorry, i got disconnected :(
May 30 17:26:40 <bluelightning> jtoomey: ok, so the story is the x264 recipe wasn't in the core in dylan and the patch I had doesn't apply
May 30 17:26:45 <bluelightning> jtoomey: however I'm fairly sure you should be able to change SRCREV to bfed708c5358a2b4ef65923fb0683cefa9184e6f  which is apparently the new equivalent for the old revision upstream
May 30 17:27:16 <jtoomey> so - do i need to do a bbappend?
May 30 17:28:43 <bluelightning> how is this recipe getting into your build though?
May 30 17:29:04 <bluelightning> I'd expect you would be carrying it separately since it's not in the core
May 30 17:31:30 <jtoomey> i dont know tbh - i assumed that it was being pulled in as a dep of something else
May 30 17:32:18 <bluelightning> jtoomey: I'm not referring to why it's being built, I mean where is the file from?
May 30 17:32:31 <bluelightning> jtoomey: are you depending on meta-oe to get it, or shipping it as part of your layers?
May 30 17:33:10 <jtoomey> bluelightning: these are very complicated questions for 6:30 on a friday evening
May 30 17:33:25 <bluelightning> you can find out where the file is quickly by running: bitbake -e x264 | grep ^FILE=
May 30 17:34:11 <jtoomey> ah - im told that we take a few packages from meta-oe
May 30 17:34:43 <bluelightning> right, I figured you might be
May 30 17:34:59 <bluelightning> in which case, just edit that file directly and change SRCREV I would suggest
May 30 17:35:03 <jtoomey> things have changed a lot since i was working on this last...
May 30 17:35:29 <bluelightning> (assuming the old value was 1cffe9f406cc54f4759fc9eeb85598fb8cae66c7)
May 30 17:37:29 <jtoomey> ok - so, the srcrev can be changed using a bbappend right?
May 30 17:38:09 <jtoomey> rather than taking a copy of the original recipe?
May 30 17:38:27 <bluelightning> jtoomey: yes, it can
May 30 17:39:25 <jtoomey> ok - maybe thats the way to go. assuming the file is _gone_ gone, i can try to use the newer version when i get back on tuesday
May 30 17:39:52 <bluelightning> jtoomey: sorry I'm not following - the "file" is gone?
May 30 17:40:01 <jtoomey> oh
May 30 17:40:14 <jtoomey> the recipe points to an actual file - a tarball
May 30 17:40:20 <jtoomey> http://sources.openembedded.org/git2_git.videolan.org.x264.git.tar.gz
May 30 17:40:35 <jtoomey> or at least that the impression i get from the log file
May 30 17:40:45 <jtoomey> it doesnt look like its going to try any mirrors
May 30 17:41:06 <bluelightning> that's just it trying to fetch a mirror tarball I would think
May 30 17:41:24 <jtoomey> oh
May 30 17:41:26 <bluelightning> what happened is upstream reinitialised their git repository
May 30 17:41:33 <jtoomey> let me see what the log says
May 30 17:42:16 <bluelightning> FWIW, here's a map that someone created from old revision to new: http://sprunge.us/dGOU
May 30 17:42:57 <jtoomey> oh - it looks like you are right, it does try a bunch of different mirrors
May 30 17:43:24 <bluelightning> it will by default yes
May 30 17:43:46 <jtoomey> is this worth fixing upstream or is Dylan out of support?
May 30 17:44:20 <bluelightning> I've just found there is a patch for meta-oe that will fix it, but it hasn't really been submitted properly
May 30 17:44:24 <bluelightning> it will be fixed there though
May 30 17:44:48 <bluelightning> (the patch just changes SRCREV as we've discussed)
May 30 17:45:35 <jtoomey> ok cool, well ill try the bbappend fix on tuesday.
May 30 17:45:52 <bluelightning> ok
May 30 17:46:06 <jtoomey> thanks for your help!! much appreciated :D
May 30 17:46:15 <bluelightning> no worries :)
May 30 17:49:31 <jtoomey> ok, time to get out of here i think. have a good weekend and thanks again!
May 30 17:49:47 <bluelightning> jtoomey: and you :)
May 30 20:24:44 <eliza411> pidge, looks like we will be able to do what you asked ... script the release data into json or csv, then import it, bypassing the web ui.
May 30 20:26:26 <pidge> eliza411: W00t!
May 30 20:26:31 <pidge> <3 eliza411
May 30 20:26:45 <pidge> json would be best imho
May 30 20:27:00 <pidge> eliza411: I can do that really easy from the AB
May 30 20:27:48 <eliza411> pidge, sweet. if there's a day next week that I could work at intel and interrupt you off and on, we could probably hammer it out in a single afternoon.
May 30 20:28:24 <eliza411> pidge, including a bunch of the visual presentation
May 30 20:28:43 <pidge> eliza411: it'll have to be next week, I'm off to philly the week after
May 30 20:29:11 <eliza411> pidge, how's tuesday?
May 30 20:29:36 <pidge> eliza411: that works
May 30 20:30:40 <eliza411> pidge, is there a best time of day for you?
May 30 20:31:14 <pidge> eliza411: not o dark 30? ;)
May 30 20:31:25 <pidge> afternoon generally is best
May 30 20:32:04 <eliza411> pidge, I'll put 1pm on the calendar.
May 30 20:32:14 <pidge> eliza411: excellent
**** ENDING LOGGING AT Sat May 31 03:00:00 2014