I’m currently still on openHAB 2.5 and obviously get an error from apt when I periodically check for outdated software packages on my Raspberry Pi 3B+.
Should I also remove the apt repository link to Bintray since it’s apparently gone (403 Forbidden error messages), or should I remove the trusted key from /etc/apt/sources.list?
There are two errors that come up in relation to this.
openHAB errors in the logs failing to download and install any add-on.
Error from apt/yum/etc. indicating it cannot download the list of packages from bintray.
Downloading the kar file only fixes 1. To fix 2 one needs to eliminate the link to bintray from the repos used by the package manager (e.g. apt). openHABian has an option to do that for you. For those who ran an apt upgrade prior to May 1st the upgrade did this for you. However, those who failed/did not know to run an upgrade prior to May 1st will still have an entry in their sources list pointing to bintray and running apt update will generate an error.
/var/lib/openhab2/etc directory. So, there is no /var/lib/openhab2/etc/org.ops4j.pax.url.mvn.cfg
And the only .kar files on the system are:
/usr/share/openhab2/runtime/system/org/apache/karaf/deployer/org.apache.karaf.deployer.kar
/srv/openhab2-sys/runtime/system/org/apache/karaf/deployer/org.apache.karaf.deployer.kar
o
So, it doesn’t appear the system has ever gotten the files locally.
I don’t know if this is possible but would having a DNS entry to always point to where ever the files are be a good idea?
That way if something like the bintray situation happens again then all is needed is a DNS change and the links would all work and no users would notice and everything would function.
Just an idea.
There are probably reasons this hasn’t been done before. Who knows?