• Recent
  • Tags
  • Unsolved
  • Solved
  • MagicMirror² Repository
  • Documentation
  • 3rd-Party-Modules
  • Donate
  • Discord
  • Register
  • Login
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.

MM Update - GIT error

Scheduled Pinned Locked Moved Solved Troubleshooting
17 Posts 4 Posters 5.9k 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.
  • J Offline
    justjim1220 Module Developer @Pakmann
    last edited by Oct 23, 2018, 9:05 PM

    @pakmann

    try…

    npm rebuild
    from the MagicMirror directory

    then reboot your system

    "Life's Too Short To Dance With Ugly People"
    Jim Hallock - 1995

    P 1 Reply Last reply Oct 23, 2018, 9:35 PM Reply Quote 0
    • P Offline
      Pakmann @justjim1220
      last edited by Oct 23, 2018, 9:35 PM

      @justjim1220 said in MM Update - GIT error:

      @pakmann

      try…

      npm rebuild
      from the MagicMirror directory

      then reboot your system

      rebuild was sucessfull, but not working. Problem still alive

      J 1 Reply Last reply Oct 23, 2018, 9:40 PM Reply Quote 0
      • J Offline
        justjim1220 Module Developer @Pakmann
        last edited by Oct 23, 2018, 9:40 PM

        @pakmann

        delete the file causing new error…

        .git/objects/36/766f9a0089766d4a0e164f3f0b198dadcf60c4 is empty

        Then rebuild again…

        npm rebuild

        then reboot again

        if this doesn’t work, you may need to do the git pull && npm install again

        "Life's Too Short To Dance With Ugly People"
        Jim Hallock - 1995

        P 1 Reply Last reply Oct 23, 2018, 9:57 PM Reply Quote 0
        • P Offline
          Pakmann @justjim1220
          last edited by Oct 23, 2018, 9:57 PM

          @justjim1220 said in MM Update - GIT error:

          git pull && npm install

          • detele file: check
          • npm rebuild: check
          • reboot: check
          • new request for git pull && npm install: same behaviour…
          git pull && npm install
          error: refs/remotes/origin/develop does not point to a valid object!
          error: refs/remotes/origin/develop does not point to a valid object!
          error: refs/remotes/origin/develop does not point to a valid object!
          error: refs/remotes/origin/develop does not point to a valid object!
          remote: Enumerating objects: 507, done.
          remote: Counting objects: 100% (507/507), done.
          remote: Total 1591 (delta 507), reused 507 (delta 507), pack-reused 1084
          Empfange Objekte: 100% (1591/1591), 691.80 KiB | 463.00 KiB/s, Fertig.
          error: object file .git/objects/df/fc042df5d96cc8f7a956c12a2e002004d4cf7d is empty
          fatal: SHA1 KOLLISION MIT dffc042df5d96cc8f7a956c12a2e002004d4cf7d GEFUNDEN !
          fatal: index-pack fehlgeschlagen
          
          
          J 2 Replies Last reply Oct 23, 2018, 9:58 PM Reply Quote 0
          • J Offline
            justjim1220 Module Developer @Pakmann
            last edited by Oct 23, 2018, 9:58 PM

            @pakmann

            Well, I am not sure what is happening…
            My best guess is to delete the .git folder then redo the git pull && npm install

            "Life's Too Short To Dance With Ugly People"
            Jim Hallock - 1995

            1 Reply Last reply Reply Quote 0
            • J Offline
              justjim1220 Module Developer @Pakmann
              last edited by Oct 23, 2018, 10:03 PM

              @pakmann

              OR…
              Rename your MagicMirror folder to MM-BAK

              then git clone MagicMirror for a fresh install

              Then move your modules folder, config.js, and custom.css files over to the fresh install

              might also need to move the package.json and package-lock.json files from the bak to the fresh install

              And, anytime I have dealt with anything like this, I always have to rebuild, or reboot, or both

              "Life's Too Short To Dance With Ugly People"
              Jim Hallock - 1995

              1 Reply Last reply Reply Quote 0
              • M Offline
                mochman Module Developer
                last edited by Oct 23, 2018, 10:05 PM

                Maybe this was the issue.
                https://www.geekwire.com/2018/github-recovering-widespread-outage-caused-networking-database-issues/

                J 1 Reply Last reply Oct 23, 2018, 10:06 PM Reply Quote 1
                • J Offline
                  justjim1220 Module Developer @mochman
                  last edited by Oct 23, 2018, 10:06 PM

                  @mochman

                  Yeah, it’s possible if the update was retrieved during that time.

                  "Life's Too Short To Dance With Ugly People"
                  Jim Hallock - 1995

                  1 Reply Last reply Reply Quote 0
                  • P Offline
                    Pakmann
                    last edited by Oct 23, 2018, 10:32 PM

                    @justjim1220

                    so i did it. After that i try to make the npm install. Suprise… the next issues. What a hard MM update! Maybe you have any idea ?

                     git pull && npm install
                    Bereits aktuell.
                    (node:1893) [DEP0022] DeprecationWarning: os.tmpDir() is deprecated. Use os.tmpdir() instead.
                    npm ERR! Error: Method Not Allowed
                    npm ERR!     at errorResponse (/usr/share/npm/lib/cache/add-named.js:260:10)
                    npm ERR!     at /usr/share/npm/lib/cache/add-named.js:203:12
                    npm ERR!     at saved (/usr/share/npm/node_modules/npm-registry-client/lib/get.js:167:7)
                    npm ERR!     at FSReqWrap.oncomplete (fs.js:135:15)
                    npm ERR! If you need help, you may report this *entire* log,
                    npm ERR! including the npm and node versions, at:
                    npm ERR!     <http://github.com/npm/npm/issues>
                    
                    npm ERR! System Linux 4.14.71-v7+
                    npm ERR! command "/usr/bin/node" "/usr/bin/npm" "install"
                    npm ERR! cwd /home/pi/MagicMirror
                    npm ERR! node -v v8.11.1
                    npm ERR! npm -v 1.4.21
                    npm ERR! code E405
                    npm WARN deprecated nomnom@1.8.1: Package no longer supported. Contact support@npmjs.com for more info.
                    |
                    > phantomjs-prebuilt@2.1.16 install /home/pi/MagicMirror/node_modules/jshint/node_modules/phantomjs-prebuilt
                    > node install.js
                    
                    PhantomJS not found on PATH
                    Unexpected platform or architecture: linux/arm
                    It seems there is no binary available for your platform/architecture
                    Try to install PhantomJS globally
                    npm WARN This failure might be due to the use of legacy binary "node"
                    npm WARN For further explanations, please read
                    /usr/share/doc/nodejs/README.Debian
                    
                    
                    > electron-chromedriver@1.6.0 install /home/pi/MagicMirror/node_modules/spectron/node_modules/electron-chromedriver
                    > node ./download-chromedriver.js
                    
                    npm WARN optional dep failed, continuing phantomjs-prebuilt@2.1.16
                    npm WARN deprecated circular-json@0.3.3: CircularJSON is in maintenance only, flatted is its successor.
                    npm WARN deprecated browserslist@2.11.3: Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools.
                    npm ERR!
                    npm ERR! Additional logging details can be found in:
                    npm ERR!     /home/pi/MagicMirror/npm-debug.log
                    npm ERR! not ok code 0
                    
                    
                    J 2 Replies Last reply Oct 23, 2018, 10:40 PM Reply Quote 0
                    • J Offline
                      justjim1220 Module Developer @Pakmann
                      last edited by Oct 23, 2018, 10:40 PM

                      @pakmann

                      GEEZ!!!

                      I literally just installed a fresh MagicMirror to an Ubuntu OS, and had zero issues.

                      I did a manual install of Browserlist…

                      npm install Browserlist@3.0 -g

                      then I also did a manual install of PhantomJS…

                      sudo npm insall PhantomJS@latest -g

                      Then I made sure I had updated versions of npm, node, and electron

                      npm install npm@latest -g
                      npm install node@ latest -g
                      sudo npm electron@latest -g

                      "Life's Too Short To Dance With Ugly People"
                      Jim Hallock - 1995

                      1 Reply Last reply Reply Quote 0
                      • 1
                      • 2
                      • 1 / 2
                      1 / 2
                      • First post
                        10/17
                        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