aboutsummaryrefslogtreecommitdiffstats
path: root/scripts/osmocom-latest-packages.sh
diff options
context:
space:
mode:
authorHarald Welte <laforge@osmocom.org>2020-08-05 10:19:09 +0200
committerHarald Welte <laforge@osmocom.org>2020-08-05 11:48:25 +0200
commit1d5d879be0abacd512e6f7c45e695044a75ddbd8 (patch)
tree2d76c3aa36f9891dc134597dbefe2093cae23150 /scripts/osmocom-latest-packages.sh
parent523aa0874e2488af0dfee7090989c0280bf81581 (diff)
Revert "nightly-packages: Hard-code LimeSuite to 20.01.0 as 20.07.0 is broken"
This reverts commit e17a4d66d06ad5acb74a728ca378ad0cc9fffdf0, i.e. we are back to building the latest tag, now that v20.07.1 has been released, which actually builds again. However, the package name in debian/changelog has not been updated to reflect that version change, resulting in v20.07.1 being packaged in a package called v20.07.0. Change-Id: I01b77f03924a0b303103fb737dfee15b9c4b0c9c
Diffstat (limited to 'scripts/osmocom-latest-packages.sh')
-rwxr-xr-xscripts/osmocom-latest-packages.sh5
1 files changed, 0 insertions, 5 deletions
diff --git a/scripts/osmocom-latest-packages.sh b/scripts/osmocom-latest-packages.sh
index 219ae6d..212bb4c 100755
--- a/scripts/osmocom-latest-packages.sh
+++ b/scripts/osmocom-latest-packages.sh
@@ -30,11 +30,6 @@ prepare() {
get_last_tag() {
project="$1"
- if [ "$project" = "limesuite" ]; then
- # temp workaround, see https://github.com/myriadrf/LimeSuite/issues/313
- echo "v20.01.0"
- return
- fi
if [ "$project" = "limesuite" ] || [ "$project" = "open5gs" ]; then
ver_regexp="^v[0-9]*.[0-9]*.[0-9]*$"
else