#4995: Access for launchy DENIED to lzap
Fedora Release Engineering
rel-eng at fedoraproject.org
Thu Dec 1 15:41:55 UTC 2011
#4995: Access for launchy DENIED to lzap
---------------------+------------------------------------------------------
Reporter: lzap | Owner: rel-eng at lists.fedoraproject.org
Type: defect | Status: new
Milestone: | Component: git
Resolution: | Keywords:
---------------------+------------------------------------------------------
Comment (by tibbs):
I have no problems cloning it, and the gitolite configuration looks OK to
me:
{{{
repo launchy
RWC master = lzap @provenpackager
RWC f16 = lzap @provenpackager
- f[0-9][0-9] = @all
- el[0-9] = @all
- olpc[0-9] = @all
RWC refs/tags/ = lzap @provenpackager
RWC = lzap @provenpackager
}}}
Here are the relevant bits from the gitolite log:
{{{
gitolite-2011-10.log:2011-10-07.12:15:29 limb 76.204.165.225
/usr/local/bin/pkgdb2branch.py launchy
gitolite-2011-10.log:2011-10-07.15:41:42 lzap 78.80.253.33
Die generated at line 156 in /usr/bin/gl-auth-command : R access for
launchy DENIED to lzap<<newline>>(Or there may be no repository at the
given path. Did you spell it correctly?)<<newline>> <<newline>>
gitolite-2011-10.log:2011-10-07.15:42:39 lzap 78.80.253.33
Die generated at line 156 in /usr/bin/gl-auth-command : R access for
launchy DENIED to lzap<<newline>>(Or there may be no repository at the
given path. Did you spell it correctly?)<<newline>> <<newline>>
gitolite-2011-12.log:2011-12-01.15:27:57 tibbs 129.7.128.2
git-upload-pack '/launchy'
}}}
Was this actually tested again before you reported this issue? Nothing
appears in the logs to indicate that.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/4995#comment:1>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
More information about the rel-eng
mailing list