public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: [cygwin] Cygwin's git says "error: failed to read delta-pack base object"
Date: Thu, 04 Dec 2014 09:53:00 -0000	[thread overview]
Message-ID: <20141204095345.GF3810@calimero.vinschen.de> (raw)
In-Reply-To: <CAOOocNmPvq+gZjkCvDtONwZeWZrD7HcA3m10N8ryxiuzca_wtg@mail.gmail.com>

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

On Dec  3 18:07, Dave Lindbergh wrote:
> On Wed, Dec 3, 2014 at 3:42 PM, Jason Pyeron <jpyeron@pdinc.us> wrote:
> > [copy off list, because the sourceware system admins throws temper tantrums]
> >> -----Original Message-----
> >> From: Dave L
> >> Sent: Wednesday, December 03, 2014 15:30
> >>
> >> ...but the git from github.com works fine.
> >>
> >> I installed Cygwin's version of git, and get this:
> >>
> >>     $ git clone https://github.com/nerdfever/pic32mx-bmf
> >>     Cloning into 'pic32mx-bmf'...
> >>     remote: Counting objects: 12, done.
> >>     remote: Total 12 (delta 0), reused 0 (delta 0)
> >>     error: failed to read delta-pack base object
> >>     300bdeb2fd209d24afb865584da10b78aa8fefc4
> >>     fatal: unpack-objects failed
> >
> > What file system are you on? Local NTFS or remote?
> 
> Aha - you're right.
> 
> It works fine on a local NTFS volume.
> 
> I get the error when I do it on Z:, which is mapped to a network drive
> (on another Windows box).

It works fine for me on a network drive mounted from another Windows
machine used via the cygdrive prefix:

  $ mount | grep cygdrive/z
  Z: on /cygdrive/z type ntfs (binary,posix=0,user,noumount,auto)
  $ cd /cygdrive/z
  $ git clone https://github.com/nerdfever/pic32mx-bmf
  Cloning into 'pic32mx-bmf'...
  remote: Counting objects: 12, done.
  remote: Total 12 (delta 0), reused 0 (delta 0)
  Unpacking objects: 100% (12/12), done.
  Checking connectivity... done.

I tried with two different mount points, one to a Cygwin-created remote
dir, one to a Windows-created remote dir.

> Is there a workaround? Why does this happen?

No idea.  How do you mount the drive, e.g., what does `mount' print for
the drive?  Or could this be a permission problem?  If all else fails
you could try to find out what happens via strace.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2014-12-04  9:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-03 20:30 Dave L
2014-12-03 20:40 ` Marco Atzeri
     [not found] ` <BCA71D26F26F4EC487E0D811F70EC4F5@black>
2014-12-03 23:07   ` [cygwin] " Dave Lindbergh
2014-12-04  9:53     ` Corinna Vinschen [this message]
2014-12-05  5:05     ` Andrey Repin
2014-12-04 21:28 Dave Lindbergh
2014-12-04 22:43 ` Adam Dinwoodie
2014-12-05 11:35   ` Corinna Vinschen
2014-12-05 17:39     ` Dave L
2014-12-07 10:11       ` Corinna Vinschen
2014-12-05  8:46 ` Csaba Raduly

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20141204095345.GF3810@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.com \
    --cc=cygwin@cygwin.com \
    /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.
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).