AM3352: AM3352: Accessing META-PROCCESOR SDK REPO - RELATES TO PREVIOUS CASE# CS3621696

Hi Dylan,

This is a known issue on git.ti.com, and the IT infrastructure team is still working on a fix. Until then, the pre-seed workaround below will get your build going.

A default clone sends one very large request listing all refs, and the server rejects it with HTTP 501:

error: RPC failed; HTTP 501 curl 22 The requested URL returned error: 501
fatal: error reading section header 'shallow-info'

Small requests, such as git ls-remote or a single-branch clone, work fine. BitBake’s git fetcher runs git clone --bare --mirror, which requests every ref, so it hits this failure. Changing the URL scheme or the git protocol version won’t help, and the server isn’t rejecting --bare itself.

Workaround: pre-seed the BitBake download cache

BitBake checks DL_DIR/git2/ before fetching, and if the pinned SRCREV is already there, it skips the network entirely. You can fill that cache yourself with a single-branch clone, which works, and leave the recipe untouched.

1. Find the cache directory BitBake expects for the recipe:

bitbake -e <recipe-name> | grep ^GITDIR

It will look like <DL_DIR>/git2/git.ti.com.git.<path>.git.

2. Remove any partial or failed download at that path:

rm -rf <GITDIR>

3. Create the bare clone there, using the branch named in the recipe’s SRC_URI:

git clone --bare --single-branch --branch <branch> \
git.ti.com/.../<repo>.git <GITDIR>

4. Check that the recipe’s SRCREV is present in the clone:

git -C <GITDIR> cat-file -e <SRCREV>^{commit} && echo OK

4. If this fails, the commit is on a different branch. Repeat step 3 with the correct branch, or fetch only that ref:

git -C <GITDIR> fetch origin <ref>

Avoid git fetch --all and --tags, since they send the same large request that fails.

5. Re-run the build:

bitbake <recipe-name>

Repeat these steps for each repo that fails with the 501, one per recipe. Please treat this as a temporary hack until the server-side fix is in place.

Regards,
Vinu

Hi Vinu,

Thank you very much for the workaround. I just confirmed this in fact works and my build was able to successfully be built. Thank you for your assistance and I hope TI can fully resolve the errors at some point.

Thank you