From: "Randall S. Becker" <rsbecker@nexbridge.com>
To: <lyle.ziegelmiller@gmail.com>,
"'brian m. carlson'" <sandals@crustytoothpaste.net>
Cc: <git@vger.kernel.org>
Subject: RE: ! [remote rejected] master -> master (unpacker error)
Date: Mon, 17 Feb 2020 17:45:28 -0500 [thread overview]
Message-ID: <005501d5e5e3$f7082260$e5186720$@nexbridge.com> (raw)
In-Reply-To: <001801d5e5ae$e4375780$aca60680$@gmail.com>
> -----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.
next prev parent reply other threads:[~2020-02-17 22:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-16 16:10 ! [remote rejected] master -> master (unpacker error) lyle.ziegelmiller
2020-02-16 21:16 ` brian m. carlson
2020-02-17 16:25 ` lyle.ziegelmiller
2020-02-17 17:17 ` brian m. carlson
2020-02-17 22:45 ` Randall S. Becker [this message]
2020-02-18 5:19 ` Jeff King
2020-02-27 21:04 ` Johannes Schindelin
2020-02-27 21:24 ` lyle.ziegelmiller
2020-02-27 22:58 ` Jeff King
2020-02-28 22:53 ` Johannes Schindelin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='005501d5e5e3$f7082260$e5186720$@nexbridge.com' \
--to=rsbecker@nexbridge.com \
--cc=git@vger.kernel.org \
--cc=lyle.ziegelmiller@gmail.com \
--cc=sandals@crustytoothpaste.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).