This bug was introduced in dbconfig-common 2.0.3, which is in Xenial. The fix is already in Debian as 2.0.4 (along with a couple other fixes). What is necessary to get dbconfig-common 2.0.4 into Xenial?
This bug was introduced in dbconfig-common 2.0.3, which is in Xenial. The fix is already in Debian as 2.0.4 (along with a couple other fixes). What is necessary to get dbconfig-common 2.0.4 into Xenial?