fetch failure from git2.kernel.org?

is this known?  transient?

    $ git-fetch
    warning: no common commits
    remote: Generating pack...
    remote: Done counting 0 objects.
    remote: aborting due to possible repository corruption on the remote side.
    fatal: protocol error: bad pack header
    fatal: Fetch failure: git://git2.kernel.org/pub/scm/git/git.git
    $

-- 
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
[off-list ref] <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!

Randal L. Schwartz, Sun, Apr 22, 2007 12:03:45 +0200:

is this known?  transient?

    $ git-fetch
    warning: no common commits
    remote: Generating pack...
    remote: Done counting 0 objects.
    remote: aborting due to possible repository corruption on the remote side.
    fatal: protocol error: bad pack header
    fatal: Fetch failure: git://git2.kernel.org/pub/scm/git/git.git
    $

Confirm this. BTW, git1 and git2 point to the same 140.211.167.38
(poseidon.kernel.org). It used to be different addresses

On Sun, Apr 22, 2007 at 02:53:07PM CEST, Alex Riesen wrote:

Randal L. Schwartz, Sun, Apr 22, 2007 12:03:45 +0200:

quoted

is this known?  transient?

    $ git-fetch
    warning: no common commits

This in itself is weird. :-)

quoted

    remote: Generating pack...
    remote: Done counting 0 objects.
    remote: aborting due to possible repository corruption on the remote side.
    fatal: protocol error: bad pack header
    fatal: Fetch failure: git://git2.kernel.org/pub/scm/git/git.git
    $

Confirm this. BTW, git1 and git2 point to the same 140.211.167.38
(poseidon.kernel.org). It used to be different addresses

Curiously enough, I have hit no problems with fetching from the
repo.or.cz mirror (which is using several months old git version, if
that might matter).

-- 
				Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
Ever try. Ever fail. No matter. // Try again. Fail again. Fail better.
		-- Samuel Beckett

On Sun, 22 Apr 2007, Randal L. Schwartz wrote:

is this known?  transient?

Junio seems to have tightened his permissions on kernel.org, and as a 
result the most recent pack is unreadable by anybody but him (I'm not sure 
if such private files even get mirrored out - but even if they do, they 
will get mirrored out with the same tight permissions and won't be 
readable).

		Linus