Upgrade to newer mythtv protocol version

[Patrick Ruckstuhl]

impact: mythtvfs will fail when upgrading from jaunty to karmic due to changes in the MythTV protocol.
addressed: backported minimal required piece of new upstream version.
regression potential: very low, effectively a data-only change.
work-around: add "program-width=47" to the mount options.
TEST CASE:
 1) install mythtv on karmic
 2) mythtvfs -o host=localhost /var/lib/mythtv/recordings /mnt
Step 2 will succeed when it can talk to mythtv again.

original bug report:

In karmic this package does no longer work together with mythtv as mythtv now uses protocol 50.

[MilkBoy (michael-wikberg)]

Try this patch. You could also mount with the extra option "-o program-width=47" =)

[Launchpad Janitor (janitor)]

This bug was fixed in the package mythtvfs-fuse - 0.6.1-1

---------------
mythtvfs-fuse (0.6.1-1) unstable; urgency=low

  * New upstream release, supports MythTV 0.22 (LP: #468429).
    - 04_xopen_source.patch: dropped, taken upstream.
 -- Kees Cook <email address hidden> Sun, 13 Dec 2009 19:26:46 +0000

[Steve Langasek (vorlon)]

Accepted into karmic-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

[Martin Pitt (pitti)]

Anyone who can test the proposed package? If not, the proposed update will be removed again. Thanks!

[Kees Cook (kees)]

FWIW, it's been working for me fine on my karmic myth system for months now.

[Launchpad Janitor (janitor)]

This bug was fixed in the package mythtvfs-fuse - 0.6.0-1ubuntu0.1

---------------
mythtvfs-fuse (0.6.0-1ubuntu0.1) karmic-proposed; urgency=low

  * 50_protocol-update.patch: backport upstream changes for new
    protocol (LP: #468429).
 -- Kees Cook <email address hidden> Sun, 13 Dec 2009 11:38:58 -0800