[bitbake-devel] bitbake fetching fails on git repo but can manually git clone

Zhou, Luwei luwei.zhou at intel.com
Fri Mar 18 08:20:41 UTC 2016


Hi all

I am new to yocto and hope the mail list is the right place to ask.

I am using jethro 2.0 to build my yocto system. I have met some weird issue when bitbake fetching source. When I try bitbake image, there would be fetching error caused by some components(mraa etc). I have tried enabling -D option when running bitbake -D mraa -c fetch to see the log.  I can see bitbake will first trying using git clone to fetch the code and failed(with a return of warning) and then trying mirror still failed with error. However, When I manually run the command  below:

git -c core.fsyncobjectfiles=0 clone --bare --mirror git://github.com/intel-iot-devkit/mraa.git /home/luweizho/build/ambr-yocto-build/build/downloads/git2/github.com.intel-iot-devkit.mraa.git

The git clone can be completed. My current setting is below. It is kind of weird.  Why git clone can work manually but bitbake fetching would return warning and then fail.

https://wiki.yoctoproject.org/wiki/Working_Behind_a_Network_Proxy

~/.bashrc:
export SOCKS_SERVER=proxy-png.intel.com
export HTTP_PROXY=http://proxy-chain.intel.com:911
export HTTPS_PROXY=https://proxy-chain.intel.com:912
export HTTP_DIRECT=intel.com,.intel.com,10.0.0.0/8,192.168.0.0/16,localhost,127.0.0.0/8,134.134.0.0/16
export FTP_PROXY=$HTTP_PROXY
export ftp_proxy=$HTTP_PROXY
export http_proxy=$HTTP_PROXY
export https_proxy=$HTTPS_PROXY
export NO_PROXY=$HTTP_DIRECT
export no_proxy=$NO_PROXY
export GIT_PROXY_COMMAND=/home/luweizho/tool/gitproxy.sh

luweizho at pglvm2014-v03:~/build/ambr-yocto-build/build$ cat ~/tool/gitproxy.sh
#!/bin/sh
exec socat stdio SOCKS:$SOCKS_SERVER:$1:$2


The following is the warning message when running bitbake -D mraa -c fetch. After the warning, bitbake would try the mirror link by http and fails.

DEBUG: Fetcher accessed the network with the command git -c core.fsyncobjectfiles=0 clone --bare --mirror git://github.com/intel-iot-devkit/mraa.git /home/luweizho/build/ambr-yocto-build/build/downloads/git2/github.com.intel-iot-devkit.mraa.git
DEBUG: Running export no_proxy="intel.com,.intel.com,10.0.0.0/8,192.168.0.0/16,localhost,127.0.0.0/8,134.134.0.0/16"; export NO_PROXY="intel.com,.intel.com,10.0.0.0/8,192.168.0.0/16,localhost,127.0.0.0/8,134.134.0.0/16"; export ftp_proxy="http://proxy-chain.intel.com:911"; export FTP_PROXY="http://proxy-chain.intel.com:911"; export https_proxy="https://proxy-chain.intel.com:912"; export HTTPS_PROXY="https://proxy-chain.intel.com:912"; export http_proxy="http://proxy-chain.intel.com:911"; export HTTP_PROXY="http://proxy-chain.intel.com:911"; export PATH="/home/luweizho/build/ambr-yocto-build/build/tmp/sysroots/x86_64-linux/usr/bin/python-native:/home/luweizho/build/ambr-yocto-build/scripts:/home/luweizho/build/ambr-yocto-build/build/tmp/sysroots/x86_64-linux/usr/bin/x86_64-poky-linux:/home/luweizho/build/ambr-yocto-build/build/tmp/sysroots/intel-corei7-64/usr/bin/crossscripts:/home/luweizho/build/ambr-yocto-build/build/tmp/sysroots/x86_64-linux/usr/sbin:/home/luweizho/build/ambr-yocto-build/build/tmp/sysroots/x86_64-linux/usr/bin:/home/luweizho/build/ambr-yocto-build/build/tmp/sysroots/x86_64-linux/sbin:/home/luweizho/build/ambr-yocto-build/build/tmp/sysroots/x86_64-linux/bin:/home/luweizho/build/ambr-yocto-build/scripts:/home/luweizho/build/ambr-yocto-build/bitbake/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games"; export HOME="/home/luweizho"; git -c core.fsyncobjectfiles=0 clone --bare --mirror git://github.com/intel-iot-devkit/mraa.git /home/luweizho/build/ambr-yocto-build/build/downloads/git2/github.com.intel-iot-devkit.mraa.git
WARNING: Failed to fetch URL git://github.com/intel-iot-devkit/mraa.git;protocol=git;rev=ba5318fee92e63e1481ad1392ec56e7a6ebaf4fe, attempting MIRRORS if available

Best Regards
Luwei

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openembedded.org/pipermail/bitbake-devel/attachments/20160318/7c50f240/attachment-0002.html>


More information about the bitbake-devel mailing list