Re: 2.37.2 can't "git pull" but 2.18.0 can

From: Jeff King <peff@peff.net>
Date: Sep 3, 2022, 01:07 UTC
Message-ID: <YxKo2l5nBoOa9Jfa@coredump.intra.peff.net>
In-Reply-To: <CA+4x=b_07g6STT0nvma_gRhv=zdj+7TQx5SxKLUtuqONLwv=TQ@mail.gmail.com>

On Fri, Sep 02, 2022 at 03:27:55PM -0400, Lana Deere wrote:

Show 17 quoted lines

> I'm testing an upgrade to git 2.37.2 from the current version we're
> using of 2.18.0.  When I try to pull in my development tree, 2.37.2
> gives me an error but 2.18.0 things all is fine:
> 
> $ /tools/linux-x86_64/git/2.37.2/bin/git pull
> Your configuration specifies to merge with the ref
> 'refs/heads/feature/switch-to-qt5'
> from the remote, but no such ref was fetched.
> 
> $ /tools/linux-x86_64/git/2.18.0/bin/git pull
> From http://githost:7990/scm/dp/sw
>  * branch                  feature/switch-to-qt5 -> FETCH_HEAD
> Already up to date.
> 
> Anyone have any ideas about this?  All I could find on google was a
> suggestion that the "no such ref" message indicates the remote branch
> was deleted, but that's not the case here.

It's curious that the older version shows us fetching into FETCH_HEAD, but the new one doesn't. I wonder if you have some unusual refspecs. Or perhaps a branch.*.remote config option which fetches from a different remote. The "git config" output brian asked for may be instructive there.

If it's possible for you to build Git from source, it may also be interesting to bisect to find the commit that caused the change.

-Peff