MagicMirror² v2.13.0 is available! For more information about this release, check out this topic.

Update to MagicMirror² v2.13.0 failed



  • Just run git pull to update from v2.12.0 and it did the update but would not run afterwards. I had to do a clean install of v2.13.0 and copy the config and modules I had installed over to the new install and it now runs fine. Anyone any ideas why it would not run? Might be useful to anyone else with problems.



  • @ColinT no idea… but I made a script to handle upgrades a year ago now…

    https://github.com/sdetweil/MagicMirror_scripts

    the ‘best’ part is the log file, so we can see what went on…

    many times u have to do an npm install in the module folders too

    wait,I re-read your post…

    after git pull, you did npm install , right?


  • Project Sponsor

    Hallo, I used Sams upgrade script and it works fine …

    Thank you sam for your work and help.



  • @Stoffbeuteluwe my pleasure… one failure was a module problem, the other my be network… unknown


  • Project Sponsor

    This post is deleted!


  • @Stoffbeuteluwe what module is that?


  • Project Sponsor

    @sdetweil default current weather


  • Project Sponsor

    @sdetweil i have it…

    appendLocationNameToHeader: false,
    

  • Project Sponsor

    Sam using your script and this is the output…this all that needs to be done?

    pi@raspberrypi:~ $ bash -c  "$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/upgrade-script.sh)"
    No LSB modules are available.
    
    doing test run = true, NO updates will be applied!
    
    update log will be in /home/pi/MagicMirror/installers/upgrade.log
    
    saving custom.css
    upgrading from version 2.12.0 to 2.13.0
    fetching latest revisions
    there are 3 local files that are different than the master repo
    
       installers/mm.sh
       modules/default/compliments/compliments.js
       package-lock.json
    
    any *-lock.json files do not need to be saved
    do you want to save these files for later   (Y/n)?y
    processing dependency changes for active modules with package.json files
    
    processing for module MMM-EARTH please wait
    ----------------------------------
    skipped processing for MMM-EARTH, doing test run
    processing complete for module MMM-EARTH
    
    processing for module MMM-FlightRadarTracker please wait
    ----------------------------------
    skipped processing for MMM-FlightRadarTracker, doing test run
    processing complete for module MMM-FlightRadarTracker
    
    processing for module MMM-DarkSkyForecast please wait
    ----------------------------------
    skipped processing for MMM-DarkSkyForecast, doing test run
    processing complete for module MMM-DarkSkyForecast
    
    restoring custom.css
    test run, restoring files stashed
    pi@raspberrypi:~ $
    
    


  • @swvalenti said in Update to MagicMirror² v2.13.0 failed:

    doing test run = true,

    there are TWO passes… one in test mode
    and one with apply

    what is wrong with my doc?

    upgrade-script.sh will do the git pull and npm install, and refresh npm setup for any modules that might need it
    it should handle all the work… and give you a trial run of all that…
    
    only applying changes if u request them
    
    give it a try this works on Mac as well, cut/paste this line into the terminal window on your device
    
    bash -c  "$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/upgrade-script.sh)"
    no changes are made to the local repo or the working copy
    
    if you WANT to actually apply the changes, cut/paste this line into the terminal window on your device 
    
    bash -c  "$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/upgrade-script.sh)" apply
    there is a log file (upgrade.log) in the MagicMirror/installers folder…
    
    
    

    i don’t understand how everyone misses this

    if you WANT to actually apply the changes, cut/paste this line into the terminal window on your device
    

Log in to reply