Read the statement by Michael Teeuw here.
MMM-Remote-Control
-
@sdetweil
just ran a testrun of your upgrade script:pi@MagicMirrorPi5:~/MagicMirror $ bash -c "$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/upgrade-script.sh)" update log will be in /home/pi/MagicMirror/installers/upgrade.log doing test run = true, NO updates will be applied! Check current Node installation ... Node currently installed. Checking version number. Minimum Node version: v22.18.0 Installed Node version: v20.18.1 Node should be upgraded. Node.js upgrade defered, doing test run Check current NPM installation ... NPM currently installed. Checking version number. Minimum npm version: V10.9.2 Installed npm version: V10.8.2 npm should be upgraded. npm upgrade defered, doing test run ... saving custom.css reverting to master branch from _fix_clipping, saving changed files would restore file modules/default/weather/current.njk before switch back to master branch would restore file package-lock.json before switch back to master branch would restore file package.json before switch back to master branch error: Your local changes to the following files would be overwritten by checkout: package-lock.json package.json Please commit your changes or stash them before you switch branches. Aborting unable to change back to master branch, stopping executionWhat does the last message mean?
“unable to change back to master branch, stopping execution”
What have I to do? -
@sdetweil
BTW: Do you know if it is possible to restore the “old” version from remote-control?
May THIS is the better option for me? -
@rkorell can you tell me when old was? luckily this module uses tags for releases, so you could restore to one of the previous releases…
in the module folder do
git fetch --all --tagsthen when we figure out which release to try, we can
git checkout <tag_name>Release 3.2.1 was about 5 months ago.
-
@sdetweil I’ve found V3.3.2 and just try "git checkout 1f451ce "
-
@rkorell if you pull the tags, you can use the tag name
git checkout v3.3.2
-
@sdetweil
For some really strange reasons, neitherpi@MagicMirrorPi5:~/MagicMirror/modules/MMM-Remote-Control $ git fetch --all --tags pi@MagicMirrorPi5:~/MagicMirror/modules/MMM-Remote-Control $ git fetch --tagscurrently give any feedback…
So I’ve worked with the found git-hash:
git checkout 1f451ceThis at least worked and rolled back to V. 3.3.2.
Unfortunately some dependencies (package-lock.json ???) are not strict enough, so the rollback produces an error message:
[ERROR] Error when loading MMM-Remote-Control: require() of ES Module /home/pi/MagicMirror/modules/MMM-Remote-Control/node_modules/uuid/dist-node/index.js from /home/pi/MagicMirror/modules/MMM-Remote-Control/API/api.js not supported.So I downgraded UUID:
cd ~/MagicMirror/modules/MMM-Remote-Control npm install uuid@9.0.1 npm ci --omit=devWith this module is running again.
From now on I’m in a in ‘detached HEAD’ state - but this seems OK.
Thanks for your time, effort and always great help!Ralf
-
@rkorell I was just about to add that you needed to redo the npm install for the module after deleting the node_modules folder
else you were trying to run the new dependencies with the old codebut you fixed it…
-
@sdetweil
Yes :-)In fact I’ve used
npm ci --omit=devthis does the deletion of the node_modules folder inherently AFAIK …
Thanks again, dear Sam!
Ralf
-
@rkorell said in MMM-Remote-Control:
npm ci
be careful… the package.json was built and tested on a cloud based virtual machine.
pi and other hardware types MAY need a different version of a dependency, i’ve only seen it myself twice in 6 years, butnpm ci uses the exact package.json
npm install will get the appropriate for this platform, even if the version changes.anyhow… I use npm install --omit=dev when I do the installs script or MMM-Config
-
@sdetweil
OK; thanks for this hint.
May npm install has avoided the resulting error which I had to solve…Anyway: Thanks a LOT!
Regards,
Ralf
