无法同步Android 16 Pixel 6a内核源码问题咨询

问题描述 #

我尝试执行命令repo init -u https://android.googlesource.com/kernel/manifest -b android-gs-bluejay-6.1-android16同步Bluejay（Pixel 8a）的Android 16内核分支，但repo同步失败。此前同步Android 14源码一切正常，想确认是操作有误还是谷歌端的问题？另外是否可以基于android-gs-bluejay-6.1-android15-qpr2-beta分支构建内核？

执行命令及错误输出 #

admin@freedomer:~/bluejay$ repo init -u https://android.googlesource.com/kernel/manifest -b android-gs-bluejay-6.1-android16 --depth=1
Downloading Repo source from https://gerrit.googlesource.com/git-repo
remote: Finding sources: 100% (4/4)
remote: Total 4 (delta 0), reused 4 (delta 0)

Your identity is: Vladislav <1585118v@gmail.com>
If you want to change this, please re-run 'repo init' with --config-name

repo has been initialized in /home/admin/bluejay
admin@freedomer:~/bluejay$ repo sync -c --no-tags -j$(nproc) --fail-fast
fatal: couldn't find remote ref refs/heads/android-gs-bluejay-6.1-android16

platform/build/bazel_common_rules:
fatal: couldn't find remote ref refs/heads/android-gs-bluejay-6.1-android16
platform/build/bazel_common_rules: sleeping 4.0 seconds before retrying
fatal: couldn't find remote ref refs/heads/android-gs-bluejay-6.1-android16
Syncing:   1% (1/82), done in 4.651s
================================================================================
Repo command failed due to the following `SyncFailFastError` errors:
GitCommandError: 'fetch --depth=1 --no-auto-gc --quiet --progress aosp --prune --recurse-submodules=no --no-tags +refs/heads/android-gs-bluejay-6.1-android16:refs/remotes/aosp/android-gs-bluejay-6.1-android16' on platform/build/bazel_common_rules failed
stdout: fatal: couldn't find remote ref refs/heads/android-gs-bluejay-6.1-android16
admin@freedomer:~/bluejay$ 

问题分析与解答 #

1. 同步失败原因
   错误核心提示fatal: couldn't find remote ref refs/heads/android-gs-bluejay-6.1-android16，说明你指定的android-gs-bluejay-6.1-android16分支并未在谷歌的内核仓库中存在，不是你的操作问题，属于谷歌端分支未上线或已被移除的情况。

2. 能否基于android-gs-bluejay-6.1-android15-qpr2-beta构建内核
   完全可以。该分支是Pixel 8a的Android 15 QPR2测试版内核分支，基于Linux 6.1稳定内核，具备完整的代码结构和构建配置。只要你的编译环境满足对应要求（比如安装了适配Android 15的clang工具链、build配套工具等），就能正常编译出可用的内核镜像。

内容的提问来源于stack exchange，提问作者Vladislav Ukhanev