pydantic_core makes all build fails about python-for-android

[magowiz]

Probably I will try also to set a constraint to pydantic package, I don't know if that version needs also a pydantic_core, maybe is just a pure python package, worth trying.

By the way thank you very much for your help, I close this.

[T-Dynamos]

@magowiz

Can you clear that what you mean by "all builds"? all requirements?
As I see only see ffpyplayer build is failing.

So issue is about ffpyplayer build failure?

[magowiz]

@magowiz

Can you clear that what you mean by "all builds"? all requirements? As I see only see ffpyplayer build is failing.

I mean for each of the build I launch, one for each architecture

So issue is about ffpyplayer build failure?

I don't know, before I add pydantic_core to requirements the builds were all fine, so I thought it was pydantic_core offending package, but if you see that ffpyplayer is failing, maybe there could be a sort of conflict between those packages?

I will try again, after cleaning all directories to build with all requirements except pydantic_core so I would be able to confirm you this.

[magowiz]

@T-Dynamos :
sorry, probably due to the cache I had some false positive: successful builds that should have failed with a clean build (empty buildozer home and build folders), in order to get a working build I had to remove:

• shazamio_core
• pydantic_core
• rustup from dockerfile
• p4a from develop to master

I added those because master branch doesn't have the possibility to run rust recipes, shazamio_core and pydantic_core.

once I reverted all those changes, the build start to succeed, so I think it could be the switch of p4a branch from develop to master.

How do you suggest to proceed? Should I try to switch to develop branch and attach updated information in this issues?

[T-Dynamos]

Thanks for insights, I will look into it.

[T-Dynamos]

@magowiz Please test #3025 .

[magowiz]

I've seen you did, in #3025, the merge into develop, so, I'm asking for confirmation: are you telling me I should test develop right now after your 5h ago change?

[T-Dynamos]

@magowiz Yes.

[magowiz]

@magowiz Yes.

I tried but builds still failing, but probably on another package, it seems to me sqlalchemy I'm going to attach you the full log in order to provide you most information possible. If is it another package/recipe, do I need to open a new issue?

I compressed the log because was huge (~56MB)
build.zip

Let me know what should I do to address this issue, if it is another one.

Thanks in advance,
magowiz

[T-Dynamos]

Seeing your build order sqlalchemy seems like last package needs to be fixed.
Will look into it. :)

[magowiz]

Seeing your build order sqlalchemy seems like last package needs to be fixed. Will look into it. :)

Thank you very much, let's hope that after this also shazamio_core and pydantic_core, which are rust builds, will work.

[T-Dynamos]

@magowiz You can try develop branch now. #3027 is merged.

[magowiz]

Yeah, it worked, I'm going to try pydantic_core and shazamio_core

[magowiz]

The build went fine but if I open the armv8 apk on my phone, I find out that probably a library for another architecture were installed:

 ImportError: dlopen failed: "/data/data/net.magowiz.musenote/files/app/_python_bundle/site-packages/pydantic_core/_pydantic_core.so" is for EM_X86_64 (62) instead of EM_AARCH64 (183)

[T-Dynamos]

@magowiz This meant that your build didn't picked pydantic_core recipe.

[magowiz]

I saw that recipe folder is pydantic-core and I put pydantic_core in requirements, could it be for dash/underscore difference in the name? Do I need to write in requirements exactly pydantic-core? Otherwise how could it possible that mine build didn't pick up the according recipe?

[magowiz]

I was able to build it correctly, I needed to put the same exact name as recipe. I was missing also annotated_types and I was able to add it, by the way it seems that is having some issues I don't have when I run the same code from desktop:

   File "/home/jenkins/workspace/nization_folder_musenote_develop/.buildozer/arm64-v8a/android/platform/build-arm64-v8a/build/python-installs/musenote/arm64-v8a/shazamio/__init__.py", line 1, in <module>
   File "/home/jenkins/workspace/nization_folder_musenote_develop/.buildozer/arm64-v8a/android/platform/build-arm64-v8a/build/python-installs/musenote/arm64-v8a/shazamio/serializers.py", line 3, in <module>
   File "/home/jenkins/workspace/nization_folder_musenote_develop/.buildozer/arm64-v8a/android/platform/build-arm64-v8a/build/python-installs/musenote/arm64-v8a/shazamio/schemas/base.py", line 20, in <module>
   File "/home/jenkins/workspace/nization_folder_musenote_develop/.buildozer/arm64-v8a/android/platform/build-arm64-v8a/build/python-installs/musenote/arm64-v8a/pydantic/_internal/_model_construction.py", line 115, in __new__
   File "<frozen abc>", line 106, in __new__
 TypeError: Cannot create a consistent method resolution
 order (MRO) for bases BaseModel, BaseIdTypeHref, Generic

I don't know if this could be related to pydantic

[T-Dynamos]

You should report this to shazamio.

[magowiz]

I found the reason:
on my poetry.lock I have version 1.10.15 of pydantic, and a constraint that tells
pydantic = ">=1.10.2,<2.0.0"

on pydantic-core recipe we have version 2.16.1, also the fact that there isn't a way to resolve automatically dependencies and to use packages constraints on p4a doesn't help, so probably with a pydantic 1.x won't fail, by the way I'll report it to shazamio project.

Should I close this one?

[magowiz]

I commented original issue on shazamio, if they introduce compatibility with pydantic 2.x it should work.

[T-Dynamos]

Should I close this one?

Yes.

so probably with a pydantic 1.x won't fail

Let's hope.