Then this must have been a recent change. There’s the stable releases, the milestone releases (which my setup is tracking) and the daily snapshot releases (unstable).
So far I automatically received updates up to 2.5.4. Only 2.5.5 gives problems with the repository.
I ran openhabian-config today. First time in ages. And behold, a warning appeared:
┌──────────────────────────────┤ openHABian breaking NEWS ├──────────────────────────────┐
│ │
│ This is the new announcement page to pop up whenever you start openhabian-config and
│ there's significant news we would like to share with you. Hit tab to unselect buttons
│ and scroll through the text using UP/DOWN/PG UP/PG DOWN.
│ When you choose 'I have read this' the message will not appear on startup anymore.
│ All announcements will be stored in /opt/openhabian/docs/NEWSLOG for you to lookup.
│
│ ## May 31, 2020
│ ### Stable branch
│ Introducing a new versioning scheme to openHABian. Please welcome `stable` branch.
│ Similar to openHAB where there's releases and snapshots, you will from now on be using
│ the stable branch. It's the equivalent of an openHAB release.
│ We will keep providing new changes to the master branch first as soon as we make them
│ available, just like we have been doing in the past. If you want to keep living on the
│ edge, want to make use of new features fast or volunteer to help a little in advancing
│ openHABian, you can choose to switch back to the master branch.
│ Anybody else will benefit from less frequent but well better tested updates to happen
│ to the stable branch in batches, whenever the poor daring people to use `master` have
│ reported their trust in these changes to work flawlessly.
│ You can switch branches at any time using the menu option 01.
│
│ ### Supported hardware and Operating Systems
│ openHABian now fully supports all Raspberry Pi SBCs with our fast-start image. As an
│ add-on package, it is supposed to run on all Debian based OSs.
│
│ Check the [README](#README.md) to see what "supported" actually means and what you can
│ do if you want to run on other HW or OS.
│
│ ### ZRAM per default
│ Swap, logs and persistence files are now put into ZRAM per default.
│ See [ZRAM status thread](https://community.openhab.org/t/zram-status/80996) for more
│ information.
│
│ ### New Java options
│ Preparing for openHAB 3, new options for the JDK that runs openHAB are now available:
│
│ - Java Zulu 8 32-Bit OpenJDK (default on ARM based platforms)
│ - Java Zulu 8 64-Bit OpenJDK (default on x86 based platforms)
│ - Java Zulu 11 32-Bit OpenJDK (beta testing)
│ - Java Zulu 11 64-Bit OpenJDK (beta testing)
│ - AdoptOpenJDK 11 OpenJDK (beta replacement for Zulu)
│
│ openHAB 3 will be Java 11 only. 2.5.X is supposed to work on both, Java 8 and Java
│ 11.
│ Running the current openHAB on Java 11 however has not been tested on a wide scale.
│
│ Please participate in beta testing to help create a smooth transition user experience
│ for all of us.
│ See [announcement thread](https://community.openhab.org/t/Java-testdrive/99827) on the
│ community forum.
│
│ <I have read this> <keep displaying>
│ │
└────────────────────────────────────────────────────────────────────────────────────────┘
It appears that this message was created or updated yesterday.
I must have missed the notice to run openhabian-config after having upgraded to 2.5.
Additionally, the stable versions (including 2.5.4, 2.5.5, etc.) are available in the APT testing and snapshot repositories anyway. The stable repository however is hosted in a more stable location (Bintray) so should be the recommended repository for openHAB 2.5.X
The way to get the openHAB patch releases apparently changed somewhere along with the new patch release… there were 3 channels (release, milestones, snapshots), now apparently only 2 (release, snapshots). I’m just trying to find where this change originated from.
When 2.5.0 was released, they stopped core development to work on OH3. The not only release snapshots & monthly releases with newer bindings. for 2.5.x.
See the first post in this thread for a little more information.
It has been and for the foreseeable future will be the same 3 channels:
Snapshots - These are built daily when something in the source changes. The apt unstable repository contains these.
Testing - Contains milestones, betas and release candidates there hasn’t been one for a while. The apt testingandunstable repositories contain these.
Stable - Contains only stable releases, including the patch releases, these are hosted on Bintray. All apt repos (unstable, testing and stable) contain these.
IMO the only way to fix that behaviour for 2.5.x is by putting the bundles in the addons-directory. These are never touched by an update. Core bundles do not change.
Thanks. For some reason all the searches I was doing didn’t find that. Really this is the kind of thing that should be in the release notes imho. It doesn’t seem like an insignificant change.
Sure. But this also prevents installation of new bindings.
I agree that it is a but unexpected, that installing or uninstalling one binding updates the version of another binding or that installing 2.5.4 and cleaning cache results in 2.5.5.
It is meant to automatically provide critical patches. It will make more sense for upcoming 3.0.x releases - with 2.5.x we are not sticking nicely to patches, but there are indeed unexpected feature changes.