Mailing List Archive

On 29 Mar 2010, at 03:11, Chris Adams wrote:

> Hi,
>
> Currently I'm on mythbuntu 9.10 with JYA's 0.22-fixes repo and his
> nvidia 185 drivers.
> I'm planning an upgrade to mythbuntu weekly auto-builds to get 0.23rc1.
>
> Just wondering if there's any special steps recommended, for instance
> removing JYA's myth or nvidia packages before activating the
> auto-builds.

I've just completed this update, well I was using nvidia 195 drivers but jya 0.22-fixes to Mythbuntu weekly 0.23-fixes (rc-1)is the main thing.

I had a few gotchas, it seems jya's packages show up as 2:0.22 which apt thinks is newer than 0.23 so that was a pain. I upgraded a couple of backends and three frontends, same problem on each, apt didn't want to upgrade anything even after commenting out the jya repo and trying again.

What I did was to add the mythbuntu 0.23 weekly builds repository, disable the jya repository, apt-get update, then manually apt-get remove all the mythtv packages, doesn't really matter everything is in the database after all.
I then installed mythtv, or mythtv-frontend or mythtv-backend and mythtv-themes as appropriate.
I had to manually flush the /usr/share/mythtv/themes directory as I had some manually installed themes that wouldn't go away and caused me some crashes, mythfrontend.real -v is very useful. I also found a /etc/default/mythtv-backend file that was breaking the user environment for the master backend (couldn't find mysql.txt), removed it and the backend-started happily rather than looping crazily.

I found that lirc had also been removed as a dependency so had to re-install that and replace the config files from a backup.

It's all working now, some small issues for another thread but looks pretty good, first impression is the backend is using a lot less cpu cycles and frontend seems a lot snappier. Couple of hours to do two backends and three frontends including finding the gotchas and and some head scratching over themes that crashed mythtv-setup.


> Also wondering if people think I should keep JYA for nvidia drivers,
> or use mythbuntu for nvidia too.

I'm keeping the jya drivers but it looks like mythbuntu packages them up as two part now so maybe there's no major difference now? JYA is always really quick at packaging new drivers versions but those 2:0.22 version numbers will presumably cause apt to "upgrade" everything back to 0.22 if I re-enable the repo?

>
> And a third thing: is nvidia 195 ready for prime-time yet? Just

Works well here for me, based on a sample of two it's perfect ;-)


> wondering, 'cos I heard word of performance and HDMI audio regressions
> in some 195 versions.
>
> Cheers!
> Chris.
>
> NB. Yes backups will be done :-)
> _______________________________________________
> mythtv-users mailing list
> mythtv-users@mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
>

_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

> I had a few gotchas, it seems jya's packages show up as 2:0.22 which apt thinks is newer than 0.23 so that was a pain. I upgraded a couple of backends and three frontends, same problem on each, apt didn't want to upgrade anything even after commenting out the jya repo and trying again.

Yep, same thing I saw. He would've done it on purpose to make double
sure the packages stomped on mythbuntu's base when you first add his
repo.

> What I did was to add the mythbuntu 0.23 weekly builds repository, disable the jya repository, apt-get update, then manually apt-get remove all the mythtv packages, doesn't really matter everything is in the database after all.
> I then installed mythtv, or mythtv-frontend or mythtv-backend and mythtv-themes as appropriate.

That's what I was thinking of, but was afraid the mythconverg database
would be killed as part of removing mythtv-database. I've backed it up
though, so.. what's the worst that can happen, I'll restore it and let
myth upgrade it :)

I was considering forcing a downgrade (apt-get install
package=version) but it was going to downgrade more other packages
than I was willing to take a risk on, so I haven't done anything just
yet..

> I had to manually flush the /usr/share/mythtv/themes directory as I had some manually installed themes that wouldn't go away and caused me some crashes, mythfrontend.real -v is very useful. I also found a /etc/default/mythtv-backend file that was breaking the user environment for the master backend (couldn't find mysql.txt), removed it and the backend-started happily rather than looping crazily.
>
> I found that lirc had also been removed as a dependency so had to re-install that and replace the config files from a backup.
>

