This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CI scripts". The branch, master has been updated via adc35d0e69bc69e8ef861e22e741ad2cd35119ff (commit) from 43aa00dbd4f0b3cca7708f21494ee0229e390b76 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- http://cgit.osmocom.org/osmo-ci/commit/?id=adc35d0e69bc69e8ef861e22e741ad2cd... commit adc35d0e69bc69e8ef861e22e741ad2cd35119ff Author: Pau Espin Pedrol <pespin@sysmocom.de> Date: Tue Nov 7 16:32:55 2017 +0100 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 ----------------------------------------------------------------------- Summary of changes: scripts/osmo-deps.sh | 1 + 1 file changed, 1 insertion(+) hooks/post-receive -- CI scripts