??? What is that supposed to do?
I’m sorry about that, I meant /cache
But you promised cash!!
does this the same stuff like
sudo rm -R /var/lib/openhab2/cache/*
and
sudo rm -R /var/lib/openhab2/tmp/*
Never mind.
I found (again):
Hi all, the huge pace of development continues and we have thus another monthly update for you:
openHAB 2.5.5, see https://github.com/openhab/openhab-distro/releases/tag/2.5.5 for the list of changes.
It is available on our download page as well as in the Linux package repos and as a Docker image. Have fun!
It appears it was available for installation before the announcement, this confused me a bit
But good to see this. Great work!
That is what should be done but was not done previously. Be sure a new version is actually available before announcing. Making it available is not an instantaneous process.
There seems to be an issue with the Ubuntu repository
smitopher@myth-server:~$ sudo apt update
[sudo] password for smitopher:
Get:1 http://security.ubuntu.com/ubuntu bionic-security InRelease [88.7 kB]
Hit:2 https://deb.nodesource.com/node_8.x bionic InRelease
Ign:3 http://download.webmin.com/download/repository sarge InRelease
Hit:4 http://ppa.launchpad.net/mosquitto-dev/mosquitto-ppa/ubuntu bionic InRelease
Hit:5 https://download.docker.com/linux/ubuntu bionic InRelease
Hit:6 http://download.webmin.com/download/repository sarge Release
Hit:7 http://ppa.launchpad.net/mythbuntu/31/ubuntu bionic InRelease
Hit:8 http://us.archive.ubuntu.com/ubuntu bionic InRelease
Get:9 http://us.archive.ubuntu.com/ubuntu bionic-updates InRelease [88.7 kB]
Get:10 http://ppa.launchpad.net/ondrej/php/ubuntu bionic InRelease [20.8 kB]
Get:11 http://us.archive.ubuntu.com/ubuntu bionic-backports InRelease [74.6 kB]
Hit:13 http://ppa.launchpad.net/webupd8team/java/ubuntu bionic InRelease
Ign:14 https://openhab.jfrog.io/openhab/openhab-linuxpkg testing InRelease
Err:15 https://openhab.jfrog.io/openhab/openhab-linuxpkg testing Release
Unknown date format Bad header data [IP: 35.231.52.82 443]
Get:16 http://us.archive.ubuntu.com/ubuntu bionic-updates/main i386 Packages [679 kB]
Get:17 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages [939 kB]
Get:18 http://us.archive.ubuntu.com/ubuntu bionic-updates/main Translation-en [320 kB]
Get:19 http://us.archive.ubuntu.com/ubuntu bionic-updates/restricted amd64 Packages [51.7 kB]
Get:20 http://us.archive.ubuntu.com/ubuntu bionic-updates/restricted Translation-en [12.9 kB]
Get:21 http://us.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages [1,070 kB]
Get:22 http://us.archive.ubuntu.com/ubuntu bionic-updates/universe Translation-en [332 kB]
Reading package lists... Done
E: The repository 'https://openhab.jfrog.io/openhab/openhab-linuxpkg testing Release' no longer has a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
That is the wrong repo for the Stable release just announced.
Still an issue
Hit:13 http://ppa.launchpad.net/webupd8team/java/ubuntu bionic InRelease
Ign:14 https://openhab.jfrog.io/openhab/openhab-linuxpkg stable InRelease
Err:15 https://openhab.jfrog.io/openhab/openhab-linuxpkg stable Release
Unknown date format Bad header data [IP: 35.231.52.82 443]
Reading package lists... Done
E: The repository 'https://openhab.jfrog.io/openhab/openhab-linuxpkg stable Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
Had the same issue and I fixed it by using the following repository for stable:
deb https://dl.bintray.com/openhab/apt-repo2 stable main
According to our official documentation the official stable repo is in bintray.
Corrected, Thank you
Took me a few times looking at my apt source to see what I was doing wrong,
A quick message to let you know that the Freebox binding is no more working in distribution 2.5.5, the authentication to the server is systematically failing.
I already proposed a fix, I hope that it will be merged quickly.
something has changed again and previous logging from jsr233 rules has stopped working. I don’t see any changes in the changes list that could impact this. It is working correctly with 2.5.3 and 2.5.4 releases.
Someone else reported something similar and it was resolved by touching the org.ops4j.pax.logging.cfg file…
That sounds more like a workaround than a resolution.
have not yet tried this, but curious how this will solve the issue if the openhab process is started from 0?
That’s because it is a workaround. I’ve seen this happen very rarely since before 2.5M2, but I update files, clear cache, and restart OH a LOT more often than the average user. The actual issue has not been identified, but the symptom is that logging stops for some loggers. The only updates in this release were to add-ons… there were no updates to scripted automation, the update script, or logging. There may be something glitchy with the update process, but it is not specific to this release. It’s something to keep an eye on, but discussion about it does not belong in this topic.
I’m not sure what you mean by this, but if you open a new topic, I’ll be happy to discuss there.