[Bug 548324] Review Request: gitolite - Highly flexible server for git directory version tracker

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.


https://bugzilla.redhat.com/show_bug.cgi?id=548324





--- Comment #9 from Lubomir Rintel <lkundrak at v3.sk>  2010-01-08 03:38:20 EDT ---
Hi Gerd,

(In reply to comment #7)
> The name of the patch is changed, but not the name of the source-file.
> 
> I suggest to extend the two lines in the spec-file from
> 
> # $ make ed2bf5.tar
> Source0:        ed2bf5.tar
> 
> to
> 
> # $ make ed2bf5.tar
> # $ mv ed2bf5.tar gitolite-%{version}.tar
> # $ gzip -9 gitolite-%{version}.tar
> Source0:        %{name}-%{version}.tar.gz  

Umm, that was an upstream decision (the file name), we don't usually rename
upstream tarballs and I'm reluctant to do so.

(In reply to comment #8)
> I tried gitolite from the git. The command to clone the "testing" repository
> works
> with:
> 
> $ git clone gitolite:testing.git
> 
> but using the username and hostname
> 
> $ git clone <user>@<host.domain>:testing.git again2
> 
> gives out the following error:
> 
> Initialized empty Git repository in /home/gz016/gitolite/testing/again2/.git/
> fatal: 'testing.git': unable to chdir or not a git archive
> fatal: The remote end hung up unexpectedly
> [gz016 at hilton testing]$  

The <user> above is always "gitolite". Gitolite doesn't use UNIX
users/permissions to implement access control, it implements its own and
determines the user name from the key used.

Therefore, after initial checkout of gitolite-admin, add your key there, push
back and you should be able to access the repositories.

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.