Update auf 2.13.0

kusselin

git remote prune origin

hi sdetweil schau hier:

pi@raspberrypi:~/MagicMirror $ git remote prune origin
pi@raspberrypi:~/MagicMirror $ 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.9.0 to 2.13.0
fetching latest revisions
error: cannot lock ref 'refs/tags/v2.12.0': unable to resolve reference 'refs/tags/v2.12.0': reference broken
From https://github.com/MichMich/MagicMirror
 ! [new tag]           v2.12.0    -> v2.12.0  (unable to update local ref)
MagicMirror git fetch failed
restoring custom.css

das gleiche wieder :-(

sdetweil

@kusselin said in Update auf 2.13.0:

reference broken

ok, one more time

git gc --prune=now
git remote prune origin

then script again

kusselin

@sdetweil said in Update auf 2.13.0:

git remote prune origin

pi@raspberrypi:~ $ cd MagicMirror
pi@raspberrypi:~/MagicMirror $ git gc --prune=now
fatal: bad object refs/tags/v2.12.0
fatal: failed to run repack
pi@raspberrypi:~/MagicMirror $ git remote prune origin
pi@raspberrypi:~/MagicMirror $ 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.9.0 to 2.13.0
fetching latest revisions
error: cannot lock ref 'refs/tags/v2.12.0': unable to resolve reference 'refs/tags/v2.12.0': reference broken
From https://github.com/MichMich/MagicMirror
 ! [new tag]           v2.12.0    -> v2.12.0  (unable to update local ref)
MagicMirror git fetch failed
restoring custom.css

sdetweil

ok, another try

git remote set-head origin --auto
git gc --prune=now
git remote prune origin

kusselin

@sdetweil said in Update auf 2.13.0:

git remote prune origin

pi@raspberrypi:~/MagicMirror $ git gc --prune=now
fatal: bad object refs/tags/v2.12.0
fatal: failed to run repack
pi@raspberrypi:~/MagicMirror $ git remote prune origin
pi@raspberrypi:~/MagicMirror $ 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.9.0 to 2.13.0
fetching latest revisions
error: cannot lock ref 'refs/tags/v2.12.0': unable to resolve reference 'refs/tags/v2.12.0': reference broken
From https://github.com/MichMich/MagicMirror
 ! [new tag]           v2.12.0    -> v2.12.0  (unable to update local ref)
MagicMirror git fetch failed
restoring custom.css

Wo ist das Problem…ist klar…bei mir läuft nie was auf Anhieb :-(

der Pi ist auf aktuellem Stand mit update && upgrade

sdetweil

something has happened to the git repo, it has lost a reference

we are trying to clean it up

one more time (note there is a dot in front of git/)

mv .git/refs/remotes/origin/HEAD /tmp
git gc --prune=now
git remote prune origin

kusselin

@sdetweil said in Update auf 2.13.0:

git remote prune origin

the same :-(

pi@raspberrypi:~/MagicMirror $ mv .git/refs/remotes/origin/HEAD /tmp
pi@raspberrypi:~/MagicMirror $ git gc --prune=now
fatal: bad object refs/tags/v2.12.0
fatal: failed to run repack
pi@raspberrypi:~/MagicMirror $ git remote prune origin
pi@raspberrypi:~/MagicMirror $ 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.9.0 to 2.13.0
fetching latest revisions
error: cannot lock ref 'refs/tags/v2.12.0': unable to resolve reference 'refs/tags/v2.12.0': reference broken
From https://github.com/MichMich/MagicMirror
 ! [new tag]           v2.12.0    -> v2.12.0  (unable to update local ref)
MagicMirror git fetch failed
restoring custom.css

sdetweil

@kusselin ok… show me results of

git branch
git remote -v

I’m not a git guru, so struggling to find solution

kusselin

You are the best!!!

pi@raspberrypi:~/MagicMirror $ git branch
* master
pi@raspberrypi:~/MagicMirror $ git remote -v
origin  https://github.com/MichMich/MagicMirror.git (fetch)
origin  https://github.com/MichMich/MagicMirror.git (push)

sdetweil

@kusselin ok, ONE more try

git update-ref -d 'refs/remotes/origin/HEAD'
git prune
git gc

then try again

kusselin

@sdetweil said in Update auf 2.13.0:

git gc

pi@raspberrypi:~/MagicMirror $ git update-ref -d 'refs/remotes/origin/HEAD'
pi@raspberrypi:~/MagicMirror $ git prune
fatal: Konnte Objekt 'refs/tags/v2.12.0' nicht parsen.
pi@raspberrypi:~/MagicMirror $ git gc
fatal: bad object refs/tags/v2.12.0
fatal: failed to run repack
pi@raspberrypi:~/MagicMirror $ 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.9.0 to 2.13.0
fetching latest revisions
error: cannot lock ref 'refs/tags/v2.12.0': unable to resolve reference 'refs/tags/v2.12.0': reference broken
From https://github.com/MichMich/MagicMirror
 ! [new tag]           v2.12.0    -> v2.12.0  (unable to update local ref)
MagicMirror git fetch failed
restoring custom.css

sdetweil

@kusselin said in Update auf 2.13.0:

refs/tags/v2.12.0
man, what a challenge

rm -rf .git/refs/tags/v2.12.0
git prune
git gc

then try again

kusselin

@sdetweil said in Update auf 2.13.0:

git gc

Should i save this file now??

this comes in the console now…

sdetweil

@kusselin i don’t understand?

kusselin

sdetweil

@kusselin looks like u might have changed compliments.js for some reason…

unless u applied a fix, you should never change the code in the module folders…
(else u run into this problem)…

I would say no, and figure out what needs to be saved and then restart it…
(this is test mode, so we are not changing anything)

kusselin

@sdetweil said in Update auf 2.13.0:

looks like u might have changed compliments.js for some reason…
unless u applied a fix, you should never change the code in the module folders…
(else u run into this problem)…
I would say no, and figure out what needs to be saved and then restart it…
(this is test mode, so we are not changing anything)

o.k. look:

pi@raspberrypi:~/MagicMirror $ rm -rf .git/refs/tags/v2.12.0
pi@raspberrypi:~/MagicMirror $ git prune
Prüfe Konnektivität: 16017, Fertig.
pi@raspberrypi:~/MagicMirror $ git gc
Objekte aufzählen: 16017, Fertig.
Zähle Objekte: 100% (16017/16017), Fertig.
Delta-Kompression verwendet bis zu 4 Threads.
Komprimiere Objekte: 100% (5873/5873), Fertig.
Schreibe Objekte: 100% (16017/16017), Fertig.
Gesamt 16017 (Delta 9849), Wiederverwendet 15910 (Delta 9746)
pi@raspberrypi:~/MagicMirror $ 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.9.0 to 2.13.0
fetching latest revisions
From https://github.com/MichMich/MagicMirror
 * [new tag]         v2.12.0    -> v2.12.0
there are 2 local files that are different than the master repo

   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)?n
skipping restore for modules/default/compliments/compliments.js, doing test run
skipping restore for package-lock.json, doing test run
processing dependency changes for active modules with package.json files

processing for module MMM-Remote-Control please wait
----------------------------------
skipped processing for MMM-Remote-Control, doing test run
processing complete for module MMM-Remote-Control

processing for module MMM-SoccerLiveScore please wait
----------------------------------
skipped processing for MMM-SoccerLiveScore, doing test run
processing complete for module MMM-SoccerLiveScore

processing for module MMM-SmartWebDisplay please wait
----------------------------------
skipped processing for MMM-SmartWebDisplay, doing test run
processing complete for module MMM-SmartWebDisplay

processing for module MMM-ioBroker please wait
----------------------------------
skipped processing for MMM-ioBroker, doing test run
processing complete for module MMM-ioBroker

processing for module MMM-FRITZ-Box-Callmonitor please wait
----------------------------------
skipped processing for MMM-FRITZ-Box-Callmonitor, doing test run
processing complete for module MMM-FRITZ-Box-Callmonitor

processing for module MMM-Fuel please wait
----------------------------------
skipped processing for MMM-Fuel, doing test run
processing complete for module MMM-Fuel

processing for module MMM-PublicTransportHafas please wait
----------------------------------
skipped processing for MMM-PublicTransportHafas, doing test run
processing complete for module MMM-PublicTransportHafas

processing for module MMM-Tools please wait
----------------------------------
skipped processing for MMM-Tools, doing test run
processing complete for module MMM-Tools

restoring custom.css
pi@raspberrypi:~/MagicMirror $ 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.9.0 to 2.13.0
fetching latest revisions
there are 2 local files that are different than the master repo

   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)?n
skipping restore for modules/default/compliments/compliments.js, doing test run
skipping restore for package-lock.json, doing test run
processing dependency changes for active modules with package.json files

processing for module MMM-Remote-Control please wait
----------------------------------
skipped processing for MMM-Remote-Control, doing test run
processing complete for module MMM-Remote-Control

processing for module MMM-SoccerLiveScore please wait
----------------------------------
skipped processing for MMM-SoccerLiveScore, doing test run
processing complete for module MMM-SoccerLiveScore

processing for module MMM-SmartWebDisplay please wait
----------------------------------
skipped processing for MMM-SmartWebDisplay, doing test run
processing complete for module MMM-SmartWebDisplay

processing for module MMM-ioBroker please wait
----------------------------------
skipped processing for MMM-ioBroker, doing test run
processing complete for module MMM-ioBroker

processing for module MMM-FRITZ-Box-Callmonitor please wait
----------------------------------
skipped processing for MMM-FRITZ-Box-Callmonitor, doing test run
processing complete for module MMM-FRITZ-Box-Callmonitor

processing for module MMM-Fuel please wait
----------------------------------
skipped processing for MMM-Fuel, doing test run
processing complete for module MMM-Fuel

processing for module MMM-PublicTransportHafas please wait
----------------------------------
skipped processing for MMM-PublicTransportHafas, doing test run
processing complete for module MMM-PublicTransportHafas

processing for module MMM-Tools please wait
----------------------------------
skipped processing for MMM-Tools, doing test run
processing complete for module MMM-Tools

restoring custom.css

it look good so or?

sdetweil

@kusselin well, you still need to resolve the problem with compliments.js…

if u don’t save it, then u lose whatever changes u made (but it might not matter)
if u DO save it, (and restore it) then it might not work anymore, or cause problems…

the test run warns that there WILL be a problem u need to fix first… (or understand how to resolve later)

kusselin

o.k. but one question…must i update my magic mirror? now it runs good…an i know there is a statement:

“NEVER CHANGE A RUNNING SYSTEM”

what you say?

sdetweil

@kusselin you do NOT HAVE to update, unless u have a problem , or unless u need a new feature…