! [remote rejected] master -> master (unpacker error)

! [remote rejected] master -> master (unpacker error)

[lyle.ziegelmiller]

Hi

Any updates on this error I emailed a while back?

lylez@LJZ-DELLPC ~/python
$ git push
Enumerating objects: 5, done.
Counting objects: 100% (5/5), done.
Delta compression using up to 4 threads
Compressing objects: 100% (2/2), done.
Writing objects: 100% (3/3), 279 bytes | 23.00 KiB/s, done.
Total 3 (delta 1), reused 0 (delta 0)
remote: fatal: not a git repository: '.'
error: remote unpack failed: unpack-objects abnormal exit
To
//lylez-laptop/Users/Administrator/bare-repositories/python-bare-repository.
git
 ! [remote rejected] master -> master (unpacker error)
error: failed to push some refs to
'//lylez-laptop/Users/Administrator/bare-repositories/python-bare-repository
.git'

lylez@LJZ-DELLPC ~/python

Regards

Lyle Ziegelmiller

Re: ! [remote rejected] master -> master (unpacker error)

[brian m. carlson]

[-- Attachment #1: Type: text/plain, Size: 919 bytes --]

On 2020-02-16 at 16:10:12, lyle.ziegelmiller@gmail.com wrote:
> Hi
> 
> Any updates on this error I emailed a while back?
> 
> lylez@LJZ-DELLPC ~/python
> $ git push
> Enumerating objects: 5, done.
> Counting objects: 100% (5/5), done.
> Delta compression using up to 4 threads
> Compressing objects: 100% (2/2), done.
> Writing objects: 100% (3/3), 279 bytes | 23.00 KiB/s, done.
> Total 3 (delta 1), reused 0 (delta 0)
> remote: fatal: not a git repository: '.'

This error is telling you that Git doesn't think the remote location is
a Git repository.  It could be because it really isn't one, or it could
be that the permissions are wrong.

It could also be that the repository is mostly there but very slightly
corrupt and therefore can't be detected as one.  For example, it could
be missing its HEAD reference.
-- 
brian m. carlson: Houston, Texas, US
OpenPGP: https://keybase.io/bk2204

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 868 bytes --]

RE: ! [remote rejected] master -> master (unpacker error)

[lyle.ziegelmiller]

I wrote a bunch of emails about this in December 2019. Did they all get lost?

I'm consistently able to clone the repository, but I can never push to it. I used to be able to. I've explored all possibilities that I know of.

I'm using Windows 10, and the Cygwin version of Git.

$ git --version
git version 2.21.0

Regards

Lyle

-----Original Message-----
From: brian m. carlson <sandals@crustytoothpaste.net> 
Sent: Sunday, February 16, 2020 2:16 PM
To: lyle.ziegelmiller@gmail.com
Cc: git@vger.kernel.org
Subject: Re: ! [remote rejected] master -> master (unpacker error)

On 2020-02-16 at 16:10:12, lyle.ziegelmiller@gmail.com wrote:
> Hi
> 
> Any updates on this error I emailed a while back?
> 
> lylez@LJZ-DELLPC ~/python
> $ git push
> Enumerating objects: 5, done.
> Counting objects: 100% (5/5), done.
> Delta compression using up to 4 threads Compressing objects: 100% 
> (2/2), done.
> Writing objects: 100% (3/3), 279 bytes | 23.00 KiB/s, done.
> Total 3 (delta 1), reused 0 (delta 0)
> remote: fatal: not a git repository: '.'

This error is telling you that Git doesn't think the remote location is a Git repository.  It could be because it really isn't one, or it could be that the permissions are wrong.

It could also be that the repository is mostly there but very slightly corrupt and therefore can't be detected as one.  For example, it could be missing its HEAD reference.
--
brian m. carlson: Houston, Texas, US
OpenPGP: https://keybase.io/bk2204

Re: ! [remote rejected] master -> master (unpacker error)

[brian m. carlson]

