diff options
author | Otto Kekäläinen <otto@mariadb.org> | 2018-03-31 22:35:51 +0300 |
---|---|---|
committer | Otto Kekäläinen <otto@mariadb.org> | 2018-04-04 22:43:45 +0300 |
commit | ec53e031bb364b3a6eea2308fa31a542c903dc7e (patch) | |
tree | adfa76e6142ba1b6adf4f64478bae89bde470d31 /debian | |
parent | 2b0c6b7aa14857bdfffad6a2a0fb27e8d1f9bb31 (diff) | |
download | mariadb-git-ec53e031bb364b3a6eea2308fa31a542c903dc7e.tar.gz |
Deb: Bump epoch to supercede 1:10.1.29-6 in Debian
A non-MariaDB.org contributor introduced the epoch 1: in Debian.
There is no way to revert it, so we just need to adapt to it to
ensure no 10.3 installation would downgrade to that version in
Debian/Ubuntu, as 1: is considered higher than any version before.
Diffstat (limited to 'debian')
-rwxr-xr-x | debian/autobake-deb.sh | 2 | ||||
-rw-r--r-- | debian/changelog | 6 |
2 files changed, 7 insertions, 1 deletions
diff --git a/debian/autobake-deb.sh b/debian/autobake-deb.sh index d43f8dbec4a..078bcba65a8 100755 --- a/debian/autobake-deb.sh +++ b/debian/autobake-deb.sh @@ -110,7 +110,7 @@ PATCHLEVEL="+maria" LOGSTRING="MariaDB build" CODENAME="$(lsb_release -sc)" -dch -b -D ${CODENAME} -v "${UPSTREAM}${PATCHLEVEL}~${CODENAME}" "Automatic build with ${LOGSTRING}." +dch -b -D ${CODENAME} -v "1:${UPSTREAM}${PATCHLEVEL}~${CODENAME}" "Automatic build with ${LOGSTRING}." echo "Creating package version ${UPSTREAM}${PATCHLEVEL}~${CODENAME} ... " diff --git a/debian/changelog b/debian/changelog index 4813c5bd86f..dec49bd4282 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,9 @@ +mariadb-10.3 (1:10.3.0) unstable; urgency=low + + * Bump epoch to supersede 1:10.1.29-6 in Debian + + -- Otto Kekäläinen <otto@mariadb.org> Sat, 31 Mar 2018 22:34:34 +0300 + mariadb-10.3 (10.3.0) unstable; urgency=low * Initial release. |