Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Fixed
-
None
-
None
Description
The base_url / deb_repo_maxscale changes from /maxscale/ to /maxscale-enterprise fixed installation for the most recent Maxscale Enterprise 25.01 release, but broke it for all prior releases that still are in the maxscale/, not the maxscale-enterprise repositories.
I only tested this for apt/deb releases on Ubuntu and Debian so far, but assume that the same is the case for RPM based distributions, to.
We either need to make sure that older release packages are copied over to the new maxscale-enterprise repository, or fix the repo setup script to distinguish between older and current/future major releases and set up the repository base URL accordingly.
./mariadb_es_repo_setup --token="...token..." --apply --mariadb-maxscale-version=22.08.12 --verbose --skip-server --skip-tools
|
|
|
# [info] Checking for script prerequisites.
|
|
|
|
|
# [info] Token is valid.
|
|
|
|
|
# [info] Repository file successfully written to /etc/apt/sources.list.d/mariadb.list
|
|
|
|
|
# [info] Adding trusted package signing keys...
|
|
|
|
|
# [info] Running apt-get update...
|
|
|
E: The repository 'https://dlm.mariadb.com/repo/...token.../maxscale-enterprise/22.08.12/apt focal Release' does not have a Release file.
|
|
|
# [error] Failed to add trusted package signing keys
|