[debian-mysql] Etch point releases

[Edward Allcutt]

Norbert Tretkowski wrote:
> Am Montag, den 05.01.2009, 14:18 -0500 schrieb Edward Allcutt:
>> Are there any plans to include MySQL bugfixes in an etch point release?
> Yes, but at very low priority, because I'm personally no longer using
> MySQL 5.0.32 in production.
Admittedly I've been neglecting this myself, but there have been a 
couple point release in the meantime and another security update for 
mysql in etch.

>> The logs for some bugs (#464218, #480954, #453127) indicate this is 
>> planned but there have been 3-4 etch point releases since the last 
>> activity and nothing for mysql.
> 
> Right, it's still on my TODO list, but as you realized already, my main
> focus is on MySQL 5.0.51a in lenny and 5.1.30 in experimental.
> 
>> If there's anything I can do to help getting bugfixes into the next 
>> point release please let me know.
> 
> Send patches! :-)
#453127 has a patch which you applied to then testing. This is fairly 
minor and doesn't affect most users but you did say it was on you list 
for the next point release.

#480954 (important) apparently already has a patch committed to svn. Is 
this waiting on anything else?

#464218 (important) seems to me at least as serious a security bug as 
the one that just got a security update in etch (CVE-2008-3963). The 
patch doesn't look as trivial as the others (there are 4 upstream 
commits that all claim to fix it[0]). Perhaps the security team would be 
interested in helping out with this?

[0] http://lists.mysql.com/commits/24675
     http://lists.mysql.com/commits/25401
     http://lists.mysql.com/commits/25516
     http://lists.mysql.com/commits/26070

-- 
Edward Allcutt
Network Operations
Gleim Publications