[MDEV-14658] Selecting certain versions in mariadb_repo_setup results in failed install and broken repository Created: 2017-12-14 Updated: 2017-12-18 Resolved: 2017-12-16 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Configuration |
| Affects Version/s: | None |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Minor |
| Reporter: | Juan | Assignee: | Kolbe Kegel (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Environment: |
Tested on Centos 6 & 7 |
||
| Description |
|
Looking at https://downloads.mariadb.org/mariadb/+releases/ one could be led to think 10.0.10, the first stable 10.0 release, is a good one to install. Running
does not result in any errors. It concludes normally.
However, then trying to install the server results in an error
and tryign to install any package after that also results in an error
Subsequently selecting a package that does exist in the repository and running mariadb_repo_setup again results in a successful installation. |
| Comments |
| Comment by Daniel Black [ 2017-12-15 ] |
|
I strongly suspect --mariadb-server-version only takes a major version like 10.0 rather than a specific release version like 10.0.10 |
| Comment by Sergei Golubchik [ 2017-12-15 ] |
|
Not really, 10.0.29, for example, works. I didn't try to install ☺ but looking at the url — https://downloads.mariadb.com/MariaDB/mariadb-10.0.29/yum/rhel/ — it should. While for 10.0.10 — https://downloads.mariadb.com/MariaDB/mariadb-10.0.10/yum/rhel/ — it doesn't. |
| Comment by Kolbe Kegel (Inactive) [ 2017-12-15 ] |
|
The issue here is that the directory structure for releases changed at some point. The script can only support the new directory structure, and I don't think investing a lot of time into changing that makes sense. I think "10.0.10, the first stable 10.0 release, is a good one to install" is troubling logic, and I'm not inclined to change this repository configuration script to make it easier to install old software with lots of known security, stability, and other bugs ... |
| Comment by Juan [ 2017-12-18 ] |
|
I'm not sure I understand the logic "trouble" with a customer choosing to install something MariaDB calls "a stable release" unless there's a problem trusting MariaDB's assertion that 10.0.10 is stable & supported. |
| Comment by Kolbe Kegel (Inactive) [ 2017-12-18 ] |
|
The salient point here is that it was never possible to use mariadb_repo_setup (or the "MariaDB Package Repository") to install MariaDB Server 10.0.10. The directory structure of releases changed to more easily facilitate package repository configuration with the MariaDB Server 10.0.18 release, a couple years before "MariaDB Package Repository" was created. Anyone who installed MariaDB Server 10.0.10 will have done so using the repository configuration tool at mariadb.org or by downloading the packages directly or via some other means. Those options continue to be available for anyone who needs to install older product releases not supported by the MariaDB Package Repository. |