On 11/25/2013 01:32 PM, michael_e_br...@dell.com wrote:
> Several repositories have broken git pulls over http on git.yoctoproject.org.
>
> Working:
>
> $ git clone --mirror http://git.yoctoproject.org/git/yocto-kernel-tools
> Initialized empty Git repository in 
> /home/michael_e_brown/f10/sources/f/yocto-kernel-tools.git/
> remote: Counting objects: 1067, done.
> remote: Compressing objects: 100% (462/462), done.
> remote: Total 1067 (delta 711), reused 958 (delta 603)
> Receiving objects: 100% (1067/1067), 273.41 KiB | 251 KiB/s, done.
> Resolving deltas: 100% (711/711), done.
>
>
> Broken:
>
> $ git clone --mirror http://git.yoctoproject.org/git/linux-yocto-3.10
> Initialized empty Git repository in 
> /home/michael_e_brown/f10/sources/f/linux-yocto-3.10.git/
> error: RPC failed; result=52, HTTP code = 100
Failing with an HTTP continue code is sort of odd. I wonder if you are
going through a proxy which could be causing this issue only for larger
repos like the kernels. I think the content length header might be wrong
or undefined for large objects at the moment which could give certain
proxy software trouble. I've tried to correct those headers. Can you
test again?

I tested with git version 1.7.9.5 and no proxy and was able to clone all
the kernels.

Michael Halstead
Yocto Project / System Administrator


> All of the kernel pulls appear to be broken in the same way (3.10, 3.8, etc)
>
> URLs taken directly from the cgit HTTP url listed.
> --
> Michael
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>


Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Reply via email to