Right, I need some help - I have gotten myself totally in a mix.
I originally ran a manual install, but later replaced this with an apt-get install using:
Please note I am not a linux guy, so I am largely poking this beast with a stick for reactions.
A repo list using apt returns these installs:
openhab2/unstable 2.1.0~20170212123642-1 all
openhab2-addons/unstable 2.1.0~20170212123642-1 all
openhab2-addons-legacy/unstable 2.1.0~20170212123642-1 all
openhab2-online/now 2.0.0~20170108170225-1 all [installed,local]
So this appears to be an apt-get install.
Now according to
Backing/Restoring up openHAB2.x , my userdata and conf are at:
/var/lib/openhab2/ and /etc/openhab2/ - which they appear to be (in fact, I have been editing the conf text files and they are having the desired effect)
Which means I should have the details required to follow:
http://docs.openhab.org/installation/linux.html#upgrade
When I look at this though - it tells me:
If you’re using a version earlier than 2.1.0, then you can use the following commands in Terminal to download the script and run it. Assuming the openHAB directory is in /opt/openhab:
Of course - I don’t have anything in /opt
In fact: http://docs.openhab.org/installation/linux.html#file-locations tells me my repo install installation path should be /usr/share/openhab2 (again this appears correct)
Now here’s the winner . .
If I try follow the upgrade script mentioned above http://docs.openhab.org/installation/linux.html#upgrade and I replace the incorrect path (/opt/openhab) with what should be the valid path (user/share/openhab2) the script STILL fails to run
blah@openHab2:/$ cd /usr/share/openhab2/
blah@openHab2:/usr/share/openhab2$ ls
addons bin LICENSE.TXT runtime start_debug.sh start.sh
blah@openHab2:/usr/share/openhab2$ sudo sh -c "$(curl -fsSL https://raw.githubusercontent.com/openhab/openhab-distro/master/distributions/openhab/src/main/resources/bin/update)" -- 2.1.0
[sudo] password for blah:
#########################################
openHAB 2.x.x update script
#########################################
The script must be called from openHAB's root directory.
Either specify a directory or place this update script in and run from openHAB's root folder.
Now - cracking open the script, I learn that the script is looking for the folders userdata and conf in the current directory - in order to determine that this is in fact a valid openhab root directory.
I’d like to just get to the point where I can upgrade via the script, since I keep coming accross nasties and the solution always seems to be “the nightly release fixed this issue”
Please could someone point me in the right direction - as you can see above, I have spent a fair chunk of time trying to figure this one out