Package: mysql-server
Version: 5.0.18-8
Severity: normal

Hello,

when upgrading from 4.1 to 5.0, I get a message "cannot upgrade if ISAM
tables are present". Ok... why not convert them? But hey, the old server
which could have done it is already removed at the time I get this
message, and the installation process just bails out... bummer!

I suggest that the upgrade script _first_ determines if there are any
ISAM tables left over, then offers to automatically convert them to
MyISAM (or just do it, don't know), and then removes the old server and
installs the new one, not the other way round. Currently, I have:

$ dpkg -l mysql-server
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err:
uppercase=bad)
||/ Name           Version        Description
+++-==============-==============-============================================
iU  mysql-server   5.0.18-8       mysql database server (current version)


Thank you!


Best,
--Toni++

PS: No need to fix it just for me...


-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.4.27-2-686-smp
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages mysql-server depends on:
pn  mysql-server-5.0              <none>     (no description available)

mysql-server recommends no packages.

-- debconf information:
* mysql-server/skip_networking: false
  mysql-server/really_downgrade_from_41: false
  mysql-server/want_chroot: false
* mysql-server/start_on_boot: true
  mysql-server/postrm_remove_databases: false
* mysql-server/mysql_install_db_notes:
  mysql-server/nis_warning:
  mysql-server/mysql_update_hints1:
* mysql-server/postrm_remove_database: false
  mysql-server/fix_privileges_warning:


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to