[MXS-4809] Old maxscale version in debian\ubuntu repo Created: 2023-10-12 Updated: 2023-10-13 Resolved: 2023-10-13 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | Repositories |
| Affects Version/s: | None |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Minor |
| Reporter: | Xela | Assignee: | Daniel Bartholomew |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Description |
|
Hello! When I used mariadb_repo_setup script, it configured following repo:
And maximum version maxscale there is 23.02.4~bookworm-1
But there is a 23.08 version available for download on the mariadb website. |
| Comments |
| Comment by markus makela [ 2023-10-12 ] | |||||||||||||||||||||||||||
| Comment by Daniel Bartholomew [ 2023-10-12 ] | |||||||||||||||||||||||||||
|
I'll need to work with IT to get this fixed. The 'latest' symlink is supposed to point at whatever is the latest release, so something has gone awry with it. | |||||||||||||||||||||||||||
| Comment by Daniel Bartholomew [ 2023-10-12 ] | |||||||||||||||||||||||||||
|
Turns out I didn't need to involve IT after all. I took a look in the tools backend at the MariaDB MaxScale 23.08 release series and saw that it was marked as "Beta" and not "GA". The actual MaxScale 23.08.1 release was marked as GA, but the 23.08 release series was not. This is what was messing up the "latest" symlink as the system looks for the latest GA release series, which was still 23.02. Anyway, I switched the release series to GA and when I did a test install it installed MaxScale 23.08.1. I tested on Ubuntu Jammy and on RHEL 8 and because those work the other repositories should as well. Please check to verify it is working on your side. Thanks! | |||||||||||||||||||||||||||
| Comment by Xela [ 2023-10-13 ] | |||||||||||||||||||||||||||
|
I confirm, it is working on Debian 12.2 (Bookworm). Thank you, Daniel!
| |||||||||||||||||||||||||||
| Comment by markus makela [ 2023-10-13 ] | |||||||||||||||||||||||||||
|
That's perfect! I'll go ahead and close this issue as the problem now appears to be fixed. |