Re: Permission denied ONLY after pulling bundles

> Hi,
>
> On Thu, Jun 4, 2015 at 3:04 PM, Rossella Barletta
> <rossella.barletta@gmail.com> wrote:
>> Dear git group,
>>
>>
>> I would like to ask your help for a problem that we cannot fix in any 
>> way.
>>
>> We have a git repository in folder on Windows.
>>
>> Then we use VMware player on CentOS_6 on which we create a clone of
>> the git repository, after of course having mounted the directory in
>> which the repository is.
>>
>> So the repository is on windows and the clone on Linux.
>>
>> We are able to perfom all the git operations we need, except for the
>> pull .bundle, which is successful in itself but prevent us from
>> pushing after that.
>
> It is not very clear how the bundle has been made, and on which
> machine you made it and you pulled from it.
>
>> As we try to push after pulling a .bundle in a branch we get the 
>> error message
>>
>> NODE1:fdp> git push
>> Counting objects: 1977, done.
>> Delta compression using up to 2 threads.
>> Compressing objects: 100% (423/423), done.
>> fatal: write error: Permission denied00 KiB | 158 KiB/s
>> error: pack-objects died of signal 13
>> error: pack-objects died with strange error
>
> Can you have a look at the machine you push to and see if some file or
> directory permissions changed between before and after you made the
> bundle or you pulled the bundle?
>
>> We have checked all the permissions, changed the users, recreated the
>> clone but nothing worked.
>
> What do you mean by checked all the permissions?
> You mean that permissions haven't changed at all since before you
> pulled the first bundle?
>
>> The push operation works perfectly until we pull a bundle. After
>> pulling a bundle we are not able to push anymore.We tryed to delete
>> the branches, recreate others and all works perfectly, also the
>> push.As we pull the .bundle we cannot get the permission to do the
>> push anymore.
>>
>> What has this to do with the bundle?
>
> Did you try to everything (cloning, creating a bundle, pulling it and
> pushing on the same machine to see if it makes a difference? Also did
> you try with another smaller fake repository?
>
> If you can reproduce with a smaller fake repo on just one machine it
> could help us reproduce on one of our machine and have a look.
>
> And could you tell us which version of git (using git --version) you
> are using on both machines?
>