Re: Permission denied ONLY after pulling bundles
- From
- Rossella Barletta <rossella.barletta@gmail.com>
- Date
- Jun 8, 2015, 08:34 UTC
- Message-ID
- <CAJeiYQHmXjxdk7eGSsd9TN5hfPF72ssS-j0xGZ6QOYD+5Gb++g@mail.gmail.com>
- In-Reply-To
- <CAP8UFD0gMCnaJnXNxe6Tmwxes7c4Wqgga1d8AzSNEcFxtHtGWg@mail.gmail.com>
I followed all your indications (created a small fake repo on windows, cloned it and playing with bundles) and in this case everything works.On windows i dont have any problem and i used the version 1.9.5.
Then i created a clone of my original repo, again on Windows (since my original one is a bare repository) and i pulled the bundle and then pushed in the branch and it worked. Same operation that doesnt work on Linux works on Windows.
So i went again on Linux, pulled on my branch of the clone repo , i has to commit first since i had some changes. So i committed, pulled, and then pushed again.The push was unsuccessful giving the error message that i indicated at the beginning.
So i cannot push only my clone on Linux.
Rossella
2015-06-05 18:01 GMT+02:00 Christian Couder <christian.couder@gmail.com>:
Show 38 quoted lines
> On Fri, Jun 5, 2015 at 8:54 AM, Rossella Barletta > <rossella.barletta@gmail.com> wrote: > > [...] > >> FIST ONE (PERMISSION PROBLEMS) >> >> - Repo is on windows >> - Repo folder is shared >> -Repo is a copy of another repository being on a machine in another >> city on which we cannot access. We got all the files, included the >> folder .git a put everything in our shared folder >> - Mounted the Repo folder on Linux >> -Created the clone >> - got a bundle from the original repository (bundle created from a branch) >> -pulled the bundle in the same branch >> >> >> >> SECOND ONE (NO PROBLEMS BUT WE CANT USE THIS) >> - Repo is on Linux >> -Repo is a copy of another repository being on a machine in another >> city on which we cannot access. >> - got a bundle from the original repository (bundle created from a branch) >> -pulled the bundle in the same branch >> >> >> >> 4) Git version is 1.7.1 > > It would be nice if you could try to reproduce the problem: > > - using a recent Git, as v1.7.1 is 5 years old, > - using a small fake repo, > - doing everything on Windows. > > Best, > Christian.
-- Rossella