From: Junio C Hamano <gitster@pobox.com>
To: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
Cc: git@vger.kernel.org
Subject: Re: "error: non-monotonic index" during fresh linux-2.6.git cloning.
Date: Sat, 19 Jul 2008 11:15:16 -0700 [thread overview]
Message-ID: <7v8wvx211n.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <7vfxq521ab.fsf@gitster.siamese.dyndns.org> (Junio C. Hamano's message of "Sat, 19 Jul 2008 11:10:04 -0700")
Junio C Hamano <gitster@pobox.com> writes:
> Evgeniy Polyakov <johnpol@2ka.mipt.ru> writes:
>
>> $ git clone http://kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
>> Getting alternates list for http://kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git/
>> Getting pack list for http://kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git/
>> Getting index for pack 81cec7c6b26c755e466a79de8dbe1c7b827a48d6
>> error: non-monotonic index
>> /usr/bin/git-clone: line 33: 2025 Segmentation fault git-http-fetch -v -a -w "$tname" "$name" "$1/"
>>
>> $ git --version
>> git version 1.4.4.4
>>
>> Fresh 32bit Debian testing.
>
> The repository you are cloning uses pack idx version #2; 1.4.4.4 predates it
> by a wide margin.
By the way, Debian folks are very aware of the issue and already has a
backported material to cut a 1.4.4.5, but I do not know what the release
schedule for their update is.
Is it an option for you to update to a more modern version from say
backports.org? Everybody using git for anything serious should be using
1.5.3 or newer these days.
next prev parent reply other threads:[~2008-07-19 18:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-19 17:47 "error: non-monotonic index" during fresh linux-2.6.git cloning Evgeniy Polyakov
2008-07-19 18:10 ` Junio C Hamano
2008-07-19 18:15 ` Junio C Hamano [this message]
2008-07-19 19:59 ` Evgeniy Polyakov
2008-07-19 22:00 ` Junio C Hamano
2008-07-20 6:41 ` Evgeniy Polyakov
2008-07-20 6:52 ` Junio C Hamano
2008-07-20 7:21 ` Evgeniy Polyakov
2008-07-19 18:20 ` Petr Baudis
2008-07-19 20:06 ` Evgeniy Polyakov
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=7v8wvx211n.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=johnpol@2ka.mipt.ru \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).