[-- Attachment #1: Type: text/plain, Size: 1110 bytes --]

On 2020-02-17 at 16:25:38, lyle.ziegelmiller@gmail.com wrote:
> I wrote a bunch of emails about this in December 2019. Did they all get lost?

No, I don't believe so.  However, sometimes people get busy and things
fall through the cracks, so pinging like you did is a good idea.

> I'm consistently able to clone the repository, but I can never push to it. I used to be able to. I've explored all possibilities that I know of.
> 
> I'm using Windows 10, and the Cygwin version of Git.
> 
> $ git --version
> git version 2.21.0

It looks like you're pushing to a UNC path, and I don't know how that
works with Cygwin.  It may be that it used to work, but something
changed in Cygwin or Git.

I've CC'd the Git for Windows maintainer (Dscho) in case he has some
ideas.  While he doesn't package the Cygwin Git, he might know what's
going on.  I'm not very familiar with Cygwin at all, not being a Windows
user.  You could also try reporting this to the Cygwin bug tracker and
see if they can figure things out.
-- 
brian m. carlson: Houston, Texas, US
OpenPGP: https://keybase.io/bk2204

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 868 bytes --]

RE: ! [remote rejected] master -> master (unpacker error)

[Randall S. Becker]

> -----Original Message-----
> From: git-owner@vger.kernel.org <git-owner@vger.kernel.org> On Behalf
> Of lyle.ziegelmiller@gmail.com
> Sent: February 17, 2020 11:26 AM
> To: 'brian m. carlson' <sandals@crustytoothpaste.net>
> Cc: git@vger.kernel.org
> Subject: RE: ! [remote rejected] master -> master (unpacker error)
> 
> I wrote a bunch of emails about this in December 2019. Did they all get lost?
> 
> I'm consistently able to clone the repository, but I can never push to it. I used
> to be able to. I've explored all possibilities that I know of.
> 
> I'm using Windows 10, and the Cygwin version of Git.
> 
> $ git --version
> git version 2.21.0
> 
> Regards
> 
> Lyle
> 
> -----Original Message-----
> From: brian m. carlson <sandals@crustytoothpaste.net>
> Sent: Sunday, February 16, 2020 2:16 PM
> To: lyle.ziegelmiller@gmail.com
> Cc: git@vger.kernel.org
> Subject: Re: ! [remote rejected] master -> master (unpacker error)
> 
> On 2020-02-16 at 16:10:12, lyle.ziegelmiller@gmail.com wrote:
> > Hi
> >
> > Any updates on this error I emailed a while back?
> >
> > lylez@LJZ-DELLPC ~/python
> > $ git push
> > Enumerating objects: 5, done.
> > Counting objects: 100% (5/5), done.
> > Delta compression using up to 4 threads Compressing objects: 100%
> > (2/2), done.
> > Writing objects: 100% (3/3), 279 bytes | 23.00 KiB/s, done.
> > Total 3 (delta 1), reused 0 (delta 0)
> > remote: fatal: not a git repository: '.'
> 
> This error is telling you that Git doesn't think the remote location is a Git
> repository.  It could be because it really isn't one, or it could be that the
> permissions are wrong.
> 
> It could also be that the repository is mostly there but very slightly corrupt
> and therefore can't be detected as one.  For example, it could be missing its
> HEAD reference.

It also could be that the security setup on the server is messed up and you cannot run programs from wherever git is installed.

Re: ! [remote rejected] master -> master (unpacker error)

[Jeff King]

On Sun, Feb 16, 2020 at 09:16:04PM +0000, brian m. carlson wrote:

> On 2020-02-16 at 16:10:12, lyle.ziegelmiller@gmail.com wrote:
> > Hi
> > 
> > Any updates on this error I emailed a while back?
> > 
> > lylez@LJZ-DELLPC ~/python
> > $ git push
> > Enumerating objects: 5, done.
> > Counting objects: 100% (5/5), done.
> > Delta compression using up to 4 threads
> > Compressing objects: 100% (2/2), done.
> > Writing objects: 100% (3/3), 279 bytes | 23.00 KiB/s, done.
> > Total 3 (delta 1), reused 0 (delta 0)
> > remote: fatal: not a git repository: '.'
> 
> This error is telling you that Git doesn't think the remote location is
> a Git repository.  It could be because it really isn't one, or it could
> be that the permissions are wrong.
> 
> It could also be that the repository is mostly there but very slightly
> corrupt and therefore can't be detected as one.  For example, it could
> be missing its HEAD reference.

