Christian,
I too, have faced this problem while upgrading from 2.0.21 to 2.5.7
The 'invalid utf8 character' may be only a symptom of the problem.
My only guess is around the following -
- the database was using 'latin1' as default charset, RB 2.5.x expects
'utf8'. So some mismatch/warning results.
- the database was using 'MyISAM' with which the evolution fails; one
has to change the engine to 'InnoDB' before evolution.
If you want a sample diff, I can possibly produce it - let me know how,
please give me step by step instructions.
Bottomline, this upgrade has not yet been successful for me.
Any help is appreciated.
Thanks
Koushik Roy.
--
Supercharge your Review Board with Power Pack:
https://www.reviewboard.org/powerpack/
Want us to host Review Board for you? Check out RBCommons:
https://rbcommons.com/
Happy user? Let us know! https://www.reviewboard.org/users/
---
You received this message because you are subscribed to the Google Groups
"reviewboard" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
