Bug #19357 | mysql_upgrade calls fix_priv_tables with --silent which is a no-op | ||
---|---|---|---|
Submitted: | 25 Apr 2006 21:56 | Modified: | 3 Aug 2006 10:47 |
Reporter: | Christian Hammers (Silver Quality Contributor) (OCA) | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Server: Packaging | Severity: | S3 (Non-critical) |
Version: | 5.0.22-BK, 5.0.20a | OS: | Linux (Debian GNU/Linux Sid) |
Assigned to: | CPU Architecture: | Any |
[25 Apr 2006 21:56]
Christian Hammers
[26 Apr 2006 7:19]
Peter Laursen
I have another experience on SuSE 10 and MySQL 5.1.9 (glibc23 RPM build) from yesterday. first: mysql_upgrade was not copied from the RPM package next: mysql_fix_privileges_tables did not display a comma! Actually i am in doubt if it exectued OK ... My opinion .. keep it noisy - I want to see what is happening :-)
[26 Apr 2006 12:03]
Valeriy Kravchuk
Thank you for a bug report. Verified just as described with 5.0.22-BK: openxs@suse:~/dbs/5.0> grep silent bin/mysql_upgrade $bindir/mysql_fix_privilege_tables --silent $args $bindir/mysql_fix_privilege_tables --silent --user=$user $args openxs@suse:~/dbs/5.0> grep silent bin/mysql_fix_privilege_tables openxs@suse:~/dbs/5.0>
[3 Jul 2006 10:47]
Joerg Bruehe
Any experience with previous releases (5.0.22, 5.1.9) is becoming invalid now as 5.0.23 will see the fix of bug#18516: The binary "mysql_upgrade" will be included in all packages, replacing the shell script with the same name. For 5.1, this should happen with 5.1.12-beta (fixing bug#20556). Please check with 5.0.23 (to be published this week, or next) or 5.1.2-beta (later) whether it still behaves in a way you think inapproppriate.
[3 Aug 2006 23:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".