72bcff3081
Our git download backend switches the remote of our local clone, and fetches all refs and tags from that remote. When the local clone has a tag fetched from another remote, and the new remote also has a tag by the same name, and that tag points to another commit, then git refuses to fetch the new tag and exits in error, as it considers that the new tag would clobber the existing one. This is safe and sane behaviour when run interactively with a human that can take a decision. However, in our case, we don't care about any tags that were present before, as only the last one makes sense in our case: the one from the remote the user has requested for the current build. Tell git to forcefully pull tags, even if they would clobber existing ones. Note that, although this changes the git backend, it does not change the content of generated archives, so we do not need to bump the suffix version. Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr> Signed-off-by: Arnout Vandecappelle <arnout@mind.be> |
||
---|---|---|
.. | ||
bzr | ||
cargo-post-process | ||
check-hash | ||
cvs | ||
dl-wrapper | ||
file | ||
git | ||
go-post-process | ||
helpers | ||
hg | ||
scp | ||
sftp | ||
svn | ||
wget |