View Issue Details
|ID||Category||Date Submitted||Last Update|
|0007328||other||2017-04-22 11:12||2017-04-22 13:16|
|Product Version||5.X git (version in description)|
|Fixed in Version|
|Summary||0007328: Github release tarballs are empty|
|Description||The latest few Github release tarballs seem to be empty. This is especially an issue for packagers, as Ardour does not seem to provide a versioned tarball on the official website. A fix to this issue would be appreciated at your earliest convenience.|
|Steps To Reproduce||Go to: https://github.com/Ardour/ardour/releases/tag/5.8|
Download the tar.gz
Check the contents of ardour-5.8.tar.gz
|Additional Information||$ ls -lah ardour-5.8.tar.gz |
-rw-r--r-- 1 mepholic mepholic 212 Apr 22 07:09 ardour-5.8.tar.gz
$ tar tvf ardour-5.8.tar.gz
drwxrwxr-x root/root 0 2017-02-27 10:40 ardour-5.8/
|Tags||No tags attached.|
This in intentional. Github provided zips and tar bundles never worked.
The version of Ardour is maintained using git-tags.
Compiling Ardour depends on either
1) `git describe`
or a file generated by `./waf dist` which uses `git describe` and is added to the zip:
Github does not allow to use a hook or git-attribute to inject a version file while zipping.
Also the git-tag is the very first step in the release procedure. If some issues or regressions are found during the release process, the tag is skipped (e.g. there was no Ardour 5.7 release; 5.7-2 became 5.8). The last step in a release process is the upstream source tar which constitutes a release.
You can use uscan to watch https://community.ardour.org/src/Ardour-(.*)\.tar\.bz2 for new upstream releases and get a tar from there.