Skip to content
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

Bump mariadb 10.5 to mariadb 10.7 #2623

Open
Mte90 opened this issue Jun 30, 2022 · 9 comments
Open

Bump mariadb 10.5 to mariadb 10.7 #2623

Mte90 opened this issue Jun 30, 2022 · 9 comments

Comments

@Mte90
Copy link
Member

Mte90 commented Jun 30, 2022

We need to bump the numbers in the *list files (https://github.com/Varying-Vagrant-Vagrants/VVV/blob/e95f4b70d6eada0486b1d77ed91fa01027e56c6a/provision/core/mariadb/sources-ubuntu-focal.list) and in the provision

echo mariadb-server-10.5 mysql-server/root_password password "root" | debconf-set-selections

@tomjn
Copy link
Member

tomjn commented Sep 10, 2022

What's our plan for upgrading those still on 10.5 and 10.4 without breaking things? If we just bump the source to 10.7 it'll break for anyone trying to upgrade on 10.5/4

@Mte90
Copy link
Member Author

Mte90 commented Sep 12, 2022

I didn't saw any issues on upgrading them, I have them also locally on debian and everything worked fine.

@tomjn
Copy link
Member

tomjn commented Sep 12, 2022

When the sources for 10.4 were changed to 10.5, anybody who had 10.4 would fail provisioning when upgrading because it no longer had access to the 10.4 packages it needed to perform the upgrade.

For this reason, we can't just replace the lines for 10.5 with 10.7 in the sources file.

@Mte90
Copy link
Member Author

Mte90 commented Sep 12, 2022

I see in the past we just changed the repositories 8d3e208

If we change the package to mariadb-server it will always use the latest mariadb version available instead to defining the version and as we are defining the repository for the latest version we want I think that we fix everything.

@tomjn
Copy link
Member

tomjn commented Sep 12, 2022

that's because this is an active outstanding bug that has not been resolved

@tomjn
Copy link
Member

tomjn commented Sep 12, 2022

@Mte90 switching to mariadb-server should be a simple swap out though? Even if it doesn't touch this issue it should make upgrades simpler right?

@Mte90
Copy link
Member Author

Mte90 commented Sep 12, 2022

on my experience it is a solution that just works with no problems also with other packages.

@tomjn
Copy link
Member

tomjn commented Nov 7, 2022

now 10.8, as for the problem, we know it happens because people have encountered it and raised issues, no fix was ever implemented for it, so we need a path forwards

@Mte90
Copy link
Member Author

Mte90 commented Nov 7, 2022

I didn't got problems on upgrading the mariadb version so I am not sure about the issues we have right now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants