I'm having a very similar error. But in my case, the bundler is updated.. 
deleting and creating again does nothing

Reported here: https://gitlab.com/gitlab-org/gitlab-ce/issues/417

On Friday, 27 June 2014 17:34:06 UTC+1, [email protected] wrote:
>
> Axillea,
>
> You pin pointed the problem very well! Yes it was because of an older 
> version of bundler... which I missed it in the upgrade guide (though it was 
> a dependency if you upgraded ruby, which I neededn't). After upgrading 
> bundler and all bundles the problem with the wiki eliminated. However the 
> problem pushing to new repositories persisted. In order to overcome this I 
> had to remove (empty) repositories that were created in this period (after 
> upgrading to 7.0 and before fixing bundler). I hope it didn't introduce any 
> more inconsistencies in the database...
>
> Great Help!
> Efxaristw! :D
>
> On Friday, June 27, 2014 6:43:05 PM UTC+3, Achilleas Pipis wrote:
>>
>> On 06/27/2014 06:00 PM, [email protected] wrote: 
>> > After extra investigation, I discovered that pushing new code also has 
>> > problem but this time production.log is more descriptive. 
>> > So on a new repository if I try to push I get the error: 
>> > ---- 
>> > Access denied. 
>> > fatal: Could not read from remote repository. 
>> > 
>> > Please make sure you have the correct access rights 
>> > and the repository exists. 
>> > ---- 
>> > 
>>
>> <snip> 
>>
>> Can you try to install bundler again? It should pull 1.6.3. 
>>
>> sudo gem install bundler --no-doc 
>>
>> Then run again the bundle install command to ensure rake is picked up 
>> correctly. 
>>
>> -- 
>> GPG : 0xABF99BE5 
>> Blog: http://axilleas.me 
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"GitLab" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/gitlabhq/5288ec5c-2218-4a80-bdb1-f4c177c11692%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to