affects 677057 + bacula usertags 677700 + debian-packaging thanks Hi Andreas! IMHO bacula-director-mysql_5.2.6+dfsg-1 is not broken at all, but leaving Severity: to serious and Cc:ing debian-release@ for an advice. On Sat, 16 Jun 2012 11:49:34 +0200, Andreas Beckmann wrote: > during a test with piuparts I noticed your package fails to upgrade from > 'wheezy'. > It installed fine in 'wheezy', then the upgrade to 'sid' fails. Actually, I was not able to install bacula-director-mysql_5.0.3-1+b1 on a clean wheezy (CD-1_20120618-04:55; d-i_20120508) with the default mysql-server, i.e. 5.5: ===== root@debian:~# apt-get update [...] root@debian:~# apt-cache policy bacula-director-mysql bacula-director-mysql: Installed: (none) Candidate: 5.0.3-1+b1 Version table: 5.0.3-1+b1 0 500 http://cdn.debian.net/debian/ wheezy/main amd64 Packages root@debian:~# apt-get install bacula-director-mysql [...] The following NEW packages will be installed: bacula-common bacula-common-mysql bacula-director-common bacula-director-mysql dbconfig-common libaio1 libdbd-mysql-perl libdbi-perl libhtml-template-perl libmysqlclient16 libmysqlclient18 libnet-daemon-perl libplrpc-perl libpython2.7 mysql-client mysql-client-5.5 mysql-common mysql-server mysql-server-5.5 mysql-server-core-5.5 [...] Setting up mysql-client-5.5 (5.5.24+dfsg-3) ... Setting up mysql-client (5.5.24+dfsg-3) ... Setting up bacula-director-mysql (5.0.3-1+b1) ... dbconfig-common: writing config to /etc/dbconfig-common/bacula-director-mysql.conf Creating config file /etc/dbconfig-common/bacula-director-mysql.conf with new version ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2). unable to connect to mysql server. error encountered creating user: ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) ===== This is caused by the fact that there is no MySQL server running yet. While this could be solved via a Pre-Depends: in bacula-director-mysql, this is actually not possible because the MySQL server could be on a remote location. BTW, this happens to bacula-director-pgsql, too. The story is not finished, given that even installing the MySQL server *beforehand* does not result in a correct installation of bacula-director-mysql: ===== root@debian:~# dpkg-query -W \*mysql\* libdbd-mysql-perl 4.021-1+b1 libmysqlclient-dev libmysqlclient18:amd64 5.5.24+dfsg-3 mysql-client mysql-client-5.0 mysql-client-5.1 mysql-client-5.5 5.5.24+dfsg-3 mysql-common 5.5.24+dfsg-3 mysql-server 5.5.24+dfsg-3 mysql-server-5.0 mysql-server-5.1 mysql-server-5.5 5.5.24+dfsg-3 mysql-server-core mysql-server-core-5.0 mysql-server-core-5.1 mysql-server-core-5.5 5.5.24+dfsg-3 rsyslog-mysql virtual-mysql-client virtual-mysql-server root@debian:~# apt-get update [...] root@debian:~# apt-get install bacula-director-mysql [...] The following NEW packages will be installed: bacula-common bacula-common-mysql bacula-director-common bacula-director-mysql dbconfig-common libmysqlclient16 libpython2.7 [...] Setting up libmysqlclient16 (5.1.62-1) ... Setting up bacula-common-mysql (5.0.3-1+b1) ... Setting up bacula-director-common (5.0.3-1+b1) ... Setting up dbconfig-common (1.8.47+nmu1) ... Creating config file /etc/dbconfig-common/config with new version Setting up bacula-director-mysql (5.0.3-1+b1) ... Creating config file /etc/dbconfig-common/bacula-director-mysql.conf with new version granting access to database bacula for bacula@localhost: success. verifying access for bacula@localhost: success. creating database bacula: success. verifying database bacula exists: success. populating database via sql... error encountered populating database: mysql said: ERROR 1064 (42000) at line 316: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'MaxValue INTEGER DEFAULT 0, CurrentValue INTEGER DEFAULT 0, WrapCounter TI' at line 4 dbconfig-common: bacula-director-mysql configure: ignoring errors from here forwards done. dbconfig-common: flushing administrative password dbconfig-common: bacula-director-mysql configure: ignoring errors from here forwards dbconfig-common: bacula-director-mysql configure: ignoring errors from here forwards Processing configuration...Ok. [.ok.] Starting Bacula Director...:. ===== I could not test the above with mysql-server-5.1, since it is actually not installable as you have already reported: <http://bugs.debian.org/677057> I do not know how to solve this bug, given that IMHO it is not a bug at all: 5.0.3-1+b1 is no more installable on wheezy and 5.2.6+dfsg-1 solves this (the latter installs fine with mysql-server-5.5_5.5.24+dfsg-3). >>From the attached log (scroll to the bottom...): > > Setting up bacula-director-mysql (5.2.6+dfsg-1) ... > Installing new version of config file /etc/bacula/scripts/make_catalog_backup.pl ... > Installing new version of config file /etc/bacula/scripts/make_catalog_backup ... > invoke-rc.d: policy-rc.d denied execution of stop. > dbconfig-common: writing config to /etc/dbconfig-common/bacula-director-mysql.conf > creating database backup in /var/cache/dbconfig-common/backups/bacula-director-mysql_5.0.3-1+b1.mysql. > applying upgrade sql for 5.0.3-1+b1 -> 5.2.0. > error encountered processing /usr/share/dbconfig-common/data/bacula-director-mysql/upgrade/mysql/5.2.0: > mysql said: ERROR 1146 (42S02) at line 21: Table 'bacula.Version' doesn't exist I guess this is the result of the fact that the bacula database is not initialized because of the errors above. Thx, bye, Gismo / Luca
Attachment:
pgpzlfC8Ojox0.pgp
Description: PGP signature