From: "Jon Smirl" <jonsmirl@gmail.com>
To: "Nicolas Pitre" <nico@cam.org>
Cc: "Git Mailing List" <git@vger.kernel.org>
Subject: Re: non-monotonic index error
Date: Tue, 2 Sep 2008 19:48:47 -0400 [thread overview]
Message-ID: <9e4733910809021648y5b0db178vc953fb81144881b0@mail.gmail.com> (raw)
In-Reply-To: <alpine.LFD.1.10.0809021859030.23787@xanadu.home>
On 9/2/08, Nicolas Pitre <nico@cam.org> wrote:
> On Tue, 2 Sep 2008, Jon Smirl wrote:
>
> > On 9/2/08, Nicolas Pitre <nico@cam.org> wrote:
> > > On Tue, 2 Sep 2008, Jon Smirl wrote:
> > >
> > > > I pulled from linus, did stg rebase linus/master, git push digispeaker
> > > > and got these errors.
> > > >
> > > > Where's the problem, at my local machine or the digispeaker one? How
> > > > do I fix this?
> > > >
> > > > jonsmirl@terra:~/fs$ stg --version
> > > > Stacked GIT 0.14.3.195.g36a0
> > > > git version 1.5.6.GIT
> > > > Python version 2.5.2 (r252:60911, Jul 31 2008, 17:31:22)
> > > > [GCC 4.2.3 (Ubuntu 4.2.3-2ubuntu7)]
> > > > jonsmirl@terra:~/fs$
> > > >
> > > > [digispeaker]$ git --version
> > > > git version 1.4.4.4
> > >
> > >
> > > This should be upgraded to at least version 1.4.4.5. If this is a
> > > Debian distro and they didn't provide an updated package for git then
> > > please fill a bug with Debian.
> > >
> >
> > I just built the current version in my local directory, I'm still
> > getting the monotonic error on push. Do I need to repack or something?
>
>
> Probably because the version in your local directory is not the one used
> when the push is performed. Still, on pushes it is the native git
> protocol which is used and in that case there should not be any index
> version issues.
>
> Puzzled.
Whack tree at server.
Clone from linus.
Push to the tree again.
Problem is gone.
--------------------------------------
This may be a clue...
[digispeaker]$ git repack
error: non-monotonic index
error: non-monotonic index
error: non-monotonic index
error: non-monotonic index
error: non-monotonic index
error: non-monotonic index
error: non-monotonic index
error: non-monotonic index
error: non-monotonic index
error: non-monotonic index
error: non-monotonic index
error: non-monotonic index
error: non-monotonic index
error: non-monotonic index
error: non-monotonic index
error: non-monotonic index
error: non-monotonic index
error: non-monotonic index
error: non-monotonic index
error: non-monotonic index
error: non-monotonic index
error: non-monotonic index
error: non-monotonic index
error: non-monotonic index
Generating pack...
error: non-monotonic index
error: non-monotonic index
error: non-monotonic index
error: non-monotonic index
error: non-monotonic index
error: non-monotonic index
error: non-monotonic index
error: non-monotonic index
error: non-monotonic index
error: non-monotonic index
error: non-monotonic index
error: non-monotonic index
error: non-monotonic index
error: non-monotonic index
error: non-monotonic index
error: non-monotonic index
error: non-monotonic index
error: non-monotonic index
error: non-monotonic index
error: non-monotonic index
error: non-monotonic index
error: non-monotonic index
error: non-monotonic index
error: non-monotonic index
fatal: bad object bce7f793daec3e65ec5c5705d2457b81fe7b5725
[digispeaker]$ git show bce7f793daec3e65ec5c5705d2457b81fe7b5725
error: non-monotonic index
error: non-monotonic index
error: non-monotonic index
error: non-monotonic index
error: non-monotonic index
error: non-monotonic index
error: non-monotonic index
error: non-monotonic index
error: non-monotonic index
error: non-monotonic index
error: non-monotonic index
error: non-monotonic index
error: non-monotonic index
error: non-monotonic index
error: non-monotonic index
error: non-monotonic index
error: non-monotonic index
error: non-monotonic index
error: non-monotonic index
error: non-monotonic index
error: non-monotonic index
error: non-monotonic index
error: non-monotonic index
error: non-monotonic index
error: non-monotonic index
error: non-monotonic index
error: non-monotonic index
error: non-monotonic index
error: non-monotonic index
error: non-monotonic index
error: non-monotonic index
error: non-monotonic index
error: non-monotonic index
error: non-monotonic index
error: non-monotonic index
error: non-monotonic index
error: non-monotonic index
error: non-monotonic index
error: non-monotonic index
error: non-monotonic index
error: non-monotonic index
error: non-monotonic index
error: non-monotonic index
error: non-monotonic index
error: non-monotonic index
error: non-monotonic index
error: non-monotonic index
error: non-monotonic index
fatal: bad object bce7f793daec3e65ec5c5705d2457b81fe7b5725
[digispeaker]$
That's a valid object so it should have been ok. I think my tree got
corrupted somehow.
--
Jon Smirl
jonsmirl@gmail.com
next prev parent reply other threads:[~2008-09-02 23:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-02 19:57 non-monotonic index error Jon Smirl
2008-09-02 20:28 ` Nicolas Pitre
2008-09-02 21:37 ` Jon Smirl
2008-09-02 23:04 ` Nicolas Pitre
2008-09-02 23:48 ` Jon Smirl [this message]
2008-09-02 20:53 ` Junio C Hamano
2008-09-02 21:01 ` Jon Smirl
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=9e4733910809021648y5b0db178vc953fb81144881b0@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=git@vger.kernel.org \
--cc=nico@cam.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 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).