On Mon, May 7, 2012 at 4:28 AM, Clark WANG <[email protected]> wrote: > On Sat, May 5, 2012 at 5:46 AM, Glenn Fowler <[email protected]> wrote: >> >> >> the AT&T Software Technology ast beta 2012-05-04 source release >> has been posted to the download site >> http://www.research.att.com/sw/download/beta/ >> >> the git source repository has also been updated >> http://www.research.att.com/sw/gitweb/ > > > I still have probelm cloning the repo (with HTTP proxy): > > $ git clone > http://I.accept.www.opensource.org.licenses.eclipse:[email protected]/sw/git/ast-open > Cloning into ast-open... > error: RPC failed; result=22, HTTP code = 405 > fatal: The remote end hung up unexpectedly > $ > > And `git pull' in a previously cloned repo also fails now: > > $ git pull > error: RPC failed; result=22, HTTP code = 405 > fatal: The remote end hung up unexpectedly > $ > > Note that I can clone other git repo through the HTTP proxy. E.g.: > > $ git clone http://git.savannah.gnu.org/r/screen.git > Cloning into screen... > remote: Counting objects: 3900, done. > remote: Compressing objects: 100% (930/930), done. > remote: Total 3900 (delta 2990), reused 3848 (delta 2954) > Receiving objects: 100% (3900/3900), 2.36 MiB | 499 KiB/s, done. > Resolving deltas: 100% (2990/2990), done. > $ >> >> >> the recent git web problems should be fixed
Try wget --http-user="I accept www.opensource.org/licenses/eclipse" --http-passwd="." 'http://www.research.att.com/sw/download/beta/INIT.2012-05-04.tgz' and wget --http-user="I accept www.opensource.org/licenses/eclipse" --http-passwd="." 'http://www.research.att.com/sw/download/beta/ast-open.2012-05-04.tgz' git is a b*tch when it comes to http proxies. The only good way to avoid it is to use either git's native protocol or try to use https. Irek _______________________________________________ ast-users mailing list [email protected] https://mailman.research.att.com/mailman/listinfo/ast-users
