-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problem: 1.16 Release Notes do mention requiring MySQL8 #1694
Comments
@misilot We dropped MySQL 5.x support in Archivematica 1.15.0:
We also added a section to the docs about upgrading MySQL 5.x to 8.x. Does that help? |
Thanks, guess I missed that when upgrading to 1.15 :( Working up converting the collation types. I put a PR in for the deploy-pub to install MySQL 8 (Or upgrade) Though I think this needs to have the major-minor version when it is 8.0 (at least on ubuntu 22.04) since there isn't a package called |
@replaceafill so I am trying to use that script and it errors out on one of the views
|
@mamedin Could you take a look at this when you have a chance? |
It seems database has some views or temp tables. Please, can you try the following script:
Summary of Changes:
|
Thanks @mamedin currently reimporting the database and will test this. |
Thanks @mamedin that worked! It is failing at the migrations now, with tables already existing but I will put in another ticket for that since it seems unrelated to this. |
Perfect, I just added a note to that new issue. Thanks! |
Expected behaviour
Mention that MySQL 8.x is required in 1.16 now
Current behaviour
Does not mention it at https://wiki.archivematica.org/Archivematica_1.16.0_and_Storage_Service_0.22.0_release_notes
Steps to reproduce
Upgrade from 1.15 to 1.16 with the deploy-pub playbook, and it will error out.
Your environment (version of Archivematica, operating system, other relevant details)
Ubuntu 22.04
Archivematica 1.15 upgrading to 1.16
For Artefactual use:
Before you close this issue, you must check off the following:
The text was updated successfully, but these errors were encountered: