git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: inted problems when upgrading to 1.6.0.4

From
Johannes Sixt <j.sixt@viscovery.net>
Date
Nov 25, 2008, 10:14 UTC
Message-ID
<492BD01C.8070807@viscovery.net>
In-Reply-To
<492BC56A.6040506@xmos.com>
Luis Gutierrez schrieb:
Show 9 quoted lines
> At my company we have been using git for the past months, and except for
> a few people, everyone is happy with it. Last week, we discovered that
> the mac version of git was misbehaving (v1.5.6.4), but upgrading the
> client to the latest one (v1.6.0.4) fixed the issue. Fearing consistency
> issue between version, I decided to update the version of the central
> repository (ie, the place were people can go and synchronize their code)
> on a RHEL4 box from 1.5.6.4 to 1.6.0.4.
> went to my git directory, pulled, checkout v1.6.0.4, and compiled with
> 'make --prefix=/usr/loca/ all' and installed with the same comamnd.

It's not necessarily the cause of your problems, but didn't make install warn you:

        !! You have installed git-* commands to new gitexecdir.
        !! Old version git-* commands still remain in bindir.
        !! Mixing two versions of Git will lead to problems.
        !! Please remove old version commands in bindir now.
Did you do as you were told?
-- Hannes
Previous: Luis GutierrezNext: Arafangion
Message 2 of 8 in “inted problems when upgrading to 1.6.0.4”
  1. Luis GutierrezNov 25, 2008
  2. Johannes SixtNov 25, 2008
  3. ArafangionNov 25, 2008
  4. Brian FosterNov 25, 2008
  5. Johannes SixtNov 25, 2008
  6. ArafangionNov 25, 2008
  7. Luis GutierrezNov 25, 2008
  8. ArafangionNov 25, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.