The actual command contain the back slash, it’s just the browser\website escaping them
That’s what I nean.with my remark
what do you mean is still not clear.
was the command that I ran was wrong or the command that is posted in forum seems wrong ?
Sirry, your username has confused me.
The command with the back slash was ok. But i’m talking only about a supported pie device build NOT about a building of an xiaomi device !!
Could you pls add the log from telegram group ? It’s needed for finding the issue
It’s fine.
You asked me to build sailfish for Pie and I tried to build and shared my result.
I’ll try to build Xiaomi device once I’m successful in building supported device.
Pls use del.dog for all logs. Thx
Sure. Deleted the logs from the post, but the link shared , remains.
It would be better if we sub catagorise devices based on official build versions(nougat / Oreo / Pie) .
Also we should NOT list the devices whose ROMS are not getting built automatically/manually by the Docker environment, without any intervention. Eg : v1-oreo for Tissot is not getting built by Docker image and still the page : https://doc.e.foundation/how-tos/build-e contais its name in the example.
Atleast the examples mentioned should run flawlessly.
I am facing the same issue with the docker build.
Got the latest docker image for /e/
Tried building for “kiwi” device as per example in the how to
And ended up with the below error:
OSError: [Errno 17] File exists: ‘/srv/src/NOUGAT/vendor/xiaomi/.git’
onerror(os.listdir, path, sys.exc_info())
File “/usr/lib/python2.7/shutil.py”, line 237, in rmtree
names = os.listdir(path)
OSError: [Errno 2] No such file or directory: ‘/srv/src/NOUGAT/vendor/xiaomi/.git’
Xiaomi devices won’t work because TheMuppets has closed the sources. For Xiaomi device you have to use the build way for ‘lineage unsupported devices’
It’s not working either . I’m testing the one provided by @harvey186.
I’ll be logging bugs for Docker & non-Docker methods not working for building ROM.
You have used my sailfish.sh script and cloned manually the missing policy files and still getting errors ???
After making the changes mentioned by you, getting source from internet was good and smooth.
Sadly, there was a “storage” bottleneck on my PC and it ran out of space while building.
Restarted the process again.
Will share the result by today evening.
If you are using my salfish.sh you will use 100 GB ccache. You can change the value back to 50 GB in the script
I just made the “sepolicy” related changes, nothing else was changed in your script. -)