READ THE CHANGELOG BEFORE UPDATING!
new update/upgrade script, ready for testing
This post is deleted!
@spitzlbergerj no attachment… send via mail… same ID as here on gmail
evroom last edited by evroom
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 statusand you alias
LC_ALL=C gitto the name
git, not the command
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.
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
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?
Sorry, I’ve always done the update via git. Now I am confused …
sdetweil last edited by sdetweil
@spitzlbergerj yes, please erase this file
it was copied early by the official updater in error
evroom last edited by
It is always difficult creating something and having it run flawlessly on many different systems with their many different settings, some exotic
One more thing I stumbled upon when googling:
shopt -s expand_aliases
Add this before the alias command, or just at the top of your script.
Seems to work.
OK, now I have another problem . The upgrade script ran and I think it upgraded some stuff.
At some point, I must have gotten my permissions mixed up. There were a number of directories that were root:root. Here there was Permission denied.
I have now corrected the owners. But now the upgrade script doesn’t run anymore, because it assumes that I am already on 2.10.
Can I force another upgrade?
@spitzlbergerj yes, change ‘apply’ to ‘force’
@evroom I decided to forget about alias altogether…