bb-bonescript-installer-beta ( 0.5.0-beta5) upgrade fails

bb-bonescript-installer-beta upgrade fails:

make: Entering directory ‘/usr/local/lib/node_modules/bonescript/node_modules/ffi/node_modules/ref/build’
CXX(target) Release/obj.target/binding/src/binding.o
SOLINK_MODULE(target) Release/obj.target/binding.node
COPY Release/binding.node
make: Leaving directory ‘/usr/local/lib/node_modules/bonescript/node_modules/ffi/node_modules/ref/build’

serialport@2.0.6 install /usr/local/lib/node_modules/bonescript/node_modules/serialport
node-pre-gyp install --fallback-to-build

make: Entering directory ‘/usr/local/lib/node_modules/bonescript/node_modules/serialport/build’
CXX(target) Release/obj.target/serialport/src/serialport.o
Killed
dpkg: error processing package bb-bonescript-installer-beta (–configure):
subprocess installed post-installation script returned error exit status 137
Setting up doc-beaglebone-getting-started (1.20151204-2~bpo80+20160421+1) …
Errors were encountered while processing:
bb-bonescript-installer-beta
E: Sub-process /usr/bin/dpkg returned an error code (1)

kernel: 4.1.18-ti-r56
Beagleboard.org Debian Image 2016-04-03

Its been pretty solid up to now, all the bonescript examples ( analogWrite() analogRead(), digitalWrite(), digitalRead() attachInterrupt() )seem to work without extraneous error or warning messages.

I’ve been doing apt-get update, apt-get upgrade pretty regularly hoping to keep current.

Has a required kernel upgrade come it that doesn’t install with apt-get upgrade?

I’ve been using this system the way I figure a newbie who only wanted bonescript, python, and node-red might do.
I can see how pushing kernel upgrades could rather quickly get you into space issues if confined to the 4GB eMMC, but if its a real dependency not doing so would seem to be a problem.

bb-bonescript-installer-beta upgrade fails:

make: Entering directory
'/usr/local/lib/node_modules/bonescript/node_modules/ffi/node_modules/ref/build'
  CXX(target) Release/obj.target/binding/src/binding.o
  SOLINK_MODULE(target) Release/obj.target/binding.node
  COPY Release/binding.node
make: Leaving directory
'/usr/local/lib/node_modules/bonescript/node_modules/ffi/node_modules/ref/build'

> serialport@2.0.6 install
/usr/local/lib/node_modules/bonescript/node_modules/serialport
> node-pre-gyp install --fallback-to-build

make: Entering directory
'/usr/local/lib/node_modules/bonescript/node_modules/serialport/build'
  CXX(target) Release/obj.target/serialport/src/serialport.o
Killed
dpkg: error processing package bb-bonescript-installer-beta (--configure):
subprocess installed post-installation script returned error exit status
137
Setting up doc-beaglebone-getting-started (1.20151204-2~bpo80+20160421+1)
...
Errors were encountered while processing:
bb-bonescript-installer-beta
E: Sub-process /usr/bin/dpkg returned an error code (1)

kernel: 4.1.18-ti-r56
Beagleboard.org Debian Image 2016-04-03

Its been pretty solid up to now, all the bonescript examples (
analogWrite() analogRead(), digitalWrite(), digitalRead() attachInterrupt()
)seem to work without extraneous error or warning messages.

I've been doing apt-get update, apt-get upgrade pretty regularly hoping
to keep current.

Has a required kernel upgrade come it that doesn't install with apt-get
upgrade?

Nope...

I've been using this system the way I figure a newbie who only wanted
bonescript, python, and node-red might do.
I can see how pushing kernel upgrades could rather quickly get you into
space issues if confined to the 4GB eMMC, but if its a real dependency not
doing so would seem to be a problem.

Odd, was this the iot or lxqt or console image?

if you do : dpkg --list | pastebinit

we can compare against:

https://paste.debian.net/440395/

From a fresh 2016-04-03 iot image i'm seeing:

debian@beaglebone:~$ cat /etc/dogtag
BeagleBoard.org Debian Image 2016-04-03
debian@beaglebone:~$ uname -r
4.1.18-ti-r56
debian@beaglebone:~$ sudo apt-get update ; sudo apt-get upgrade

Reading state information... Done

