"DENIED by fallthru" error while pushing a branch upstream

[Ming]

When i tried to push a branch back to the Gitolite server, i got the following error:
...
FATAL: W any foo/feeds firstname.lastname DENIED by fallthru
(or you mis-spelled the reponame)
fatal: Could not read from remote repository.

In the ~gitolite/.gitolite/logs, there is the following:

ssh ARGV=firstname.lastname SOC=git-receive-pack 'foo/feeds.git' FROM=....
2013-05-13.17:08:03 1404 access(foo/feeds, firstname.lastname, W, 'any'),-> W any foo/feeds firstname.lastname DENIED by fallthru
2013-05-13.17:08:03 1404 trigger,Writable,access_1,ACCESS_1,foo/feeds,firstname.lastname,W,any,W any foo/feeds firstname.lastname DENIED by fallthru
2013-05-13.17:08:03 1404 die W any foo/feeds firstname.lastname DENIED by fallthru<<newline>>(or you mis-spelled the reponame)

Gitolite version: v3.1-4-ga802071 on git 1.7.12.2

The weird thing is i've no problem pushing other repos in my conf/gitolite.conf and all the repos have identical configuration as in:

repo foo/feeds
RW = @developers
R = gitweb daemon
config gitweb.description = "foo/feeds"

Thanks.

[Sitaram Chamarty]

this sort of thing usually ends up being a typo somewhere.

Paste your *entire* config -- UN-edited -- as well as your entire "git
push" command and response, plus output of "git remote -v".

If you're not comfortable doing that, or are convinced there is no
typo, you need to be able to give me some steps to reproduce the
problem on my side so I can test.

> --
> You received this message because you are subscribed to the Google Groups "gitolite" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to gitolite+u...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>



--
Sitaram

[Ming]

On Monday, May 13, 2013 8:32:10 PM UTC-4, Ming wrote:
> When i tried to push a branch back to the Gitolite server, i got the following error:
> ...
> FATAL: W any foo/feeds firstname.lastname DENIED by fallthru
> (or you mis-spelled the reponame)
> fatal: Could not read from remote repository.
>
> In the ~gitolite/.gitolite/logs, there is the following:
>
> ssh ARGV=firstname.lastname SOC=git-receive-pack 'foo/feeds.git' FROM=....
> 2013-05-13.17:08:03 1404 access(foo/feeds, firstname.lastname, W, 'any'),-> W any foo/feeds firstname.lastname DENIED by fallthru
> 2013-05-13.17:08:03 1404 trigger,Writable,access_1,ACCESS_1,foo/feeds,firstname.lastname,W,any,W any foo/feeds firstname.lastname DENIED by fallthru

> 2013-05-13.17:08:03 1404 die W any foo/feeds firstname.lastname DENIED by fallthru<>(or you mis-spelled the reponame)

[Hseu-Ming Chen]

Sorry for the pre-mature "Send".   i cannot access my Git config right now so i'll do that tomorrow.   i should have pointed out a few other things:

* 2 of my co-workers issued the same push command and got the same error.   i think the probability that all three

  of us made some typo is low

* i changed the permission above from:
      RW  =  @developers

  to
      RW+  =  @developers

  then all three of us were able to push to the branch successfully

* the repo was originally created with "git filter-branch --index-filter ..." and i migrated it into Gitolite a few days back

i apologize for not including the info above earlier

[Sitaram Chamarty]

On Tue, May 14, 2013 at 6:47 AM, Hseu-Ming Chen <hseu...@gmail.com> wrote:
> Sorry for the pre-mature "Send". i cannot access my Git config right now
> so i'll do that tomorrow. i should have pointed out a few other things:
> * 2 of my co-workers issued the same push command and got the same error.
> i think the probability that all three
> of us made some typo is low

*shrug*. I didn't say the typo was in your command; maybe it is in the conf.

>
> * i changed the permission above from:
> RW = @developers
> to
> RW+ = @developers
> then all three of us were able to push to the branch successfully

doesn't make sense to me. The error you got was from the "pre git"
access check, at which point the distinction between RW and RW+ does
not exist.

> * the repo was originally created with "git filter-branch --index-filter
> ..." and i migrated it into Gitolite a few days back

As long as you have added the repo to the conf/gitolite.conf file and
pushed the change to the gitolite-admin repo on the server, it doesn't
matter how the actual repo was created.

What version of gitolite is this, by the way?

--
Sitaram

[Hseu-Ming Chen]

> *shrug*.  I didn't say the typo was in your command; maybe it is in the conf.

but we have our own Git conf files ...    Same typo in all our individual Git conf files??? 

> The error you got was from the "pre git" access check, at which point the distinction
> between RW and RW+ does not exist.

That puzzles me as well. 

> What version of gitolite is this, by the way?

i included the info in my first message in this thread:

>  Gitolite version: v3.1-4-ga802071 on git 1.7.12.2

i've migrated many Git repos created by various approaches, namely "git filter-branch --[tree|index|subdirectory]-filter ...", etc., into Gitolite successfully without a hitch by following the instructions of the master doc.

By the way, i like Gitolite and thank you for the well-crafted tool.

[Sitaram Chamarty]

On Tue, May 14, 2013 at 7:41 AM, Hseu-Ming Chen <hseu...@gmail.com> wrote:
>> *shrug*. I didn't say the typo was in your command; maybe it is in the
>> conf.
>
> but we have our own Git conf files ... Same typo in all our individual
> Git conf files???

I meant conf/gitolite.conf, which there should be only one (on the
server) that matters.

Anyway this is getting nowhere. Please respond when you have access
to your system and can either send the full conf etc as I asked, or
steps to reproduce it.