Git failed

Git failed

[Julien Danjou]

[-- Attachment #1: Type: text/plain, Size: 308 bytes --]

Hi,

Am I the only one unable to clone the Git repo:

% git clone https://git.gnus.org/gnus.git
Cloning into 'gnus'...
error: RPC failed; result=56, HTTP code = 0
fatal: The remote end hung up unexpectedly

?

-- 
Julien Danjou
;; Free Software hacker & freelance
;; http://julien.danjou.info

[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]

Re: Git failed

[Adam Sjøgren]

On Thu, 18 Oct 2012 08:27:14 +0200, Julien wrote:

> Am I the only one unable to clone the Git repo:

> % git clone https://git.gnus.org/gnus.git
> Cloning into 'gnus'...
> error: RPC failed; result=56, HTTP code = 0
> fatal: The remote end hung up unexpectedly

> ?

I get the same error over https.

But it works on http:

    $ git clone http://git.gnus.org/gnus.git
    Initialized empty Git repository in /tmp/gnus/.git/
    remote: Counting objects: 80105, done.
    remote: Compressing objects: 100% (18408/18408), done.
    remote: Total 80105 (delta 65943), reused 74605 (delta 61551)
    Receiving objects: 100% (80105/80105), 18.97 MiB | 2.97 MiB/s, done.
    Resolving deltas: 100% (65943/65943), done.
    $ 


  Best regards,

    Adam

-- 
 "A cat has nine lives, but a bullfrog croaks                 Adam Sjøgren
  every day."                                            asjo@koldfront.dk

Re: Git failed

[Julien Danjou]

[-- Attachment #1: Type: text/plain, Size: 331 bytes --]

On Thu, Oct 18 2012, Adam Sjøgren wrote:

> I get the same error over https.

What OS are you running on?
I'm on Debian sid, and I wonder if that cames from the client rather
than the server, since Tassilo do not have any problem.

-- 
Julien Danjou
/* Free Software hacker & freelance
   http://julien.danjou.info */

[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]

Re: Git failed

[Adam Sjøgren]

On Thu, 18 Oct 2012 15:37:50 +0200, Julien wrote:

> What OS are you running on?
> I'm on Debian sid, and I wonder if that cames from the client rather
> than the server, since Tassilo do not have any problem.

I am on Debian unstable as well. Let me try on a Debian stable machine...

    $ GIT_SSL_NO_VERIFY=1 git clone https://git.gnus.org/gnus.git
    Cloning into gnus...
    remote: Counting objects: 80105, done.
    remote: Compressing objects: 100% (18408/18408), done.
    remote: Total 80105 (delta 65943), reused 74605 (delta 61551)
    Receiving objects: 100% (80105/80105), 18.95 MiB | 1.38 MiB/s, done.
    Resolving deltas: 100% (65943/65943), done.
    $  wajig status git-core
    Package                 Installed       Previous        Now             State
    =======================-===============-===============-===============-=====
    git-core                1:1.7.2.5-3     1:1.7.2.5-3     1:1.7.2.5-3     install
    $ 

So it works on Debian stable but not on unstable.

Hm.


  Best regards,

    Adam

-- 
 "A cat has nine lives, but a bullfrog croaks                 Adam Sjøgren
  every day."                                            asjo@koldfront.dk

Re: Git failed

[Tassilo Horn]

asjo@koldfront.dk (Adam Sjøgren) writes:

>     $ GIT_SSL_NO_VERIFY=1 git clone https://git.gnus.org/gnus.git

By the way, I just noticed that you don't have to disable ssl
verification anymore.  At least, I don't.

Bye,
Tassilo

Re: Git failed

[Tassilo Horn]

Julien Danjou <julien@danjou.info> writes:

> Am I the only one unable to clone the Git repo:
>
> % git clone https://git.gnus.org/gnus.git
> Cloning into 'gnus'...
> error: RPC failed; result=56, HTTP code = 0
> fatal: The remote end hung up unexpectedly

For me both http and https work fine.

Bye,
Tassilo

Re: Git failed

[Sven Joachim]

On 2012-10-18 09:08 +0200, Tassilo Horn wrote:

> Julien Danjou <julien@danjou.info> writes:
>
>> Am I the only one unable to clone the Git repo:
>>
>> % git clone https://git.gnus.org/gnus.git
>> Cloning into 'gnus'...
>> error: RPC failed; result=56, HTTP code = 0
>> fatal: The remote end hung up unexpectedly
>
> For me both http and https work fine.

Looks like the https problem was introduced in curl 7.28.0:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=690551.

Cheers,
       Sven