threads / discuss / 24230

Confusing error message from "git pull" when upstream repo no longer exists

Subject: Confusing error message from "git pull" when upstream repo no longer exists

## tl;dr

3 messages between Jun 29, 2010 and Jun 29, 2010.

replies: 2people: 2as markdown or json

Per Cederqvist· Jun 29, 2010, 10:33 UTC · lore

When running "git pull", I get this error message:

     fatal: /usr/local/libexec/git-core/git-pull cannot be used without a  
working tree.

"git fetch" gives me a much clearer error message:

     fatal: '/var/git/project.git' does not appear to be a git repository
     fatal: The remote end hung up unexpectedly

/var/git/project.git does no longer exist on the origin server, so I understand why the commands fail. I think "git pull" should have a less confusing error message, though.

     /ceder

-- 
Per Cederqvist, cederp@opera.com

Santi Béjar· Jun 29, 2010, 10:55 UTC · re: Per Cederqvist · lore

Re: Confusing error message from "git pull" when upstream repo no longer exists

On Tue, Jun 29, 2010 at 12:33 PM, Per Cederqvist <cederp@opera.com> wrote:

> When running "git pull", I get this error message:
>
>    fatal: /usr/local/libexec/git-core/git-pull cannot be used without a
> working tree.

This error message is shown when you try to pull in a bare repository (without a working tree). It seems you don't have a working tree, but you have a repository, so you can still fetch. (the working tree check is done before the fetch).

HTH, Santi

Per Cederqvist· Jun 29, 2010, 11:14 UTC · re: Santi Béjar · lore

Re: Confusing error message from "git pull" when upstream repo no longer exists

On Tue, 29 Jun 2010 12:55:29 +0200, Santi Béjar <santi@agolina.net> wrote:

Show 14 quoted lines

> On Tue, Jun 29, 2010 at 12:33 PM, Per Cederqvist <cederp@opera.com>  
> wrote:
>> When running "git pull", I get this error message:
>>
>>    fatal: /usr/local/libexec/git-core/git-pull cannot be used without a
>> working tree.
>
> This error message is shown when you try to pull in a bare repository
> (without a working tree). It seems you don't have a working tree, but
> you have a repository, so you can still fetch. (the working tree check
> is done before the fetch).
>
> HTH,
> Santi

Oh. You are correct. I was in a bare repository, so I guess the message is good after all. Sorry for my mistaken report.

     /ceder

-- 
Per Cederqvist, cederp@opera.com