I'm thinking to move forward to R5.5 (from R5F27) instead of waiting for R6. Optimistic that I will get some free time soon!

In my set up, all my front ends and my master backend (running virtualized) are KM. But I have my analogue tuners running on the native OS of my main web/mail/etc server and acts as a slave backend.

In R5F27, I was able to cleanly map that to 0.20.2 and retrieve the RPMs at atrpms.

From what I gather R5.5 was cut from a very specific version of 0.21-fixes. It is not clear to me though if it picks up the rest of the updates in 0.21-fixes.

If not, is there a reasonable way to map the KM version to the atrpms version?

My concern is ensuring database and protocol are fully compatible.

I think I am half way there as I dig further. Hadn't noticed the detailed version info at atrpms.

R5.5 is based on SVN 17686. Is this constant or does the install/upgrade update to a more recent version in the branch?

atrpms has two current releases
193 SVN 18753
198 SVN 19217

So if R5.5 stays at SVN 17686 (as I suspect) then I guess the question is how to simply determine if there were protocol or database schema changes between these versions.

No matter the distro, any version of -fixes should work together.

Thank you. It is what I had hoped to hear.

My entire family is hooked on KM so breaking it could risk my sanity

Fortunately I run the MBE in a VMWare VM so that part of the upgrade will be easy to verify.

Cecil, I know you hear this endlessly but KM is a marvelous piece of work. I recommend it continuously to people edging into Mythtv. I even wrote How-to's over at contribs.org to get myth backend integrated into that server and then recommend KM for the front end

Cheers!

Christ

Happy to help. Thanks for passing the word!