Hi all!
I am new to /e/OS and want to compile the OS for my Oneplus 13 myself.
I already tried a few days ago, but i had to do some HW changes on my computer and reinstall it’s OS.
Yesterday I wanted to try buildung again, but e / os / 🚀 Releases · GitLab has no releases anymore and no tags.
What did I miss? Did something change or are there server issues?
I would be glad for any feedback!
In documentation, we currently see :
List of tags to use for
BRANCH_NAMEis available at https://gitlab.e.foundation/e/os/releases/-/tags.
But the link currently go to nowhere…
.
Did you tried :
repo init -u https://gitlab.e.foundation/e/os/releases.git -b refs/tags/v4.0-a16
or simply :
repo init -u https://gitlab.e.foundation/e/os/releases.git -b v4.0-a16
The link @piero mentioned is the one I have bookmarked for tags https://gitlab.e.foundation/e/os/releases/-/tags
The 404 page suggests
Please contact your GitLab administrator if you think this is a mistake.
Did something change?
Is this page throwing a 404 for you.
Yes, @Manoj it is, thank you.
I am able to access the page. Guess there could be an issue with the page permissions. Will ask the team to check and update.
Maybe. When I try to access the page already logged in, I see
Sign out and sign in with a different account
For me, the whole release sub page is not available (or empty) and therefore every link going there ends with Error 404:
I don’t have an account and therefore I am not logged in.
Are there any updates?
Yes. Since Manoj said he would ask the team the day updated from a Saturday to a Sunday now 
.
It is the weekend. The team members usually respond on Monday during EU office hours. Will ping them again on Monday to change the page permissions.
Ok, thanks for your help, makes sense, sorry for the pressure!
Is repo init as Post #2 throwing an error? Although clearly when you start a build you just want to study the branches and tabs. Just ask if there is anything we can suggest from memory.
Yes, this throws an error:
repo init -u https://gitlab.e.foundation/e/os/releases.git -b refs/tags/v4.0-a16
Downloading Repo source from https://gerrit.googlesource.com/git-repo
repo: Updating release signing keys to keyset ver 2.3
git requires authentication, but repo cannot perform interactive authentication. Check git credentials.
fatal: cannot obtain manifest https://gitlab.e.foundation/e/os/releases.git
================================================================================
Repo command failed: UpdateManifestError
Unable to sync manifest default.xml
I guess this is from the 404 error?
Now as you ask, this would be my first build command:
sudo docker run \
-v "/e/os/src:/srv/e/src:z" \
-v "/e/os/zips:/srv/e/zips:z" \
-v "/e/os/logs:/srv/e/logs:z" \
-v "/e/os/ccache:/srv/e/ccache:z" \
-v "/e/os/keys:/srv/keys:z" \
-e "CCACHE=true" \
-e "CCACHE_SIZE=100G" \
-e "SIGNATURE_SPOOFING=restricted" \
-e "CLEAN_AFTER_BUILD=true" \
-e "SIGN_BUILDS=true" \
-e "KEYS_SUBJECT=/C=AT/ST=California/L=Mountain View/O=eOS/OU=Build/CN=test/emailAddress=android@android.com" \
-e "USER_NAME=test Build" \
-e "USER_MAIL=test@e.os" \
-e "INCLUDE_PROPRIETARY=true" \
-e "OTA_URL=" \
-e "BRANCH_NAME=a16" \
-e "DEVICE_LIST=OP5D55L1" \
-e "REPO=https://gitlab.e.foundation/e/os/releases.git -b refs/tags/v4.0-a16" \
registry.gitlab.e.foundation:5000/e/os/docker-lineage-cicd:community
The command should do the following:
Is this command correct? Do I miss something?
Thanks a lot!
BRANCH NAME without version number is expected to build latest branch so e-4.1.1, for a “stable” version you can try v4.0-a16 or 4.0-a16
Also, according to [UNOFFICIAL BUILD] OnePlus 13 (dodge) for eOS-a15 3.1.x,
DEVICE LIST device codename should be (dodge)
(Note : I don’t use Docker as i feel traditional way to build more flexible and deduggable…)
I admit I am not up to speed on this but are your git credentials up to date? If you are used to signing, I guess they are.
My guess would be that if you run a correct repo init to an empty directory the missing permission to display html (404) should not effect the ability to repo init.
However if repo init fails then perhaps permissions were more thoroughly withdrawn by accident. In which case debugging docker would be “too difficult”, imho.
Thanks for your answer!
I tried v4.0-a16, but after that I got:
/root/build.sh: line 48: DEVICE_LIST_V4.0-A16: invalid variable name
At the official build guide it says I can use adb shell getprop ro.product.device and I got OP5D55L1 for the device code. I was also confused because the official name was dodge, but I was not sure if I just understand something wrong… I will try dodge in the future, maybe that helps.
I am also planning to not use docker because I can’t really see what’s going on.
Is this a good guide to build /e/OS without docker?
Thanks for the feedback.
I am not sure because I was using docker before, I just wanted to try your command. I will try doing a repo init and not using docker for that…
EDIT:
I think the credential error is because of the missing permissions, I will try when I can access the source again
This is what i use to use building a11 (my computer’s 16gb RAM don’t allow me to build current version)
Note :
The steadfasterX’s "/e/ vendor repo" was not updated for years (some flag related to /e/'s docker file have been renamed/replaced from /e/'s side),
if you want to customise your build, better is to use his generic “EXTENDROM” repo.
See also @ronnz98’s Ultimate how-to guide: Unofficial Builds using repo style for using lineage or other aosp sources that are not supported by /e/OS
In light of
. .. in order to eliminate the /e/ repo permission on a Sunday, I would also just run repo init from the Lineage build page guide.