Arch Linux User Repository

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.

hi I just like to mention, that many java devs (including me) prefer the gradle wrapper script over a global installed gradle. Therefore it's possible to remove the gradle dependecy and simply invoke the build steps with ./gradlew instead of gradle

I'm not sure where I should post this since it involves Awesome WM but...

Using Awesome WM I'm trying to make Chatty always with start in a specific position and size. The position parameters are working as intended, but Chatty doesn't care about the W and H dimensions, it always start with the last dimensions bypassing the ones I putted in the rc.lua

PD: One weird thing is that every time I'm changing the window size it also moves, always in a bottom right direction. This is annoying but not a problem, I'm mentioning this just in case it is related to the possible issue.

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).

i am just a noob, but why do the package need gradle now and why the PKGBUILD fails? Isn't Chatty just a .jar file? Simply pasting over the old .jar is not an option?

Freso: please commit this patch to fix the path issue Stebs mentioned.

https://gitlab.com/morningpee/chatty/commit/ba467a95.patch

Checksum of chatty-0.9.1.tar.gz is wrong. After manually correcting this, install fails with: /home/user/.cache/pacaur/chatty/PKGBUILD: line24: cd: chatty-0.9.1: file or folder not found

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.

Remove the disable_version_check.patch please.

Not going to happen. If the package is outdated (like now), the version check will do nothing towards updating it, other than be in your way while you're running the program. You can install the upstream version in your $HOME if you wish to do that rather than using your package manager to install it system-wide. The changes from chatty 0.8 to 0.9 are too many that updating the PKGBUILD is as easy as updating the $pkgver, which is why it's taking a while.

Remove the disable_version_check.patch please.

I was using this for months without realizing it is an old version. Wouldn't display FFZ emotes anymore since a couple of weeks and I tried to find the cause.

I'm cleaning up the PKGBUILD a bit now, before updating to 0.9.1, but none of the patches from the current PKGBUILD seem to apply outright and 0.9.1 doesn't seem to build without the patches either. I need to look into it some more and probably switch to using the tools used by upstream (ie., gradle).

If anyone wants to discuss how to handle the package going forward, please feel free to contact me.