[00:29] <bregol> Just upgraded from 12.04 to 14.04.1 and had a question about the repos added by Mythbuntu Control Centre. The MythTV Updates one is straightforward, but the other 2 aren't found for Trusty when I apt-get update.  Are these other 2 repos (Mythbuntu Updates and XMLTV) needed for a "normal" user? What do those repos give that aren't in the main Ubuntu repos?
[00:33] <Kwisher> bregol: i had the same issues, just unselect the XMLTV one
[00:40] <bregol> I did unselect both xmltv and mythbuntu updates.  Just wondering if either of those are used for anything. Looking at http://ppa.launchpad.net/mythbuntu/xmltv/ubuntu/dists/ there is nothing after Precise.  It also looks like a year since anything happened in http://ppa.launchpad.net/mythbuntu/testing/ubuntu/dists/
[11:48] <enyc> superm1: (a) We would like to understand, about  whats' really going on with  'libav' vs 'ffmpeg'  and this being 'external' or  internally provided by mythtv source tree etc...
[11:56] <superm1> enyc: hop in #mythtv
[11:56] <superm1> jya: and a few others should be able to discuss more
[11:56] <superm1> But jist right now is there are patches on top of ffmpeg not upstream
[11:57] <superm1> And features not in libav
[11:57] <jya> enyc: I have already answered most of those questions in the debian-devel list a couple of days ago
[12:00] <jya> mythtv uses its own fork for ffmpeg, currently based on ffmpeg. we use our own mpeg-ts demuxer, various additions in particular related to subtitle support, mheg, stream change detection etc
[12:54] <enyc> jya: aaah yes the latter parts helps // makes sense =)
[12:56] <jya> we have tried along the years to get our changes committed upstream… too much effort, and often dealing with people who saw no interest in what we wanted made a frustrating experience
[12:56] <jya> every single person of mythtv who have attempted to get our changes committed upstreams gave up
[12:57] <jya> and there’s been a few in close to 15 years
[12:57]  * jya off to bed
[12:58] <enyc> jya: i see dont woryr =)
[13:53] <enyc> superm1: as far as I can tell,  trusty AND precuse  mythtv source packge (and so, built packages) is vulnerable to security issue:  http://git.videolan.org/?p=ffmpeg.git;a=commitdiff;h=9ade5b804ea1ff98971972769c43497a597b0e77
[13:54] <enyc> superm1: its a simple patch, resulted in new ffmpeg point releases.  In the case of mythtv 0.27.x newer, I wonder if this should be done by merging ffmpeg 1.2.7 over 1.2.6 in there last I checked...
[13:55] <enyc> superm1: should I be filing ubuntu bug or something against our packages?
[14:37] <enyc> superm1: i note, thecre are a few related / extra fixes in:  http://git.videolan.org/?p=ffmpeg.git;a=shortlog;h=n1.2.7
[15:55] <superm1> enyc: best thing to do is file a bug upstream with mythtv guys
[15:55] <superm1> enyc: they'll include it in the next point release they cut
[15:55] <superm1> and it will get pulled into our -fixes branch builds immediately then
[16:19] <Bregol> !help
[16:19] <Zinn> !help For a  complete list of my knowledge visit: http://www.baablogic.net/Zinn.cgi  Other available commands: !status, !about, !bug [bug_number].
[16:22] <enyc> superm1: aha.  apparently, it is in fixes already, https://github.com/MythTV/mythtv/commit/f4195b2eb88296523351813c29933e81e6bd851f
[16:22] <superm1> enyc: ah nice
[16:23] <enyc> superm1: but  when I apt-get source etc agaist 'trusty' deb-src's... the un-fixed code is still there.  I'm guessing we simply need to re-pull fixes again now?
[16:23] <superm1> enyc: well we filed an SRU to get a newer mythtv point release in
[16:23] <superm1> but it's gone nowhere
[16:23] <superm1> we have the fixes in our fixes PPA though that means
[16:24] <superm1> https://launchpad.net/~mythbuntu/+archive/0.27
[16:24] <enyc> superm1: sure, a 0.27.3  PPA -or- SRU  would be good but thats' in some means separate...?  we still should get precise-lts-0.25  and trusty-lts-0.27  security-fixed ?
[16:24] <superm1> we try to point people at the PPA for now since SRU's don't seem to be happening
[16:25] <tgm4883> the PPA is the recommended way
[16:25] <superm1> https://bugs.launchpad.net/bugs/1323391
[16:25] <superm1> is the bug we were trying to get going, you can see the lack of activity from people who did need to ack it
[16:30] <tgm4883> we need to do a new request
[16:30] <tgm4883> and I'm not 100% sure it's going to be an SRU
[16:30] <tgm4883> (but neither does the release team :/ )
[16:32] <enyc> tgm4883: does it 'help' that we now have missing security-problem etc.?
[16:32] <tgm4883> probably
[16:45] <enyc> tgm4883: okay I'll leave you on that case =)
[16:46] <enyc> I'm getting bits and pieces and trying builds with   ARM (armel, armhf, rpi(raspbian)) with  opengl enabled etc..  I need to check when get to the other desk but I got the impression it can now build without needing to 'disable' opengl