Re: Mythtv at 0.25.2

On Thu, Jul 19, 2012 at 5:59 AM, Richard Shaw <[email protected]> wrote:

> On Thu, Jul 19, 2012 at 12:51 AM, Mogens Kjaer <[email protected]> wrote:
> > Are there any hints on how to change mythtv installation from
> > atrpms to rpmfusion?
>
> I wouldn't think there would be much difference overall since it's
> building from the same sources...
>
>
> > On my backed running CentOS 6, I've:
> >
> > 1. Made a backup of my mythtv database
> > 2. Removed all packages from the atrpms repo
> > 3. Set up EPEL and rpmfusion.
> > 4. Manually installed xmltv from atrpms
> > 5. Installed mythtv-0.25.1
> > 6. Started the backend.
> >
> > But I can't get in contact with it, neither from my frontend (on which
> I've
> > done the same), from mythweb, or from a DLNA client.
> >
> > On mythweb I get the:
> >
> > !!NoTrans: Unexpected response to MYTH_PROTO_VERSION '72': !!
>

also remember that mythweb is now a separate rpm package.

Make sure no old rpm are lingering behind.


> >
> > message. I have set a proper, i.e. not localhost, IP address in
> > mythtv-setup.
> >
> > I don't see any hints in the /var/log/mythtv/mythbacked.*.log file.
>
> This is a new one for me. It would appear that something strange is
> happening on the backend. I wonder if there's any leftover files from
> the previous package causing issues? I would check /etc/mythtv and
> make sure there's nothing there that doesn't belong. I know mysql.txt
> is still usable but it's depreciated in favor of config.xml. Perhaps
> there's some conflict if both exist?
>
> Another thing to check is the init scripts may not be the same and
> could use different environment variable settings for HOME and/or
> MYTHCONFDIR... The sysv init script runs mythbackend as root and sets
> both environment variables to /etc/mythtv.
>
> Sorry you're having this issue but there hasn't been much testing of
> the EL build as of yet because of the missing xmltv requirement so it
> looks like you're the beta tester :)
>
> What version of mythtv did you "upgrade" from? I haven't had any DB
> schema update issues but that's not to say it couldn't happen.
>
> Just some ideas, hope it helps.
>
> Richard
>
> _______________________________________________
> atrpms-users mailing list
> [email protected]
> http://lists.atrpms.net/mailman/listinfo/atrpms-users
>

_______________________________________________
atrpms-users mailing list
[email protected]
http://lists.atrpms.net/mailman/listinfo/atrpms-users