we were constantly changing to git, but we are always using git to
download the goods in the makefile now for some reason

The problem with that approach is that it may break build
bots. Besides, if someone wants something else than postfix, they can
install it before Aegir is installed.

Issue #1800066 updated accordingly

This reverts commit cc6aeabc.

Conflicts:
	debian/control

we need increment from the official release number otherwise dch gives
an error

it's also more logical: if debian/changelog is updated, that means
there was a release at some point

we use the version from the changelog so that we increment reliably

with the previous scheme, builds failed when I added the alpha1
release.

now we also use the jenkins build tag so that this will automatically
increase with new builds.

This reverts commit 836ab5d3.

This reverts commit 454502f0.

this is a rather crude way, to implement this better, we'd need to have a trace of the previous client/site name

IP addresses are managed through the frontend now and passed down
here.

we are not properly handling IP addresses however, as there is a
duplication between the site_ip_addresses and ip_address field.

this deprecates the assign_certificate_ip(), get_ip_certificate() and
free_certificate_ip() in the Provision_Service_http_ssl class. the
clear_certs() function in Provision_Service_http_ssl is also
deprecated.

we also refactor the way the uri-level receipt files are managed to
encapsulate the code in functions and automatically cleanup
certificates within that allocation code.

apache2 remains the default