new update/upgrade script, ready for testing

evroom

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

i remove the alias so, the output will not tell us anything…

It will tell you if you get English as output, despite any language & variable settings.

I temporary changed the locale to de_DE.utf8 for testing and git status gave me German output.
Then I did LC_ALL=C git status and it replied in English.
LC_MESSAGES=C git status continued to reply in German.

Just FYI, perhaps it will help you, perhaps not :-)

sdetweil

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

Then I did LC_ALL=C git status and it replied in English.

cool… thats what the test script does… sets alias for git to ‘LC_ALL=C git’

I think I will just force alias

sdetweil

@spitzlbergerj great, thanks… u can run the update script again now…

if it says already at 2.10, the change the parm from apply to force

evroom

@sdetweil

Sam,

for some reason your testlang.sh script, using alias, is still responding in German, whereas the plain command responses in English:

pi@raspberrypi:~/MagicMirror $ curl -sL https://www.dropbox.com/s/80fevh39jme3iig/testlang.sh?dl=0 | bash
Auf Branch master
Ihr Branch ist auf demselben Stand wie 'origin/master'.
:
:

pi@raspberrypi:~/MagicMirror $ LC_ALL=C git status
On branch master
Your branch is up to date with 'origin/master'.
:
:

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

Also interesting; using sh iso bash:

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

EDIT - recommendations / friendly advice:

1/ Use #!/bin/bash in your script, not ~/bin/bash
2/ Do not alias the git command, just plain LC_ALL=C git status

I am on 2.10.0, but can try your testlang.sh script when needed.
Will keep the language settings on German for a while.

sdetweil

@evroom thanks… I have multiple commands to issue, and wanted to use alias for it…

thanks for the catch on #~…

can u try the test script again?
u can also look at the alias list , to make sure the one for git is set

alias

spitzlbergerj

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

locale -a

the output is:

C
C.UTF-8
de_DE.utf8
POSIX

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)