Read the statement by Michael Teeuw here.
2318 commits behind...
-
@bastilimbach Any help?
-
@savona - Would it make sense to build from image, rename the git files, pull, update and then upload the fixed image as a PR?
-
@bhepler maybe.
but I saw that the originator of the docker image said it was updated daily with a cronjob on this post:
https://forum.magicmirror.builders/topic/5316/automatic-docker-build/2
-
@savona Both
package-lock.json
can just be deleted. Did you intentionally change the files in thedefault
directory? -
@idoodler No I did not change the default directory at all. That is why this is so odd to me.
-
I got a message saying my MM was out of date, so I pulled the new docker image and now have the 2318 message also.
The top of my CHANGELOG.md reads “## [2.5.0] - 2018-10-01”
Though the “image date” as reported by Portainer is “Created 2019-01-01 15:08:22”Do we need to wait for bastilimbach?
-
@savona OK, you may have a corrupt git directory then. You may try to clone it again.
-
I just blew away the docker image and did a new pull and it is fixed and on 2.6.0.
grep version package.json
“version”: “2.6.0”,
-
I was able to proceed past this error by using the command ‘git stash’. This worked for two Magic Mirrors.
-
Hello everybody
I have three MagicMirrors in use. On two mirrors he shows me that I’m 2318 and 124 behind the master respectively.
If I enter git pull in the MagicMirror folder, error occurs
Aktualisiere 6db61b4..de57daa error: Ihre lokalen Änderungen in den folgenden Dateien würden durch den Merge überschrieben werden: package-lock.json vendor/package-lock.json Bitte committen oder stashen Sie Ihre Änderungen, bevor sie mergen. Abbruch
What do I have to do to bring the MagicMirror up to date?