new update/upgrade script, ready for testing

spitzlbergerj

@sdetweil Hi, I run the script just now again. The output is the same I guess:

curl -sL https://www.dropbox.com/s/80fevh39jme3iig/testlang.sh?dl=0 | bash
Auf Branch master
Ihr Branch ist zu 'origin/master' um 117 Commits hinterher, und kann vorgespult werden.
  (benutzen Sie "git pull", um Ihren lokalen Branch zu aktualisieren)
Unversionierte Dateien:
  (benutzen Sie "git add <Datei>...", um die Änderungen zum Commit vorzumerken)

        core
        installers/dumpactivemodules.js

nichts zum Commit vorgemerkt, aber es gibt unversionierte Dateien (benutzen Sie "git add" zum Versionieren)

sdetweil

@spitzlbergerj don’t yah love it… what is supposed to work, doesn’t…

arg

sop I changed test script to do it your way… try it out

spitzlbergerj

@sdetweil Sorry if I misunderstood something. Should I have corrected something on my own?

OK, I started the script again. Now the output is as follows:

curl -sL https://www.dropbox.com/s/80fevh39jme3iig/testlang.sh?dl=0 | bash
On branch master
Your branch is behind 'origin/master' by 117 commits, and can be fast-forwarded.
  (use "git pull" to update your local branch)
Untracked files:
  (use "git add <file>..." to include in what will be committed)

        core
        installers/dumpactivemodules.js

nothing added to commit but untracked files present (use "git add" to track)

And the update script returns the following output:

bash -c  "$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/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
upgrading from version 2.9.0 to 2.10.0
fetching latest revisions
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-NetworkScanner please wait
----------------------------------
skipped processing for MMM-NetworkScanner, doing test run
processing complete for module MMM-NetworkScanner

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

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

restoring custom.css

So it all worked out now, right?

Thanks for your help @sdetweil and @evroom

sdetweil

@spitzlbergerj said in new update/upgrade script, ready for testing:

upgrading from version 2.9.0 to 2.10.0

all looks good… thank you so much for your time and patience…

but… the upgrader says u are still on 2.9… maybe a different folder? (as u said u were on 2.10 already)

spitzlbergerj

This post is deleted!

sdetweil

@spitzlbergerj no attachment… send via mail… same ID as here on gmail

evroom

@sdetweil said in new update/upgrade script, ready for testing:

I changed test script to do it your way… try it out

pi@raspberrypi:~/MagicMirror $ curl -sL https://www.dropbox.com/s/80fevh39jme3iig/testlang.sh?dl=0 | bash
On branch master
Your branch is up to date with 'origin/master'.

Sam. I think the issue is, that the command is git status and you alias LC_ALL=C git to the name git, not the command git.
You cannot use the alias as a replacement for a part of your command, but I might be wrong.

I think the only solution is to check for language en_US and then for every git command either use plain git or else by using LC_ALL=C.

Or just use LC_ALL=C for every git call.

sdetweil

@evroom

name git, not the command git

i don’t understand this…

its been working fine for quite a few months, handling LC_ALL and LANGUAGE, just hs system has LANG too…

anyhow, alias is supposed to work on ‘commands’ issued, and replace the started command with the replacement string (once)

this is how the git doc suggested dealing with this issue and stackexchange posts over quite some time echoed it…

I changes to the ‘LC_ALL=C git’ approach anyhow

I don’t even check now, just do it… on english system, it doesn’t hurt

spitzlbergerj

no, I didn’t say I was on 2.10.

i have now run the script in apply mode. The output is very long and apparently it was not updated, right?

Link Text

Sorry, I’ve always done the update via git. Now I am confused …

sdetweil

@spitzlbergerj yes, please erase this file

~/MagicMirror/installers/dumpactivemodules.js

it was copied early by the official updater in error