Closed vbajs closed 6 months ago
Note:If u cannot run it in linux,you may need do "chmod a+x ./*"
Note:If u cannot run it in linux,you may need do "chmod a+x ./*"
Unfortunately, this has done nothing. Also, the issue needs to be updated now to also indicate that this is also effecting unpacking too
A month late, but a proper solution for those who are experiencing this
chmod +x bin/Linux/x86_64/*
Looks like chmod doesn't really recursively set execute permission throughout the entire directory Credits to @ookiineko for finding this and sending it on the telegram group (linked in README)
Looks like chmod doesn't really recursively set execute permission throughout the entire directory
in fact, i think this is a bug in the repository, binary files dont have executable permission by default, unless you run the build.py to produce a binary distribution. btw, maybe you can also use chmod -R +x YOUR_DIR
to change the permissons recursively
if execution permission is missing, maybe the tool will also break on macos when running directly from source, @ColdWindScholar, maybe change the file mode for binaries in this repository (by doing chmod +x for once and commit on a posix machine)
in fact i think changing it in tree is reasonable, since we also want to support running the tool without building, and no need to make the source tree dirty by doing the chmod locally, since i have also encountered this problem on my linux machine while testing with the locales lately
should be fixed by the pr
now the chmod workaround should be no longer needed
MIO-KITCHEN Source was used @ 2a9922ffacb41c16c18c95c05909861c742ab00e Running Arch linux and did the following steps to run
When attempting to pack any partition as either ext4 with the option to use MK2FS+ESDROID or EROFS, the following error occurs
Attempted but failed workarounds
1. run `tool.py` as sudo We then experience the issue of the python script unable to find tk. 2. `sudo chown -r $USER MIO-KITCHEN-SOURCE` Unforunately does nothing