Question
When using the unified/standard manifest, "repo sync" fails with errors while cloning the Tizen Git repository over HTTPS:
error: Unable to get pack file https://git.tizen.org/cgit/platform/framework/web/chromium-efl/objects/pack/pack-f9b033ba120dc295098f9b1fdcf66450d4cb8a12.pack
transfer closed with outstanding read data remaining
The process consistently gets stuck on this file during synchronization. I attempted the following workaround:
$ wget https://git.tizen.org/cgit/platform/framework/web/chromium-efl/objects/pack/pack-f9b033ba120dc295098f9b1fdcf66450d4cb8a12.idx
--> 33704996 bytes file successfully downloaded
$ git verify-pack -v pack-f9b033ba120dc295098f9b1fdcf66450d4cb8a12.idx
fatal: early EOF
I'm unsure whether this issue stems from our HTTP proxy server or the Tizen Git database. How can I further investigate and resolve this problem?
Answer
Problem Understanding
The issue occurs when trying to clone the Tizen repository using repo sync, specifically failing to download a pack file from the Tizen Git server. The error suggests either:
- Network connectivity issues (possibly related to proxy settings)
- Server-side problems with the Tizen Git repository
- Corrupted Git objects
Solution Methods
-
Verify Network Connectivity:
- Check your internet connection and proxy settings
- Try accessing the URL directly in a browser to verify accessibility
- Test with different network configurations if possible
-
Alternative Cloning Method:
- Try cloning using SSH instead of HTTPS:
git clone git@git.tizen.org:platform/framework/web/chromium-efl.git - If SSH is not an option, try using a different Git client or updating your current Git version
- Try cloning using SSH instead of HTTPS:
-
Manual Download and Verification:
- If the issue persists, manually download the repository as a ZIP from the Tizen source page
- Verify the integrity of downloaded files using checksums
Additional Tips
- Ensure you have followed the official environment setup guide: Tizen Development Environment Setup
- Check the Tizen developer forums for similar issues and solutions
- Consider trying the sync operation at a different time in case of temporary server issues
