Re: git clone failing with "fatal: index-pack failed"

[Balaji Venkataraman <balaji dot s dot venkataraman at gmail dot com>]

On Tue, Nov 5, 2013 at 7:28 AM, Andrew DeFaria <Andrew@defaria.com> wrote:

> On 10/31/2013 08:04 AM, Andrew DeFaria wrote:
>>
>> On 10/26/2013 03:12 PM, Balaji Venkataraman wrote:
>>>
>>> On Sat, Oct 26, 2013 at 9:23 AM, Andrew DeFaria wrote:
>>>>
>>>> It's been very quite about this issue. Usually at least somebody
>>>> responds. I
>>>> fear that perhaps nobody's seeing this. Could somebody, anybody, simply
>>>> respond if even just to say "Yeah, I see this. Don't have an answer
>>>> though"
>>>> I'd appreciate it.
>>>
>>> I see something similar intermittently but only when I try to clone in
>>> a non-Administrator shell and that too only on cygwin32. It doesn't
>>> happen when I'm in an administrator shell. Haven't been able to figure
>>> it out - although I'm having other problems where I can't run many
>>> commands from a 32bit Cygwin shell - so I don't want to set you off on
>>> a random thread. Are you able to do things like man, make etc. from
>>> the same shell?

Did you try these (man, make etc.) from a non-admin shell?

>> Interesting. Running an administrator shell works! The odd thing is that I
>> logged in as the user Administrator, the local user Administrator. I assume
>> it has administrator rights but I know that there are administrator rights
>> and then there are administrator rights. So it seems the problem lies
>> between the two. How to debug this further and fix it?
>
> Another error that I'm getting is the following:
>
> $ git fetch
> Warning: No xauth data; using fake authentication data for X11 forwarding.
> X11 forwarding request failed on channel 0
> fatal: Out of memory? mmap failed: Resource temporarily unavailable
> $
>
> Note that this happens whether or not I start an administrator shell. Also

Could you do the following and report back:
- open windows explorer and navigate to C:\Cygwin\bin (or where ever
the root of your 32 bit Cygwin installation).
- scroll down to find sh.exe and check whether you see the windows
'Administrator' shield on it?

If it has a shield on it, that is the source of all problems.

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple