repo sync fault! about documentation HOT 9 CLOSED

Is this the entire repo sync output? Google translate does suggest any of the supplied text is an error message...

If you are getting errors it would be better to run "repo sync" without the "-j8" since it will reduce the amount of parallel activity (which it turn should make error messages more obvious). Can you re-run and share the full output.

from documentation.

Thanks Daniel,

I tried same job as you said, without '-j8' option.
But same error occurred at different time as follow;

 * [새로운 태그]               v4.3-rc6               -> v4.3-rc6
 * [새로운 태그]               v4.3-rc7               -> v4.3-rc7

error: Exited sync due to fetch errors

This log was cut only several lines at the end.

I would like to run self-built Android M on DB410c indeed,
but any kind of instructions did not help me.

Any other advice?

from documentation.

Still, in part, I suggest trying to switch repo into English. You mentioned you are not seeing a clear error report and I wonder it there might be some problem with the i18n.

I know this because I do get a clear error report:

Fetching projects:  99% (462/466)  fatal: remote error: access denied or repository not exported: /gitroot/android-x86/platform/external/libpciaccess
error: Cannot fetch platform/external/libpciaccess

error: Exited sync due to fetch errors

This turns out to be because sourceforge has altered their git hosting requiring changes to the repo manifest. I made the following changes to my .repo/local_manifests as was able to complete the pull:
sf_fix.txt

from documentation.

Thanks Daniel,
To build, I modified .repo/local_manifests/linaro.xml as your diff.
Build job was done with couple of further modifications and running build command several times.
Finally, I've got 7 img files, that is,

boot-db410c.img  
boot.img  
cache.img  
dt.img  
ramdisk.img  
system.img  
userdata.img.

While flash fusing these img files through fastboot, system.img and userdata.img return fastboot fail and fastboot crashes..

Should I redefine partition for this target??

from documentation.

What version of the bootloader do you have installed? I suspect this release would have been tested with: http://builds.96boards.org/releases/dragonboard410c/linaro/rescue/16.06/dragonboard410c_bootloader_emmc_android-50.zip

from documentation.

After installation dragonboard410c_bootloader_emmc_android-50.zip,
when I try to fuse userdata.img and system.img, fastboot crashed with this error message on terminal.

Then, I'm re-building whole source tree to try once more.

from documentation.

Any news here?

What does the file command say about the images.

For example:

wychelm$ file system.img 
system.img: Android sparse image, version: 1.0, Total of 314554 4096-byte output blocks in 2809 input chunks.
wychelm$ file userdata.img 
userdata.img: Android sparse image, version: 1.0, Total of 1310720 4096-byte output blocks in 203 input chunks.

from documentation.

Thanks Daniel,

I attach the result;

youngwha@db410c$ file system.img
system.img: Linux rev 1.0 ext4 filesystem data, UUID=da594c53-9beb-f85c-85c5-cedf76546f7a, volume name "system" (extents) (large files)
youngwha@db410c$ file userdata.img
userdata.img: Linux rev 1.0 ext4 filesystem data, UUID=c25d03d9-ea27-3358-873e-b911bfaab62b, volume name "data" (extents) (large files)

from documentation.

Interesting that these are not sparse images. Having said that fastboot should handle raw images like this automatically. How old if the version of fastboot you are using?

from documentation.