2010-06-12 07:33:53 +02:00
|
|
|
#!/bin/bash
|
|
|
|
|
|
|
|
|
|
export TESTDIR=$PWD
|
|
|
|
|
|
|
|
|
|
# prepare local ssh
|
|
|
|
|
mkdir -p $HOME/.ssh; chmod go-rx $HOME/.ssh
|
|
|
|
|
[ -f "$HOME/.ssh/id_rsa" ] || ssh-keygen -q -N "" -t rsa -f $HOME/.ssh/id_rsa
|
|
|
|
|
|
|
|
|
|
# blank out the client side
|
|
|
|
|
rm -rf ~/gitolite-admin
|
|
|
|
|
# make sure we have the u1-u6 keys and the config to refer to them
|
|
|
|
|
cp $TESTDIR/keys/config ~/.ssh
|
|
|
|
|
cp $TESTDIR/keys/u[1-6]* ~/.ssh
|
|
|
|
|
chmod 755 ~/.ssh ~/.ssh/config ~/.ssh/*pub
|
|
|
|
|
chmod 600 ~/.ssh/u?
|
|
|
|
|
|
|
|
|
|
# blank out the server side
|
|
|
|
|
echo the next command MAY ask for a password
|
make REPO_BASE absolute early
$ENV{GL_REPO_BASE_ABS} is meant to point to the same directory as
$REPO_BASE, except it is meant to be passed to hooks, ADCs and other
child programs. And since you can't be sure where the child program
starts in, this became an absolute path.
Gradually, however, I started using it wherever I needed an absolute
path (mostly in code that jumps around various directories to do stuff).
Which is silly, because there's no reason $REPO_BASE cannot also be made
an absolute, even if the rc file has a relative path.
So that's what I did now: made $REPO_BASE absolute very early on, and
then systematically changed all uses of the longer form to the shorter
form when appropriate. And so the only thing we now use the longer one
for is to pass to child programs.
(Implementation note: The actual change is not very big, but while I was
about it I decided to make the test suite able to test with an absolute
REPO_BASE also, which is why the commit seems so large.)
----
This all started with a complaint from Damien Regad. He had an
extremely odd setup where his bashrc changed PWD to something other than
$HOME before anything else ran. This caused those two variables to
beceom inconsistent, and he had a 1-line fix he wanted me to apply.
I generally don't like making special fixes for for non-standard setups,
and anyway all he had to do was set the full path to REPO_BASE in the rc
file to get around this. Which is what I told him and he very politely
left it at that.
However, this did get me thinking, and I soon realised I was needlessly
conflating "relative versus absolute" with "able to be passed to child
programs". Fixing that solved his problem also, as a side-effect.
So I guess this is all thanks to Damien!
2011-03-18 06:29:52 +01:00
|
|
|
ssh gitolite-test@localhost rm -rf .ssh .gitolite .gitolite.rc repositories gitolite-install /tmp/glrb
|
2010-06-12 07:33:53 +02:00
|
|
|
echo the next command SHOULD ask for a password
|
|
|
|
|
ssh-copy-id -i ~/.ssh/id_rsa gitolite-test@localhost
|
|
|
|
|
echo the next command should NOT ask for a password
|
|
|
|
|
|
|
|
|
|
# install it
|
|
|
|
|
../src/gl-easy-install -q gitolite-test localhost tester
|
|
|
|
|
|
|
|
|
|
# add 6 keys
|
|
|
|
|
cd ~/gitolite-admin
|
|
|
|
|
cp $TESTDIR/keys/u*pub keydir
|
|
|
|
|
git add keydir; git commit -m 'added 6 keys'
|
|
|
|
|
git push
|
|
|
|
|
|
|
|
|
|
# make the rollback.tar files on both sides
|
|
|
|
|
cd
|
|
|
|
|
tar cf rollback.tar gitolite-admin
|
make REPO_BASE absolute early
$ENV{GL_REPO_BASE_ABS} is meant to point to the same directory as
$REPO_BASE, except it is meant to be passed to hooks, ADCs and other
child programs. And since you can't be sure where the child program
starts in, this became an absolute path.
Gradually, however, I started using it wherever I needed an absolute
path (mostly in code that jumps around various directories to do stuff).
Which is silly, because there's no reason $REPO_BASE cannot also be made
an absolute, even if the rc file has a relative path.
So that's what I did now: made $REPO_BASE absolute very early on, and
then systematically changed all uses of the longer form to the shorter
form when appropriate. And so the only thing we now use the longer one
for is to pass to child programs.
(Implementation note: The actual change is not very big, but while I was
about it I decided to make the test suite able to test with an absolute
REPO_BASE also, which is why the commit seems so large.)
----
This all started with a complaint from Damien Regad. He had an
extremely odd setup where his bashrc changed PWD to something other than
$HOME before anything else ran. This caused those two variables to
beceom inconsistent, and he had a 1-line fix he wanted me to apply.
I generally don't like making special fixes for for non-standard setups,
and anyway all he had to do was set the full path to REPO_BASE in the rc
file to get around this. Which is what I told him and he very politely
left it at that.
However, this did get me thinking, and I soon realised I was needlessly
conflating "relative versus absolute" with "able to be passed to child
programs". Fixing that solved his problem also, as a side-effect.
So I guess this is all thanks to Damien!
2011-03-18 06:29:52 +01:00
|
|
|
ssh gitolite-test@localhost mkdir -p repositories /tmp/glrb
|
2010-06-12 07:33:53 +02:00
|
|
|
ssh gitolite-test@localhost tar cf rollback.tar .ssh .gitolite .gitolite.rc repositories gitolite-install
|
make REPO_BASE absolute early
$ENV{GL_REPO_BASE_ABS} is meant to point to the same directory as
$REPO_BASE, except it is meant to be passed to hooks, ADCs and other
child programs. And since you can't be sure where the child program
starts in, this became an absolute path.
Gradually, however, I started using it wherever I needed an absolute
path (mostly in code that jumps around various directories to do stuff).
Which is silly, because there's no reason $REPO_BASE cannot also be made
an absolute, even if the rc file has a relative path.
So that's what I did now: made $REPO_BASE absolute very early on, and
then systematically changed all uses of the longer form to the shorter
form when appropriate. And so the only thing we now use the longer one
for is to pass to child programs.
(Implementation note: The actual change is not very big, but while I was
about it I decided to make the test suite able to test with an absolute
REPO_BASE also, which is why the commit seems so large.)
----
This all started with a complaint from Damien Regad. He had an
extremely odd setup where his bashrc changed PWD to something other than
$HOME before anything else ran. This caused those two variables to
beceom inconsistent, and he had a 1-line fix he wanted me to apply.
I generally don't like making special fixes for for non-standard setups,
and anyway all he had to do was set the full path to REPO_BASE in the rc
file to get around this. Which is what I told him and he very politely
left it at that.
However, this did get me thinking, and I soon realised I was needlessly
conflating "relative versus absolute" with "able to be passed to child
programs". Fixing that solved his problem also, as a side-effect.
So I guess this is all thanks to Damien!
2011-03-18 06:29:52 +01:00
|
|
|
ssh gitolite-test@localhost tar -C /tmp -cf \$HOME/rollback2.tar glrb
|