hholzgra, there's an example here of a versioned repo https://mariadb.com/kb/en/library/yum/

Debian/Ubuntu, don't think there's a documented example however http://archive.mariadb.org/mariadb-10.3.3/repo/debian/ probably could be used as the base url.

This is not about per-version repos, this is about multi version repos so that e.g.

apt install mariadb-server=10.2.9

or

yum install mariadb-server-10.2.9

without having to tweak the repository setup itself.

This would also allow to have per-package version policies, e.g. with MDEV-14799, before it was fixed in 10.2.12, I might have wanted to explicitly install mariadb-server 10.2.10, but would be fine to have the then-current mariadb-10.2.11 client package

I could then also use "apt-get hold mariadb-server; apt-get upgrade" to upgrade everything but just that one package.

This would require changing how we build and maintain the repositories. I agree that it would be a good thing to have. The biggest issue is the lack of proper docs on how to do it properly. That was the case the last time I looked into it, maybe it has changed recently. In any case, I'll investigate it.

On RedHat/CentOS/Fedora, this appears to be pretty straightforward to do. It requires updates to the script used to create the yum/dnf repositories, but the changes do not appear to be difficult. This will be in place for all future MariaDB releases. If there are no objections, I'll standardize on having the last 4 releases present in the repositories.

The initial version of this is in place for our yum repositories as of the 10.2.14 and 10.1.32 releases. The yum repositories for these releases also contain the previous release in the series (10.2.13 and 10.1.31, respectively). Releases will continue to be added, with none taken out until there are four releases in the repositories and then as new releases come out the oldest version in the repository will be removed.

Information on how to actually use this (i.e. how to specify older versions in yum and how to query what versions are available) is not in place yet, that will be my next task for this MDEV.

After the documentation is in place I'll need to add the logic to my mkrepo-yum script for removing old versions as new ones are added, but that won't be needed for probably at least two months (based on our normal release schedule), so it's a lower priority. So after the yum doc updates are done I'll turn my attention to multi-version Debian / Ubuntu repos.

Documentation on how to show available versions and install a specific version added to: https://mariadb.com/kb/en/library/yum/

There's a fork of reprepro that adds support for multi-version deb repositories here. The author says they are working to get his patches merged upstream. I'll install it locally and create some test repos.

My tests with a locally compiled version of reprepro patched for multiversion and ddeb support have not yielded anything we can use. The binary throws all sorts of errors and refuses to include new packages.

I will try again later, but for now we're still unable to have multi-version repositories for Debian/Ubuntu.

This was fixed a while ago, but neglected to close the task.

Basically, the fix was to use a patched version of reprepro that adds the multi-version capability and the ability to import Ubuntu's .ddeb packages. A README for how I compiled it is here: https://gist.github.com/dbart/0ba0f991e9b86d472e28e02998fce835