Updating to current release

[MTecknology]

I'm trying to upgrade to the current release of mantis. I'm coming from the package maintainers version. I threw in the new code and started running the update process. The first error complained about a vote column not existing in a table to drop. I dropped it and moved on. Now I'm at this error.

"Add primary key on mantis_project_version_table 0.17-jf-9 ERROR: Multiple primary key defined"

I went to the table and I only see one primary key set up on this table. It's set to 'id'.

Thanks,


----
I did a Print All and attached the file.

[autra]

I had the same problem.

From which version of mantis do you want to upgrade ?

My solution :
-Reinstall the previous version.
-Close your mantis session
-Delete navigator cache, cooking.
-Upgrade your code
-Restart your navigator and run the DB upgrade.

It works for me. And if the upgrade process is successful, ignore all other messages saying that your database is out of date.

Hope this will help, please tell me !

[MTecknology]

Sorry, I had a late night and got a little too frustrated. I wound up wiping the database clean and struggling through a fresh setup. Which shouldn't have been to difficult but was.

I think my issue came because of the massive leap in versions.

[autra]

From which version do you want to update ?

[artgroup]

I have the same problem with a fresh release 1.1.2. I tried many times and I always have a massive number of error while trying to upgrade the database using the Admin utilities.

Most of this upgrade are probably already into 1.1.2 so that there are a lot of duplicate entry error or table already exists.
The only workaround is to manually add an entry into the mantis_upgrade_table with the upgrade_id that fails, for example the first upgrade that fails is:
0.17-jf-9

just run this script from SQL: INSERT INTO `mantis_upgrade_table` (`upgrade_id`, `description`) VALUES ('0.17-custom-field-1', 'FORCED PATCH');