first, the symlink was just not created because a variable wasn't
passed properly.

second, permissions were fixed on the directories only on installs,
which is error-prone: we should fix them all the time.

see #2003712

provision is just a drush extension, no need to configure the
webserver directly here. if users want to use provision by hand, they
should be able to create that symlink themselves.

the trade off between duplicating the checks and logic between the two
packages just wasn't worth it

This reverts commit 7d5f546e.

those are drush packets that spew out on stderr

This reverts commit 59a0a654.

it seems that those packets are sent to stderr, so we merge stderr
into stdout. we also pass the --debug flag to backend-parse so that it
actually shows the debug output when debugging is enabled

otherwise the other provision commands will not work properly

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.

apache2 remains the default

email sending should work regardless of the MTA used...

this is done partly in part of this complaint: #1800066