Source: mariadb Version: 1:10.11.2-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: affects -1 + mariadb-plugin-gssapi-server
Hi, during a test with piuparts I noticed your package fails to upgrade from 'bullseye'. It installed fine in 'bullseye', then the upgrade to 'bookworm' fails. This test was planned to do a 2-stage upgrade: apt-get upgrade && apt-get distupgrade (the first part does not install any new packages, that will happen in the second part) but the first part already failed. I try to summarize what seems to happen: * In a bullseye chroot (which alles starting services) install mariadb-plugin-gssapi-server * switch sources.list to bookworm, run 'apt-get update' * run 'apt-get upgrade' - this only upgrades mysql-common and mariadb-common - this triggers a mariadb-server-10.5 restart which fails >From the attached log (scroll to the bottom...): ... Preparing to unpack .../24-mysql-common_5.8+1.1.0_all.deb ... Unpacking mysql-common (5.8+1.1.0) over (5.8+1.0.7) ... Preparing to unpack .../25-mariadb-common_1%3a10.11.2-1_all.deb ... Unpacking mariadb-common (1:10.11.2-1) over (1:10.5.19-0+deb11u2) ... ... Setting up mysql-common (5.8+1.1.0) ... ... Setting up mariadb-common (1:10.11.2-1) ... ... Processing triggers for mariadb-server-10.5 (1:10.5.19-0+deb11u2) ... invoke-rc.d: could not determine current runlevel Stopping MariaDB database server: mariadbd. Starting MariaDB database server: mariadbd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [ESC][31mfailed![ESC][0m invoke-rc.d: initscript mariadb, action "restart" failed. dpkg: error processing package mariadb-server-10.5 (--configure): installed mariadb-server-10.5 package post-installation script subprocess returned error exit status 1 Processing triggers for debianutils (5.7-0.4) ... Processing triggers for libc-bin (2.36-9) ... Errors were encountered while processing: mariadb-server-10.5 This might indicate that mariadb-common needs a Breaks: mariadb-server-10.5 I cannot reproduce this by testing default-mariadb-server in the same way, so mariadb-plugin-gssapi-server seems to be needed to trigger that bug. cheers, Andreas
mariadb-plugin-gssapi-server_1:10.11.2-1.log.gz
Description: application/gzip
