Fetching projects: 33% (73/221) error: Cannot fetch platform/bootable/bootloader/legacy
error: Cannot fetch platform/bionic
Exception in thread Thread-78:
Traceback (most recent call last):
File "/usr/lib/python2.7/threading.py", line 552, in __bootstrap_inner
self.run()
File "/usr/lib/python2.7/threading.py", line 505, in run
self.__target(*self.__args, **self.__kwargs)
File "/home/nir/WORKING_DIRECTORY/.repo/repo/subcmds/sync.py", line 186, in _FetchHelper
current_branch_only=opt.current_branch_only)
File "/home/nir/WORKING_DIRECTORY/.repo/repo/project.py", line 926, in Sync_NetworkHalf
if alt_dir is None and self._ApplyCloneBundle(initial=is_new, quiet=quiet):
File "/home/nir/WORKING_DIRECTORY/.repo/repo/project.py", line 1463, in _ApplyCloneBundle
exist_dst = self._FetchBundle(bundle_url, bundle_tmp, bundle_dst, quiet)
File "/home/nir/WORKING_DIRECTORY/.repo/repo/project.py", line 1527, in _FetchBundle
raise DownloadError('%s: %s ' % (req.get_host(), str(e)))
DownloadError: android.googlesource.com: <urlopen error [Errno -2] Name or service not known>
error: Couldn't resolve host 'android.googlesource.com' while accessing https://android.googlesource.com/platform/external/libpcap/info/refs
fatal: HTTP request failed
error: Couldn't resolve host 'android.googlesource.com' while accessing https://android.googlesource.com/platform/external/libphonenumber/info/refs
fatal: HTTP request failed
error: The requested URL returned error: 403 while accessing https://android.googlesource.com/platform/external/libpcap/info/refs
fatal: HTTP request failed
error: The requested URL returned error: 403 while accessing https://android.googlesource.com/platform/external/libphonenumber/info/refs
fatal: HTTP request failed
error: Cannot fetch platform/external/libpcap
error: Cannot fetch platform/external/libphonenumber
error: Exited sync due to fetch errors
does anyone knows what's the problem?
thanks for your help
Try changing the network adapter from NAT to "bridged adapter" in VirtualBox's network settings.
Also see: https://groups.google.com/forum/#!topic/android-building/aU-TQs6B-kU
The solution to the DNS-related error that you've encountered [error: Couldn't resolve host
] is detailed on the Known Issues resolution page at Google's AOSP Developer Site. Apply this fix by adding the appropriate host entry for your remote repository android.googlesource.com
inside your development machine's /etc/hosts
config file. Begin by clicking here to execute the IP address lookup tool provided by the free web resource: http://network-tools.com/nslook/.
Google's full description of this issue with detailed resolution I've included here:
Difficulties syncing the source tree (DNS issues).
Symptom: When running repo sync, the process fails with various errors
related to not recognizing the hostname. One such error is
<urlopen error [Errno -2] Name or service not known>
.
EDIT: Another lookup error might be error: Couldn't resolve host
.
Cause: Some DNS systems have a hard time coping with the high number
of queries involved in syncing the source tree (there can be several
hundred requests in a worst-case scenario).
Fix: Manually resolve the relevant hostnames, and hard-code those
results locally.
You can resolve them with the nslookup command, which will give you
one numerical IP address for each of those (typically in the "Address"
part of the output).
Note that this will only work as long as the
servers' addresses don't change, and if they do and you can't connect
you'll have to resolve those hostnames again and edit etc/hosts
accordingly.
see below:
The first step is to create a password from the password generator and to save it in ~/.netrc according to the instructions on that page.you need have a google account.
The second step is to force authenticated access, by using the following manifest URI: https://android.googlesource.com/a/platform/manifest. say:
$ repo init -u https://android.googlesource.com/a/platform/manifest
then say:
$ repo sync
it would start download everything
Hope it could help u
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.