Hi guys,
I have installed OH2 with openhabian, so I assume I automatically got the latest snapshot release.
Today I ran my usually sudo apt-get update && apt-get upgrade procedure, which ran without errors and this conclusion:
Unpacking openhab2-offline (2.0.0~20161012185825) over (2.0.0~20161009032837) ...
Processing triggers for systemd (215-17+deb8u5) ...
Setting up openhab2-offline (2.0.0~20161012185825) ...
Installing new version of config file /etc/openhab2/html/index.html ...
Installing new version of config file /etc/openhab2/html/readme.txt ...
So I thought I got the newest release dated 2016-10-12. Furthermore the openhabian MOTD stated build #530. So far, so good (as far as #530 IS the latest build, I didn’t checked this…)
But interestingly a console “bundle:list” showed nearly all bundles with a slightly older date:
94 | Active | 80 | 0.9.0.201610080632 | Eclipse SmartHome Config Core
95 | Active | 80 | 0.9.0.201610080632 | Eclipse SmartHome Configuration Discovery
96 | Active | 80 | 0.9.0.201610080632 | Eclipse SmartHome Config Dispatcher
97 | Active | 75 | 0.9.0.201610080632 | Eclipse SmartHome Config XML
98 | Active | 80 | 0.9.0.201610080632 | Eclipse SmartHome Core
99 | Active | 80 | 0.9.0.201610080632 | Eclipse SmartHome Core Audio
100 | Active | 80 | 0.9.0.201610080632 | Eclipse SmartHome AutoUpdate Binding
101 | Active | 80 | 0.9.0.201610080632 | Eclipse SmartHome Core Binding XML
102 | Active | 80 | 0.9.0.201610080632 | Eclipse SmartHome Core ID
103 | Active | 80 | 0.9.0.201610080632 | Eclipse SmartHome Core Persistence
104 | Active | 80 | 0.9.0.201610080632 | Eclipse SmartHome Scheduler Service
105 | Active | 80 | 0.9.0.201610080632 | Eclipse SmartHome Core Thing
106 | Active | 75 | 0.9.0.201610080632 | Eclipse SmartHome Core Thing XML
107 | Active | 80 | 0.9.0.201610080632 | Eclipse SmartHome Transformation Service
108 | Active | 80 | 0.9.0.201610080632 | Eclipse SmartHome Core Voice
109 | Active | 80 | 0.9.0.201610080632 | Eclipse SmartHome Console
110 | Active | 80 | 0.9.0.201610080632 | Eclipse SmartHome Console for OSGi runtime Karaf
111 | Active | 80 | 0.9.0.201610080632 | Eclipse SmartHome JavaSound I/O, Fragments: 169
112 | Active | 80 | 0.9.0.201610080632 | Eclipse SmartHome Monitor
113 | Active | 80 | 0.9.0.201610080632 | Eclipse SmartHome Net I/O Bundle
114 | Active | 80 | 0.9.0.201610080632 | Eclipse SmartHome REST Interface Bundle
115 | Active | 80 | 0.9.0.201610080632 | Eclipse SmartHome Core REST API
116 | Active | 80 | 0.9.0.201610080632 | Eclipse SmartHome REST mDNS Announcer
117 | Active | 80 | 0.9.0.201610080632 | Eclipse SmartHome Sitemap REST API
118 | Active | 80 | 0.9.0.201610080632 | Eclipse SmartHome SSE REST API
119 | Active | 80 | 0.9.0.201610080632 | Eclipse SmartHome Voice REST API
120 | Active | 80 | 0.9.0.201610080632 | Eclipse SmartHome Bonjour/MDS Service Discovery Bundle
121 | Active | 80 | 0.9.0.201610080632 | Eclipse SmartHome Model Core
122 | Active | 80 | 0.9.0.201610080632 | Eclipse SmartHome Item Model
123 | Active | 80 | 0.9.0.201610080632 | Eclipse SmartHome Item Model Runtime
124 | Active | 80 | 0.9.0.201610080632 | Eclipse SmartHome Persistence Model
125 | Active | 80 | 0.9.0.201610080632 | Eclipse SmartHome Persistence Runtime
126 | Active | 80 | 0.9.0.201610080632 | Eclipse SmartHome Rule Model
…and so on…
Also the zwave binding was some days old. For cross checking I did a bundle:update 196 (which is the zwave binding) and surprise, surprise, I got a newer version after the update (remember: I did an apt-get upgrade just seconds before).
That leaved me with the question: Don’t I get all the latest updates with apt-get update && upgrade? Until now I thought I would…
Any help is appreciated!
Regards,
Stefan