[mythtv-users] Upgrading to .23 on Gentoo database question

[sonofzev at iinet.net.au]

On Tue Oct 26 10:58 , Phil Bridges  sent:

>On Mon, Oct 25, 2010 at 7:39 PM, Dale Pontius DEPontius at edgehp.net> wrote:
>> On 10/20/10 10:30, Phil Bridges wrote:
>>> On Wed, Oct 20, 2010 at 10:28 AM, Tom Dexter digitalaudiorock at gmail.com> wrote:
>>>> On Wed, Oct 20, 2010 at 10:00 AM, Phil Bridges gravityhammer at gmail.com> wrote:
>>>>> I'm finally upgrading my Gentoo mythbackend from .22 to .23.  IIRC, I
>>>>> had to do some funky database maneuvering to set the correct character
>>>>> encoding.  Is there anything I'll need to look out for before I start
>>>>> up the .23 backend?  I made a backup of my myth database before I
>>>>> upgraded the myth files.
>>>>
>>>> Since the database encoding stuff was straightened out in 0.22 the
>>>> upgrades should be straight forward.  I upgraded from 0.22 directly ro
>>>> 0.23.1 on my Gentoo myth boxes with no problem.
>>>>
>>>
>>> Great!  Thanks for the response.
>>
>> Are you upgrading to 0.23 or 0.23.1?  I noticed the other day that the
>> really-old 0.23 ebuilds had been supplemented by new 0.23.1 ones.
>>
>
>Yep - it's .23.1.  Hopefully it won't take us too long to get .24!


Same experience here ...although I went from 0.21 to 0.22 without the database
hassle.... not sure whose instructions I followed or whether it was a fluke but
when I checked the encoding everything was fine... 

Have since done the 0.22 to 0.23 to 0.23.1 .. actually I simply keep going up
with the ebuilds.. and keep everything in sync.. my MBE updates portage from the
web.. but me 2 FE's update portage from my MBE .... keeps version consistency and
means I only run emerge --sync against the web once for all my boxes ..  (myth or
otherwise).. I also have the distfiles directory distibuted via nfs to save on
bandwidth as well..