All of lore.kernel.org
 help / color / mirror / Atom feed
From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: Ajay <ajay.dadgas@galaxyweblinks.in>
Cc: git@vger.kernel.org
Subject: Re: bug reporting
Date: Fri, 26 Sep 2014 23:51:58 +0000	[thread overview]
Message-ID: <20140926235158.GC6553@vauxhall.crustytoothpaste.net> (raw)
In-Reply-To: <54256D0F.4000003@galaxyweblinks.in>

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

On Fri, Sep 26, 2014 at 07:11:35PM +0530, Ajay wrote:
> Hello,
> 
>          I have faced a git bug. When I try to clone a git repo it shows an
> error "protocol error: bad pack header".
> 
>          This is the full error message which I got while cloning git
> project :
> 
> Clone: protocol error: bad pack header
>     $ git clone -v --progress
> http://dev.galaxylipl.com:88/galaxygit/privatenovator.git
> /home/lipl/privateschoolinnovator
>     Cloning into '/home/lipl/privatenovator'...
>     POST git-upload-pack (190 bytes)
>     remote: error: Could not read e9a6c4c684a5e8758026e8b0e25867c03332fe7c
>     remote: fatal: bad tree object e9a6c4c684a5e8758026e8b0e25867c03332fe7c
>     remote: aborting due to possible repository corruption on the remote
> side.
>     protocol error: bad pack header

This indicates some sort of corruption between the client and server.  I
notice you're cloning over HTTP.  Are you using a proxy?  Can you try
using a git, ssh, or https (without MITM) URL?  Sometimes broken proxies
can end up corrupting data.

Also, what version of git are you using on the client and the server?
-- 
brian m. carlson / brian with sandals: Houston, Texas, US
+1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only
OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187

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

  reply	other threads:[~2014-09-26 23:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-26 13:41 bug reporting Ajay
2014-09-26 23:51 ` brian m. carlson [this message]
     [not found] <1621111620246345@mail.yandex.ru>
2021-05-05 22:37 ` Bug reporting Alejandro Colomar (man-pages)
     [not found]   ` <1492841620310804@mail.yandex.ru>
2021-05-09 16:40     ` Michael Kerrisk (man-pages)
2021-05-09 17:20       ` Alexander Monakov
2021-05-09 17:58         ` Michael Kerrisk (man-pages)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140926235158.GC6553@vauxhall.crustytoothpaste.net \
    --to=sandals@crustytoothpaste.net \
    --cc=ajay.dadgas@galaxyweblinks.in \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.