Gitolite 3 warns about empty groups

[Ronan Cunningham]

Gitolite 3 warns about empty groups e.g

remote: WARNING: syntax error, ignoring: '@tbs_cmed_test_ro ='

Does not happen with G2.

It suits us to have empty groups for various reasons as we automate adding users and repositories etc

Is there any way to supress the message (other than adding a user to the group)?

[Sitaram Chamarty]

I'll think about it, but since groups accumulate, you could just say
@foo = DUMMY

where DUMMY is a user that will never exist.

[Sitaram Chamarty]

On 09/04/2013 03:51 PM, Ronan Cunningham wrote:

Thinking about it some more, I'm curious why you actually need this at
all. Are you in a situation where you end up adding a group which does
not have any member at all? Or do you do something like this:

@foo =
@foo = alice
@foo = bob

?

In any case, it is unlikely to change unless lots of people ask. What I
*can* do, however, is write you a "sugar" script that you can enable
which gets rid of such lines before the main "compile" snags on it.

[Cunningham, Ronan]

Hi

We have:

@foo =


We have a lot of churn of users. When we create a repo, we create a RW and
RO group for that repo by default.
Normally the RO group is empty initially, then gets populated over time.
Our automated scripts look for this specific group name when adding a user.

Adding a dummy user is probably the best option for now, though not ideal
as we create automated access reports for review based on the conf files
contents which could confuse some people.

Assuming it's a WARNING, the rest of the compile should happen ok?

Thanks for the offer of help but we will manage it. I just raised it as G2
did not do this. Not a big deal.

Thanks for reading

Ronan

>--
>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.

[Ralf Hemmecke]

> We have a lot of churn of users. When we create a repo, we create a RW and
> RO group for that repo by default.
> Normally the RO group is empty initially, then gets populated over time.
> Our automated scripts look for this specific group name when adding a user.

I don't know your exact use case, but it somehow sounds like you might
want to look into wild repos [1] and use the perms command (ssh git@host
perms -h) to add and remove users to the repo.

[1] http://gitolite.com/gitolite/wild.html

Ralf

[Sitaram Chamarty]

On 09/04/2013 07:34 PM, Cunningham, Ronan wrote:
> Hi
>
> We have:
>
> @foo =
>
>
> We have a lot of churn of users. When we create a repo, we create a RW and
> RO group for that repo by default.
> Normally the RO group is empty initially, then gets populated over time.
> Our automated scripts look for this specific group name when adding a user.
>
> Adding a dummy user is probably the best option for now, though not ideal
> as we create automated access reports for review based on the conf files
> contents which could confuse some people.
>
> Assuming it's a WARNING, the rest of the compile should happen ok?

yes.

> Thanks for the offer of help but we will manage it. I just raised it as G2
> did not do this. Not a big deal.

I seem to recall some people getting confused that a "syntax error" was not pointed out (when they made some typo I guess).

Again, if enough people feel this should be OK, I'm happy to change it. Not that hard...