Error resolving artifact org.jline:jline:jar:3.5.1-sp1?

[aolshove (Alex Olshove)]

@rlkoshak

I’m not completely clear on which verison of OH you are currently running right now.

I started out running 2.2 build 1114 when that error appeared after reboot. Then I went back to like 1098 with the same error after reboot, and finally back to 2.1 stable with the same error appearing after reboot. I used:

sudo apt-cache show openhab2
sudo apt-get install openhab2=<snapshot version>

I searched the community for help and found the clear cache stuff and tried those to no avail. Then I posted this community thread asking for help since I’m way over my head linux-wise.

[quote=“rlkoshak, post:6, topic:37017, full:true”]
If it is 2.2 then there is a backup script in /usr/share/openhab2/bin I think. You can look at that to see what files it backs up. The backup and restore scripts only backup/restore your configs so a restore will not overwrite your clean install and your config is not causing this problem.

All of your Things are either in .things files or in /var/lib/openhab2/jsondata.
[\quote]

The only backup/restore facility I know of is in the Openhabian config utility as a menu option but even that menu option confused me as it asked wanted some input from me that I was not sure how to answer at the time. To think that I know where the backup scripts would be and how to read them would be optimistic on your part to the point of absurdity.

The best I can do is follow very succinct step-by-step instructions at this point. It appears that I was very arrogant and ignorant to believe that using the latest snapshot would not brick my OH2 install. After this is fixed I think I shouldn’t venture into SnapShot territory ever again. I only did it as a recommendation by you in another thread when I was wondering how to get a new device recognized. Before that, OH2 2.1 was extremely stable:

@rlkoshak

I think it doesn’t come up as much because the typical practice is if the device is not in your current version of OH then one either waits for the next release or updates to the snapshot. If the device is not in the database at all, one submits the necessary information to the database, waits a couple of days, and then uses the snapshot.

Please don’t get me wrong. I really do appreciate your help, knowledge, and time. I’m just laying out my history and trying to stress my complete ignorance to know any better. I know, I should have taken the “waits for another release” option.

@rlkoshak

If you are worried, make a full backup of /etc/openhab2 and /var/lib/openhab2. Then use the backup script. Then do the purge. Then do the restore.

Thank you for the additional info.

@rlkoshak

@aolshove

my node numbers will get all screwed up

If you are talking about zwave, the node number is assigned by the controller. They will not change.

I am talking about ZWave. Sorry. Thanks for the explanation and for your time and patience. I really am trying to learn but simply searching these forums is very difficult for a noobie whom isn’t educated in Linux file structures. I barely know how to “sudo nano” much less why there’s an /etc, /opt, /lib, and why/how certain config files are put in certain areas and then throw in security and how to use apt-get and how that even works. I have so many blank areas in my Linux knowledge base it’s not funny.

Thank you again. I’ve read a lot of your other threads (presence detection is another subject that I’ve decided is over my head for now) and your knowledge is amazing.