Closed kcrossen closed 5 years ago
Hi, just before transfering, this is not a Kivy issue itself, but more about python-for-android. You have warning in your backlog that you should take care of (libtoolize, pkg-config, autoconf/make, etc). Also, as per your previous issue that you manually copied some stuff and say it's working, then later reopen an issue about that it's not, please avoid :)
It would be best to first discuss about it on support channel before opening anything.
The instructions on: https://kivy.org/doc/stable/guide/packaging-osx.html and on: https://kivy.org/doc/stable/guide/android.html were followed to the letter, double checked, followed again.
The problem I am experiencing is that the posted instructions don't work on OSX 10.11.6 w/ Python 2.7.16. They fail sequentially, repeatedly. They fail w/ 1.9.1 @ https://kivy.org/downloads/, referenced from https://kivy.org/doc/stable/installation/installation-osx.html. They fail w/ Kivy-1.10.1_osx10.13.5_builtin_python2_r1.dmg.
Intuit (QuickBooks) became a giant by rounding up secretaries and people off the street to test each new release. The analog in Kivy's case is to test your build scripts on virgin machines and if it doesn't work, it's not releasable. This correctly models the problems of all new Kivy recruits.
How does it matter about "You have warning in your backlog that you should take care of (libtoolize, pkg-config, autoconf/make, etc)." How can this even apply to your VirtualBox VMs, which have many of the same failures, and should work absolutely out of the box as per instructions.
How would someone just stumbling across Kivy have any idea where to post what? How would anyone who is not an insider know that this all comes down python-for-android? You know because that's where you live. I'm not a newbie, I'm just new to Kivy, and if you think about it that's where most of your experts started.
IMHO, of course, Ken
The actual topic of all my "issues" is that procedures that could have failed in testing, instead failed for me, and according to StackExchange and your own issues board has failed for many others in exactly the same way. It's actually less work for the community as a whole, and probably for the volunteers as well, to get it right before release.
It has only just become clear where that kind of discussion happens.
See ya on the flip side.
@kcrossen your issue does not seem coherent to me.
On one hand you talk about packaging osx app with kivy/buildozer
and open the issue on kivy/kivy
.
Your log is of python-for-android which is while using linux to build a android apk.
You see we didn't ask you not to post a issue, just post a issue in the correct place, and without mixing up logs.
With the issue the way it is it's difficult to figure out what the issue is about specifically?
Is it a issue with Buildozer? then we should move it to http://github.com/kivy/buildozer Is it a issue with python-for-android? If so then it should be posted in http://kivy/python-for-android
You are new to kivy so we asked you to take help from support channel for figuring out the different projects and where to report your issue.
Basically to help us help you better.
You are new to kivy so we asked you to take help from support channel for figuring out the different projects and where to report your issue.
Basically to help us help you better.
Point well taken and well stated. Where is the discoverable guidance on your point? Here? https://kivy.org/doc/stable/contact.html, no. Here? https://kivy.org/#support, no. Here? https://github.com/kivy/kivy, no. Here? https://github.com/kivy/kivy, no.
Put yourself in the position of someone who has built several large, mission-critical Qt4/Qt5/C++ applications over the years. Who has participated in developing widgets for Qt. And couldn't find any guidance on the excellent points you mention. You, of course, know where nearly any relevant topic should be posted because you live here, it's your condo.
So I will state my problem (as I see it) by quoting you: Please "help us help you better."
(also posted in #general)
BTW, this all happened using naked buildozer on OSX 10.11.6, absolute latest of everything else, Python 2.7.16, Kivy 1.10, etc.
This is a lose-lose recipe for severely increasing support issues, see below.
(copied from #general) Another eample of toxic mix of DOC and SUPPORT, a dev philosophy issue where Kivy is shooting at its own feet (or rather the volunteer devs' feet)
File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/ssl.py", line 828, in do_handshake
self._sslobj.do_handshake()
IOError: [Errno socket error] [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:727)
Ugly temporary fix in ssl.py starting at line 590:
# create the SSL object
try:
self._context.check_hostname = False
self._context.verify_mode = CERT_NONE
self._sslobj = self._context._wrap_socket(self._sock, server_side,
server_hostname, ssl_sock=self)
if do_handshake_on_connect:
What happened here (and similar) happens over and over again., issue closed and reopened. When naked buildozer wakes up it has no idea of it's environment. When it's tested by Kivy devs, it's hardly a virgin machine, so it probably works...mostly. Promoting raw buildozer installs looks like a sure loser to me. Docker / VMs, on the other hand, should work identically on virgin machines and on dev machines, and dev testing will be universally applicable.
@kcrossen are you here to just make several incoherent links to absolutely unrelated logs/code? or to raise a actual issue? to get some help to try help solve a possible issue?
What is the issue? <- Give us actual log of the actual problem you retrying to solve.
For some one supposed to be so experienced
I would assume you would be able to follow a simple issue template.
Issues are not for rants.
Please open a issue following the issue template if there is a support issue.
I never did get buildozer.spec to successfully build an OSX app. I wound up studying how the code worked and then did all the same operations by hand. It took a tiny fraction of the time I had already invested in tracing down bugs in the buildozer scripts. By hand worked.
I'll post my method at https://github.com/kcrossen/CloudWatch_Remote_Monitor/tree/master/Source_Code
Versions
As in many previously posted issues, no changes.
Description
// REPLACE ME: What are you trying to get done, what has happened, what went wrong, and what did you expect?
Code and Logs