tags 296403 + needhelp moreinfo unreproducible thanks Hello
Sadly, I'm still not able to reproduce the bug :-( On 2005-02-28 sean finney wrote: > On Sun, Feb 27, 2005 at 08:31:27PM -0500, Joe Drew wrote: > > + '[' -f /etc/mysql/dpkg__mysql_should_be_started ']' > > + exit 0 > > so that file wasn't there because it's only created by the preinst > script during fresh installs. No, it's mainly created by the last version's prerm script if "/usr/bin/mysqladmin --defaults-extra-file=/etc/mysql/debian.cnf ping" gives some output which is "mysqld alive" if the server is currently running. The calling order in your case (4.1.9-2 to 4.1.10-1 is) (old) mysql-server-4.1.prerm upgrade 4.1.10 (new) mysql-server-4.1.preinst upgrade 4.1.9 (old) mysql-server-4.1.postrm upgrade 4.1.10 (new) mysql-server-4.1.postinst configure 4.1.9 for a fresh install it would be (new) mysql-server-4.1.preinst install (new) mysql-server-4.1.postinst configure If it's an upgrade and mysqld was running the flag is set in (old)prerm else if it's a fresh install then (new)preinst sets it in every case. > +if [ "$1" = "install" -o "$1" = "upgrade" ]; then No, that would be the same as unconditionally start the server at the end of postinst but the intend was to preserve the running state before the upgrade or start the server if it is a fresh install. I've spend the evening with up and downgrading various versions using file-rc and sysv-rc but it always worked :-/ It would be very helpful to get the output of the *complete* upgrade process inclusive the prerm when running with "set -v -x" or with "export DEBIAN_SCRIPT_DEBUG=1". Thanks! bye, -christian- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
