This machine was purchased and shipped to the OSL per bug 170463. We have a 'soc.gentoo.org' DNS alias that points to a machine that is not currently up. We have no soc.dev.gentoo.org (per 170463's summary). Do we know where this box is and whether we can get it up? Thanks -Alec
It (vulture.g.o) is up, and on the new cfengine now. What do you want on it?
Can you please install git daemon on soc.dev? I want to be able to use a git:// link for the git repos hosted on the machine so they can be accessed from the web file interface (Redblade) hosted on soc.gentooexperimental Thanks, Seraphim
The actual git repos are on git.overlays, not soc.dev. I haven't seen any request for git repos from you. pakhuchiy and bkheeling have got theirs already. http://git.overlays.gentoo.org/gitweb/?p=proj/autotua.git;a=summary http://git.overlays.gentoo.org/gitweb/?p=proj/etc-managed-with-git.git;a=summary Having them centrally gets them into our backup system.
Robin, could I have one too ;) I guess Clutering-liveCD would be adequate.
(In reply to comment #4) > Robin, could I have one too ;) I guess Clutering-liveCD would be adequate. > Surely you mean cluStering-livecd? ;)
kyron: use the tmeplate on the git.overlays page please, and email it. i'll do it later tonight or tmrw morning.
I would like to deploy the (pre-alpha uber-testing) AutotuA master server on soc.dev.gentoo.org sometime next week. Having a master-server setup is important for testing since it's inconvenient for a tester to have to setup both master _and_ slave on his machine to test AutotuA. The master-server's web interface is still in it's infancy, but I should have it user-navigable within this week. Hence, I would like it if soc.dev.gentoo.org would have www-servers/lighttpd[fastcgi] installed (if there isn't another webserver already) I would also need dev-python/python-fastcgi + =dev-python/django-9999[sqlite] + =dev-lang/python-2.5[sqlite] to run the master and the slave Thanks! :)
It looks like this bug can be closed now. Any objections?
(In reply to comment #8) > It looks like this bug can be closed now. Any objections? > timeout.