the directory which contains the pubkeys must be in lower case

Change-Id: I23176efed0f1778d905bca372a605d3806ab79f7
Added variables DOING_UPGRADE, DOING_RECONFIGURE etc. in debian scripts

These variables can be used to selectively do things only on first
installation, during an upgrade etc. To make sure that everything works
as expected currently the values are logged to stderr (debconf can get
confused when using stdout).

Change-Id: I20400e9d57892db398e8ee531d9b05548932ce52
fix broken result tab of ocra/ocra2 rollout

for manage and for selfservice

Change-Id: Ieb6f98d4f55f054fe2f07b4f9a1740dd6c87d080
Merge "fix broken result tab of ocra/ocra2 rollout" into branch-v2.7.1
fix fail of selenium test

Change-Id: Id81b8573c73d438ddbfb85d4dd1ee6ce1c8c9da1
(cherry picked from commit 5b91fa8770b5498f6e31254af18c46927df2366b)
adjusted requirements for seleniumtest to depend on LinOTPAdminClientCLI

Change-Id: Ic41d9b9ab15ed8bbfcf6f8046d10c335cbfff5d5
Fix ask_createdb debconf question being asked on upgrade

linotp/mysql/ask_createdb is a debconf question asked during
installation of the LinOTP debian package. Depending on the users answer
it will automatically create a MySQL database. Most users would probably
select 'Yes' (stored as 'true').

In LinOTP 2.5.X it was discovered this caused some problems because
since debconf stores 'true', in some cases it would try to re-create the
database on package upgrade.

The solution implemented in LinOTP 2.6 was to do a debconf RESET of
linotp/mysql/ask_createdb in the postinst script. The problem with RESET
is, it deletes all flags, including the 'seen' flag.

This means that from LinOTP 2.6 onwards when doing a manual package
upgrade the question "Do you want to create the LinOTP 2 database, now?"
is asked again (regardless of the fact that the databse already exists -
in most cases at least).

The first part of this fix is doing a debconf SET false instead of RESET
in the postinst script.

The second part is to set the 'seen' flag of the question to true when
detecting you are upgrading from a LinOTP version between 2.6
(inclusive) and 2.7.1.

refs #12298
closes #12718

Change-Id: I655983592437aa25e70b35b359fae1027898e673
Set some debconf questions to false in debian postinst

These values are only relevant during first installation and should not
be used during an upgrade.

A dpkg-reconfigure can be used to reset the debconf database and repeat
all questions.

Change-Id: I65f5c7e24bbfb94dd868c982a1785dafa474d8e9
Merge topic 'debconf' into branch-v2.7.1

* changes:
  Set some debconf questions to false in debian postinst
  Fix ask_createdb debconf question being asked on upgrade
  Added variables DOING_UPGRADE, DOING_RECONFIGURE etc. in debian scripts
fixed fuzzy translation flag

Change-Id: I401cddc30bbadbc5bbed72f43b860a6ea79537ef
Move block that fixes ask_createdb issue

On Ubuntu 12.04 the debian/config check_mysql_tables() function has
different results causing a different path in the code to be taken which
means that the debconf FSET is not executed.

Now FSET is always executed when using a MySQL database, and upgrading
from a LinOTP version between 2.6 (inclusive) and 2.7.1 .

Also fix a small issue that could have lead to big problems: dpkg
--compare-versions returns a non-zero value when the check fails. Since
errexit is set this means that the whole config script would die,
preventing the package from being installed. By surrounding the block
with 'set +e' and 'set -e' this issue is prevented.

closes #12718

Change-Id: Id766a51473ec830ac6a7b93ea4e19bf45def8b6f
Fix small error in German translation

Change-Id: I8586b48e13934d004e9e47c7596fbb169f2bebe7
Merge "Move block that fixes ask_createdb issue" into branch-v2.7.1
Merge branch 'branch-v2.7.1' into master

Conflicts:
	linotpd/src/linotp/lib/tokens/ocra2token.mako

Change-Id: Iaf35ca720937c67bc50b3eb9c7d58d4a7ab39415