13.04.2012 14:12, AL13N kirjoitti: > 2. do like other distros and fix to higher mysql 5.5.22 which fixes this > issue > ==> this is totally not preferred for me; > A) a big change between mysql 5.5.10 and mysql 5.5.22, which means huge > QA load > B) this also means that the mga1 -> mga2 upgrade will have to be > extensively retested
This would be my preferred option. -- Anssi Hannula
