Build Nr. 637 is displaying build 618

I updated to Build 637. Karaf console is showing 618.
Is there a reason or was it just forgotten to increment the number?

At least it shows you something: I don’t have any version number at the moment.
I’m sure it has to do with

but I couldn’t yet figure out where the version number is stored now.

    __ __                  ____
   / //_/____ __________ _/ __/
  / ,<  / __ `/ ___/ __ `/ /_
 / /| |/ /_/ / /  / /_/ / __/
/_/ |_|\__,_/_/   \__,_/_/

Apache Karaf (4.0.4)

Hit ‘’ for a list of available commands
and ‘[cmd] --help’ for help on a specific command.
Hit ‘system:shutdown’ to shutdown Karaf.
Hit ‘’ or type ‘logout’ to disconnect shell from current session.

I am on the latest build and it shows:

Launching the openHAB runtime…

                      __  _____    ____      

____ ____ ___ ____ / / / / | / __ )
/ __ / __ / _ / __ / // / /| | / __ |
/ /
/ / // / __/ / / / __ / ___ |/ // /
_/ ./_// /// /// |/_____/
/_/ 2.0.0-SNAPSHOT
Build #582

Hit ‘’ for a list of available commands
and ‘[cmd] --help’ for help on a specific command.

The reason is https://github.com/openhab/openhab-distro/issues/331 and that my fix didn’t work for older installations. Will see if I can find yet another solution to it.

On todays version I have a build number again :slight_smile:


                          __  _____    ____
  ____  ____  ___  ____  / / / /   |  / __ )
 / __ \/ __ \/ _ \/ __ \/ /_/ / /| | / __  |
/ /_/ / /_/ /  __/ / / / __  / ___ |/ /_/ /
\____/ .___/\___/_/ /_/_/ /_/_/  |_/_____/
    /_/                        2.0.0-SNAPSHOT
                               Build #639

Hit '<tab>' for a list of available commands
and '[cmd] --help' for help on a specific command.
Hit '<ctrl-d>' or type 'system:shutdown' or 'logout' to shutdown openHAB.

Hooray :slight_smile:

That reminds me of “Baby Steps” in “What about Bob” :slight_smile:
Getting closer …

Baby Steps are not working here.
Still build 618 is displayed after having installed build 644

Manual install? Unzipping with “not overwriting” option?
Then delete file branding.properties manually before upgrading … worked for me. But it’s just a a workaround.

Thanks.
I guess I will continue live with the wrong build number.

@Kai Is this issue now resolved? I ask because because Karaf has been showing me the build number as 703, for all the last few stable builds I’ve been downloading. E.g. just downloaded build 715, but karaf still showing 703.

Thanks

Are you using apt installation or how do you update?

@Benjy Are the files

userdata/etc/branding.properties
userdata/etc/branding-ssh.properties

updated through an apt-upgrade? If not, they should!

I’m not aware of any problems in this area. Just did something related to these files yesterday (upgrade and new installation). @smar Which kind of setup are you using?

userdata/etc/branding.properties is on the list of files to mark as “not a config file”, so will be overwritten but userdata/etc/branding-ssh.properties is not however so there’s a chance that this will kept (but only if the user ignores the prompt).

At this point it would be helpful to have a complete list of files in userdata/etc/ that should be overwritten on each update. So far I have:

startup.properties
config.properties
distribution.info
jre.properties
org.apache.karaf.*
profile.cfg
branding.properties

I’ll make an issue for this in linuxpkg when github comes back online?

I run OH inside a docker container. I build the image locally with the Dockerfile downloading the zip from https://openhab.ci.cloudbees.com/job/openHAB-Distribution/lastSuccessfulBuild/artifact/distributions/openhab/target/openhab-2.0.0-SNAPSHOT.zip

The userdata volume is shared with the host in the usual way and so I also tried deleting both the branding files before running OH, but the files seem to then get recreated/downloaded with the same Build #703 in them.

UPDATE: I just had a look inside the zip file, and the branding files in there ARE CORRECT. However, as I am not using the userdata folder from within the zip file, my branding files are not getting correctly updated. I can easily fix this in my Dockerfile, but the question I have is, where are the Build #703 branding files automatically coming from, when I manually delete the branding files and start openhab and why #703 and not the current stable one, e.g. #717?