XiVO GIT repository re-organisation

GIT_DIRECTORY specify the repository to use

GIT_DIRECTORY=xivo-${XIVO}
The subdirectory relative to SOURCE_GIT in which the repository
is to be found. The actual clone is composed as follows:
git clone ${SOURCE_GIT}/${GIT_DIRECTORY}.git
as of October 2011, there is a single repository named after the
XIVO variable, hence the default xivo-${XIVO} value. It will
progressively be replaced by individual repositories that can be
used as follows:
packaging-farm DIRECTORY=pf-xivo-confgen GIT_DIRECTORY=xivo-confgen submit
so that it uses:
http://git.proformatique.com/?p=official/xivo-confgen.git
instead of
http://git.proformatique.com/?p=official/xivo-skaro.git

GIT_DIRECTORY
specify the repository to use in submit-xivo.sh. Although it is only
applied to the source git directory, the name of the variable does not
contain the word SOURCE. This is in anticipation to the fact that the
debian and source repositories will eventually be merged. Even if this
does not happen, the structure of both repositories is planned to be the
same in the transition phase and the need to distinguish a directory
name that would be different is unlikely.

When reading the error, it is obvious that the removal of control.in is
the source of the error.The success of a debian package build is tested
by looking for the dpkg-genchanges -b string in the output. This is the
last step of packaging and there cannot be any error after this. Errors
that occur before running dpkg-genchange will end the script immediately
and the string will not be found. However the script looking for
dpkg-genchange did not test for a failed run of dpkg-genchange. It is a
rare condition.The status.sh script now checks if the run of
dpkg-genchange is
successful.