List:Packagers« Previous MessageNext Message »
From:Lenz Grimmer Date:September 11 2003 9:06am
Subject:Re: MySQL 4.0.15 has been released
View as plain text  
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

On Thu, 11 Sep 2003, Christian Hammers wrote:

> On Thu, Sep 11, 2003 at 11:13:10AM +0300, Michael Shigorin wrote:
>
> > Is this relevant for 3.x?  If yes, then is it going to be fixed?

Yes, it also applies to 3.23.xx and I am working on releasing 3.23.58 at
this very moment. Ideally I wanted to publish both at the same time, but
as usual Murphy struck again.

> > If no, then is there a standalone patch for this issue?

The patch below is correct. You can also find it in our BK tree:

http://mysql.bkbits.net:8080/mysql-3.23/diffs/sql/sql_acl.cc@ style="color:#666">stripped?nav=index.html|ChangeSet@-8w|cset@stripped|hist/sql/sql_acl.cc

> Something else that MySQL could do for it's porters would be to announce
> fixed for backports at least at the same time the new version is
> uploaded.

Yes, I should have done that before sending out the public release - my
bad.

> For now, the submitter on the bugtrag mailing list gave us a fix. It's
> untested (while we're at it, MySQL could confirm that the fix is ok
> because also easy looking patches sometimes fix only half of the
> problem...)

As stated above, it's the correct fix. It simply took us way too long to
get the new release out. This is something we need to discuss.

Bye,
	LenZ
- -- 
 Lenz Grimmer <lenz@stripped>
 Senior Production Engineer
 MySQL GmbH, http://www.mysql.de/
 Hamburg, Germany

 For technical support contracts, visit https://order.mysql.com/?ref=mlgr
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux)
Comment: For info see http://quantumlab.net/pine_privacy_guard/

iD8DBQE/YDszSVDhKrJykfIRAoj5AJ0bQCzoI3Fw0+k0tp4+0oO/tMppDgCeOBxh
mxz/KLFNsh6hfC7Q7GW9vOo=
=IbbD
-----END PGP SIGNATURE-----
Thread