Osmocom Libraries » libosmocore

When osmo-gbproxy was splitted from osmo-sgsn.git into its own somo-gbproxy.git, epoch was increased to 1 in order to have lower tagged released not conflicting with higher versions from old repo.
see osmo-gbproxy.git a8fa5671170580cdd8ae653e7811cfd1f1c2b36c

As a result, osmo-release.sf fails to generate a new release (happened when generating new release 0.1.0) since it doesn't handle epoch properly and "gbp dch" fails due to detecting old tag has epoch 1 while NEW_VER has epoch 0 (no "<number>:" prefix).

I was able to temporarily release it by doing this adhoc changes to osmo-release.sh:

diff --git a/osmo-release.sh b/osmo-release.sh
index eea17cf9..55c26151 100755
--- a/osmo-release.sh
+++ b/osmo-release.sh
@@ -247,7 +247,7 @@ if [ -f "TODO-RELEASE" ]; then
        git add TODO-RELEASE
 fi

-gbp dch --debian-tag='%(version)s' --auto --meta --git-author --multimaint-merge --ignore-branch --new-version="$NEW_VER" 
+gbp dch --debian-tag='%(version)s' --meta --git-author --multimaint-merge --ignore-branch --new-version="1:$NEW_VER" -s 3385506bb63747a810948fddff6f8d1c1d98c8ac
 dch -r -m --distribution "unstable" "" 
 git add ${GIT_TOPDIR}/debian/changelog
 bumpversion --current-version $VERSION $REL --tag --commit --tag-name $NEW_VER --allow-dirty