Probably. It’s not hurting anything to leave it there and not causing any other impact.
Well, it installs the compat-openssl10 package, which is affected by a number of CVEs right now. I know we’d only be affected by these CVEs if we were using a MySQL client that requires these older libraries, but it would be nice to have an easy, elegant way to remove the compatibility packages to keep our vulnerability scanner from complaining.
Side note, you do know that 5.7 dies in 40 days right? I’m hoping that this testing is prep for upgrade to 8.0
Yes! In fact you provided a very useful answer in another thread I opened regarding upgrading: InnoDB assertion failure crash when altering then optimizing table after upgrade from MySQL 5.7 to 8.0 - #6 by matthewb
But the MySQL 8 version of this compatibility package will also be installed as a dependency of the MySQL 8 version of the client. I just used 5.7 as an example since that’s the version my test VM happened to have installed when I started this thread.