Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'm running Kubuntu 14.04 LTS and a client needed MySQL 7+ for a project. I had upgraded MySQL before and these older upgrades never had issues and had no issues of back version support, but after the 7+ install I can no longer login, via phpMyAdmin nor MySQL WorkBench. I've read and there is no back version support from 7 to older version, due to login changes.
I found out after installing that older version support is not possible from MySQL 7, as they made changes to the logins to increase security so not able to use older code/methods on the new and Vice-versa.
Therefore I need to know how to:
Remove the current installation,
Install MySQL 6+ (supported version for 14.04)
Install MySQL 7+ as separate install with separate install folders.
The separate install folders will be critical, to avoid the 7+ install writing over the 6+ version.
Will also have to install phpMyAdmin 4.6.7 that support MySQL 7+ into separate folders as well, so I can create a seperate Apache alias, to be able to switch between the 2 separate versions.
When I last upgraded MySQL I had to run a supplied upgrade script over the databases because the format had changed. That was a move to version 5.7 from a much older version. Was that a required step in your upgrade? Did you do that?
I also had to install a newer version of phpMyAdmin and reconfigure it manually.
Maybe consider a container as a possibility? "perfect for 'projects'"
Docker - requires 64 bit Architecture still, I believe.
Simple bash script installs it. Grab an image. (A "pull") Start it.
Couple of coats of paint and a wing-nut, you'll be right-as-rain
With less complexity than your method above??? And doesn't turn your 14.04 LTS into a Toaster
That is my advice.
The MySql DEVs seem to have expected us! Deploying MySQL on Linux with Docker
I wish I had the vigor and/or motivation to encourage you with your plan. Scares me to death.
.deb files have 2 control files in them. They hold the installation parameters for the package.deb and some other high-level directives necessary for the package Manager.
Because of the MySQL conflicts on my machine, twice on every single time I call for "apt-get install" of anything, it always runs through the MySQL 7 install (twice).
The fresh install always resets all UIDs to only "root" and none of my 3,000+ DBs have root as UID, so can't see them. Then when I finally get MySQL WorkBench to use my default UID, I see my DBs only to have the next apt-get install wipe out all my work.
Now I can't even remember what I had to do to get back my default UID. Think I had to do it via cmd line.
Finally found and resolved the issues, got Ubuntu 14.04 default MySQL installed, then LXD, and the 16.04 MySQL 7.5 in the LXD container, but that does not launch and stay callable by default localhost apps. Still trying to figure out how to launch this on boot and make it callable from localhost.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.