Package: pdns-backend-mysql Version: 4.0.2-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts
Hi, during a test with piuparts I noticed your package fails to upgrade from 'jessie'. It installed fine in 'jessie', then the upgrade to 'sid' fails. >From the attached log (scroll to the bottom...): Setting up pdns-server (4.0.2-1) ... Installing new version of config file /etc/init.d/pdns ... Setting up pdns-backend-mysql (4.0.2-1) ... Determining localhost credentials from /etc/mysql/debian.cnf: succeeded. dbconfig-common: writing config to /etc/dbconfig-common/pdns-backend-mysql.conf Replacing config file /etc/dbconfig-common/pdns-backend-mysql.conf with new version Replacing config file /etc/powerdns/pdns.d/pdns.local.gmysql.conf with new version creating database backup in /var/cache/dbconfig-common/backups/pdns-backend-mysql_3.4.1-4+deb8u6.2017-01-14-15.05.20. applying upgrade sql for 3.4.1-4+deb8u6 -> 4.0.1-6. error encountered processing /usr/share/dbconfig-common/data/pdns-backend-mysql/upgrade/mysql/4.0.1-6: mysql said: ERROR 1074 (42000) at line 15: Column length too big for column 'comment' (max = 21845); use BLOB or TEXT instead dbconfig-common: pdns-backend-mysql configure: aborted. dbconfig-common: flushing administrative password dpkg: error processing package pdns-backend-mysql (--configure): subprocess installed post-installation script returned error exit status 1 Processing triggers for libc-bin (2.24-8) ... Processing triggers for systemd (232-10) ... Errors were encountered while processing: pdns-backend-mysql This was observed during a jessie->sid upgrade which picked a mysql-5.5 -> mysql-5.7 upgrade for the database server. Feel free to downgrade the severity if this bug is specific to that weird combination. cheers, Andreas
pdns-backend-mysql_4.0.2-1.log.gz
Description: application/gzip
