MythTV 0.20.2 in Feisty & Edgy

[superm1]

Hi everyone. As most North American users now know, guide data from Zap2it labs has gone away. Schedules direct (www.schedulesdirect.org) is out there to replace it, but requires the 0.20.2 release of MythTV.

This release is already in Gutsy, but also has been released to feisty-updates and edgy-updates.

If your a MythTV user, you can easily (and hopefully painlessly ) upgrade to the new packages. Here's how:

GUI Method:
Open up System->Administration->Software Sources.
Choose the 'Updates' tab.
Make a full checkmark in "Recommended Updates"
Here is what it should look like (although from a gutsy box, should be very similar on feisty or edgy)

Hit close, and let it update your package lists.

Open up update manager or synaptic, and you should see all of your mythtv related items listed as possible updates.

Command Line Method

1) Edit /etc/apt/sources.list
Make sure that the feisty-updates or edgy-updates line is not commented out. Also make sure universe multiverse main restricted are all listed.
2) Update package lists

sudo apt-get update

3) Update packages

sudo apt-get upgrade

4) Open up mythtv-setup
Provide your new source information
5) Run mythfilldatabase

Note: These packages just have updated MythTV / Mythplugins versions. The packaging is not updated to the same packaging in Gutsy. If you are interested in the same packaging as gutsy, you may want to look at http://www.mythbuntu.org/auto-builds

[lefthand]

Worked perfectly. I didn't even have to use synaptic, after enabling the Pre-released Updates repository the magic orange icon told me I had updates. I just ran that and mythtv was updated.

MythWeather is also working now, another pleasant surprise.

[m_yates]

Worked perfectly for me. I subscribed to schedules direct and was able to get my TV listings downloaded from them.

[newlinux]

Worked for me. It broke my mythweb slightly, however. I had to go modify the .htaccess file with the database password. But it worked fine across all my backends, both feisty and edgy. Seemless transition for my scheduled recordings however. Mythweather (at least through the web) still doesn't work for me. I didn't think to try it on the frontend. Perhaps it needs configuring again. I'll look at it when I get home.

[dannyboy79]

can some1 please inform me what the url's are for those that would like to try this thru ssh or non-GUI. thank you. is it just enabling the backports repo's? Will that bring anything else that I don't want to bring from the backports or am I barking up the wrong tree and that's not even the repo to enable thru ssh?? Any help would be appreciated.

Also, Newlinux, can you maybe be a little more specific as to how mythweb broke? I use it a lot and would like to be prepared on how to fix it. I currently am not even sure how I enabled security but it's on. When I look in /usr/share/mythtv/mythweb/.htaccess I see a bunch of stuff but the important stuff from what I remember is commented out, see below:
#AuthType Digest
#AuthName "MythTV"
#AuthUserFile /etc/apache2/httpd-passwords
#Require valid-user
#BrowserMatch "MSIE" AuthDigestEnableQueryStringHack=On
#Allow from 192.168.1.
#Satisfy any


So i must be using another method. I remember I had a lot of problems enabling security for mythweb but ended up getting it working just don't remember how. I think I am using the method toward the bottom of this guide but obviously the paths that they use (/etc/httpd/conf/httpd-passwords) would be different for ubuntu. DAMN IT, I just lost my ssh connection so I can't check. I hate this when this happens. My internet will go down due to torrenting (i think) and then the only way to get it working again is to unplug the modem and router, and then plug in modem first, wait a second, then plug in router. You guys have a possible solution for this?

[newlinux]

Originally Posted by dannyboy79 can some1 please inform me what the url's are for those that would like to try this thru ssh or non-GUI. thank you. is it just enabling the backports repo's? Will that bring anything else that I don't want to bring from the backports or am I barking up the wrong tree and that's not even the repo to enable thru ssh?? Any help would be appreciated.

It's the proposed (pre-release) repo, not the backports repo. I think there are a couple of other things in there that if you do a standard update will come through. I don't remember any of them looking like major things, but I did not install them. I'm not at home (and have ssh blocked through my firewall - someone kept trying to break in) so I can't explicitely check the URL...

[newlinux]

I think it is just the standard repo url (http://archive.ubuntu.com/ubuntu I think) with feisty-proposed, or edgy-proposed as the repo (and it would be in the multiverse).

[dannyboy79]

well whenever you can confirm I would appreciate it. Also, you didn't comment on the mythweb access issue. can you make any comments?

[superm1]

Yes standard repo line just with feisty-proposed or edgy-proposed rather than. So something like this:

deb http://archive.ubuntu.com/ubuntu feisty-proposed main multiverse universe restricted

As for mythweb htaccess, this has been changed entirely in Gutsy. I didn't backport the code to prevent risk of further regression. So the situation with setting a htaccess password should have been the same as before this SRU.

[newlinux]

Originally Posted by dannyboy79 well whenever you can confirm I would appreciate it. Also, you didn't comment on the mythweb access issue. can you make any comments?

Sorry. Somehow I completely missed your post about mythweb. For some reason my .htaccess file (located at /usr/share/mythtv/mythweb/ I think) was softlinked to a file that no longer existed after the update (this is on edgy). I don't remember softlinking it at all, but it has been a while. So I basically did not have a .htaccess file. In that direct was the generic .htaccess.dist file, which I copied over as .htaccess and changed the database access password from "mythtv" to what I have my database password set as. That was it. It didn't affect my apache password protection, which is set somewhere else. It only affected mythweb's access to the mythconverg database. If you are at all worried about this, just backup your .htaccess file somewhere safe.


I do have to wonder why you want to do this over a flaky ssh connection. sounds kind of problematic to me. Also, if you aren't forwarding X, you won't be able to go into mythtv-setup and modify the video sources to use schedules direct.