View Issue Details

IDCategoryLast Update
0007328other2017-04-22 13:16
ReportermepholicAssigned Tox42 
Reproducibilityalways 
Status resolvedResolutionwon't fix 
Product Version5.X git (version in description) 
Fixed in Version 
Summary0007328: Github release tarballs are empty
DescriptionThe 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 ReproduceGo 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/
TagsNo tags attached.

Activities

x42

2017-04-22 13:16

administrator   ~0019619

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:
 2) libs/ardour/revision.cc
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.

Issue History

Date Modified Username Field Change
2017-04-22 11:12 mepholic New Issue
2017-04-22 13:16 x42 Note Added: 0019619
2017-04-22 13:16 x42 Status new => resolved
2017-04-22 13:16 x42 Resolution open => won't fix
2017-04-22 13:16 x42 Assigned To => x42