I think it's more subtle than that, though. If it wasn't a git
repository at all, then receive-pack would fail to start, and you'd get
something like this:

  $ git push /foo/bar
  fatal: '/foo/bar' does not appear to be a git repository
  fatal: Could not read from remote repository.
  
  Please make sure you have the correct access rights
  and the repository exists.

The output above, plus the:

  error: remote unpack failed: unpack-objects abnormal exit

makes it looks like receive-pack started just fine, but something about
the way it set up the environment made the child unpack-objects unhappy
when it tried to initialize its internal repo variables.

I have no clue what that "something" is, though. Windows and UNC paths
were mentioned elsewhere, which seem plausible. It mentions ".", so
presumably we've chdir()'d into the receiving repository and set
$GIT_DIR. Which I'd think rules out any weird interpretations of UNC
paths in $GIT_DIR.

I'd expect that error if we did a chdir() internally to some other path
after setting up $GIT_DIR, but I don't know why we'd do that (I thought
at first that the quarantine code in receive-pack might be related, but
we don't ever chdir() into the quarantine dir; we just set up
GIT_OBJECT_DIRECTORY).

-Peff

Re: ! [remote rejected] master -> master (unpacker error)

[Johannes Schindelin]

Hi Peff,

On Tue, 18 Feb 2020, Jeff King wrote:

> On Sun, Feb 16, 2020 at 09:16:04PM +0000, brian m. carlson wrote:
>
> > On 2020-02-16 at 16:10:12, lyle.ziegelmiller@gmail.com wrote:
> > >
> > > Any updates on this error I emailed a while back?
> > >
> > > lylez@LJZ-DELLPC ~/python
> > > $ git push
> > > Enumerating objects: 5, done.
> > > Counting objects: 100% (5/5), done.
> > > Delta compression using up to 4 threads
> > > Compressing objects: 100% (2/2), done.
> > > Writing objects: 100% (3/3), 279 bytes | 23.00 KiB/s, done.
> > > Total 3 (delta 1), reused 0 (delta 0)
> > > remote: fatal: not a git repository: '.'
> >
> > This error is telling you that Git doesn't think the remote location is
> > a Git repository.  It could be because it really isn't one, or it could
> > be that the permissions are wrong.
> >
> > It could also be that the repository is mostly there but very slightly
> > corrupt and therefore can't be detected as one.  For example, it could
> > be missing its HEAD reference.
>
> I think it's more subtle than that, though. If it wasn't a git
> repository at all, then receive-pack would fail to start, and you'd get
> something like this:
>
>   $ git push /foo/bar
>   fatal: '/foo/bar' does not appear to be a git repository
>   fatal: Could not read from remote repository.
>
>   Please make sure you have the correct access rights
>   and the repository exists.
>
> The output above, plus the:
>
>   error: remote unpack failed: unpack-objects abnormal exit
>
> makes it looks like receive-pack started just fine, but something about
> the way it set up the environment made the child unpack-objects unhappy
> when it tried to initialize its internal repo variables.
>
> I have no clue what that "something" is, though. Windows and UNC paths
> were mentioned elsewhere, which seem plausible. It mentions ".", so
> presumably we've chdir()'d into the receiving repository and set
> $GIT_DIR. Which I'd think rules out any weird interpretations of UNC
> paths in $GIT_DIR.

I thought that I remembered that it is not possible to `chdir()` into a
UNC path. And it would seem that `cmd.exe` still cannot have a UNC path as
a current directory.

But PowerShell can, and so does `git.exe`, apparently (I tested this using
`wsl bash -lc "cd ~ && git.exe -C . version"`).

But I vividly remember that there used to be a problem even with
`git.exe`, probably still is a problem on older Windows versions. That
might be the problem here?

Ciao,
Dscho

> I'd expect that error if we did a chdir() internally to some other path
> after setting up $GIT_DIR, but I don't know why we'd do that (I thought
> at first that the quarantine code in receive-pack might be related, but
> we don't ever chdir() into the quarantine dir; we just set up
> GIT_OBJECT_DIRECTORY).
>
> -Peff
>

RE: ! [remote rejected] master -> master (unpacker error)

[lyle.ziegelmiller]

