On Wed, Feb 1, 2012 at 5:19 AM, lkcl luke <[email protected]> wrote:
>
> ok, i've just added peter and anthony to both these projects: i had
> one other person ask me, i can't remember who it was now, can you
> remind me, if you can remember who you are? :)

i should have already been enabled? i've been using for some time now.

> the git clone commands are:
>
> git clone [email protected]:pyjamaslamson
> git clone [email protected]:pyjamasgitweb
>
> anthony, please use that rather than arse about trying to bypass
> gitolite - it'll only end in tears

i have been using that ;-) i've put about 20 commits or so on
pyjamaslamson over the last week getting it into shape.

> (i managed to screw things up by
> accidentally setting the permissions of one of the files in the object
> store to "daemon" how the hell i did it i really don't know, had to go
> in and chmod/chown things to fix it).

i saw that ... i thought i fixed it but maybe i got distracted.
anyways, the permissions are totally !@#$ all over the place ... it
doesn't affect most things, but i am slowly working to consolidate
everything under the `pyjs.org` user, a single application server
[uWSGI], and better webserver [mongrel2, possibly uWSGI].  right now
stuff is spread all over in funky places, duplicates, obsolete
attempts, varying permissions ... you've been hard at work ... and
committing *everything* along the way, without removing ;-)

... also, we have a problem with `git://` and `ssh://gitolite`; for
some reason they are exporting different directories ...

git-daemon == /var/cache/git/
gitolite == /var/lib/gitolite/repositories/

... why? it's unnecessary and causing weird problems, eg. in
pyjamaslamson, `git status` == "ahead [...] by 14 commits", but a `git
push` == "Everything up-to-date".  i'll change git-daemon to export
the gitolite repos directly before i sign off for the night.

-- 

C Anthony

Reply via email to