On 1/11/06, Chris Petersen <[EMAIL PROTECTED]> wrote:
> > I could see in the new mythweb the ability to select the jobs to run
> > as part of the schedule, but I want to run it once the recording is
> > complete (i.e, I haven't had time to watch the latest episode of the
> > simpsons on my TV, so k
> I could see in the new mythweb the ability to select the jobs to run
> as part of the schedule, but I want to run it once the recording is
> complete (i.e, I haven't had time to watch the latest episode of the
> simpsons on my TV, so kick off my user job to export it to my PDA for
> on the train)
Darryl Ross wrote:
>Chris Petersen wrote:
>
>
>>That's the answer. If you want to use svn, use svn for everything.
>>
>>
>
>It is possible to retrieve older revisions out of subversion. That is
>what I am wanting to do.
>
>All I am asking is what subversion revision number was used in the 1
On 1/11/06, Chris Petersen <[EMAIL PROTECTED]> wrote:
> Could find the patch in the ticket history, or the history for that page...
I could see in the new mythweb the ability to select the jobs to run
as part of the schedule, but I want to run it once the recording is
complete (i.e, I haven't had
> There isn't anyting in SVN that I would need so bad on my real mythweb
> though. What I would like is the ability to set off a user job from
> the recordings screen.
Could find the patch in the ticket history, or the history for that page...
-Chris
_
On 1/11/06, Darryl Ross <[EMAIL PROTECTED]> wrote:
>
> I have just tried to update my mythweb to the current version that's in
> SVN (rev 8554) but when I try to load the pages up I'm getting:
>
Just the other day I wanted to look at what had changed in MythWeb so
despite running 0.18.1, I went a
> It is possible to retrieve older revisions out of subversion. That is
> what I am wanting to do.
Then check out the .18.1 tag, not trunk. Or look at the revision number
on the .18.1 branch:
http://svn.mythtv.org/trac/browser/tags/release-0-18-1/mythplugins/mythweb
-Chris
Chris Petersen wrote:
> That's the answer. If you want to use svn, use svn for everything.
It is possible to retrieve older revisions out of subversion. That is
what I am wanting to do.
All I am asking is what subversion revision number was used in the 18.1
release (well, more specifically which
Darryl Ross wrote:
> Chris Petersen wrote:
>> Darryl Ross wrote:
>
>>> Which revision of mythweb is compatible with 18.1 then?
>> The one that shipped with .18.1
>
> That was really bloody useful.
That's the answer. If you want to use svn, use svn for everything. If
you don't want to upgrade
Chris Petersen wrote:
> Darryl Ross wrote:
>>Which revision of mythweb is compatible with 18.1 then?
>
> The one that shipped with .18.1
That was really bloody useful.
signature.asc
Description: OpenPGP digital signature
___
mythtv-users mailing list
Darryl Ross wrote:
> Kevin Kuphal wrote:
>> Darryl Ross wrote:
>
>>> I have just tried to update my mythweb to the current version that's in
>>> SVN (rev 8554) but when I try to load the pages up I'm getting:
>
User Notice at /home/httpd/mythweb/includes/mythbackend.php, line 163:
Incom
Kevin Kuphal wrote:
> Darryl Ross wrote:
>>I have just tried to update my mythweb to the current version that's in
>>SVN (rev 8554) but when I try to load the pages up I'm getting:
>>>User Notice at /home/httpd/mythweb/includes/mythbackend.php, line 163:
>>>Incompatible protocol version (mythweb=
Darryl Ross wrote:
>Hey All,
>
>I have a three machine mythtv network here: the master backend, a
>dedicated file/database/web server and a combined frontend/backend. The
>backends are using the 18.1 RPMS from atrpms.
>
>I have just tried to update my mythweb to the current version that's in
>SVN
Hey All,
I have a three machine mythtv network here: the master backend, a
dedicated file/database/web server and a combined frontend/backend. The
backends are using the 18.1 RPMS from atrpms.
I have just tried to update my mythweb to the current version that's in
SVN (rev 8554) but when I try to
14 matches
Mail list logo
