Mailing List Archive: MythTV: Users

Mixing SVN Frontend (0.21) with 0.20.2 Backend

Index | Next | Previous | View Threaded

jongitech at gmail

Dec 24, 2007, 5:20 AM

Post #1 of 7 (1103 views)
Permalink

Mixing SVN Frontend (0.21) with 0.20.2 Backend

Hi,

On my master system (back and frontend) I am running MythTV 0.20.2 on a Fedora 8 box. All is working fine. I decided to install the SVN on another computer which I want to use as a remote front end. So I compiled SVN and all seemed to go well.

When I start mythfrontend on the remote system the following comes up:

Warning: MythTV wants to upgrade your database schema, from 1160 to 1202.
[Exit / Upgrade]

So I chose exit. I then went to the master system and did a reboot to see whether I would get this same message there. It didn't appear. Thing is the frontend on the remote system will not progress if I choose exit. Is there anyway around this using SVN or should I just compile 0.20.2 on the remote system as well?

Jongi

timlitw at gmail

Dec 24, 2007, 7:35 AM

Post #2 of 7 (1035 views)
Permalink

Re: Mixing SVN Frontend (0.21) with 0.20.2 Backend [In reply to]

Your versions have to match. Either use all .20.2 or use all SVN

On Dec 24, 2007 7:20 AM, jongi <jongitech[at]gmail.com> wrote:

> Hi,
>
> On my master system (back and frontend) I am running MythTV 0.20.2 on a
> Fedora 8 box. All is working fine. I decided to install the SVN on another
> computer which I want to use as a remote front end. So I compiled SVN and
> all seemed to go well.
>
> When I start mythfrontend on the remote system the following comes up:
>
> Warning: MythTV wants to upgrade your database schema, from 1160 to 1202.
> [Exit / Upgrade]
>
> So I chose exit. I then went to the master system and did a reboot to see
> whether I would get this same message there. It didn't appear. Thing is the
> frontend on the remote system will not progress if I choose exit. Is there
> anyway around this using SVN or should I just compile 0.20.2 on the remote
> system as well?
>
> Jongi
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users[at]mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
>
>

jongitech at gmail

Dec 24, 2007, 9:13 AM

Post #3 of 7 (1010 views)
Permalink

Re: Mixing SVN Frontend (0.21) with 0.20.2 Backend [In reply to]

I suspected as much. Thanks.

Tim Litwiller wrote:

Your versions have to match. Either use all .20.2 or use all SVN

On Dec 24, 2007 7:20 AM, jongi <jongitech[at]gmail.com> wrote:

Hi,

On my master system (back and frontend) I am running MythTV 0.20.2 on a Fedora 8 box. All is working fine. I decided to install the SVN on another computer which I want to use as a remote front end. So I compiled SVN and all seemed to go well.

When I start mythfrontend on the remote system the following comes up:

Warning: MythTV wants to upgrade your database schema, from 1160 to 1202.
[Exit / Upgrade]

So I chose exit. I then went to the master system and did a reboot to see whether I would get this same message there. It didn't appear. Thing is the frontend on the remote system will not progress if I choose exit. Is there anyway around this using SVN or should I just compile 0.20.2 on the remote system as well?

Jongi

_______________________________________________
mythtv-users mailing list
mythtv-users[at]mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users"]http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

_______________________________________________ mythtv-users mailing list mythtv-users[at]mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users"]http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

greg at phaze

Dec 24, 2007, 9:25 AM

Post #4 of 7 (1035 views)
Permalink

Re: Mixing SVN Frontend (0.21) with 0.20.2 Backend [In reply to]

> choose exit. Is there anyway around this using SVN or should I just
> compile 0.20.2 on the remote system as well?
> Jongi

You cannot mix versions. You will have to choose one version and use the same on both.

_______________________________________________
mythtv-users mailing list
mythtv-users[at]mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

w.munson at comcast

Dec 25, 2007, 4:55 AM

Post #5 of 7 (1022 views)
Permalink

Re: Mixing SVN Frontend (0.21) with 0.20.2 Backend [In reply to]