" But I vividly remember that there used to be a problem even with
`git.exe`, probably still is a problem on older Windows versions. That might
be the problem here?"

I'm using the latest version of Windows 10 and Cygwin's version of git -
version 2.21.0. This is being executed in a Cygwin window, not a DOS
terminal.

All of this stuff used to work.

Regards

Lyle

-----Original Message-----
From: Johannes Schindelin <Johannes.Schindelin@gmx.de> 
Sent: Thursday, February 27, 2020 1:05 PM
To: Jeff King <peff@peff.net>
Cc: brian m. carlson <sandals@crustytoothpaste.net>;
lyle.ziegelmiller@gmail.com; git@vger.kernel.org
Subject: Re: ! [remote rejected] master -> master (unpacker error)

Hi Peff,

On Tue, 18 Feb 2020, Jeff King wrote:

> On Sun, Feb 16, 2020 at 09:16:04PM +0000, brian m. carlson wrote:
>
> > On 2020-02-16 at 16:10:12, lyle.ziegelmiller@gmail.com wrote:
> > >
> > > Any updates on this error I emailed a while back?
> > >
> > > lylez@LJZ-DELLPC ~/python
> > > $ git push
> > > Enumerating objects: 5, done.
> > > Counting objects: 100% (5/5), done.
> > > Delta compression using up to 4 threads Compressing objects: 100% 
> > > (2/2), done.
> > > Writing objects: 100% (3/3), 279 bytes | 23.00 KiB/s, done.
> > > Total 3 (delta 1), reused 0 (delta 0)
> > > remote: fatal: not a git repository: '.'
> >
> > This error is telling you that Git doesn't think the remote location 
> > is a Git repository.  It could be because it really isn't one, or it 
> > could be that the permissions are wrong.
> >
> > It could also be that the repository is mostly there but very 
> > slightly corrupt and therefore can't be detected as one.  For 
> > example, it could be missing its HEAD reference.
>
> I think it's more subtle than that, though. If it wasn't a git 
> repository at all, then receive-pack would fail to start, and you'd 
> get something like this:
>
>   $ git push /foo/bar
>   fatal: '/foo/bar' does not appear to be a git repository
>   fatal: Could not read from remote repository.
>
>   Please make sure you have the correct access rights
>   and the repository exists.
>
> The output above, plus the:
>
>   error: remote unpack failed: unpack-objects abnormal exit
>
> makes it looks like receive-pack started just fine, but something 
> about the way it set up the environment made the child unpack-objects 
> unhappy when it tried to initialize its internal repo variables.
>
> I have no clue what that "something" is, though. Windows and UNC paths 
> were mentioned elsewhere, which seem plausible. It mentions ".", so 
> presumably we've chdir()'d into the receiving repository and set 
> $GIT_DIR. Which I'd think rules out any weird interpretations of UNC 
> paths in $GIT_DIR.

I thought that I remembered that it is not possible to `chdir()` into a UNC
path. And it would seem that `cmd.exe` still cannot have a UNC path as a
current directory.

But PowerShell can, and so does `git.exe`, apparently (I tested this using
`wsl bash -lc "cd ~ && git.exe -C . version"`).

But I vividly remember that there used to be a problem even with `git.exe`,
probably still is a problem on older Windows versions. That might be the
problem here?

Ciao,
Dscho

> I'd expect that error if we did a chdir() internally to some other 
> path after setting up $GIT_DIR, but I don't know why we'd do that (I 
> thought at first that the quarantine code in receive-pack might be 
> related, but we don't ever chdir() into the quarantine dir; we just 
> set up GIT_OBJECT_DIRECTORY).
>
> -Peff
>

Re: ! [remote rejected] master -> master (unpacker error)

[Jeff King]

On Thu, Feb 27, 2020 at 01:24:04PM -0800, lyle.ziegelmiller@gmail.com wrote:

> " But I vividly remember that there used to be a problem even with
> `git.exe`, probably still is a problem on older Windows versions. That might
> be the problem here?"
> 
> I'm using the latest version of Windows 10 and Cygwin's version of git -
> version 2.21.0. This is being executed in a Cygwin window, not a DOS
> terminal.
> 
> All of this stuff used to work.

