Read the statement by Michael Teeuw here.
MM Update - GIT error
-
Hey guys,
i want to update my MM system from version 2.1.3 -> 2.4.x.
It looks like i am to stupid for it -.-
I am in the MagicMirror folder an try to make an GIT pull. I received an error immediatly.
May you have an idea for this issue ?
sudo git pull && npm install error: object file .git/objects/5d/fba0b834306cc81693307ab0d1bf24e798a46a is empty error: object file .git/objects/5d/fba0b834306cc81693307ab0d1bf24e798a46a is empty fatal: loose object 5dfba0b834306cc81693307ab0d1bf24e798a46a (stored in .git/objects/5d/fba0b834306cc81693307ab0d1bf24e798a46a) is co rrupt fatal: The remote end hung up unexpectedly -
@Pakmann
2 ideas:- in which folder are you trying to run the pull? It should be /MagicMirror/
- do it without sudo rights
AxLED
-
@AxLed
strange behaviour… i am in my root folder for MagicMirror: /home/pi/MagicMirror/without sudo command same result
-
delete the file giving he error…
.git/objects/5d/fba0b834306cc81693307ab0d1bf24e798a46a is empty
-
thanks a lot! This works, but now the next issue -.-
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. error: object file .git/objects/36/766f9a0089766d4a0e164f3f0b198dadcf60c4 is empty fatal: SHA1 KOLLISION MIT 36766f9a0089766d4a0e164f3f0b198dadcf60c4 GEFUNDEN ! fatal: index-pack fehlgeschlagen -
-
@justjim1220 said in MM Update - GIT error:
try…
npm rebuild
from the MagicMirror directorythen reboot your system
rebuild was sucessfull, but not working. Problem still alive
-
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
-
@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 -
Well, I am not sure what is happening…
My best guess is to delete the .git folder then redo the git pull && npm install -
OR…
Rename your MagicMirror folder to MM-BAKthen 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
-
Maybe this was the issue.
https://www.geekwire.com/2018/github-recovering-widespread-outage-caused-networking-database-issues/ -
Yeah, it’s possible if the update was retrieved during that time.
-
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 -
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 -
I’m not using pi, so I don’t really know if this will help or not… could be different
-
hmm… it looks like my system is broken. npm makes a lot of problems too.
I decide to reset the systems completely. Fresh OS and a new MM installation. It was easier as to find the root cause. Now everythink is running up again.
Thanks a lot for your ideas and your help
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login