The support to debian 6 was dropped, so this compatibility layer is not needed anymore.

  On OBS the build system is quite particular and it has to work in a specific way,
  This file handles the difference between build from source and prepare things to OBS.

It will allow to track behaviour of the test on various test nodes.

Drop not needed references and logic for ssl_ca_crt old implementation.

  This version only display informations to change keyboard and set a NDB.

In "caddy-frontend: Improve generated files" ssl_ca_crt was mistakenly used
for client authentication, which is in reality not supported nor needed.

It came from misunderstanding of apache configuration.

custom_domain and server-alias on given slave do not have to clash, and
can be deduplicated during request parameter analysis.

/reviewed-on !444

Since caddy-frontend: Support wildcards the wildcards are supported.

server-alias and custom_domain can be wildcards, so support such case.

/reviewed-on !446

The assertion was fixed incorrectly.

By setting maxDiff to None the test failures are more explanatory.

authorised --> authorized

Because of checking slave id in a whole string, slaves which shall not be
authorized has been put on authorized list.

Example: -frontend-authorized-slave-string == "custom_http",
         slave_id = "custom" has been authorized.

As test_https_url proves, the separation of url and https-url is correctly
implemented.

The case where test runner is not enabled got broken in
2a457867

This time, we had test to prevent regression.

/reviewed-on nexedi/slapos!440

So that it renders correctly on https://pypi.org/project/slapos.cookbook

I checked with :
 * `python setup.py checkdocs`
 * `python setup.py check --restructuredtext`

as described on https://stackoverflow.com/questions/16367770/my-rst-readme-is-not-formatted-on-pypi-python-org

/reviewed-on nexedi/slapos!441

we are using trafficserver nowadays, varnish recipe is deprecated

with minimal tests to reproduce the issue that instanciation is broken
when no test runner.

note that we don't put tests in "one big test.py", but from the
beginning we separate so that we can put test for each software type in
test/test_$(software type).py and test for default software type in
test/test_erp5.py

The case where test runner is not enabled got broken in
2a457867