[debian-mysql] Bug#688792: syntax error
Nicholas Bamber
nicholas at periapt.co.uk
Wed Sep 26 17:07:46 UTC 2012
On 26/09/12 17:20, Ross Boylan wrote:
> On Wed, 2012-09-26 at 12:07 +0100, Nicholas Bamber wrote:
>> tag 688792 +moreinfo
>> thanks
> I'm not sure what more info you want.
Well the information you have sent is useful in its own right, but I
have not really got a good idea of all the details. The ideal would be
if you can document how to go from a machine (perferably without an
external myslq instance - but with one if that is part of the issue),
through the building of chroot and so on. But that is the ideal and see
below.
>
> The host mysql was shut down when I ran the install; in fact, I've
> disabled the host start up script mysql, although I haven't touch
> mysql-ndb and mysql-ndb-mgm (I don't know what they do).
This is ringing alarm bells. These are part of MySQL cluster and are no
longer part of the core MySQL product. It may be just that your external
MySQL is just very old.
>
> Do you have any idea what the significance is of the SQL code that
> didn't run?
>
THey are trying to upgrade the privilege tables from an old format.
Probably the SQL should be removed but I need to check that.
> Ross
>> Ross,
>> Thanks for the report.
>>
>> First of all whenever I play with mysql inside a chroot I have to bring
>> down the real mysql server as otherwise there is a port clash. (I'm not
>> sure how piuparts avoids this issue.) And that certainly causes upgrade
>> failures.
>>
>> That said I have not yet managaed to get the postinst script to run
>> that SQL. Given that the code is there that should just be a matter of
>> me studying precisely what is needed to trigger it.
>>
>> Also I am fairly sure that all the maintenance scripts need a thorough
>> review but I am trying quite hard to not make any non-essential changes
>> until the freeze is over.
>
More information about the pkg-mysql-maint
mailing list