MagicMirror Forum
    • Recent
    • Tags
    • Unsolved
    • Solved
    • MagicMirror² Repository
    • Documentation
    • 3rd-Party-Modules
    • Donate
    • Discord
    • Register
    • Login
    A New Chapter for MagicMirror: The Community Takes the Lead
    Read the statement by Michael Teeuw here.

    Problem with updating to 2.10.0 from 2.9.0 using update script

    Scheduled Pinned Locked Moved Unsolved Troubleshooting
    15 Posts 3 Posters 4.8k Views 3 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • S Offline
      sdetweil @outlying
      last edited by

      @outlying close that terminal window and reopen it, npm should not have been removed…

      Sam

      How to add modules

      learning how to use browser developers window for css changes

      O 1 Reply Last reply Reply Quote 0
      • O Offline
        outlying @sdetweil
        last edited by outlying

        @sdetweil I’ve done it right away it but it’s not there anymore, somehow it’s messed up

        S 1 Reply Last reply Reply Quote 0
        • S Offline
          sdetweil @outlying
          last edited by

          @outlying weird… sudo apt-get install npm
          then sudo npm i -g npm to get latest

          node -v
          and
          npm -v
          to verify levels

          Sam

          How to add modules

          learning how to use browser developers window for css changes

          1 Reply Last reply Reply Quote 0
          • C Offline
            ChrizZz
            last edited by

            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”.

            1 Reply Last reply Reply Quote 1
            • O Offline
              outlying
              last edited by

              @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

              S 1 Reply Last reply Reply Quote 0
              • S Offline
                sdetweil @outlying
                last edited by

                @outlying save your magicmirror config.js at least!

                Sam

                How to add modules

                learning how to use browser developers window for css changes

                1 Reply Last reply Reply Quote 0
                • 1
                • 2
                • 1 / 2
                • First post
                  Last post
                Enjoying MagicMirror? Please consider a donation!
                MagicMirror created by Michael Teeuw.
                Forum managed by Sam, technical setup by Karsten.
                This forum is using NodeBB as its core | Contributors
                Contact | Privacy Policy