#510232 upgrade wording about changing root password not clear

Package:
mysql-server
Source:
mysql-8.0
Description:
MySQL database server and system database setup
Submitter:
Date:
2010-07-01 18:33:04 UTC
Severity:
wishlist
#510232#5
Date:
2008-12-30 18:16:35 UTC
From:
To:
When we upgrade we are greeted with this screen that mentions setting
a mysql root password.

The problem is the wording is not entirely clear as to if your script
has detected we presently have no root password, and should make
one -- or if perhaps we might already have one...
#510232#10
Date:
2008-12-30 18:26:20 UTC
From:
To:
Am Mittwoch, den 31.12.2008, 02:16 +0800 schrieb jidanni@jidanni.org:

You should not get asked for a password during an upgrade. From which
version did you upgrade to 5.1.30-2? Was it 5.1.30-1, or a 5.0 release?

	Norbert
#510232#15
Date:
2008-12-30 18:45:19 UTC
From:
To:
Let me start of by saying I haven't actually ran mysql in a year via
rcconf, and had it on hold in aptitude to save wasted downloading.
However upon moving from sid to experimental, I decided to clear all holds.

NT> You should not get asked for a password during an upgrade. From which
NT> version did you upgrade to 5.1.30-2? Was it 5.1.30-1, or a 5.0 release?
/var/log/aptitude:
[INSTALL, DEPENDENCIES] libmysqlclient16
[INSTALL, DEPENDENCIES] mysql-client-5.1
[INSTALL, DEPENDENCIES] mysql-server-5.1
[REMOVE, DEPENDENCIES] mysql-client-5.0
[REMOVE, DEPENDENCIES] mysql-server-5.0
[UPGRADE] mysql-client 5.0.51a-13 -> 5.1.30-2
[UPGRADE] mysql-server 5.0.51a-13 -> 5.1.30-2
# grep upg.*mysql /var/log/dpkg.log
2008-12-31 00:07:01 upgrade mysql-common 5.0.75-1 5.1.30-2
2008-12-31 00:57:52 upgrade mysql-client 5.0.51a-13 5.1.30-2
2008-12-31 00:57:53 upgrade mysql-server 5.0.51a-13 5.1.30-2
#510232#20
Date:
2010-07-01 18:22:39 UTC
From:
To:
This message is unclear.  I have a password set, but this message makes it sound like I don't.


mysqld_safe[22351]: PLEASE REMEMBER TO SET A PASSWORD FOR THE MySQL root USER !
mysqld_safe[22351]: To do so, start the server, then issue the following commands:

mysqld_safe[22351]: /usr/bin/mysqladmin -u root password 'new-password'
mysqld_safe[22351]: /usr/bin/mysqladmin -u root -h orange password 'new-password'

mysqld_safe[22351]: Alternatively you can run:
mysqld_safe[22351]: /usr/bin/mysql_secure_installation

mysqld_safe[22351]: which will also give you the option of removing the test
mysqld_safe[22351]: databases and anonymous user created by default.  This is
mysqld_safe[22351]: strongly recommended for production servers.