[10:30] <Shred00> is https://launchpad.net/~mythbuntu/+archive/0.25/+packages still tracking master?  will it be switched to track fixes/0.25?
[10:30] <Zinn> [launchpad.net] Packages in “0.25” : 0.25 : “Mythbuntu Developers” team
[10:31] <Shred00> looks like unfortunately, it's only a single commit behind 0,25 GA.  :-(
[11:14] <Seeker`> how long until there is a new repo tracking master again?
[11:35] <Shred00> Seeker`: i guess depending on the answer to my question, no time at all -- it's still happening.  :-)
[12:33] <tgm4883> Shred00, our 0.25 repo hasn't been tracking master for quite some time, upstream has a 0.25 branch
[12:33] <Shred00> oh, i didn't realize upstream branched already
[12:34] <tgm4883> yea they branched awhile ago
[12:34] <tgm4883> they have to as some features don't make it into 0.25
[12:35] <Shred00> although looking at the tip of both master and fixes/0.25, but for the two "Force a commit" commits on master, they appear the same.
[12:36] <tgm4883> I don't know much about git, but I do know that the two are different as web setup didn't make it into 0.25
[12:37]  * Shred00 pulls from git to see what's going on
[12:43] <Shred00> yeah, 0.25 is only those two (noop_ commits i mentioned behind master
[12:44] <Shred00> i'm not sure why they'd branch so early if they intended to keep the branch in sync with master.  or maybe that wasn't necessarily the intention but just how it worked out.
[12:44]  * tgm4883 shrugs
[12:45] <tgm4883> Web setup didn't make it in 0.25, it was there and was pulled. So if it isn't in master I'm unsure where that code lives right now
[12:46] <Shred00> well, if there was a separate fixes/0.25 and master branches it didn't make sense to pull it from master
[12:47] <tgm4883> Shred00, exactly
[12:47] <tgm4883> Seeker`, to answer your earlier question, https://launchpad.net/~mythbuntu/+archive/0.26
[12:47] <Zinn> [launchpad.net] 0.26 : “Mythbuntu Developers” team
[12:47] <tgm4883> There aren't any builds there yet though
[12:48] <Shred00> tgm4883: well, not so much "exactly".  if it was in master and it's not in 0.25 then it was pulled from master too.
[12:48] <tgm4883> sorry, I meant that was my thought process as well
[12:50] <Seeker`> tgm4883: yeah, found that. Will it be populated with packages overnight?
[12:50] <Seeker`> Or is it a more manual process?
[12:51] <tgm4883> Seeker`, we have to change the build scripts over to 0.26. It's a fairly simple process but we have to work out why the last build of 0.25 failed
[12:52] <Seeker`> fair enough. I've just updated to pangolin, so I have the commit I wanted now (the liveTV one)
[13:57] <Shred00> packages on fixes/0.25 are rebuilt every 24 hours is it?
[14:03] <Seeker`> If it is the same as the old 0.25 repo, yes
[14:03] <Seeker`> anyone else suffering the video buffering failed too many times issue with livetv?
[19:30] <Shadow__X> is it recommended to upgrade to .25 yet?
[19:36] <Seeker`> it is the current stable release
[20:12] <rhpot1991> Shadow__X: Seeker` I think we are still waiting for the latest build which would match the stable release
[20:12] <rhpot1991> superm1: confirm ^ ?
[20:12] <tgm4883> yes
[20:12] <tgm4883> http://smithers.mythbuntu.org/~autobuild/weekly_mythtv.txt
[20:12] <Zinn> [smithers.mythbuntu.org] N/A
[20:12] <rhpot1991> tgm4883: thanks
[21:02] <Shadow__X> rhpot1991: ah ok thanks. I checked windows and mac builds and they are not there yet either so it makes sense just to wait regardless thanks