Ticket #1514 (closed defect: fixed)
FoodForce2 Activity has malformed python files
| Reported by: | mikus | Owned by: | garycmartin |
|---|---|---|---|
| Priority: | Unspecified by Maintainer | Milestone: | Unspecified by Release Team |
| Component: | ActivityTeam | Version: | 0.84.x |
| Severity: | Unspecified | Keywords: | |
| Cc: | mikus@… | Distribution/OS: | OLPC |
| Bug Status: | Unconfirmed |
Description
Run 'file FoodForce2.activity/*.py' and look at the output.
There are files there that do not have proper line-endings for Linux Python. [Some have line-endings left by a Windows editor; some I can't figure out.]
I found this when the FoodForce2-1 Activity would not launch on an XO-1.5 system -- some of the python files (e.g. load_images.py) had been written-over by binary garbage (those files were correct before the launch of FoodForce2 was invoked), which in turn caused a Python error when it tried to execute (i.e., interpret) the now-garbage files.
[I was able to bypass the over-writing_with_binary_garbage problem by setting all the .py files in FoodForce2.activities to read-only.]
I do not know what caused this improper over-writing with binary garbage -- but cleaning up the form of the Python files should be the first step towards fixing the failure-to-launch problem I experienced on the XO-1.5
