> > *I've never had these kinds of problems with apt-get install failures on > other Ubuntu & Debian systems.* >
I've seen several, and in fact when udev was new, and incorporated into Ubuntu. You could apt-get install several "applications" that fell flat on their faces. Xen, and iSCSI tools were two such cases I can remember. I also distinctly remember a gcc bug creeping into Debian stable when Sarge was still in testing. Yes, these were all a long time ago. Anyway the short point of it all is that no one, and nothing created by humans is perfect. *Am I doomed in my attempt to keep an "old" Jessie system reasonably up to > date as things evolve?* > You know I thought you had something working before. So I've been wondering why didn't you stick with that ? On Fri, Apr 29, 2016 at 10:49 AM, Wally Bkg <[email protected]> wrote: > I'm still having issues with installing the node-red & bonescript stuff. > > I have a BBW that has been running my IOT application 24/7 with great > success for about the last four or five months. Its running: > cat /etc/dogtag > BeagleBoard.org Debian Image 2015-11-12 > uname -a > Linux alarmbone 4.1.18-ti-r49 #1 SMP PREEMPT Fri Feb 26 00:12:54 UTC 2016 > armv7l GNU/Linux > > It was installed from a 2GB console image but I've apt-get installed > enough X stuff to get ssh -X gedit to work (although I rarely actually use > it this way). Its been kept current with apt get update and apt-get > upgrade a couple of times a month although its basically dedicated to > running this app and its development/testing/debugging. > > I also have a BBG that I'm setting up for a friend that has a nicely > working bonescript and node-red starting from an lxqt 2016-04-03 image. > While playing with this I though of a simple idea to add some mqtt > functionality to my IOT application using node-red. My BBW is already > running the mosquito mqtt broker and I've used it as such while testing > node-red on the BBG and RPi2 So now I thought I'd install node-red to my > BBW console image but the installation fails. > > I've never had these kinds of problems with apt-get install failures on > other Ubuntu & Debian systems. > > > apt-get install bb-node-red-installer > Reading package lists... Done > Building dependency tree > Reading state information... Done > The following NEW packages will be installed: > bb-node-red-installer > 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. > Need to get 4,140 B of archives. > After this operation, 49.2 kB of additional disk space will be used. > Do you want to continue? [Y/n] Y > Get:1 http://repos.rcn-ee.com/debian/ jessie/main bb-node-red-installer > all 0.13.4-0rcnee1~bpo80+20160321+1 [4,140 B] > Fetched 4,140 B in 0s (32.3 kB/s) > Selecting previously unselected package bb-node-red-installer. > (Reading database ... 80178 files and directories currently installed.) > Preparing to unpack > .../bb-node-red-installer_0.13.4-0rcnee1~bpo80+20160321+1_all.deb ... > Unpacking bb-node-red-installer (0.13.4-0rcnee1~bpo80+20160321+1) ... > Setting up bb-node-red-installer (0.13.4-0rcnee1~bpo80+20160321+1) ... > bb-node-red-installer:npm: [1.4.21] > bb-node-red-installer:node: [v0.10.42] > bb-node-red-installer:Installing: systemd-0.2.6 (for node-red) > [email protected] /usr/local/lib/node_modules/systemd > bb-node-red-installer:Installing: node-red-0.13.4 (for node-red) > > > [email protected] install > /usr/local/lib/node_modules/node-red/node_modules/bcrypt > > node-gyp rebuild > > make: Entering directory > '/usr/local/lib/node_modules/node-red/node_modules/bcrypt/build' > CXX(target) Release/obj.target/bcrypt_lib/src/blowfish.o > CXX(target) Release/obj.target/bcrypt_lib/src/bcrypt.o > CXX(target) Release/obj.target/bcrypt_lib/src/bcrypt_node.o > Killed > dpkg: error processing package bb-node-red-installer (--configure): > subprocess installed post-installation script returned error exit status > 137 > Errors were encountered while processing: > bb-node-red-installer > E: Sub-process /usr/bin/dpkg returned an error code (1) > > > Am I doomed in my attempt to keep an "old" Jessie system reasonably up to > date as things evolve? > > -- > For more options, visit http://beagleboard.org/discuss > --- > You received this message because you are subscribed to the Google Groups > "BeagleBoard" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/beagleboard/36157370-385d-4003-8b0f-b33750846faa%40googlegroups.com > <https://groups.google.com/d/msgid/beagleboard/36157370-385d-4003-8b0f-b33750846faa%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CALHSORqZw-nw8uAf9if1uuSC3mPBtKe2J2qwtHVH%2BPLzWrVKtQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