If you have a version of Git that works and one that doesn't, it might
be worth using git-bisect to find the commit that introduced the
problem. That does imply being able to build from source; I don't know
how hard that is on cygwin.

-Peff

RE: ! [remote rejected] master -> master (unpacker error)

[Johannes Schindelin]

Hi Lyle,

On Thu, 27 Feb 2020, lyle.ziegelmiller@gmail.com wrote:

> " But I vividly remember that there used to be a problem even with
> `git.exe`, probably still is a problem on older Windows versions. That might
> be the problem here?"
>
> I'm using the latest version of Windows 10 and Cygwin's version of git -
> version 2.21.0. This is being executed in a Cygwin window, not a DOS
> terminal.

I was talking about Git for Windows, not about Cygwin Git.

Ciao,
Johannes

> All of this stuff used to work.
>
> Regards
>
> Lyle
>
> -----Original Message-----
> From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
> Sent: Thursday, February 27, 2020 1:05 PM
> To: Jeff King <peff@peff.net>
> Cc: brian m. carlson <sandals@crustytoothpaste.net>;
> lyle.ziegelmiller@gmail.com; git@vger.kernel.org
> Subject: Re: ! [remote rejected] master -> master (unpacker error)
>
> Hi Peff,
>
> On Tue, 18 Feb 2020, Jeff King wrote:
>
> > On Sun, Feb 16, 2020 at 09:16:04PM +0000, brian m. carlson wrote:
> >
> > > On 2020-02-16 at 16:10:12, lyle.ziegelmiller@gmail.com wrote:
> > > >
> > > > Any updates on this error I emailed a while back?
> > > >
> > > > lylez@LJZ-DELLPC ~/python
> > > > $ git push
> > > > Enumerating objects: 5, done.
> > > > Counting objects: 100% (5/5), done.
> > > > Delta compression using up to 4 threads Compressing objects: 100%
> > > > (2/2), done.
> > > > Writing objects: 100% (3/3), 279 bytes | 23.00 KiB/s, done.
> > > > Total 3 (delta 1), reused 0 (delta 0)
> > > > remote: fatal: not a git repository: '.'
> > >
> > > This error is telling you that Git doesn't think the remote location
> > > is a Git repository.  It could be because it really isn't one, or it
> > > could be that the permissions are wrong.
> > >
> > > It could also be that the repository is mostly there but very
> > > slightly corrupt and therefore can't be detected as one.  For
> > > example, it could be missing its HEAD reference.
> >
> > I think it's more subtle than that, though. If it wasn't a git
> > repository at all, then receive-pack would fail to start, and you'd
> > get something like this:
> >
> >   $ git push /foo/bar
> >   fatal: '/foo/bar' does not appear to be a git repository
> >   fatal: Could not read from remote repository.
> >
> >   Please make sure you have the correct access rights
> >   and the repository exists.
> >
> > The output above, plus the:
> >
> >   error: remote unpack failed: unpack-objects abnormal exit
> >
> > makes it looks like receive-pack started just fine, but something
> > about the way it set up the environment made the child unpack-objects
> > unhappy when it tried to initialize its internal repo variables.
> >
> > I have no clue what that "something" is, though. Windows and UNC paths
> > were mentioned elsewhere, which seem plausible. It mentions ".", so
> > presumably we've chdir()'d into the receiving repository and set
> > $GIT_DIR. Which I'd think rules out any weird interpretations of UNC
> > paths in $GIT_DIR.
>
> I thought that I remembered that it is not possible to `chdir()` into a UNC
> path. And it would seem that `cmd.exe` still cannot have a UNC path as a
> current directory.
>
> But PowerShell can, and so does `git.exe`, apparently (I tested this using
> `wsl bash -lc "cd ~ && git.exe -C . version"`).
>
> But I vividly remember that there used to be a problem even with `git.exe`,
> probably still is a problem on older Windows versions. That might be the
> problem here?
>
> Ciao,
> Dscho
>
> > I'd expect that error if we did a chdir() internally to some other
> > path after setting up $GIT_DIR, but I don't know why we'd do that (I
> > thought at first that the quarantine code in receive-pack might be
> > related, but we don't ever chdir() into the quarantine dir; we just
> > set up GIT_OBJECT_DIRECTORY).
> >
> > -Peff
> >
>
>