[mythtv-users] Downgrading from 0.28 to 0.27

[Justin Alcorn]

On Wed, Oct 22, 2014 at 4:33 PM, Mark Perkins <perkins1724 at hotmail.com> wrote:
>
>
>> On 23 Oct 2014, at 3:08 am, "Justin Alcorn" <justin at jalcorn.net> wrote:
>>
>> I built my mythtv system on ubuntu and used the PPA to install.  Seeing 0.28, I of course chose the latest version  - not realizing I was using a pre-release version.  It's worked well, but I'm running into problems with mythcommflag and the H.264 files I need. Also, I later on decided to create a dedicated front end in my exercise room - only to discover that I couldn't use Mythbuntu.
>
> Should be able to use 0.28 on Mythbuntu, IIRC you just load Mythbuntu-control-center and select, read the warning, type in the override and good to go.
>

Mythbuntu Frontend said database schema was too high, it refused to
connect.  I'll see if I can power through it this weekend.

>>
>> There's also the "Hey, 0.28 is working (mostly), so just leave well enough alone.
>
> Hey, 0.28 is working! (Not just mostly working). Plus in a few months (give or take a few years) it will be general release and master will be 0.29.
>
> If you have time / effort best bet is to probably post some info of the problems you are having in 0.28 and get them fixed - the same problems probably exist in 0.27 anyway, I very much doubt there is intentional breakage in 0.28 of something that worked in 0.27.

Well, I posted about mythcommflag not updating the recordedseek table.
Nobody seems to know what's going on there, but it's apparently
related to a similar problem that has been fixed in 0.27.  What's
weird is that mythcommflag was working FINE, then I did a general
apt-get upgrade, and suddenly - as soon as I try to flag comemrcials
or rebuild a seek table - POOF - no seektable for that recording
anymore.   THe trace showed the SQL to delete the database entries,
and then it doesn't try to put them back in.



--
Justin B. Alcorn
PGP Fingerprint A36D D691 C5B0 BE15 5A2A AF49 AA1C 372C