git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Martin Langhoff <martin.langhoff@gmail.com>
To: Git Mailing List <git@vger.kernel.org>
Subject: Strangely hosed git install
Date: Thu, 28 May 2009 09:08:58 +0200	[thread overview]
Message-ID: <46a038f90905280008h5510d03aj5f6e5728ca075027@mail.gmail.com> (raw)

My main laptop (and part-time dev box) has a partially hosed git
installation. This is an ubuntu intrepid machine where I have been
building git from src for a while. Perhaps there's a way to diagnose
this before I take more drastic measures :-)

So far gc, repack and stash show errors. No dataloss AFAICS (though
the git stash errors scared me initially).

gc and repack error out thus:

$ git gc
usage: git-pack-objects [{ -q | --progress | --all-progress }]
        [--max-pack-size=N] [--local] [--incremental]
        [--window=N] [--window-memory=N] [--depth=N]
        [--no-reuse-delta] [--no-reuse-object] [--delta-base-offset]
        [--threads=N] [--non-empty] [--revs [--unpacked | --all]*] [--reflog]
        [--stdout | base-name] [--keep-unreachable] [<ref-list | <object-list]
error: failed to run repack
$ echo $?
255

And stash...

$ git stash
usage: git-diff-index [-m] [--cached] [<common diff options>]
<tree-ish> [<path>...]
common diff options:
(...)

usage: git-diff-index [-m] [--cached] [<common diff options>]
<tree-ish> [<path>...]
common diff options:
(...)
Saved working directory and index state "WIP on master: 1eac877... WIP
olpc-update-query: if the lease is due soon avoid
randomly_do_nothing()"
HEAD is now at 1eac877... WIP olpc-update-query: if the lease is due
soon avoid randomly_do_nothing()
(To restore them type "git stash apply")
$ echo $?
0
$ git stash show
 olpc-update-query |    5 +++++
 1 files changed, 5 insertions(+), 0 deletions(-)
$ git stash apply # does the right thing

Some background diagnostics info

 - $ git --version
   git version 1.6.3.1.26.gf5b223

 - $ which git
   /home/martin/bin/git
  # there is no other git install anywhere on the box

 - the git-core package was once installed temporarily (to try out a
package that depends on git-core)

 - some oldstyle "dashed" commands trigger a helper bash extension, thus
   $ git-diff
   The program 'git-diff' is currently not installed.  You can install
it by typing:
   sudo apt-get install git-core
   bash: git-diff: command not found


I can't figure out what is wrong with the install. I have bisected a
few bugs in the past, but that had never left any traces behind.

It's not a serious problem -- I just wonder whether it'd affect other
people developing / tracking git.

cheers,



m
--
 martin.langhoff@gmail.com
 martin@laptop.org -- School Server Architect
 - ask interesting questions
 - don't get distracted with shiny stuff  - working code first
 - http://wiki.laptop.org/go/User:Martinlanghoff

             reply	other threads:[~2009-05-28  7:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-28  7:08 Martin Langhoff [this message]
2009-05-28  7:18 ` Strangely hosed git install Junio C Hamano
2009-05-28  7:22   ` Martin Langhoff
2009-05-28  8:29     ` Michael J Gruber
2009-05-28  9:34       ` Martin Langhoff
2009-05-28  9:39         ` Martin Langhoff
2009-05-28  9:47         ` Michael J Gruber
2009-05-28 10:11           ` Martin Langhoff

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=46a038f90905280008h5510d03aj5f6e5728ca075027@mail.gmail.com \
    --to=martin.langhoff@gmail.com \
    --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 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).