jigsaw
June 15, 2025, 10:27pm
1
I am following the build-e documentation.
Step 6. Start build, I tried BRANCH_NAME=v3.0.1-a14
, which results in
/root/build.sh: line 46: DEVICE_LIST_V3.0.1-A14: invalid variable name
/root/build.sh: line 85: DEVICE_LIST_V3.0.1-A14: invalid variable name
v3.0.1-t
and v3.0.1-s
don’t have this issue.
build-community.sh#L44 · master · e / os / docker-lineage-cicd · GitLab doesn’t support numbers in the branch name of the tag, sed
fails silently, same line 83.
For reference, another post had this error with v2.8-a14
, “1st go with the documentation and failing” (can’t add a 3rd link)
piero
June 15, 2025, 11:39pm
2
Hello @jigsaw , Welcome to the /e/ forum.
if you want latest / current branch (master) you can try using “v1-a14” or “v1-u”
also if you want to use tag, you may try “v3.0.1-u” that is equivalent to “v3.0.1-a14” witch is the new convention (you could get the same error)
hope this trick helps
.
i don’t know docker, as i failled to install it
08. Building an e ROM Using Docker · Wiki · e / documentation / A Generic Guide on porting eOS · GitLab
.
09: Building e OS for an unsupported device · Wiki · e / documentation / A Generic Guide on porting eOS · GitLab
i like to use the repo way…
07: Building an e ROM the Repo Sync way · Wiki · e / documentation / A Generic Guide on porting eOS · GitLab
.
README.md · main · steadfasterX / android vendor e · GitLab
i don’t know the a-14 branch as for now i build for old devices
jigsaw
June 16, 2025, 12:10am
3
Thanks!
v1-a14
has the same issue.
I don’t see v3.0.1-u
nor v1-u
in releases/-/tags. The last release with -u is v2.7-u
.
If I try anyway:
...
Running: yes | repo init -u ... -b "v3.0.1-u"
ERROR: Failed to initilize repository
v1-u is syncing. I will update on it.
I will take a look at the repo sync too.
piero
June 16, 2025, 12:16am
4
looking at e / os / android · GitLab i understand new convention for BRANCH_NAME
is now simply a14
and no more v1-u
or v1-a14
look like “v
” is now only use for tags
To initialize your local repository using the /e/ trees, use either a tag (you now what you get) or a branch (the latest code of a branch) :
repo init -u https://gitlab.e.foundation/e/os/android.git -b refs/tags/<tag>
or
repo init -u https://gitlab.e.foundation/e/os/android.git -b <branch>
old :
repo init -u https://gitlab.e.foundation/e/os/android.git -b refs/tags/v0.9.4-pie
repo init -u https://gitlab.e.foundation/e/os/android.git -b v1-pie
new :
repo init -u https://gitlab.e.foundation/e/os/android.git -b refs/tags/v3.0.1-a14 --git-lfs
repo init -u https://gitlab.e.foundation/e/os/android.git -b a14 --git-lfs