Comprehensive list of broken recipes #1402
Comments
AndreMiras
added a commit
to AndreMiras/python-for-android
that referenced
this issue
Oct 14, 2018
Populated the list of broken recipes and moved to a dedicated `constants.py` file. Broken recipes are mostly devided in 3 categories: 1) recipes not yet migrated from python2 to python3crystax 2) recipes that don't have environment var well setup 3) recipes that are not broken but require a system package
AndreMiras
added a commit
to AndreMiras/python-for-android
that referenced
this issue
Oct 14, 2018
Populated the list of broken recipes and moved to a dedicated `constants.py` file. Broken recipes are mostly divided in 3 categories: 1) recipes not yet migrated from python2 to python3crystax 2) recipes that don't have environment var well setup 3) recipes that are not broken but require a system package
tshirtman
added a commit
that referenced
this issue
Oct 14, 2018
…cipe_list List of broken recipes for python3crystax, refs #1402
AndreMiras
added a commit
that referenced
this issue
Oct 14, 2018
…cipe_list_python2 List of broken recipes for python2, fixes #1402
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When working on #1401 I realised we still have some broken recipes in the tree at least for python3crystax.
Even though we don't want to have red builds for things that were already broken, we still want to have a clear status of what's broken and what's not.
Basically the idea is to try to compile every single recipes and add the broken ones in the ignore list (
BROKEN_RECIPES) from #1401. That way we can track and fix them later on meanwhile keeping a green build.I would like to address it in this task. Basically the output of the task should be a PR making the
BROKEN_RECIPESlist comprehensive. With bonus points for creating an issue per broken recipes 😄The text was updated successfully, but these errors were encountered: