<p dir="ltr"><br>
On Sep 17, 2014 11:07 AM, "Simo Sorce" <<a href="mailto:ssorce@redhat.com">ssorce@redhat.com</a>> wrote:<br>
><br>
><br>
> I was looking at this:<br>
> <a href="https://fedoraproject.org/wiki/Packaging:SourceURL?rd=Packaging/SourceURL#Github">https://fedoraproject.org/wiki/Packaging:SourceURL?rd=Packaging/SourceURL#Github</a><br>
><br>
> But it doesn't look like the URL constructed with these instructions<br>
> lead to a download-able tarball.<br>
> I guess Github has changed things again, is there any new guideline for<br>
> Github Sources ?<br>
><br>
> What I can see is that while this:<br>
> <a href="https://github.com/$OWNER/$PROJECT/archive/%{commit}/$PROJECT-%{commit}.tar.gz">https://github.com/$OWNER/$PROJECT/archive/%{commit}/$PROJECT-%{commit}.tar.gz</a><br>
> does not work, this:<br>
> <a href="https://github.com/$OWNER/$PROJECT/archive/%{commit}.tar.gz">https://github.com/$OWNER/$PROJECT/archive/%{commit}.tar.gz</a><br>
> works, and the content headers tell the browser that the file name<br>
> should be $PROJECT-%{commit}.tar.gz<br>
><br>
> Any direction would be appreciated.<br>
><br>
Github has changed this several times :-( if the old url scheme is not working any longer the guidelines should be updated. Fpc ticket is probably best for that. From your description of what urls work, I'm not sure if there's a good recommendation for a github url in source0 (have to test the permutations to see). Might have to go back to putting the url in a comment.</p>
<p dir="ltr">-Toshio<br>
</p>