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

wordpress-mariadb version 10.3 is a legacy version! We recommend upgrading. #72

Closed
sebastienserre opened this issue Jun 4, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@sebastienserre
Copy link

Hello,

On lando 3.21.0, updated I can see this "error" message on a lando rebuild
wordpress-mariadb version 10.3 is a legacy version! We recommend upgrading.

Generating plugin/cli update matrix... done [nothing to update]

 PACKAGE              STATUS       COMMENT  
 ──────────────────── ──────────── ──────── 
 @lando/acquia        ✔ Up to date All good 
 @lando/apache        ✔ Up to date All good 
 @lando/backdrop      ✔ Up to date All good 
 @lando/cli           ✔ Up to date All good 
 @lando/compose       ✔ Up to date All good 
 @lando/core          ✔ Up to date All good 
 @lando/dotnet        ✔ Up to date All good 
 @lando/drupal        ✔ Up to date All good 
 @lando/elasticsearch ✔ Up to date All good 
 @lando/go            ✔ Up to date All good 
 @lando/healthcheck   ✔ Up to date All good 
 @lando/joomla        ✔ Up to date All good 
 @lando/lagoon        ✔ Up to date All good 
 @lando/lamp          ✔ Up to date All good 
 @lando/laravel       ✔ Up to date All good 
 @lando/lemp          ✔ Up to date All good 
 @lando/mailhog       ✔ Up to date All good 
 @lando/mariadb       ✔ Up to date All good 
 @lando/mean          ✔ Up to date All good 
 @lando/memcached     ✔ Up to date All good 
 @lando/mongo         ✔ Up to date All good 
 @lando/mssql         ✔ Up to date All good 
 @lando/mysql         ✔ Up to date All good 
 @lando/networking    ✔ Up to date All good 
 @lando/nginx         ✔ Up to date All good 
 @lando/node          ✔ Up to date All good 
 @lando/pantheon      ✔ Up to date All good 
 @lando/php           ✔ Up to date All good 
 @lando/phpmyadmin    ✔ Up to date All good 
 @lando/platformsh    ✔ Up to date All good 
 @lando/postgres      ✔ Up to date All good 
 @lando/proxy         ✔ Up to date All good 
 @lando/python        ✔ Up to date All good 
 @lando/redis         ✔ Up to date All good 
 @lando/ruby          ✔ Up to date All good 
 @lando/scanner       ✔ Up to date All good 
 @lando/sharing       ✔ Up to date All good 
 @lando/solr          ✔ Up to date All good 
 @lando/symfony       ✔ Up to date All good 
 @lando/tomcat        ✔ Up to date All good 
 @lando/varnish       ✔ Up to date All good 
 @lando/wordpress     ✔ Up to date All good 

As far as lando update can tell you are already up to date!
@sebastienserre sebastienserre added the bug Something isn't working label Jun 4, 2024
@reynoldsalec
Copy link
Member

That's a standard warning when a service version (in this case, your mariadb service version 10.3) is marked as legacy.

I think this does bring up a good inconsistency though, since the MariaDB service apparently has 10.3 as its default version (presumably why it's being used in your WordPress recipe project) and 10.3 is also marked as legacy, which means anyone using the default MariaDB service is probably getting this warning.

I know there have been some issues when I've looked at the update pathway of Mariadb to 10.6 (see lando/mariadb#36 and lando/pantheon#247 (comment) think we need to solve the issue of how to "smoothly" update people to 10.6 and beyond to make it easy/possible to switch to a more current LTS version of MariaDB.

For the time being, I would say either ignore that comment @sebastienserre or upgrade to a newer version of MariaDB while noting that you may need to either destroy your service before upgrading the MariaDB version OR delete the logs a la https://bbs.archlinux.org/viewtopic.php?id=259364.

recipe: wordpress
config:
  database: mariadb:10.6

@sebastienserre
Copy link
Author

Thank you

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants