[mythtv-users] possible bug in 0.28 mythtranscode

[John Pilkington]

On 06/08/16 11:38, Jim Abernathy wrote:
>
>
>> From: perkins1724 at hotmail.com
>> To: mythtv-users at mythtv.org
>> Date: Sat, 6 Aug 2016 04:08:44 +0000
>> Subject: Re: [mythtv-users] possible bug in 0.28 mythtranscode
>>
>> On 6 August 2016 11:50:40 AM ACST, Mark Perkins
> <perkins1724 at hotmail.com> wrote:
>> >
>> >>So it’s definitely different behavior than what 0.28 does. I’m going
>> >>to enable the repositories for 0.27 and update then retest.
>> >>
>> >>Jim A
>> >>
>> >>> _______________________________________________
>> >
>> >
>> >Very interesting. And looking at the changeset referenced it was NOT
>> >pushed to 0.27, only 0.28 and above. I will go away and recheck.
>> >_______________________________________________
>> >mythtv-users mailing list
>> >mythtv-users at mythtv.org
>> >http://lists.mythtv.org/mailman/listinfo/mythtv-users
>> >http://wiki.mythtv.org/Mailing_List_etiquette
>> >MythTV Forums: https://forum.mythtv.org
>>
>> Ok just checked and mythtranscode is NOT deleting the original file in
> fixes/0.27 using fifo mode.
>>
>> Sorry for the bad info.
>> _
>
> I enabled the 0.27 repositories and did an update.  crashed everything
> on reboot.  I don't think I shutdown the backend before I did the
> update, so I'll redo today making sure the backend is stopped.
>
> What is the correct way to do this??
>
> Jim A
>

It may be the problem of mismatched database protocol; I don't think 
downgrading is supported.  Can you revert to a backup from 0.27?  But it 
won't include your recent recordings.

John P