On Tue, 2014-09-09 at 18:58 +0200, Pierre-Yves Chibon wrote:
On Fri, Sep 05, 2014 at 12:45:38PM +0200, Pierre-Yves Chibon wrote:
> That being said, I believe our options are:
> 1) Talk with upstream, in the past I believe he was quite reactive and willing
> to help us. We are the largest public deployment of gitolite maybe he'll
> still be willing to help us
> to discuss:
> - setting HOME in the authorized_keys
> - writing logs
> - accessing gitolite.conf-compiled.pm
[... snip ...]
However, the HOME question remains. Mathieu is going to contact
upstream to see
if we can manage to automate adding a HOME somehow.
As it turns out, we figured it out: we don't use the upstream tools to
generate the ~/.ssh/authorized_keys files, we have our own stuff in
We fixed this, and a couple of other things.
As of commit 13465f6a0d2ed107357b204ab9bf5ca6a4f1fef2, distgit staging
is now running with Gitolite 3 on RHEL 7.
Obviously, we are now going to migrate production to it, right in the
middle of the Alpha freeze. :P
More seriously, if anyone wants to try it out, here's an easy way. Save
the attached file into /etc/rpkg/fedpkg-stg.conf, then:
$ alias fedpkg-stg="fedpkg --config=/etc/rpkg/fedpkg-stg.conf"
Then use the fedpkg-stg command the way you'd use fedpkg (try cloning,
Things seem to work fine so far, but we need more testing, of course.