[mythtv] Github tarball from commit can change

Stuart Auchterlonie stuarta at squashedfrog.net
Mon Sep 28 12:34:38 UTC 2015

On 28/09/15 13:17, Craig Treleaven wrote:
> For my MacPorts packaging of Myth, I use the GitHub feature to create a tarball of the source as of a particular commit.  Work great…most of the time.  But not all the time and not as of yesterday.
> For example, I updated Myth on September 17 to pull from the fixes-27 branch as of September 9 (commit e9b577d3) and recorded the checksums for the archive at that time.  Yesterday, a user went to build and got different checksums which, of course, caused the build to fail.
> Comparing the contents of the archive from September 17 to now, the only difference is:
> $ diff -ur prev new
> diff -ur prev/MythTV-mythtv-e9b577d/mythtv/EXPORTED_VERSION new/MythTV-mythtv-e9b577d/mythtv/EXPORTED_VERSION
> --- prev/MythTV-mythtv-e9b577d/mythtv/EXPORTED_VERSION	2015-09-09 13:14:00.000000000 -0400
> +++ new/MythTV-mythtv-e9b577d/mythtv/EXPORTED_VERSION	2015-09-09 13:14:00.000000000 -0400
> @@ -1,2 +1,2 @@
>  SOURCE_VERSION="e9b577d"
> -BRANCH=" (fixes/0.27)"
> +BRANCH=“”
> I don’t know much about git or GitHub.  Can someone explain why that line changed and how to prevent this problem in the future.
> Craig

Pulling the tar ball will always pull the latest and greatest.
Any change to fixes/0.27 will result in a different tarball to
the previous download.

There may be a way of telling it to pull at a specific commit,
but haven't looked at it

Your other option, is to pull one of the tagged releases, but
then you are potentially a few commits behind.


More information about the mythtv-dev mailing list