Open ghost opened 1 year ago
the second thing is known, it was in the works of being resolved in another PR but i can't work on it thanks to a lack of computer to effectively do it on
This is the result of the disk image not being built. Can you please post the output of ./tools/mkimage.sh
? Also did you install the dependencies via ./tools/deps.sh
?
It looks like there is something wrong with the deps.sh script. I managed to make it work by editing it.
ANOTHER BIG PROBLEM: WHY IS DISK.IMG OVER 500GB IN SIZE?
OK, so, the problem has to do with the script attempting to use parted. parted (on my system at least) requires sudo to run, however the script did not attempt to use sudo to run it.
also, please do not create in excess of 500gb files on someone's computer without them knowing. That is half of my SSD's space. Your operating system is like 7kb it should not require that much space. FIX THAT.
bro built the entire sysroot 💀
um, I'm sorry? But, it doesn't seem like somehow changing what you build into it changes the size. https://github.com/Andy-Python-Programmer/aero/blob/master/tools/mkimage.sh#L21 The size is hardcoded into this dd command.
The command in this line creates a sparse file (if your file system supports that). The file looks like it uses 512GB but it does not. Only data written to the file later uses disk space. du -h file shows you the actual size of the file.
It looks like there is something wrong with the deps.sh script. I managed to make it work by editing it.
Can you explain what was wrong?
ANOTHER BIG PROBLEM: WHY IS DISK.IMG OVER 500GB IN SIZE?
https://github.com/Andy-Python-Programmer/aero/issues/101#issuecomment-1513662847
it still doesn't really need to be 500GB but sure.
I'm not sure exactly what the problem with deps.sh is. All I know is that it didn't work properly as is. I removed the if else around the deps_linux file and kept just the Debian code and it worked fine after that. Probably because Debian has ID
and not ID_LIKE
.
mins@debian:~$ cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 11 (bullseye)"
NAME="Debian GNU/Linux"
VERSION_ID="11"
VERSION="11 (bullseye)"
VERSION_CODENAME=bullseye
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"
hey, I met the same question with you. But my system is ubuntu22.04. How did you solve your problem? I delete the ID LIKE in the /etc/os-release but it doesn't work. Whether do I need to build the entire sysroot(it's so big that I not really want to install it)? @minneelyyyy
Literally why is it 500GB in size?
This entire build pipeline is sending me. First deps.sh
is wholly problematic because it doesn't check your distribution, then a 500GB image is created without consent, and there is no way to use the QEMU command generated by aero.py
without building, so you must have the dependencies installed.
Edit: Apparently there is an --only-run
flag, but then you still run into the issue of needing the dependencies installed, since the mkimage.sh
script is not designed to run in a container, whatsoever. Which after running, of course, builds a 500GB image.
The command in this line creates a sparse file (if your file system supports that). The file looks like it uses 512GB but it does not. Only data written to the file later uses disk space. du -h file shows you the actual size of the file.
What confuses me is why the sparse file is so big. Is there a practical reason I'm missing?
I just cloned the repository, installed the dependencies, realized that I didn't have pip installed so I installed that and then pip installed requests and xbstrap, ran it and realized
meson
is not installed so i installed that, then it finally compiled and ran. However, it is giving me this error.Here is the full log:
Not sure if it's related or not, but another issue I am seeing is this