Thanks. I’m happy to heklp but I dislike mixing installation methods.
Aren’t snapshots right there to handle this ?
Remember there’s also the testing repo for those who want a little more safety.
Sadly I don’t have the spare cycles to test this immediately but at the end of next week I should have some time. I’ll come back and give the Docker images a test run.
I’d advise against trying to use the directory above as a repo (as this is where the build process is tested first and you may get very broken packages from it).
Thanks Benjy. Installed it but seems that package broke my delayed rules processing at startup. Didn’t investigate but seems my rules files were processed right from the start.
No, re-tested and it was fine now. I did a systemctl daemon-reload, possibly that wasn’t part of your package but is for the snapshot ones ? Just guessing, though.
Does this mean that the limitation to only using Java 8 goes away and the docs need to be updated or are there other libraries or ESH/OH code that still requires no later than Java 8?
I want to be sure the docs get updated if we can use the newer Javas now.
As discussed on the PR, the Karaf upgrade is a prerequisite for newer Java versions, but upgrading Karaf does not mean that we can immediately declare openHAB working with newer Java versions. So short answer: No, we stay with Java8 for now.
After logging out with logout from openhab-cli console I get:
2018-09-26 18:41:01.611 [WARN ] [org.jline ] - Failed to save history
java.nio.file.AccessDeniedException: /home/openhab
at sun.nio.fs.UnixException.translateToIOException(UnixException.java:84) ~[?:?]
at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102) ~[?:?]
at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107) ~[?:?]
at sun.nio.fs.UnixFileSystemProvider.createDirectory(UnixFileSystemProvider.java:384) ~[?:?]
at java.nio.file.Files.createDirectory(Files.java:674) ~[?:?]
at java.nio.file.Files.createAndCheckIsDirectory(Files.java:781) ~[?:?]
at java.nio.file.Files.createDirectories(Files.java:767) ~[?:?]
at org.jline.reader.impl.history.DefaultHistory.save(DefaultHistory.java:132) ~[17:org.jline.reader:3.9.0]
at org.jline.reader.impl.history.DefaultHistory.add(DefaultHistory.java:277) [17:org.jline.reader:3.9.0]
at org.jline.reader.impl.LineReaderImpl.finishBuffer(LineReaderImpl.java:944) [17:org.jline.reader:3.9.0]
at org.jline.reader.impl.LineReaderImpl.readLine(LineReaderImpl.java:594) [17:org.jline.reader:3.9.0]
at org.apache.karaf.shell.impl.console.ConsoleSessionImpl.readCommand(ConsoleSessionImpl.java:439) [14:org.apache.karaf.shell.core:4.2.1]
at org.apache.karaf.shell.impl.console.ConsoleSessionImpl.run(ConsoleSessionImpl.java:397) [14:org.apache.karaf.shell.core:4.2.1]
at java.lang.Thread.run(Thread.java:748) [?:?]
Snapshot #1372 apt install on Ubuntu 18.04 LTS, so the directory /home/openhab should never be called because it does not exist on an apt install …
Thx, yes, I found that post before I posted, but that user did use a manual openHAB install where there should be a /home/openhab directory.
So I need to create that directory manually?
As what user did you run openhab-cli console ? I usually run openHAB in Docker so I’m not familiar with the whole Debian packaging/setup. Perhaps @Benjy knows if this issue can also be solved without creating a home directory.
Looks like you can also relocate the Karaf Console history file to another directory by adding an additional line to $OPENHAB_USERDATA/etc/system.properties :