8893 2016-01-07 01:46:12 +0000 do_cleanall: Function failed: Network access disabled through BB_NO_NETWORK 2016-05-12 15:05:07 +0000 1 1 7 Build System, Metadata & Runtime BitBake bitbake 2.1 x86 Multiple RESOLVED NOTABUG Medium+ major Future 1 liezhi.yang liezhi.yang poky.bs.watcher poky.watcher richard.purdie --- --- No (bug/feature does not impact docs) oldest_to_newest 57606 0 liezhi.yang 2016-01-07 01:46:12 +0000 The meta-selinux layer: $ bitbake refpolicy-mls -ccleanall Log data follows: | DEBUG: Executing python function do_cleanall | DEBUG: Python function do_cleanall finished | ERROR: Function failed: Network access disabled through BB_NO_NETWORK (or set indirectly due to use of BB_FETCH_PREMIRRORONLY) but access requested with command git -c core.fsyncobjectfiles=0 ls-remote git://github.com/TresysTechnology/refpolicy.git (for url None) ERROR: Task 3 (/buildarea/lyang1/test_qemux86/layers/meta-selinux/recipes-security/refpolicy/refpolicy-mls_git.bb, do_cleanall) failed with exit code '1' NOTE: Tasks Summary: Attempted 4 tasks of which 0 didn't need to be rerun and 1 failed. do_cleanall should not require NETWORK. 57645 1 richard.purdie 2016-01-07 16:41:09 +0000 I suspect this is a recipe using SRCREV = ${AUTOREV} since that would trigger a network lookup using git ls-remote. We need to do that to construct PV which is needed to construct the WORKDIR paths so we know where to clean things. I therefore worry about how we'd try and fix this... 62149 2 richard.purdie 2016-05-12 15:05:07 +0000 This is a configuration issue with the layer/recipe in question. If they're set to use the network for revisions/branch lookup, they need to use the network. cleanall works fine if recipes aren't setup that way.