Invalid SHA1 error when syncing 9.0 R2

[BrokenE39]

Anyone else getting this error when trying to sync the files as described in the instruction for 9.0 R2?

platform/external/desugarerror.GitError: Cannot fetch platform/external/mesa update-ref: fatal: 05099a8ccaacb31a3e516b29b7eb251be893d06a^0: not a valid SHA1

[Chih-Wei Huang]

BrokenE39 <dwt.c...@gmail.com> 於 2021年8月21日 週六 上午5:34寫道：

> Anyone else getting this error when trying to sync the files as described in the instruction for 9.0 R2?
> platform/external/desugarerror.GitError: Cannot fetch platform/external/mesa update-ref: fatal: 05099a8ccaacb31a3e516b29b7eb251be893d06a^0: not a valid SHA1

I didn't see such an error. The commit does exist:
https://osdn.net/projects/android-x86/scm/git/external-mesa/commits/05099a8ccaacb31a3e516b29b7eb251be893d06a

$ cd external/mesa
$ git fetch x86 android-x86-9.0-r2
From git://git.osdn.net/gitroot/android-x86/platform/external/mesa
* tag android-x86-9.0-r2 -> FETCH_HEAD
$ git show FETCH_HEAD
commit 05099a8ccaacb31a3e516b29b7eb251be893d06a (tag: android-x86-9.0-r2)
Merge: 4ac25c4439c 9cda103d28d
Author: Chih-Wei Huang <cwh...@linux.org.tw>
Date: Fri Mar 13 17:10:18 2020 +0800

Merge remote-tracking branch 'mesa/19.3' into pie-x86

You should try again.

[BrokenE39]

The problem is still there if I use repo sync --no-tags --no-clone-bundle. So I did the following, not sure if it's correct but I now see files in mesa.

$ cd external/mesa

$ git fetch x86 android-x86-9.0-r2

$ git show FETCH_HEAD

$ git checkout

[utzcoz]

What about adding  --force-sync to repo command?

--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/android-x86/3724d274-3a54-4f4d-b98c-ce91456aac95n%40googlegroups.com.

[BrokenE39]

Nope. Using --force-sync like this didn't work, same error thrown. I'm rebuilding my Ubuntu VM for compiling today and just ran into it again.

repo sync --no-tags --no-clone-bundle --force-sync

[Chih-Wei Huang]

BrokenE39 <dwt.c...@gmail.com> 於 2021年9月6日 週一 上午3:39寫道：

> Nope. Using --force-sync like this didn't work, same error thrown. I'm rebuilding my Ubuntu VM for compiling today and just ran into it again.
>
> repo sync --no-tags --no-clone-bundle --force-sync

OK. I can reproduce the issue in a new init repo.
Not sure the root cause. I guess it's because
Google updated the logic of the repo script.

I updated the manifest to use the tag name directly.
It works now. Just try to repo sync again.
Thanks for the report!

Best regards,
--
Chih-Wei
Android-x86 project
http://www.android-x86.org