Bugsounet and MMM-Pir

[rkorell]

@sdetweil :-).
I like it very much because it offers a lot nice and fancy stuff as the others don’t …
(progress bar, dimming, cron-steering for sleeping times)

Ralf

[sdetweil]

@lif can you talk about this python after …

MagicMirror upgrades? if so , did you use my upgrade script?

this highlights a problem. some modules need a refresh install when nodejs and MagicMirror change
so the upgrade script does that. but that wipes the node_modules folder for the module. and the dependencies are also not available anymore.

so, if i DO try the npm install it breaks, if i dont try the npm install it might break. fun times.
i will add a check for the authors url and skip the install action

[sdetweil]

@rkorell i hear yah.

[rkorell]

@sdetweil said in Bugsounet and MMM-Pir:

some modules need a refresh install

at least in bugsounet’s README.md there is a hint in this direction …

[sdetweil]

@rkorell yes, but there is nothing I can do… the dependencies no longer exist
he had some integrated update mechanism, I added code to launch that once…
now its dead too…

[rkorell]

@sdetweil OK.
really unfortunate.
I do not understand these dependencies - so I was hopeful that an update will not destroy module’s ability to work …

So I have to stay with the old mirror version to keep module running?

Regards,
Ralf

[lif]

@sdetweil said in Bugsounet and MMM-Pir:

@lif can you talk about this python after …

MagicMirror upgrades? if so , did you use my upgrade script?

this highlights a problem. some modules need a refresh install when nodejs and MagicMirror change
so the upgrade script does that. but that wipes the node_modules folder for the module. and the dependencies are also not available anymore.

so, if i DO try the npm install it breaks, if i dont try the npm install it might break. fun times.
i will add a check for the authors url and skip the install action

I was trying to upgrade Nodejs and if failed with lots of errors.

my mm and the whole system had got messy, so I’m using this as an opportunity to clean things up (it didn’t help insofar as a restore from the most recent backup didn’t work.

[sdetweil]

@rkorell said in Bugsounet and MMM-Pir:

So I have to stay with the old mirror version to keep module running?

i do not know…

I do not understand these dependencies
rather than put all the code in the module, there are libraries of things
that can be called…

so you make those libraries as separate packages and list them in the dependencies section of package.json and npm install goes and gets them

he might have decided that multiple components needs the same functions and packaged as library, to be loaded by all that needed it, code once, ship multiple times…
except that breaks now as the dependencies also are no longer available

as I said in my initial warning post, plan for them all to fail to work

[sdetweil]

@lif yeh, my upgrade script does the nodejs upgrade too…

use the n command

sudo npm install n -g 
sudo n xxx
where xxx is the version you want to use

recent backup didn’t work

how backup? use my backup/restore

yes that is broken too, as the authors repos no longer exist and binary backup may not work on different OS level/nodejs level

[lif]

@sdetweil said in Bugsounet and MMM-Pir:

how backup? use my backup/restore

yes that is broken too, as the authors repos no longer exist and binary backup may not work on different OS level/nodejs level

IMG file on my (new) linux desktop