Error message claiming conflicting dependencies when requesting a recipe (here, python3) that was not (yet) available

[brady-ds]

Versions

• Python: 3.6.5
• OS: OpenSUSE 15.0
• Kivy: 1.10.1
• Cython: 0.28.3

Description

When asking Buildozer to build an APK using the new Python 3 recipe, I had the default p4a.branch = stable, which pulled in a version of p4a affected by #1542. I eventually fixed the problem by switching to p4a.branch = master, but the original error message was unhelpful, with an error from graph.py about requirements pulling in conflicting dependencies, which in this case was not the reason for not finding any valid dependency graphs.

buildozer.spec

Commands:

$ sudo pip3 install --upgrade pyjnius pygame kivy buildozer
$ touch main.py
$ buildozer init
$ sudo sed -i 's|android/repository|android/ndk|' /usr/lib/python3.6/site-packages/buildozer/targets/android.py
$ buildozer -v android debug

(The sed in there is to work around buildozer 760 and friends.)

Spec file: just the current default.spec

Logs

…
[INFO]:    No existing dists meet the given requirements!
[INFO]:    No dist exists that meets your requirements, so one will be built.
[ERROR]:   Didn't find any valid dependency graphs.
[ERROR]:   This means that some of your requirements pull in conflicting dependencies.
[ERROR]:   Exiting.
# Command failed: /usr/bin/python3 -m pythonforandroid.toolchain create --dist_name=myapp --bootstrap=sdl2 --requirements=python3,kivy --arch armeabi-v7a --copy-libs --color=always --storage-dir="/home/cse/.buildozer/android/platform/build"
# 
# Buildozer failed to execute the last command
# The error might be hidden in the log above this error
# Please read the full log, and search for it before
# raising an issue with buildozer itself.
# In case of a bug report, please add a full log with log_level = 2

[HeaTTheatR]

@brady-ds Broke the python-for-android again - #1542

[brady-ds]

@HeaTTheatR Thanks. I've tried to fold that info into the report. I believe the error message could still be better worded to account for ways to have zero dependency graphs other than because of conflicting requirements.

[inclement]

This happened because a python3 recipe did exist but didn't have proper functionality. That's no longer the case, and other error messages should be clearer.