Tim Litwiller wrote:
> Your versions have to match. Either use all .20.2 or use all SVN
>
Not just run SVN but you must have the same version of SVN running on
ALL your machines so you need to upgrade code on every myth machine at
the same time. Also, you cannot go backwards from SVN to release other
than by saving a copy of your database and restoring it when you want to
go back. This means anything recorded while running SVN will be lost
when reverting. On the other hand, we are getting close to another
release of Myth so the code in SVN is pretty stable right now and I
would not hesitate to suggest switching to SVN if you are willing to put
up with a few possible bugs. I have been running SVN for a year or so. I
just monitor the dev and commits lists and do not upgrade until the code
is in a stable state, ie. I wait until a few days have passed since a
major commit to allow the devs to fix any errors that crop up. I find
some of the features in the new code are required to be able to run my
system the way I want.

Bill

_______________________________________________
mythtv-users mailing list
mythtv-users[at]mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

derliebegott at gmail

Dec 25, 2007, 4:30 PM

Post #6 of 7 (1012 views)
Permalink

Re: Mixing SVN Frontend (0.21) with 0.20.2 Backend [In reply to]

2007/12/25, William Munson <w.munson[at]comcast.net>:
> Tim Litwiller wrote:
> > Your versions have to match. Either use all .20.2 or use all SVN
> >
> Not just run SVN but you must have the same version of SVN running on
> ALL your machines so you need to upgrade code on every myth machine at
> the same time. Also, you cannot go backwards from SVN to release other
> than by saving a copy of your database and restoring it when you want to
> go back. This means anything recorded while running SVN will be lost
> when reverting. On the other hand, we are getting close to another
> release of Myth so the code in SVN is pretty stable right now and I
> would not hesitate to suggest switching to SVN if you are willing to put
> up with a few possible bugs. I have been running SVN for a year or so. I
> just monitor the dev and commits lists and do not upgrade until the code
> is in a stable state, ie. I wait until a few days have passed since a
> major commit to allow the devs to fix any errors that crop up. I find
> some of the features in the new code are required to be able to run my
> system the way I want.
>
> Bill
>

this would not be a problem if mythfrontend and plugins would
communicate with mythbackend through a specified protocol without
directly writing into database. fyi, this is not a critic, just an
explanation.
_______________________________________________
mythtv-users mailing list
mythtv-users[at]mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

myth at dermanouelian

Dec 25, 2007, 4:40 PM

Post #7 of 7 (1012 views)
Permalink

Re: Mixing SVN Frontend (0.21) with 0.20.2 Backend [In reply to]

On Dec 25, 2007, at 4:30 PM, Ma Begaj wrote:

> 2007/12/25, William Munson <w.munson[at]comcast.net>:
>> Tim Litwiller wrote:
>>> Your versions have to match. Either use all .20.2 or use all SVN
>>>
>> Not just run SVN but you must have the same version of SVN running on
>> ALL your machines so you need to upgrade code on every myth machine
>> at
>> the same time. Also, you cannot go backwards from SVN to release
>> other
>> than by saving a copy of your database and restoring it when you
>> want to
>> go back. This means anything recorded while running SVN will be lost
>> when reverting. On the other hand, we are getting close to another
>> release of Myth so the code in SVN is pretty stable right now and I
>> would not hesitate to suggest switching to SVN if you are willing
>> to put
>> up with a few possible bugs. I have been running SVN for a year or
>> so. I
>> just monitor the dev and commits lists and do not upgrade until the
>> code
>> is in a stable state, ie. I wait until a few days have passed since a
>> major commit to allow the devs to fix any errors that crop up. I find
>> some of the features in the new code are required to be able to run
>> my
>> system the way I want.
>>
>> Bill
>>
>
> this would not be a problem if mythfrontend and plugins would
> communicate with mythbackend through a specified protocol without
> directly writing into database. fyi, this is not a critic, just an
> explanation.

versioning mismatch errors only happen when the protocol version has
been upgraded, not necessarily the version of mythtv. The protocol
version is only upgrade when it's necessary for new functionality. My
point is that there is a specified protocol used for communication. It
changes relatively often so having the exact same version frontend/
backend is the only supported way to run. I've run unsupported
mismatched frontend/backend versions before and it doesn't seem to
care as long as you avoid functionality that has changed between
versions. No, I'm not going to tell anyone how to do this because if
you don't know then you definitely shouldn't be doing it. ;)

_______________________________________________
mythtv-users mailing list
mythtv-users[at]mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact lists@gossamer-threads.com