From 86aeee98cffdc7c2f19e732467a69103d52fe16a Mon Sep 17 00:00:00 2001 From: Enrico Scholz Date: Sat, 30 Jun 2012 21:34:56 +0200 Subject: bitbake: git: do not execute 'git remote prune' 'git remote prune' at this location does not make much sense because the following 'git remote rm' will prune stale and non-stale branches. The 'prune' can cause trouble because it will access the network bypassing the no-network code in bitbake. When this operation fails and throws an exception, the next command (--> 'git remote rm') will be skipped. This in turn, will make all the following operations fail, because they assume that the remote does not exist yet. (Bitbake rev: 2ba23df5fad4b94d38a6aed97f7822226d72eb89) Signed-off-by: Enrico Scholz Signed-off-by: Richard Purdie --- bitbake/lib/bb/fetch2/git.py | 1 - 1 file changed, 1 deletion(-) (limited to 'bitbake/lib') diff --git a/bitbake/lib/bb/fetch2/git.py b/bitbake/lib/bb/fetch2/git.py index 3676cc3ddc..384007c81f 100644 --- a/bitbake/lib/bb/fetch2/git.py +++ b/bitbake/lib/bb/fetch2/git.py @@ -204,7 +204,6 @@ class Git(FetchMethod): needupdate = True if needupdate: try: - runfetchcmd("%s remote prune origin" % ud.basecmd, d) runfetchcmd("%s remote rm origin" % ud.basecmd, d) except bb.fetch2.FetchError: logger.debug(1, "No Origin") -- cgit v1.2.3-54-g00ecf