[mythtv-users] ATRPMs upgrade issue.

Andy Burns fedora at adslpipe.co.uk
Wed Feb 27 23:36:28 UTC 2008


On 27/02/2008 21:51, Axel Thimm wrote:

> Don't hop off until 0.21 is offially released! 

OK, I won't :-)

> Ayn testing of the bleeding package is now more important than ever! Thanks!

I moved from stable to bleeding when multirec landed, and noticed 
straight away the pre0.21 versions are *THE* most reliable ones I've run 
in over 2 years with myth, not one backend crash since!

A couple of frontend niggles, I ought to update again and if they 
persist check on the dev mailing list/trac

One thing which bit me when I first switched to 0.21bleeding, which 
struck me as a packaging issue is the initial configuration of 
/etc/httpd/conf.d/mythweb.conf

> So the bleeding packages have gone 0-21-fixes since
> 0.21-175_trunk_r15741.

That's good to know, I didn't want to "tread too far" and get a schema 
update from 0.22

> The revision is just the revision I pulled. It is the same as
> for the 0.20 fixes branch no matter what the last commit was (so
> actually the last commit revision is less than 16254, and the next
> commit revision higher).

Would it be possible to include in the changelog of the rpm (or direct 
into the corresponding .html file is that's not where it comes from) a 
link to the SVN changes between revisions, e.g.

http://svn.mythtv.org/trac/changeset?old_path=%2Ftrunk&old=15741&new_path=%2Fbranches%2Frelease-0-21-fixes&new=16131

I generally perform such a query before doing an update to see what 
changes to expect.




More information about the mythtv-users mailing list