Results 1 to 7 of 7
  1. Thread Author  Thread Author    #1  
    wormy987123's Avatar
    flashaholic

    Posts
    391 Posts
    Global Posts
    392 Global Posts
    ROM
    Stock for now

    Default Repo sync error

    I've been trying to learn more and more about from building. I've went thru all the steps to get Ubuntu set up and when I run the command repo sync -j16 it exits with error: Exited sync due to fetch errors. Any help would be great. I'm running my Ubuntu in a virtual box with 8gb ram and a amd quad core. If that helps any.

    Sent from my LS670 using Tapatalk 2
  2. #2  
    drewwalton19216801's Avatar

    Posts
    2,539 Posts
    ROM
    HydroROM

    Default Re: Repo sync error

    What repository are you trying to sync with?
  3. Thread Author  Thread Author    #3  
    wormy987123's Avatar
    flashaholic

    Posts
    391 Posts
    Global Posts
    392 Global Posts
    ROM
    Stock for now

    Default Re: Repo sync error

    Ive tried googles, cyanogen and kravens and none of them will fully go thru they have all exited with the same error
    Last edited by wormy; 05-09-2012 at 08:52 PM. Reason: spelling
  4. #4  
    drewwalton19216801's Avatar

    Posts
    2,539 Posts
    ROM
    HydroROM

    Default

    Quote Originally Posted by wormy View Post
    Ive tried googles, cyanogen and kravens and none of them will fully go thru they have all exited with the same error
    Try just "repo sync" without -j16.
  5. Thread Author  Thread Author    #5  
    wormy987123's Avatar
    flashaholic

    Posts
    391 Posts
    Global Posts
    392 Global Posts
    ROM
    Stock for now

    Default Re: Repo sync error

    ive tried that as well i found a post where some one said repo sync -f worked so its running now. ive been trying to get this for almost a week and it kept failing.


    well after about 7gb of data download it seems to be stuck its just got a blinking curser and has been that way for about 10 minutes after this line

    From git://github.com/CyanogenMod/android_prebuilt
    * [new branch] gb-release-7.2 -> github/gb-release-7.2
    * [new branch] gingerbread -> github/gingerbread
    * [new branch] gingerbread-release -> github/gingerbread-release
    * [new branch] ics -> github/ics
    * [new tag] cm-7.1.0 -> cm-7.1.0
    Last edited by wormy; 05-09-2012 at 09:12 PM. Reason: added more info
  6. #6  

    Default Re: Repo sync error

    I think I remember having a similar error when I was poking around (unsuccessfully) with the source. I even had a similar VM setup.

    Stop syncing and try deleting everything that you've downloaded (every last bit). Retry the sync and it should go through. From what I remember, I lost my internet connection in the middle of syncing and I kept getting sync errors until I deleted everything and started fresh.

    I never found anyone else with a similar error. Hopefully the above helps.
  7. #7  
    sblood86's Avatar

    Posts
    430 Posts
    ROM
    Quatrimus / CM10

    Default Re: Repo sync error

    Quote Originally Posted by wormy View Post
    ive tried that as well i found a post where some one said repo sync -f worked so its running now. ive been trying to get this for almost a week and it kept failing.


    well after about 7gb of data download it seems to be stuck its just got a blinking curser and has been that way for about 10 minutes after this line

    From git://github.com/CyanogenMod/android_prebuilt
    * [new branch] gb-release-7.2 -> github/gb-release-7.2
    * [new branch] gingerbread -> github/gingerbread
    * [new branch] gingerbread-release -> github/gingerbread-release
    * [new branch] ics -> github/ics
    * [new tag] cm-7.1.0 -> cm-7.1.0
    Yep; known error for CM... (not sure why you would be having such an issue with googles repo as it doesn't use github). The CM team has played around with this quite a bit with the Jenkins server trying to resolve their sync/build errors. What they finally landed on was actually the same thing that google did to their repo manifests; they changed the manifest to use the delivery method used to initiate the repo rather than a default assigned in the manifest.

    There are known issues:

    If you are using an "ancient" version of repo OR you first initialized your repo
    with an "ancient" version of repo, then it will cause problems. (Note: I did check
    to make sure I had latest version of repo, which I did. However, apparently, my
    repo was first initialized with an "ancient" version of repo.)

    If you see errors such as:

    "fatal: '../CyanogenMod/android.git' does not appear to be a git repository"

    then you will need to make sure you have latest version of repo and that
    your repo is re-initialized ("from scratch") with it.

    Also, it does not work with SSH-based URLs.

    To fix:

    # get latest repo with:
    curl > ~/bin/repo
    chmod a+x ~/bin/repo

    # clear old repo software and manifests:
    rm -rf .repo/repo
    rm -rf .repo/manifests .repo/manifests.git .repo/manifest.xml

    # re-initialize repo (make sure to include "-b branchname"):
    # NOTE: It is suggested to use the URL below to init (SSH URLs do not work)
    repo init -u -b ics
    NOTE: Your git repo blobs should remain intact so you should not have to re-download them.

Posting Permissions