I don't know, if this is a general problem, but for the chiliproject web application hosted on github, I can't use mirror://github. It results in: >>> Downloading 'http://cloud.github.com/downloads/chiliproject/chiliproject/tarball/v3.4.0' --2013-01-07 10:40:37-- http://cloud.github.com/downloads/chiliproject/chiliproject/tarball/v3.4.0 Auflösen des Hostnamen »cloud.github.com«... 216.137.61.129, 216.137.61.25, 216.137.61.17, ... Verbindungsaufbau zu cloud.github.com|216.137.61.129|:80... verbunden. HTTP-Anforderung gesendet, warte auf Antwort... 403 Forbidden 2013-01-07 10:40:38 FEHLER 403: Forbidden. A websearch gave some results about similar issues with other github projects. Using http://github.com/chiliproject/chiliproject/tarball/v3.4.0 instead, works fine. Perhaps the mirror has to be updated. I would like to use mirror://github, as this is a more general approach.
This is, at least, partly my fault. I made some errors, when changing the SRC_URI. My SRC_URI now is: SRC_URI="mirror://github/chiliproject/chiliproject/${P}.tar.gz", which should be correct. However, this still results in: >>> Downloading 'http://cloud.github.com/downloads/chiliproject/chiliproject/chiliproject-3.4.0.tar.gz' --2013-01-07 11:02:06-- http://cloud.github.com/downloads/chiliproject/chiliproject/chiliproject-3.4.0.tar.gz Auflösen des Hostnamen »cloud.github.com«... 216.137.61.105, 216.137.61.81, 216.137.61.57, ... Verbindungsaufbau zu cloud.github.com|216.137.61.105|:80... verbunden. HTTP-Anforderung gesendet, warte auf Antwort... 403 Forbidden 2013-01-07 11:02:06 FEHLER 403: Forbidden.
URL returns this: <Error> <Code> AccessDenied </Code> <Message> Access Denied </Message> <RequestId> D0A5F38E5D66E167 </RequestId> <HostId> wq3+1BIw/iYOuTZY3FnTf22Uk4i2MXIRXtPnsSD1xqUkE4Xce2OR8CQ0gQMVtUSA </HostId> </Error>
Didn't mindless folks from github just remove the downloads completely [1]? And the mirror://github is just for uploaded files, not the live tarballs which should be used directly. [1]:https://github.com/blog/1302-goodbye-uploads
In any case, I'd appreciate a link to a project with downloads on github, so I could debug it more and fix the mirror:// if it is broken. They have disabled adding downloads to project not having ones, so I can't test it with a new project.
Oh, never mind, grepped ebuilds. It seems that those idiots at github finally noticed that we're overriding their idiotic https redirect and added a referrer-check. I've updated thirdpartymirrors to use the regular https:// URI. Thanks for the report. By the way, does someone want to try to argue with them to provide http:// downloads? But expect being offended by their professional support.
(In reply to comment #3) > And the mirror://github is just for uploaded files, not the live tarballs > which should be used directly. Sorry. I didn't know that. With live tarballs you mean the tarballs provided for each tag? I simply wanted to use the official / general way of downloading source tarballs from github. My thoughts were, that when using mirror://github and there is a change to the URL pattern, just the mirror entry has to be adjusted and not every ebuild downloading source tarballs from github.
(In reply to comment #6) > (In reply to comment #3) > > And the mirror://github is just for uploaded files, not the live tarballs > > which should be used directly. > > Sorry. I didn't know that. With live tarballs you mean the tarballs provided > for each tag? Yes, those auto-generated tarballs. We can't catch them from mirrors since they are generated on request. > I simply wanted to use the official / general way of downloading source > tarballs from github. > My thoughts were, that when using mirror://github and there is a change to > the URL pattern, just the mirror entry has to be adjusted and not every > ebuild downloading source tarballs from github. Well, mirror://github now works fine but it's not really useful anymore. Since github does not accept tarball uploads anymore, it will fade out with package updates.
