Read the statement by Michael Teeuw here.
Problem with updating to 2.10.0 from 2.9.0 using update script
-
@sdetweil I don’t know how to respond in that case, ofc I have to had it installed earlier in order for MM to work, but right now it seems system is not seeing it, only
bash: npm: command not found
sooooo … I think since it’s fresh install I will reinstall everything -
@outlying close that terminal window and reopen it, npm should not have been removed…
-
@sdetweil I’ve done it right away it but it’s not there anymore, somehow it’s messed up
-
@outlying weird… sudo apt-get install npm
then sudo npm i -g npm to get latestnode -v
and
npm -v
to verify levels -
sorry to use the same topic. I have also trouble with the update to 2.10.0. The update script works, but I still have the notification that there is an update for MM. But the update log ends with “Upgrade ended - Do Jan 2 20:24:45 CET 2020”.
-
@sdetweil I appreciate your fast responses :-) it’s really inspiring, but it would be way easier for me to set it up again in a matter of few minutes instead of trying to figure out what went wrong
Right now I have lock on dpkg files
sudo apt-get install npm E: Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable) E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?
So it all messed up :-/ this is very fresh setup so I really don’t mind purging it
-
@outlying save your magicmirror config.js at least!