Read the statement by Michael Teeuw here.
Should I update?
-
Hi Sam,
I have a similar problem.
My memory card is defective and I had to revert to an older backup.
Unfortunately, I have been a little lax with the backup, as I always have to get the mirror off the wall a bit awkwardly to back up the SD card.I am with the mirror still on Jessie.
When I stop the MagicMirror with “pm2 stop mm” and also stop node with killall node, I get a message from your scipt (test mode) that node and npm need to be updated.
How do I get them to the latest version?I am rather beginner in Linux - so have understanding for simple queries.
Can you help me?BR
Jens -
@mymirror jessie is very old
4 releases back now. almost nothing will support running there nowI would also suggest some of the mechanisms to backup over the local network
-
@sdetweil
Hi Sam,yes i know :-( … very old.
in the meantime I got the system on “Stretch” and wanted to take the next step to “Buster”.
But I get the following error (on german):
PGP error: http://ftp.de.debian.org/debian buster InRelease: The following signatures could not be verified because their public key is not available …How can I adjust/correct this?
Thanks a lot -
@mymirror i do not know… buster is also not current
-
@sdetweil finally I tried the update: MM will not start anymore.
I am on stretch by the way.
Peter -
@peter show me the messages… fromn npm start
stretch is WAY downlevel…
need to get to buster(legacy) or bullseye…
the internet keeps changing things every week… stetch is 4 years old now
-
Is it possible to update without having to start all over?
Peter -
@peter maybe… as i said, stretch is really old…
I do not know if you can upgrade OS in place from stretch
pretty sure u need to upgrade node and npm too
node -v
npm -vwhat pi is this ?
uname -a
-
@sdetweil I think it is a Pi2b.
In 2017 I built this MM and it has been running well since.
So, that is my question: update of not.
It took me very long to build, and I do not want to start all over again.
Peter -
@peter do not update
