**** BEGIN LOGGING AT Wed Jan 18 03:00:01 2017
Jan 18 09:05:27 <Jin^eLD> morning
Jan 18 09:07:11 <mckoan> Jin^eLD: gm
Jan 18 11:53:47 <Crofton|work> fray, where did you upload the getting started tool?
Jan 18 14:02:27 <tasslehoff> Is there a way I can install all the dependencies that e.g. qtbase would install in an image, but remove the qt-packages?
Jan 18 14:04:46 <rburton> not trivially
Jan 18 14:06:07 <tasslehoff> rburton: ok. we're stuck on an old version, so we built a new qt we inject in /opt ourselves. would like to remove the old one, but keep icu and the other stuff needed.
Jan 18 14:16:09 <Crofton|work> https://www.patreon.com/tanuk
Jan 18 15:08:20 <tasslehoff> rburton: solved by comparing the manifest and adding the packages that disappeared :)
Jan 18 15:08:59 <rburton> tasslehoff: why not upgrade the qt in your layers?
Jan 18 15:16:49 <tasslehoff> rburton: because we are stuck at dylan with linux 2.6.39 & systemd 204. I've made some attempts at newer versions without success.
Jan 18 15:17:20 <tasslehoff> the hardware has an omap3530
Jan 18 18:48:54 <Crofton|work> fray, I'm about to try wr setup tool
Jan 18 18:49:04 <Crofton|work> prepare for stream of conciousness bitching!
Jan 18 18:49:31 <Crofton|work> also, I proose the name "Torte"
Jan 18 20:53:06 <Crofton|work> Marex, any intention of updating u-boot recipe to 2017.01
Jan 18 20:53:15 <Crofton|work> for oe-core?
Jan 18 21:04:14 <Marex> Crofton|work: yeah, it's in the todo, but expect UART breakage on OMAP
Jan 18 21:06:58 <Marex> Crofton|work: kinda tempted to wait for 2016.03 ... do you need 01 for some reason ?
Jan 18 21:07:16 <Marex> *2017.03
Jan 18 21:11:44 * Crofton|work balmes fischerm 
Jan 18 21:11:54 <Crofton|work> also, you have to thinnk about release timing for YP
Jan 18 21:13:44 <bluelightning> the question there is will it make end of M3
Jan 18 21:13:46 <Marex> Crofton|work: fischerm is a great boxing bag, yeah
Jan 18 21:14:02 <Marex> Crofton|work: what's the deadline ?
Jan 18 21:14:05 <Crofton|work> bluelightning, this is why I am prodding Marex
Jan 18 21:14:22 <bluelightning> I'll look it up, one sec
Jan 18 21:14:29 <bluelightning> (I really should know...)
Jan 18 21:14:40 <Crofton|work> unsure, I tried reading YP status, but they don't say simple things like finsih this now :)
Jan 18 21:14:49 <Marex> Crofton|work: +1
Jan 18 21:15:04 <Marex> Crofton|work: YP roadmap is like spaceflight planing ;-/
Jan 18 21:15:10 <Crofton|work> lol
Jan 18 21:15:20 <bluelightning> 27 Feb is M3 freeze
Jan 18 21:15:26 <bluelightning> https://wiki.yoctoproject.org/wiki/Yocto_2.3_Schedule
Jan 18 21:15:41 <Crofton|work> so any upgrades need to be done by M3?
Jan 18 21:15:43 <Marex> 2017.03 is planned for 20170313
Jan 18 21:15:51 <bluelightning> as usual, deadlines are not as far away as one might hope
Jan 18 21:15:52 <Marex> damn
Jan 18 21:16:11 <Crofton|work> 2017.01 can include patch for ompa bustage
Jan 18 21:16:21 <Crofton|work> recipe that is
Jan 18 21:16:23 <Marex> Crofton|work: well I don't want to lug a patch around for a release :/
Jan 18 21:16:24 <bluelightning> Crofton|work: typically yes, we have made exceptions on a case-by-case basis
Jan 18 21:16:37 <bluelightning> Crofton|work: depends what the impact is either way
Jan 18 21:16:39 <Crofton|work> bluelightning, lets beat Marex until he cries
Jan 18 21:16:53 <bluelightning> Crofton|work: you are violent today :p
Jan 18 21:16:57 * Crofton|work smiles
Jan 18 21:17:01 <Marex> Crofton|work: I'll ask mranostay to help me defend ...
Jan 18 21:17:06 <Crofton|work> lol
Jan 18 21:17:22 <Crofton|work> anyway, I believe we hav eeducated him about the challenges
Jan 18 21:17:40 <Marex> well, can we make an exception for the 2017.03 so we don't have to lug around a special patch ?
Jan 18 21:17:47 <Marex> I'd much prefer that
Jan 18 21:18:01 <Crofton|work> get denix to help lobby
Jan 18 21:18:09 <Crofton|work> and make damn sure it works
Jan 18 21:18:24 <bluelightning> start a thread on the ML, cc denix, rburton & RP
Jan 18 21:18:31 <Crofton|work> but really doing 2017.01 + patch as backup isn;t a bad plan
Jan 18 21:19:09 <Crofton|work> gets more testing in interim
Jan 18 21:19:20 <Crofton|work> and ou have a backup if .03 goes south
Jan 18 21:19:37 <Marex> Crofton|work: or a patch can be added to meta-ti ;-)
Jan 18 21:19:49 <Crofton|work> I'll let you and deni argue
Jan 18 21:20:03 <fischerm> Marex: at any point in time something will be broken in u-boot
Jan 18 21:20:07 <Crofton|work> but there is a beagle thing in meta-yocto-bsop, so they woul dneed it there
Jan 18 21:20:15 <Marex> fischerm: please stop contributing ...
Jan 18 21:20:19 <fischerm> Marex: :)
Jan 18 21:20:26 <Marex> hehe
Jan 18 21:20:31 <Crofton|work> the point is, Who would break OMAP in a u-boot release?
Jan 18 21:20:48 * fischerm for once didn't break it
Jan 18 21:20:53 <Marex> Crofton|work: ah darn, omap in yp bsp sucks
Jan 18 21:21:10 <fischerm> any software at any point is broken
Jan 18 21:21:47 <Marex> Crofton|work: welllllll, about that ...
Jan 18 21:21:48 <Crofton|work> every thing is broken, lets all give up and have a beer
Jan 18 21:22:19 <Marex> Crofton|work: I guess things should be good in 2017.03 , so yeah ...
Jan 18 21:22:43 <Marex> Crofton|work: besides, the UART breakage is kinda subtle and only happens if you use very long lines or type very fast iirc
Jan 18 21:22:52 <bluelightning> I guess the thing with u-boot is the consequences of it being broken can be a bit more serious depending on the device
Jan 18 21:23:22 <Marex> bluelightning: which is why so many people update u-boot so often
Jan 18 21:23:26 <Crofton|work> we need more people using u-boot from oe-core and fewer using evil vendor u-boots in bsp
Jan 18 21:23:40 <Marex> Crofton|work: +10000000
Jan 18 21:23:57 <denix> I'd rather prefer a know issue now (.01) than a whole bunch of unknown later (.03)
Jan 18 21:24:01 <Marex> Crofton|work: and if they need EVU , it should be at least somehow based on the one in core
Jan 18 21:24:08 <Marex> denix: +1
Jan 18 21:24:09 <Crofton|work> so keeping it current in oe-core is good, and understanding when freezes occur in oe is also good
Jan 18 21:24:18 <denix> s/know/known/
Jan 18 21:24:52 <Marex> I'll try to set up the build test tonight (for 2017.01 update)
Jan 18 21:24:56 <Crofton|work> pick a version, add recipe, fix issues that come from tesing with backports of fixes
Jan 18 21:24:59 <Crofton|work> repeat
Jan 18 21:25:04 <Crofton|work> each release
Jan 18 21:25:10 <Crofton|work> patches go to zero in time
Jan 18 21:25:31 <Crofton|work> Marex, thanks
Jan 18 21:25:38 <Crofton|work> fischerm, while buy you some anime
Jan 18 21:25:48 <Crofton|work> fischerm, will buy you some anime
Jan 18 21:29:08 <RP> Marex: if everyone asked for their special upgrade to have an exception, we'd never manage a release :(
Jan 18 21:29:39 <RP> Marex: you have no idea how hard it is to stablise and these "I promise my upgrade won't break things" usually doesn't turn out to be true
Jan 18 21:33:20 * Crofton|work cracks the whip
Jan 18 21:37:18 <RP> Crofton|work: I'm having a very bad day so I'd be careful ;-)
Jan 18 21:37:53 <Crofton|work> I mean on Marex
Jan 18 21:38:08 <Crofton|work> House hasn't washed away?
Jan 18 21:42:52 <Marex> RP: you certainly do come across as having a bad day ;-/
Jan 18 21:43:27 <fischerm> RP: Marex can hug you if you want
Jan 18 21:43:32 * fischerm cracks the whip
Jan 18 21:43:51 <Marex> fischerm: don't rip your brown paper bag, junior :)
Jan 18 21:44:01 * Marex puts fischerm in place ...
Jan 18 21:44:20 <fischerm> Marex: grow a beard before calling me junior
Jan 18 21:44:50 <Marex> fischerm: ok, that one cracked me up :D
Jan 18 21:45:38 <RP> Crofton|work: no, house is still standing thankfully :)
Jan 18 21:45:56 * RP was admiring some new cracks in bit of it earlier but that is to be expected
Jan 18 21:46:08 <Crofton|work> hmm
Jan 18 21:46:25 <Crofton|work> ignore the young guys, needed to get them sorted out over u-boot
**** ENDING LOGGING AT Thu Jan 19 03:00:01 2017