After upgrading compat level to 10 (in previous commit to avoid warning
on debian:testing, and this is not just a warning, but the compat level
implicitly changed to 10), hardening became working, since it requires
compat level >= 9 [1]
[1]: https://wiki.debian.org/Hardening
While hardening for clickhouse builds should not be used, so just
disable them.
Official CI builds uses ubuntu:20.04, which has the following:
- debhelper: 12.10ubuntu1
- dpkg-dev: 1.19.7ubuntu3 (should not be relevant, but let's keep it)
While debian:testing has:
- debhelper: 13.3
- dpkg: 1.20.5 (should not be relevant, but let's keep it)
In debhelper 13 compat level <= 9 has been deprecated [1], hence the
warning:
warning: Compatibility levels before 10 are deprecated (level 8 in use)
[1]: 427594c413
And this is not only warning but also compat level implicitly will be
changed to 10. For now this is only for debian:testing but in future it
will be relevant for newer ubuntu, and hence official builds.
Those configs was used by clickhouse-test-server, that is used for
ctest, but later does not used on CI, and for debian manifets
with_server was excluded.
So remove those configs not to confuse other people.
Now the script that builds debian package handle this, so I guess it has
installed some gcc version, but uses clang to compile, and this produces
new errors in other builds.
I don't see where it can be required.
And plus there is no python package in debian:testing anymore, only:
- python2
- python3
So that said that you cannot build debian package on debian:testing
anymore (but debian:stable don't have gcc9 for example).
Everything would be great, if there will be packages for python2, i.e.
python2-lxml, but there isn't, I guess because python2 had been
deprecated long time ago...
So it looks like converting to python3 is coming.
Just for the history, now it is:
- debian:stable -> buster
- debian:testing -> bullseye
