Problem with loding gevent: BadZipfile: File is not a zip file #1739
Comments
mkg20001
changed the title
|
Problem seems to be solved by using Still leaving this open as newer version should be supported |
|
The recipe is currently running on |
|
Using python2 currently isn't an option, but upstream zeronet HelloZeroNet/ZeroNet#1773 plans to upgrade in the future, so we'll simply be stuck on 1.2.2 until py3 is ready Will try once that is done |
|
Ouch so a project with over 10K ⭐ on |
is still running on Python2 only, that hurts 😨
|
It's a python3 issue now, since this is happening on ZeroNet python3 as well I have a suspicion #763 could fix that (and then also removing the greenlet recipie and making it a pip only package) since the pip way seems to build the metadata, but uses the wrong arch (which the pr would fix) |
|
Can you share the Python3 stacktrace then? |
|
There are multiple. When using a specific version for ex, the recipie is skipped and the package is instaled with pip. Here it then complains about being compiled for the wrong arch when executed. When using it with recipie (edit: normally, without anything like I can give you the stacktrace for the last mentioned case, for the others a bit of digging in tons of gitlab ci pipelines would be required, unless I'll want to waste hours with compiling |
There is the current one. HelloZeroNet/ZeroNet-kivy#60 (comment) for context on why this happens |
|
The other method results in an architecture mismatch error, since it's using the wheel that's appropriate for the machine it gets built on and not the appropriate for android (it'd probably have to build it) |
|
Thanks for the log, then I don't see how it's the same error as the one in the ticket initially created? 🤔 |
This is basically a generic "I can't get python to load/find greenlet" issue And we all know: A different error message means progress But the problem is: Which way to solve it? I also have a third stacktrace which is different too (that one where I attempted to directly specify the version, p4a ended up using a wheel for the build server architecture) And now I'm confused as to which path to continue down: Fixing the greenlet recipe or implementing wheel support as mentioned in the pr #763 and making the greenlet recipe use wheel instead of directly calling setup.py? |
|
Once we get that out of the way, we'll know which stacktrace to analyze next |
|
👋 We use the issue tracker exclusively for bug reports and feature requests. However, this issue appears to be a support request. Please use our support channels to get help with the project. If you're having trouble installing or using python-for-android, maybe you could be interested in our quickstart guide. Let us know if this comment was made in error, and we'll be happy to reopen the issue. |
Versions
Description
It should load gevent.
Instead gevent loading causes a python error about some zip file being broken/missing.
I think this is an error that occurs during bundling (it's looking for something at the wrong place), that's why I have reported it here.
buildozer.spec
Command:
Spec file:
APK files: https://gitlab.com/mkg20001-gh/ZeroNet-kivy/-/jobs/171320223/artifacts/browse/release/
Logs
Build: https://gitlab.com/mkg20001-gh/ZeroNet-kivy/-/jobs/171270719/raw
Application:
The text was updated successfully, but these errors were encountered: