AlaskaLinuxUser's Scratchpad

Commit thy works unto the LORD, and thy thoughts shall be established. - Proverbs 16:3

Error: Exited sync due to fetch errors

Error: Exited sync due to fetch errors

[CODE]
\$ repo sync
.........EDITED FOR SPACE.........
Fetching project SlimRoms/android_external_qrngd
error: Cannot fetch UBERTC/arm-eabi-5.2
Fetching project platform/external/chromium_org/third_party/libphonenumber/src/phonenumbers
Fetching projects: 86% (419/487) Fetching project SlimRoms/hardware_qcom_display
Fetching projects: 87% (424/487) Fetching project SlimRoms/hardware_qcom_display
Fetching project SlimRoms/hardware_qcom_display
Fetching projects: 89% (434/487)
error: Exited sync due to fetch errors
\$
[/CODE]

Sometimes, while syncing various sources, you might run into this error. If you don't know a way to fix it or to get around it, then this can be debilitating! There are four principle ways to fix this problem, and I would like to explore those here. First and foremost, though, what is the problem? The overal problem is that while syncing the source code, there was something missing or misplaced that cannot be found by the repo tool. In this case, while syncing LiquidSmooth 5.1-Layers, the error is that the repo tool cannot find the UBERTC/arm-eabi-5.2 repository.

As I mentioned a moment ago, there are four things that you can do about this. Lets take a quick look at those options:

1. Wait and try again.
Sometimes there are little glitches or hangups that can happen due to a server being down, or your internet dropping off, or power outages, etc. Perhaps your local network went down for a while and the sync stopped, or maybe someone was moving that repository while they made some changes, or something like that. An easy thing to do is try repo sync again and see if the problem is resolved. To add validity to this option, you could go look to see if that repository does in fact exist.

2. Remove that repository from your manifest.
There are a lot of repositories on your manifest that will not have anything to do with what you are building. For instance, in this very case, I will not be using the UBERTC arm 5.2 tool chain, so I do not really care to download this repository anyways. An easy fix here is to simply remove it from my manifest, like so:

[CODE]
\$ cd [to your folder where you were running repo sync]
\$ gedit ./.repo/manifests/default.xml
[/CODE]

You should now be presented with a file that looks like this:

[CODE]

\<remote name="ls"
fetch="https://github.com/LiquidSmooth/"
review="https://gerrit.liquidsmooth.net/"/>

\<remote name="cm"
fetch="git://github.com/CyanogenMod" />

\<default revision="refs/tags/android-5.1.1_r24"
remote="aosp"
sync-c="true"
sync-j="4" />

\<project path="android" name="android" remote="ls" revision="lp5.1-layers" />
\<project path="build" name="android_build" remote="ls" revision="lp5.1-layers" >
\<copyfile src="core/root.mk" dest="Makefile" />
\</project>
\<project path="abi/cpp" name="platform/abi/cpp" groups="pdk" />
\<project path="art" name="SlimRoms/android_art" remote="github" revision="lp5.1" />
\<project path="bionic" name="SlimRoms/android_bionic" remote="github" revision="lp5.1" />
\<project path="bootable/bootloader/legacy" name="platform/bootable/bootloader/legacy" />
\<project path="bootable/recovery" name="SlimRoms/bootable_recovery" remote="github" revision="lp5.1" />
\<project path="cts" name="platform/cts" groups="cts,pdk-cw-fs" />
\<project path="dalvik" name="platform/dalvik" groups="pdk-cw-fs" />
.............EDITED FOR SPACE................
[/CODE]

Which, in this case I edited as so:

[CODE]
\