How does somebody upgrade to roundup 2.0 if using mysql?

Hi all:

A patch needed to make tests work with mysql has the side effect of
making a mysql database created with roundup 1.x unusable with roundup
2.0 even if you continue to use python 2.

This is a significant issue that I suspect will prevent a lot of
people from upgrading.

Ralf, Joseph you probably understand this the best. Can you guys write
up an entry in the upgrading docs for this. I will plan on marking
this with a big warning in the release announcement.

IIUC performing an export using roundup-admin under the old tracker
and then creating a new tracker using 2.0 and performing an import
should work. However if you have a tracker of any size, this is a
significant investment in time and disk space that requires the
tracker be placed offline.

Is there any other alternative? Will a database only export (without
files/msgs) work?

I hope there is something missing and we can patch the code to allow
it to use an existing mysql database.

My understanding is that there was a failure with the test bed on
Ralf's system but not when running the same tests under either CI
environment.  My skills aren't up to understanding the problem much
less explaining the testing weirdness and fix it.

Have a great week.

--
				-- rouilj
John Rouillard
===========================================================================
My employers don't acknowledge my existence much less my opinions.