Calculating upgrade... Done
The following packages will be upgraded:
  bb-bonescript-installer-beta bb-wl18xx-firmware connman
  doc-beaglebone-getting-started libmraa0 linux-libc-dev openssh-client
  openssh-server openssh-sftp-server tiomapconf upm
11 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 15.6 MB of archives.
After this operation, 63.5 kB of additional disk space will be used.
Do you want to continue? [Y/n] y

0% [Working]
0% [Waiting for headers] [Waiting for headers]
Get:1 http://repos.rcn-ee.com/debian/ jessie/main libmraa0 armhf
0.9.5-git20160420-0rcnee1~bpo80+20160420+1 [408 kB]
Get:2 http://security.debian.org/ jessie/updates/main openssh-sftp-server
armhf 1:6.7p1-5+deb8u2 [33.2 kB]
Get:3 http://httpredir.debian.org/debian/ jessie-updates/main
linux-libc-dev armhf 3.16.7-ckt25-2 [1,004 kB]
Get:4 http://security.debian.org/ jessie/updates/main openssh-server armhf
1:6.7p1-5+deb8u2 [324 kB]
Get:5 http://repos.rcn-ee.com/debian/ jessie/main upm armhf
0.5.1-git20160410-0rcnee1~bpo80+20160410+1 [12.3 MB]
Get:6 http://security.debian.org/ jessie/updates/main openssh-client armhf
1:6.7p1-5+deb8u2 [643 kB]
Get:7 http://repos.rcn-ee.com/debian/ jessie/main
bb-bonescript-installer-beta all 0.5.0~beta4-1rcnee2~bpo80+20160421+1
[4,062 B]
Get:8 http://repos.rcn-ee.com/debian/ jessie/main
doc-beaglebone-getting-started all 1.20151204-2~bpo80+20160421+1 [17.2 kB]
Get:9 http://repos.rcn-ee.com/debian/ jessie/main connman armhf
1.32-git20160418-0rcnee1~bpo80+20160418+1 [307 kB]
Get:10 http://repos.rcn-ee.com/debian/ jessie/main bb-wl18xx-firmware all
1.20160413-0rcnee1~bpo80+20160413+1 [48.1 kB]
Get:11 http://repos.rcn-ee.com/debian/ jessie/main tiomapconf armhf
1.72.0-git20160414-1~bpo80+20160414+1 [535 kB]
Fetched 15.6 MB in 29s (529 kB/s)
Preconfiguring packages ...
(Reading database ... 52946 files and directories currently installed.)
Preparing to unpack
.../libmraa0_0.9.5-git20160420-0rcnee1~bpo80+20160420+1_armhf.deb ...
Unpacking libmraa0:armhf (0.9.5-git20160420-0rcnee1~bpo80+20160420+1) over
(0.9.5-git20160302-0rcnee1~bpo80+20160302+1) ...
Preparing to unpack
.../upm_0.5.1-git20160410-0rcnee1~bpo80+20160410+1_armhf.deb ...
Unpacking upm:armhf (0.5.1-git20160410-0rcnee1~bpo80+20160410+1) over
(0.5.1-git20160302-0rcnee6~bpo80+20160302+1) ...
Preparing to unpack
.../bb-bonescript-installer-beta_0.5.0~beta4-1rcnee2~bpo80+20160421+1_all.deb
...
Unpacking bb-bonescript-installer-beta
(0.5.0~beta4-1rcnee2~bpo80+20160421+1) over
(0.5.0~beta3-0rcnee1~bpo80+20160226+1) ...
Preparing to unpack
.../doc-beaglebone-getting-started_1.20151204-2~bpo80+20160421+1_all.deb ...
Unpacking doc-beaglebone-getting-started (1.20151204-2~bpo80+20160421+1)
over (1.20151204-1~bpo80+20151207+1) ...
Preparing to unpack .../openssh-sftp-server_1%3a6.7p1-5+deb8u2_armhf.deb ...
Unpacking openssh-sftp-server (1:6.7p1-5+deb8u2) over (1:6.7p1-5+deb8u1) ...
Preparing to unpack .../openssh-server_1%3a6.7p1-5+deb8u2_armhf.deb ...
Unpacking openssh-server (1:6.7p1-5+deb8u2) over (1:6.7p1-5+deb8u1) ...
Preparing to unpack .../openssh-client_1%3a6.7p1-5+deb8u2_armhf.deb ...
Unpacking openssh-client (1:6.7p1-5+deb8u2) over (1:6.7p1-5+deb8u1) ...
Preparing to unpack
.../connman_1.32-git20160418-0rcnee1~bpo80+20160418+1_armhf.deb ...
Unpacking connman (1.32-git20160418-0rcnee1~bpo80+20160418+1) over
(1.31-git20160309-0rcnee1~bpo80+20160309+1) ...
Preparing to unpack .../linux-libc-dev_3.16.7-ckt25-2_armhf.deb ...
Unpacking linux-libc-dev:armhf (3.16.7-ckt25-2) over (3.16.7-ckt25-1) ...
Preparing to unpack
.../bb-wl18xx-firmware_1.20160413-0rcnee1~bpo80+20160413+1_all.deb ...
Unpacking bb-wl18xx-firmware (1.20160413-0rcnee1~bpo80+20160413+1) over
(1.20160310-0rcnee2~bpo80+20160310+1) ...
Preparing to unpack
.../tiomapconf_1.72.0-git20160414-1~bpo80+20160414+1_armhf.deb ...
Unpacking tiomapconf (1.72.0-git20160414-1~bpo80+20160414+1) over
(1.72.0-git20150828-1~bpo80+20151023+1) ...
Processing triggers for man-db (2.7.0.2-5) ...
Processing triggers for systemd (215-17+deb8u4rcnee1~bpo80+20160313+1) ...
Processing triggers for dbus (1.8.20-0+deb8u1) ...
Setting up libmraa0:armhf (0.9.5-git20160420-0rcnee1~bpo80+20160420+1) ...
Setting up upm:armhf (0.5.1-git20160410-0rcnee1~bpo80+20160410+1) ...
Setting up bb-bonescript-installer-beta
(0.5.0~beta4-1rcnee2~bpo80+20160421+1) ...
bb-bonescript-installer:npm: [2.15.0]
bb-bonescript-installer:node: [v0.12.13]
bb-bonescript-installer:Installing: bonescript-0.5.0-beta4 (for bonescript)
[0m systemd@0.2.6: wanted: {"node":">=0.6.11 <0.11.0"} (current:
{"node":"0.12.13","npm":"2.15.0"})

spi@0.2.0 install /usr/local/lib/node_modules/bonescript/node_modules/spi
node-gyp rebuild

[0Gmake: Entering directory
'/usr/local/lib/node_modules/bonescript/node_modules/spi/build'
[0G CXX(target) Release/obj.target/_spi/src/spi_binding.o
[0G../src/spi_binding.cc: In member function ‘void
Spi::full_duplex_transfer(v8::Isolate*, const
v8::FunctionCallbackInfo<v8::Value>&, char*, char*, size_t, uint32_t,
uint16_t, uint8_t)’:
../src/spi_binding.cc:199:3: warning: missing initializer for member
‘spi_ioc_transfer::cs_change’ [-Wmissing-field-initializers]
   };
   ^
../src/spi_binding.cc:199:3: warning: missing initializer for member
‘spi_ioc_transfer::tx_nbits’ [-Wmissing-field-initializers]
../src/spi_binding.cc:199:3: warning: missing initializer for member
‘spi_ioc_transfer::rx_nbits’ [-Wmissing-field-initializers]
../src/spi_binding.cc:199:3: warning: missing initializer for member
‘spi_ioc_transfer::pad’ [-Wmissing-field-initializers]
[0G SOLINK_MODULE(target) Release/obj.target/_spi.node
  COPY Release/_spi.node
make: Leaving directory
'/usr/local/lib/node_modules/bonescript/node_modules/spi/build'

i2c@0.2.1 install /usr/local/lib/node_modules/bonescript/node_modules/i2c
node-gyp rebuild

[0Gmake: Entering directory
'/usr/local/lib/node_modules/bonescript/node_modules/i2c/build'
  CXX(target) Release/obj.target/i2c/src/i2c.o
[0G SOLINK_MODULE(target) Release/obj.target/i2c.node
[0G COPY Release/i2c.node
make: Leaving directory
'/usr/local/lib/node_modules/bonescript/node_modules/i2c/build'

epoll@0.1.17 install

/usr/local/lib/node_modules/bonescript/node_modules/epoll

node-gyp rebuild

make: Entering directory
'/usr/local/lib/node_modules/bonescript/node_modules/epoll/build'
  CXX(target) Release/obj.target/epoll/src/epoll.o
[0G SOLINK_MODULE(target) Release/obj.target/epoll.node
  COPY Release/epoll.node
make: Leaving directory
'/usr/local/lib/node_modules/bonescript/node_modules/epoll/build'

ref@1.3.2 install

/usr/local/lib/node_modules/bonescript/node_modules/ffi/node_modules/ref

node-gyp rebuild

make: Entering directory
'/usr/local/lib/node_modules/bonescript/node_modules/ffi/node_modules/ref/build'
  CXX(target) Release/obj.target/binding/src/binding.o
SOLINK_MODULE(target) Release/obj.target/binding.node
  COPY Release/binding.node
make: Leaving directory
'/usr/local/lib/node_modules/bonescript/node_modules/ffi/node_modules/ref/build'

ffi@2.0.0 install /usr/local/lib/node_modules/bonescript/node_modules/ffi
node-gyp rebuild

make: Entering directory
'/usr/local/lib/node_modules/bonescript/node_modules/ffi/build'
  CC(target) Release/obj.target/ffi/deps/libffi/src/prep_cif.o
  CC(target) Release/obj.target/ffi/deps/libffi/src/types.o
  CC(target) Release/obj.target/ffi/deps/libffi/src/raw_api.o
  CC(target) Release/obj.target/ffi/deps/libffi/src/java_raw_api.o
  CC(target) Release/obj.target/ffi/deps/libffi/src/closures.o
  CC(target) Release/obj.target/ffi/deps/libffi/src/arm/ffi.o
../deps/libffi/src/arm/ffi.c: In function ‘ffi_prep_args’:
../deps/libffi/src/arm/ffi.c:72:10: warning: comparison between signed and
unsigned integer expressions [-Wsign-compare]
    && vi < ecif->cif->vfp_nargs && vfp_type_p (*p_arg))
          ^
../deps/libffi/src/arm/ffi.c: In function ‘ffi_prep_incoming_args_SYSV’:
../deps/libffi/src/arm/ffi.c:335:10: warning: comparison between signed and
unsigned integer expressions [-Wsign-compare]
    && vi < cif->vfp_nargs && vfp_type_p (*p_arg))
          ^
../deps/libffi/src/arm/ffi.c: In function ‘layout_vfp_args’:
../deps/libffi/src/arm/ffi.c:750:17: warning: comparison between signed and
unsigned integer expressions [-Wsign-compare]
   for (i = 0; i < cif->nargs; i++)
                 ^
  CC(target) Release/obj.target/ffi/deps/libffi/src/arm/sysv.o
  AR(target) Release/obj.target/deps/libffi/libffi.a
  COPY Release/libffi.a
  CXX(target) Release/obj.target/ffi_bindings/src/ffi.o
  CXX(target) Release/obj.target/ffi_bindings/src/callback_info.o
  CXX(target)
Release/obj.target/ffi_bindings/src/threaded_callback_invokation.o
  SOLINK_MODULE(target) Release/obj.target/ffi_bindings.node
  COPY Release/ffi_bindings.node
make: Leaving directory
'/usr/local/lib/node_modules/bonescript/node_modules/ffi/build'

serialport@2.0.6 install

/usr/local/lib/node_modules/bonescript/node_modules/serialport

node-pre-gyp install --fallback-to-build

make: Entering directory
'/usr/local/lib/node_modules/bonescript/node_modules/serialport/build'
  CXX(target) Release/obj.target/serialport/src/serialport.o
  CXX(target) Release/obj.target/serialport/src/serialport_unix.o
  CXX(target) Release/obj.target/serialport/src/serialport_poller.o
  SOLINK_MODULE(target) Release/obj.target/serialport.node
  COPY Release/serialport.node
  COPY
/usr/local/lib/node_modules/bonescript/node_modules/serialport/build/Release/node-v14-linux-arm/serialport.node
  TOUCH Release/obj.target/action_after_build.stamp
make: Leaving directory
'/usr/local/lib/node_modules/bonescript/node_modules/serialport/build'
bonescript@0.5.0-beta4 /usr/local/lib/node_modules/bonescript
├── systemd@0.2.6
├── spi@0.2.0 (bindings@1.2.1)
├── winston@2.1.1 (cycle@1.0.3, stack-trace@0.0.9, eyes@0.1.8,
isstream@0.1.2, pkginfo@0.3.1, async@1.0.0, colors@1.0.3)
├── express@4.13.4 (escape-html@1.0.3, utils-merge@1.0.0,
cookie-signature@1.0.6, methods@1.1.2, range-parser@1.0.3, fresh@0.3.0,
vary@1.0.1, parseurl@1.3.1, array-flatten@1.1.1, etag@1.7.0,
content-type@1.0.1, merge-descriptors@1.0.1, path-to-regexp@0.1.7,
cookie@0.1.5, content-disposition@0.5.1, serve-static@1.10.2, depd@1.1.0,
on-finished@2.3.0, finalhandler@0.4.1, qs@4.0.0, debug@2.2.0,
proxy-addr@1.0.10, send@0.13.1, type-is@1.6.12, accepts@1.2.13)
├── i2c@0.2.1 (bindings@1.2.1, repl@0.1.3, underscore@1.8.2,
coffee-script@1.9.1)
├── socket.io@1.4.5 (has-binary@0.1.7, debug@2.2.0, socket.io-parser@2.2.6,
engine.io@1.6.8, socket.io-adapter@0.4.0, socket.io-client@1.4.5)
├── epoll@0.1.17 (bindings@1.2.1, nan@2.2.1)
├── ffi@2.0.0 (bindings@1.2.1, ref-struct@1.0.2, debug@2.2.0, nan@2.2.1,
ref@1.3.2)
└── serialport@2.0.6 (bindings@1.2.1, sf@0.1.7, async@0.9.0, debug@2.2.0,
nan@2.0.9, optimist@0.6.1)
[2Kbb-bonescript-installer:Installed
Setting up doc-beaglebone-getting-started (1.20151204-2~bpo80+20160421+1)
...
Setting up openssh-client (1:6.7p1-5+deb8u2) ...
Setting up openssh-sftp-server (1:6.7p1-5+deb8u2) ...
Setting up openssh-server (1:6.7p1-5+deb8u2) ...
Setting up connman (1.32-git20160418-0rcnee1~bpo80+20160418+1) ...
Setting up linux-libc-dev:armhf (3.16.7-ckt25-2) ...
Setting up bb-wl18xx-firmware (1.20160413-0rcnee1~bpo80+20160413+1) ...
Setting up tiomapconf (1.72.0-git20160414-1~bpo80+20160414+1) ...
Processing triggers for libc-bin (2.19-18+deb8u4) ...
debian@beaglebone:~$ node js --version
v0.12.13
debian@beaglebone:~$ /usr/bin/npm --version
2.15.0
debian@beaglebone:~$

Regards,

Has a required kernel upgrade come it that doesn’t install with apt-get upgrade?

Nope…

I’ve been using this system the way I figure a newbie who only wanted bonescript, python, and node-red might do.
I can see how pushing kernel upgrades could rather quickly get you into space issues if confined to the 4GB eMMC, but if its a real dependency not doing so would seem to be a problem.

Odd, was this the iot or lxqt or console image?

Sorry that I forgot to mention that it was an lxqt image.

if you do : dpkg --list | pastebinit

we can compare against:

https://paste.debian.net/440395/

I will do this as soon as my repeat upgrade attempt either finishes or fails

From a fresh 2016-04-03 iot image i’m seeing:

debian@beaglebone:~$ cat /etc/dogtag
BeagleBoard.org Debian Image 2016-04-03
debian@beaglebone:~$ uname -r
4.1.18-ti-r56
debian@beaglebone:~$ sudo apt-get update ; sudo apt-get upgrade

Reading state information… Done

Calculating upgrade… Done
The following packages will be upgraded:
bb-bonescript-installer-beta bb-wl18xx-firmware connman
doc-beaglebone-getting-started libmraa0 linux-libc-dev openssh-client
openssh-server openssh-sftp-server tiomapconf upm
11 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 15.6 MB of archives.
After this operation, 63.5 kB of additional disk space will be used.
Do you want to continue? [Y/n] y

Interesting, I only had two updates today:
bb-bonescript-installer-beta
doc-beaglebone-getting-started

I recall these happened last time (yesterday?)
connman openssh-client openssh-server openssh-sftp-server

The others, particularly bb-wl18xx-firmware I don’t recall happening.

Ill follow-up with the pastebinit when when the current upgrade finishes.

Has a required kernel upgrade come it that doesn't install with apt-get
upgrade?

Nope...

I've been using this system the way I figure a newbie who only wanted
bonescript, python, and node-red might do.
I can see how pushing kernel upgrades could rather quickly get you into
space issues if confined to the 4GB eMMC, but if its a real dependency not
doing so would seem to be a problem.

Odd, was this the iot or lxqt or console image?

Sorry that I forgot to mention that it was an lxqt image.

Okay, i'll check that quickly. .:wink:

if you do : dpkg --list | pastebinit

we can compare against:

https://paste.debian.net/440395/

I will do this as soon as my repeat upgrade attempt either finishes or
fails

From a fresh 2016-04-03 iot image i'm seeing:

debian@beaglebone:~$ cat /etc/dogtag
BeagleBoard.org Debian Image 2016-04-03
debian@beaglebone:~$ uname -r
4.1.18-ti-r56
debian@beaglebone:~$ sudo apt-get update ; sudo apt-get upgrade

Reading state information... Done

Calculating upgrade... Done
The following packages will be upgraded:
  bb-bonescript-installer-beta bb-wl18xx-firmware connman
  doc-beaglebone-getting-started libmraa0 linux-libc-dev openssh-client
  openssh-server openssh-sftp-server tiomapconf upm
11 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 15.6 MB of archives.
After this operation, 63.5 kB of additional disk space will be used.
Do you want to continue? [Y/n] y

Interesting, I only had two updates today:
bb-bonescript-installer-beta

^ this was a major upgrade beta3->beta4.. the problem, npm behind the
scenes does a lot of crap.. (i hate npm)

doc-beaglebone-getting-started

this was a symlink update, nothing more.

I recall these happened last time (yesterday?)
connman openssh-client openssh-server openssh-sftp-server

The others, particularly bb-wl18xx-firmware I don't recall happening.

these were last week...

Ill follow-up with the pastebinit when when the current upgrade finishes.

Regards,

I did the pastebinit, but where does the 440395 come from? I’ve never used pastebinit before.

You need to have the network connected... by "|" (or'ing) it with
pastebinit binary it'll get uploaded..

Regards,

I have pastebinit install and it apt-get install pastebinit says its the latest version.

piping dpkg --list to pastebinit (dpkg --list | pastebinit) returns:
http://paste.debian.net

I am connected to the network. I’m missing something here.
Do I need to make an account there or something?

Do we know why this said beta5, not beta4?

I’m very confused by what is going on with these npm updates being trigged by apt-get upgrades. But I got the bb-bonescript-installer-beta upgrade to apparently install by doing:
apt-get purge bb-bonescript-installer-beta
apt-get install bb-bonescript-installer-beta

The cloud9 bonescript examples seem to work, I’ve simple prototype circuits wired up to test the basics: analogRead(). analogWrite(), digitalWrite(), digitalRead(), & attachInterrupt().

The 192.168.7.2/bone101/Support/bone101/ interactive tutorial page doesn’t work and the “Navigation” pane on the left side of the page doesn’t render and I never get the “your beaglebone is connected” banner.

cd /var/lib/cloud9/
git pull

Regards,

I’ve noticed that the “testing” images all seem to be a single partition (ext4) on the SD card. Is it possible BEAGLEBONE 41MB partition that mounts via Linux File-Stor Gadget is actually the fat partition in the 4GB eMMC (Jessie with a 3.8.x kernel and less the correctly working bonescript version)? Maybe this explains why the localhost bone101 page doesn’t work right.

That virtual "fat" partition is provided by the
"doc-beaglebone-getting-started" package...

-rw-r--r-- 1 root root 40M Dec 7 17:04
/var/cache/doc-beaglebone-getting-started/beaglebone-getting-started-2015-12-04.img

the bone101 Navigation issue on the left hand side can be fixed via:

cd /var/lib/cloud9/
git pull

Regards,

Thanks!This fixes it. Any way this could be made to happen automatically as part of an apt-get bonescript upgrade?

Right now it's a git repo that supports 3 separate projects.. There is talk
of converting it to a deb package..

Regards,