Much appreciated - I'll keep a lookout for those issues.

>> Also wondering if people think I should keep JYA for nvidia drivers,
>> or use mythbuntu for nvidia too.
>
> I'm keeping the jya drivers but it looks like mythbuntu packages them up as two part now so maybe there's no major difference now? JYA is always really quick at packaging new drivers versions  but those 2:0.22 version numbers will presumably cause apt to "upgrade" everything back to 0.22 if I re-enable the repo?

I'll do what you've done too - leave the JYA drivers in place but
disable the repo.

>> And a third thing: is nvidia 195 ready for prime-time yet? Just
>
> Works well here for me, based on a sample of two it's perfect ;-)
>

Hmm.. might upgrade to 195 before disabling the repo :-)

Very helpful, cheers!
Chris
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

> Very helpful, cheers!
> Chris
>

Also - JYA your work on the repo has been very appreciated the last few months!
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

On Thursday 01/04/2010 at 11:43 am, Chris Adams wrote:
>>
>> I had a few gotchas, it seems jya's packages show up as 2:0.22 which
>> apt thinks is newer than 0.23 so that was a pain. I upgraded a couple
>> of backends and three frontends, same problem on each, apt didn't want
>> to upgrade anything even after commenting out the jya repo and trying
>> again.
>
> Yep, same thing I saw. He would've done it on purpose to make double
> sure the packages stomped on mythbuntu's base when you first add his
> repo.
>
>>
>> What I did was to add the mythbuntu 0.23 weekly builds repository,
>> disable the jya repository, apt-get update, then manually apt-get
>> remove all the mythtv packages, doesn't really matter everything is in
>> the database after all.
>> I then installed mythtv, or mythtv-frontend or mythtv-backend and
>> mythtv-themes as appropriate.
>
> That's what I was thinking of, but was afraid the mythconverg database
> would be killed as part of removing mythtv-database. I've backed it up
> though, so.. what's the worst that can happen, I'll restore it and let
> myth upgrade it :)




In the past I've purged every myth package off mythbuntu, switched
repos and reinstalled - all settings and db were preserved.

But yah, backup anyway :)





--
Lindsay Mathieson
http://blackpaw.jalbum.net/home/



_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

On 1 Apr 2010, at 02:42, Chris Adams wrote:

>> I had a few gotchas, it seems jya's packages show up as 2:0.22 which apt thinks is newer than 0.23 so that was a pain. I upgraded a couple of backends and three frontends, same problem on each, apt didn't want to upgrade anything even after commenting out the jya repo and trying again.
>
> Yep, same thing I saw. He would've done it on purpose to make double
> sure the packages stomped on mythbuntu's base when you first add his
> repo.
>
>> What I did was to add the mythbuntu 0.23 weekly builds repository, disable the jya repository, apt-get update, then manually apt-get remove all the mythtv packages, doesn't really matter everything is in the database after all.
>> I then installed mythtv, or mythtv-frontend or mythtv-backend and mythtv-themes as appropriate.
>
> That's what I was thinking of, but was afraid the mythconverg database
> would be killed as part of removing mythtv-database. I've backed it up
> though, so.. what's the worst that can happen, I'll restore it and let
> myth upgrade it :)
>
> I was considering forcing a downgrade (apt-get install
> package=version) but it was going to downgrade more other packages
> than I was willing to take a risk on, so I haven't done anything just
> yet..

I tried that too, It looked like it had worked, at first.... that was when I discovered I was going to need to remove all the mythtv packages, maybe I removed more that I needed to but it was annoying me by then!

Database didn't go anywhere when I removed it's package, it's very nice when the new system comes up all configured the way the old one was, in fact mine started a recording straight away :-)

Thanks to Jean Yves from me too, his vdpau studio level patches were what made me start using mythfrontend for daily TV. I think those patches were his rather than a backport?

Andre
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users