Firmware upload fails on the latest 2.5, build 25 image

[BrianAdams]

Hi Brian
Thanks again for the help
The OpenROV-2.5-25.img mounted on the SD card updated successfully using your work around and I could log onto both Cockpit and Dashboard and all seemed good
I then attempted doing similar with OpenROV-2.5-26.img (I also tried the OpenROV-flash-2.5-26.img after it had finished flashing to the eMMC with the same results) and this then failed with the following extracted from Putty
rov@OpenROV:$ sudo /opt/openrov/linux/arduino/firmware-installfromsource.sh
[sudo] password for rov:
unpacking
staging: build dir is /tmp/tmp.RepSbDnnuV
Traceback (most recent call last):
File "/usr/local/bin/ino", line 3, in
from ino.runner import main
File "/usr/local/lib/python2.7/dist-packages/ino/runner.py", line 23, in
import ino.commands
File "/usr/local/lib/python2.7/dist-packages/ino/commands/init.py", line 5, in
from ino.commands.build import Build
File "/usr/local/lib/python2.7/dist-packages/ino/commands/build.py", line 16, in
from ino.environment import Version
File "/usr/local/lib/python2.7/dist-packages/ino/environment.py", line 19, in
from glob2 import glob
ImportError: No module named glob2
firmware-stage.sh: Failed to initialize the Arduino project directory. Aborting
firmware-installfromsource.sh: Staging Firmware Failed! Aborting
rov@OpenROV:$

[codewithpassion]

Nice... Had the same issue with debian. glob2 is either a new package or
something like that. It's manually installed by the Debian build scripts.
Details follow tomorrow.

• Dominik
  On Jun 27, 2014 11:26 PM, "badevguru" notifications@github.com wrote:

Hi Brian
Thanks again for the help
The OpenROV-2.5-25.img mounted on the SD card updated successfully using
your work around and I could log onto both Cockpit and Dashboard and all
seemed good
I then attempted doing similar with OpenROV-2.5-26.img (I also tried the
OpenROV-flash-2.5-26.img after it had finished flashing to the eMMC with
the same results) and this then failed with the following extracted from
Putty
rov@OpenROV:$ sudo
/opt/openrov/linux/arduino/firmware-installfromsource.sh
[sudo] password for rov:
unpacking
staging: build dir is /tmp/tmp.RepSbDnnuV
Traceback (most recent call last):
File "/usr/local/bin/ino", line 3, in
from ino.runner import main
File "/usr/local/lib/python2.7/dist-packages/ino/runner.py", line 23, in
import ino.commands
File "/usr/local/lib/python2.7/dist-packages/ino/commands/init.py",
line 5, in
from ino.commands.build import Build
File "/usr/local/lib/python2.7/dist-packages/ino/commands/build.py", line
16, in
from ino.environment import Version
File "/usr/local/lib/python2.7/dist-packages/ino/environment.py", line 19,
in
from glob2 import glob
ImportError: No module named glob2
firmware-stage.sh: Failed to initialize the Arduino project directory.
Aborting
firmware-installfromsource.sh: Staging Firmware Failed! Aborting
rov@OpenROV:$

—
Reply to this email directly or view it on GitHub
#245.

[BrianAdams]

Yep. Reproduced on the latest image. Looks like we got burned with yet another package update. We will either need to move forward with getting glob2 installed on the image or find out what package moved and find a way to pin that version number.

[codewithpassion]

I'll dig up the change I had to do to get glob2 in the Debian branch.

It could be that it's a problem with ino. Might be an updated version
there.
On Jun 28, 2014 8:41 AM, "badevguru" notifications@github.com wrote:

Yep. Reproduced on the latest image. Looks like we got burned with yet
another package update. We will either need to move forward with getting
glob2 installed on the image or find out what package moved and find a way
to pin that version number.

—
Reply to this email directly or view it on GitHub
#245 (comment)
.

[BrianAdams]

Yea. Looks the the 4/15 update bit us. https://github.com/amperka/ino/blame/85d1768e9c19d72d2a32b8fa8642e8ca7ab98d03/requirements.txt

[BrianAdams]

If we can pin the ino version to this one in github I suspect we will resolve the issue: fe6e94a35e0e64fb43731eca420df3eab27b3cce

[BrianAdams]

Which is version 0.3.6

[BrianAdams]

Went ahead and grabbed @codewithpassion updates 72b37ecde3fe89d427fca2b4baa105b548403d44 and 2526c7581366debe730896b0ba8f0d66b2c323e5 to see if that will fix the issue

[BrianAdams]

Latest build of the image, 29, has this fixed now.