git issues after automatic install

benjay

Dear all,

I hope you can quickly provide support for this. After I did a successful installation of mm2 on my PI2 - I’d like to download & install new modules now. Unfortunately, GIT seems to be in a kind of hanging state and I`m a total noob to GIT. :(

Please check some of the RCs I get when trying to install a 3rd Party module.

As an example --> This happens when I try to clone a repository to my modules folder:

pi@MAGICMIRROR:~/MagicMirror/modules $ git clone https://github.com/rseidt/MMM-bringList
Cloning 'MMM-bringList' ...
remote: Enumerating objects: 22, done.
remote: Counting objects: 100% (22/22), done.
remote: Compressing objects: 100% (15/15), done.
error: Could not create temporary file: The argument is invalid
fatal: failed to write object
fatal: unpack-objects failed

OK, so far so good - seems like GIT has an issue with my local repos. I tried already GIT with the argument GIT rebase which leads to the following output:

pi@MAGICMIRROR:~/MagicMirror/modules $ git rebase
error: rebase not possible: You have changes that are not marked for commit.
error: Please commit the changes or use "stash".

Running the stash option - this asks me to provide an email etc. - so no option to move onwards.

So quick break here - hope one of you - guys have an idea how to solve this.

cheers
Benjay

sdetweil

@benjay from the MagicMirror folder do

git status
df -k

which auto install script did u use? linked from MagicMirror github readme page?
if so, erase MagicMirror/installers/dumpactivemodules.js

then run the updated installer

see here
https://forum.magicmirror.builders/topic/10171/updated-installer-script-available-for-testing

benjay

Hi Sam,

thx - so here we go:

pi @ MAGICMIRROR: ~ / MagicMirror $ git status
On branch master
Your branch is on the same level as 'origin / master'.

Changes that are not marked for commit:
  (use "git add <file> ..." to mark the commit changes)
  (use "git checkout - <file> ..." to discard the changes in the working directory)

        changed: package-lock.json

Unversioned files:
  (use "git add <file> ..." to mark the commit changes)

        0
        core

no commit commit changes (use "git add" and / or "git commit
 -a")

df -k returns (imho engough space left):

pi@MAGICMIRROR:~/MagicMirror $ df -k
Dateisystem    1K-Blöcke Benutzt Verfügbar Verw% Eingehängt auf
/dev/root       30358348 3935644  25138208   14% /
devtmpfs          443156       0    443156    0% /dev
tmpfs             447764   19884    427880    5% /dev/shm
tmpfs             447764   45300    402464   11% /run
tmpfs               5120       4      5116    1% /run/lock
tmpfs             447764       0    447764    0% /sys/fs/cgroup
/dev/mmcblk0p1    258095   53034    205061   21% /boot
tmpfs              89552       0     89552    0% /run/user/1000

The file MagicMirror/installers/dumpactivemodules.js has been erased/moved to temp folder (/home/pi/temp).

Yep - for installation - I used the CMD (user PI) from the README as below:
bash -c "$(curl -sL https://raw.githubusercontent.com/MichMich/MagicMirror/master/installers/raspberry.sh)"

I tried the update script as mentioned in the related link- please find the RCs below:

pi@MAGICMIRROR:~/MagicMirror $ curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/raspberry.sh | bash

install log being saved to /home/pi/install.log
Updating packages ...
Installing helper tools ...
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.
Statusinformationen werden eingelesen.... Fertig
build-essential ist schon die neueste Version (12.6).
curl ist schon die neueste Version (7.64.0-4).
git ist schon die neueste Version (1:2.20.1-2+deb10u1).
unzip ist schon die neueste Version (6.0-23+deb10u1).
wget ist schon die neueste Version (1.20.1-1.1).
0 aktualisiert, 0 neu installiert, 0 zu entfernen und 3 nicht aktualisiert.
Check current Node installation ...
Node currently installed. Checking version number.
Minimum Node version: v10.1.0
Installed Node version: v10.18.0
No Node.js upgrade necessary.
Check current NPM installation ...
NPM currently installed. Checking version number.
Minimum npm version: V6.0.0
Installed npm version: V6.13.4
No npm upgrade necessary.
It seems like MagicMirror is already installed.
To prevent overwriting, the installer will be aborted.
Please rename the ~/MagicMirror folder and try again.

If you want to upgrade your installation run upgrade-script from the ~/MagicMirror/installers directory.

pi@MAGICMIRROR:~/MagicMirror $ cd installers/
pi@MAGICMIRROR:~/MagicMirror/installers $ ll
insgesamt 84
drwxr-xr-x  3 pi pi  4096 Jan  6 20:22 .
drwxr-xr-x 17 pi pi  4096 Jan  5 20:45 ..
-rw-r--r--  1 pi pi   342 Jan  6 20:22 dumpactivemodules.js
-rwxr-xr-x  1 pi pi  6443 Jan  4 18:23 fixuppm2.sh
-rwxr-xr-x  1 pi pi    38 Jan  4 18:23 mm.sh
-rw-r--r--  1 pi pi   181 Jan  4 18:23 pm2_MagicMirror.json
drwxr-xr-x  2 pi pi  4096 Jan  4 18:23 postinstall
-rwxr-xr-x  1 pi pi 22409 Jan  4 18:23 raspberry.sh
-rwxr-xr-x  1 pi pi  4443 Jan  4 18:23 screensaveroff.sh
-rw-r--r--  1 pi pi  3799 Jan  6 20:22 upgrade.log
-rwxr-xr-x  1 pi pi 12710 Jan  4 18:23 upgrade-script.sh
pi@MAGICMIRROR:~/MagicMirror/installers $ ./upgrade-script.sh
the log will be /home/pi/MagicMirror/installers/upgrade.log
No LSB modules are available.
doing test run = true
update log will be in /home/pi/MagicMirror/installers/upgrade.log

saving custom.css
cp: der Aufruf von stat für 'custom.css' ist nicht möglich: Datei oder Verzeichnis nicht gefunden
upgrading from version 2.10.0 to 2.10.0
fetching latest revisions
no modules found needing npm refresh
restoring custom.css
cp: der Aufruf von stat für 'save_custom.css' ist nicht möglich: Datei oder Verzeichnis nicht gefunden
rm: das Entfernen von 'save_custom.css' ist nicht möglich: Datei oder Verzeichnis nicht gefunden

and again GIT status returns the same as above.

???
Cheers

sdetweil

@benjay ok, both install and update have bugs on the official page…

because u have moved patially to 2.10, you need to do this to update

bash -c  "$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/upgrade-script.sh)" force

I can’t tell what u wanted to do…

install is 1st time (using raspberry.sh)
update is every quarter (using update_script.sh)

benjay

Hi,

thx for the hint. I did the “forced” update as requested:

pi@MAGICMIRROR:~/MagicMirror $ bash -c  "$(curl -sL https://raw.githubuserconten                                      t.com/sdetweil/MagicMirror_scripts/master/upgrade-script.sh)" force
the log will be /home/pi/MagicMirror/installers/upgrade.log
No LSB modules are available.
doing test run = false
update log will be in /home/pi/MagicMirror/installers/upgrade.log

upgrading from version 2.10.0 to 2.10.0
fetching latest revisions
updating MagicMirror runtime, please wait

> magicmirror@2.10.0 install /home/pi/MagicMirror
> cd vendor && npm install

npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.4 (node_modules/fse                                      vents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@                                      1.2.4: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"}                                      )

audited 220 packages in 24.324s
found 5 vulnerabilities (4 low, 1 high)
  run `npm audit fix` to fix them, or `npm audit` for details

> magicmirror@2.10.0 postinstall /home/pi/MagicMirror
> sh untrack-css.sh && sh installers/postinstall/postinstall.sh && npm run insta                                      ll-fonts

MagicMirror installation successful!

> magicmirror@2.10.0 install-fonts /home/pi/MagicMirror
> cd fonts && npm install

audited 1 package in 2.217s
found 0 vulnerabilities

updated 3 packages and audited 3684 packages in 169.644s

15 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities

no modules found needing npm refresh

Unfortunately the GIT status is still reporting issues (same as before)

pi@MAGICMIRROR:~/MagicMirror/modules $ git status
Auf Branch master
Ihr Branch ist auf demselben Stand wie 'origin/master'.

Änderungen, die nicht zum Commit vorgemerkt sind:
  (benutzen Sie "git add <Datei>...", um die Änderungen zum Commit vorzumerken)
  (benutzen Sie "git checkout -- <Datei>...", um die Änderungen im Arbeitsverzeichnis zu verwerfen)

        geändert:       ../package-lock.json

Unversionierte Dateien:
  (benutzen Sie "git add <Datei>...", um die Änderungen zum Commit vorzumerken)

        ../0
        ../core

keine Änderungen zum Commit vorgemerkt (benutzen Sie "git add" und/oder "git commit -a")

benjay

reboot it was :D

sdetweil

@benjay Unfortunately the GIT status is still reporting issues (same as before)

those aren’t issues

the package-lock.json is generated by the npm install, so its new and changed.

the 0 is a bug from the installer once
and the core is some dump from npm/node crashing at some time.

all is good…
(git status in the MagicMirror folder should show the same output after reboot)