Arch Linux User Repository

For suggestions, issues, etc., please file them at https://gitlab.archlinux.org/freso/java-chatty – if submitting merge requests, do so against the java-chatty branch.

Note that when Twitch changes things, it may take a short while for those changes to get accounted for in a proper release of Chatty. If this is the case, and you need the new feature, you can try using java-chatty-beta or java-chatty-git until a new full release has been made addressing the change.

There is now also a chatty-beta package for those who want to be bleeding bleeding edge: https://aur.archlinux.org/packages/chatty-beta

For users who have used this PKGBUILD on version earlier than 0.9.x, note that from PKGBUILD 0.9.1-1 onwards, the PKGBUILD will not include as many patches as <0.9 PKGBUILDs did. One of the things this means is that the configuration will now be read from $HOME/.chatty instead of $HOME/.config/chatty. I'd recommend to either create a symlink (cd $HOME && ln -s .config/chatty .chatty) or move (or copy) the directory (cd $HOME && mv .config/chatty .chatty) prior to running version 0.9.x+ the first time.

java-environment is already a make dependency and it is theoretically possible to build and run the package with a different JDK than OpenJDK 8 (though admittedly I haven’t tried). If you fail to install and/or run it with OpenJDK 10 or 11 or Oracle’s JDK (currently 14), please submit bug reports to upstream. (Note that this is in accordance with https://wiki.archlinux.org/index.php/Java_package_guidelines#Dependencies and what upstream themselves specify ("It runs on […] Java 8 or later.").)

Please add 'jdk8-openjdk' as make-dependency to make installation easier.

jdk8-openjdk is an explicit make dependency and needs to be installed

@troyBORG That's how to fix your problem

-> Extracting chatty-0.10.tar.gz with bsdtar ==> Starting prepare()... patching file src/chatty/Chatty.java ==> Sources are ready. ==> Making package: chatty 0.10-1 (Fri 27 Dec 2019 12:13:36 PM CST) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> WARNING: Using existing $srcdir/ tree ==> Removing existing $pkgdir/ directory... ==> Starting build()...

FAILURE: Build failed with an exception.

• What went wrong: Execution failed for task ':compileJava'.

  Could not find tools.jar. Please check that /usr/lib/jvm/java-8-openjdk/jre contains a valid JDK installation.

• Try: Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

• Get more help at https://help.gradle.org

BUILD FAILED in 1s ==> ERROR: A failure occurred in build(). Aborting... checking dependencies...

Packages (1) gradle-6.0.1-1

Total Removed Size: 103.31 MiB

@Freso Please commit this patch to update to the current chatty version 0.10:

https://gist.github.com/mheob/0da42f55d11a55599388f62d7580386c#file-0001-chatty-0-10-1-patch

Just a caution, this doesn't work with the current "jdk-openjdk" package (Java 13). If you install this package when prompted, you will get the following error: = = = = = FAILURE: Build failed with an exception.

• What went wrong: A problem occurred configuring root project 'chatty-0.9.7'.

  Could not open cp_proj remapped class cache for 4w7y4hmqg9c0tc36ade1cyejo (/home/matt/.gradle/caches/5.6. Could not open cp_proj generic class cache for build file '/home/matt/aur/chatty/src/chatty-0.9.7/buil > BUG! exception in phase 'semantic analysis' in source unit 'BuildScript' Unsupported class file m = = = = = I uninstalled that package, and instead chose the LTS java version "jdk11-openjdk" and this successfully installed without issue.

@Freso thank you for the explanation.

There is now also a chatty-beta package for those who want to be bleeding bleeding edge: https://aur.archlinux.org/packages/chatty-beta

@bennyhillthebes gradle is needed to build the .jar file. This package actually builds chatty from its source, it doesn't just ship the precompiled source that upstream makes available (this would have been a binary package, recognised by the '-bin' suffix in the package name).