Re: [lmi] [lmi-commits] master 5724e39 5/5: Suggest a workaround for a puzzling git error

[Vadim Zeitlin]

On Mon, 26 Oct 2020 16:27:19 -0400 (EDT) Greg Chicares 
<gchicares@sbcglobal.net> wrote:

GC> branch: master
GC> commit 5724e39170b056170e556a26cdaa0b089d137674
GC> Author: Gregory W. Chicares <gchicares@sbcglobal.net>
GC> Commit: Gregory W. Chicares <gchicares@sbcglobal.net>
GC> 
GC>     Suggest a workaround for a puzzling git error
GC>     
GC>     The proprietary product repository in an up-to-date chroot reported:
GC>       $cd /opt/lmi/proprietary
GC>       $git rev-parse --short HEAD
GC>       e5094a5a
GC>     whereas b1243539 was the HEAD of the same repository in an out-of-date
GC>     chroot. A catchup bundle was created ["/path/to" replaces the original
GC>     pathspec, which was too long to fit on a single line]:
GC>       $git bundle create /path/to/catchup.bundle master b1243539
GC>     and moved to the out-of-date chroot, where it looked okay:
GC>       $git bundle verify /path/to/catchup.bundle
GC>       The bundle contains this ref:
GC>       e5094a5a820181422d52243cf8a6d40dc799d142 refs/heads/master
GC>       The bundle records a complete history.
GC>       /path/to/catchup.bundle is okay
GC>     but this customary command failed:
GC>       $git pull /path/to/catchup.bundle
GC>       fatal: Couldn't find remote ref HEAD
GC>     whereas this succeeded:
GC>       $git pull /path/to/catchup.bundle master

 I think this is a good solution (rather than just a workaround) in any
case, but I wonder if you have already tested any of the alternative
workarounds from my reply to your original message about this problem at

        https://lists.gnu.org/archive/html/lmi/2019-08/msg00001.html

and found them lacking or is there some other reason this error remains
puzzling?

 Regards,
VZ

pgpiRSJ7KMHFZ.pgp
Description: PGP signature