version.patch
[MDEV-18362] EPOCH=1 needs to be set for Ubuntu 18.10 cosmic builds Created: 2019-01-23 Updated: 2019-04-25 Resolved: 2019-04-25 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Packaging, Platform Debian |
| Affects Version/s: | 10.1.37 |
| Fix Version/s: | 10.2.24, 10.1.39 |
| Type: | Bug | Priority: | Critical |
| Reporter: | Daniel Bartholomew | Assignee: | Sergei Golubchik |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Attachments: |
version.patch
|
| Description |
|
MariaDB 10.1 builds for cosmic in buildbot are failing install tests at least in part because Ubuntu's MariaDB 10.1 since Ubuntu Bionic has EPOCH set to 1. We added code for Ubuntu Bionic to set EPOCH=1 in debian/autobake-deb.sh and that section needs to be extended to also include Ubuntu Cosmic. Instead of just adding cosmic to a static list, a better fix would be to set the EPOCH for any Ubuntu build greater than 18.04, that way we wouldn't have to do this again. I have a patch that does this, but I need to test it first. |
| Comments |
| Comment by Daniel Bartholomew [ 2019-01-23 ] |
|
The version.patch takes the output of lsb_release -sr, which is the Ubuntu version number (e.g. 18.10), converts it to an integer by stripping off the part after the '.', and then at the appropriate spot instead of comparing the release codename it checks to see if the number is greater than or equal to 18. Every version of Ubuntu that matches (18.04, 18.10, 19.04, etc...) needs the EPOCH flag set afaik. |