[mythtv] Found a severe decoding bug in mythffplay

[Raymond Wagner]

On 5/8/2012 05:52, Robin Gilks wrote:
>
>> On 05/04/2012 08:57 PM, Jean-Yves Avenard wrote:
>>> Hi
>>>
>>> On Saturday, 5 May 2012, Nick Morrott wrote:
>>>> On 4 May 2012 23:11, Michael T. Dean
>>>>
>>>> On a related note: are there any plans to upload nightly 0.2x-fixes
>>>> tarballs and make those available instead (or even in addition) of the
>>>> release/point release tarballs on the official website, for those
>>>> users who do not checkout from github or use pre-built binaries?
>>> IMHO; that's what point release are for.
>>
>> Yeah, I don't think it's worth doing nightly tarballs or anything.
>>
>> Then again, I'd love to just remove the tarballs from our website and
>> let users/packagers either clone the repo with git or use github tarball
>> links.  TTBOMK, this would actually work, now, since Stuart M modified
>> the version script to allow us to always keep a VERSION file in place,
>> such that it's only used on systems without git tools or where the
>> tarball contains a git export (rather than a repo).
>>
>> With that approach--as long as we post the -fixes tarball link rather
>> than the release tag tarball link--users would still get the
>> most-current fixes.
>>
>> Mike
>
> Is there any chance that the packaging scripts could use this approach?
> The Gentoo builds of 0.25 are now a month old and are for a release
> candidate. I assume that the others (OSX, Win32, rpm etc) are in the same
> position.
>

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.