hi guys,
i looked a little more into this...
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.
christian: i looked throu
sean finney wrote:
could you throw a "set -x" in the top of the postinst script and
send us the output?
Sure can!
[EMAIL PROTECTED]:~# /var/lib/dpkg/info/mysql-server-4.1.postinst configure
+ export
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/sbin:/usr/sbin:/bin
Hello Sean
On 2005-02-27 sean finney wrote:
> could you throw a "set -x" in the top of the postinst script and
> send us the output?
BTW: I put a special variable in all of my scripts so that you can
you get "set -x" and "set -v" after
export DEBIAN_SCRIPT_DEBUG=1
BTW2: I'm currently fo
hi joe,
could you throw a "set -x" in the top of the postinst script and
send us the output?
sean
--
signature.asc
Description: Digital signature
Package: mysql-server-4.1
Severity: serious
It looks as though the postinst is trying to stop mysql instead of
starting it. I had a working mysql installation previous to this, and
I haven't seen this problem before.
Relevant portions of the upgrade log are below.
Preparing to replace mysql-serv
5 matches
Mail list logo
