[mythtv] Found a severe decoding bug in mythffplay

[Robin Gilks]

> No.  Any sensible package system is going to apply one or more hashes to
> distributed binary or source tarballs, and fail on a mismatch.  Use of a
> single changing source tarball for those packaging scripts would not be
> compatible, hence the ebuild generator in the Gentoo folder. I believe
> the proper incantation is...
>
> scripts/mythtv-buildebuild.py --version=0.25 --type=5
>
> which pulls a new tarball of the latest commit to the 0.25/fixes branch
> from Github, and produces a new ebuild based off the previous copy.
> Ideally, I get some auto-build mechanism set up like MythBuntu, which
> generates a new ebuild every night, test compiles it, and pushes to the
> repository.

Sounds ideal - unfortunately:

# scripts/mythtv-buildebuild.py --version=0.25 --type=5
Traceback (most recent call last):
  File "scripts/mythtv-buildebuild.py", line 312, in <module>
    Ebuild(package).update()
  File "scripts/mythtv-buildebuild.py", line 79, in update
    self.get_cur()
  File "scripts/mythtv-buildebuild.py", line 179, in get_cur
    type = types.index(self.opts.type)
ValueError: tuple.index(x): x not in tuple

I'm afraid my python skills are not up to cryptic error messages like this :(

I'm open to suggestions...

Cheers

-- 
Robin Gilks