summaryrefslogtreecommitdiffstats
path: root/scripts
diff options
context:
space:
mode:
authorPau Espin Pedrol <pespin@sysmocom.de>2017-11-07 16:32:55 +0100
committerPau Espin Pedrol <pespin@sysmocom.de>2017-11-07 16:40:00 +0100
commitadc35d0e69bc69e8ef861e22e741ad2cd35119ff (patch)
tree7ad08d87e4a3279e8a5096d5431d2ef81b5b6119 /scripts
parent43aa00dbd4f0b3cca7708f21494ee0229e390b76 (diff)
osmo-deps.sh: Force fetching git tags
It was recently spotted, in a osmo-msc jenkins build, that an updated dependency (new commits to be fetched) contained a new tag which was not fetched with the commit. It resulted in the Makefile generating an old .version file, which ended up generating a library version in the .pc which later in the build make the configure script fail while checking at the dependencies. As far as I could understand after reading several discussion threads, it seems git fetch doesn't necessarily fetch and store locally all new tags found in the remote, and we need to explicitly add the --tags parameter to be sure all of them are downloaded. This patch adds a new fetch line instead of patching the one already present because it seems in old versions of git the --tags parameter had a different behaviour, in which only tags and not branches are fetched. This way is ensured that we get both correct regardless of git version. Change-Id: I4bfe4846959c70e435d6792a755a6f2a6f0a932c
Diffstat (limited to 'scripts')
-rwxr-xr-xscripts/osmo-deps.sh1
1 files changed, 1 insertions, 0 deletions
diff --git a/scripts/osmo-deps.sh b/scripts/osmo-deps.sh
index d5a724b..a4afec5 100755
--- a/scripts/osmo-deps.sh
+++ b/scripts/osmo-deps.sh
@@ -9,6 +9,7 @@ then
fi
cd "$project"
+git fetch --tags origin
git fetch origin
# Cleanup should already have happened during a global osmo-clean-workspace.sh,