# error: could not read '.git/rebase-apply/head-name': No such file or directory

2 messages from 2019-09-12 to 2019-09-12. Participants: Eugen Konkov, Johannes Schindelin.
Thread: https://gitlist.dev/t/51832

## Eugen Konkov, 2019-09-12 07:12

Subject: error: could not read '.git/rebase-apply/head-name': No such file or directory
Message-ID: <386490889.20190912101245@yandex.ru>
URL: https://gitlist.dev/e/386490889.20190912101245%40yandex.ru

```
Hello Git,

Next commands cause the error:

$ git pull
fatal: It seems that there is already a rebase-apply directory, and
I wonder if you are in the middle of another rebase.  If that is the
case, please try
        git rebase (--continue | --abort | --skip)
If that is not the case, please
        rm -fr ".git/rebase-apply"
and run me again.  I am stopping in case you still have something
valuable there.

$ git rebase --abort 
error: could not read '.git/rebase-apply/head-name': No such file or directory

$ git --version
git version 2.20.1

$ rm -fr ".git/rebase-apply"

$ git rebase --abort 
error: could not read '.git/rebase-apply/head-name': No such file or directory

$ git pull
fatal: It seems that there is already a rebase-apply directory, and
I wonder if you are in the middle of another rebase.  If that is the
case, please try
        git rebase (--continue | --abort | --skip)
If that is not the case, please
        rm -fr ".git/rebase-apply"
and run me again.  I am stopping in case you still have something
valuable there.


I resolved this issue by
git checkout -f some_br

But this issues should not occur


-- 
Best regards,
Eugen Konkov


```

## Johannes Schindelin, 2019-09-12 11:26

Subject: Re: error: could not read '.git/rebase-apply/head-name': No such file or directory
Message-ID: <nycvar.QRO.7.76.6.1909121326310.47@tvgsbejvaqbjf.bet>
URL: https://gitlist.dev/e/nycvar.QRO.7.76.6.1909121326310.47%40tvgsbejvaqbjf.bet
In-Reply-To: <386490889.20190912101245@yandex.ru>

```
Hi Eugen,

On Thu, 12 Sep 2019, Eugen Konkov wrote:

> $ git --version
> git version 2.20.1

First thing to try is whether Git v2.23.0 still exposes that bug.

Ciao,
Johannes

```