Yeah, sorry, the openjdk situation sucks. It's an "extra" package, which means the maintainer is a community member rather than being part of the Arch core grou

Yeah, sorry, the openjdk situation sucks. It's an "extra" package, which means the maintainer is a community member rather than being part of the Arch core group. The nice thing about Arch packages, though, is that they're basically just bash scripts. And if all you need is a simple version bump, it's usually quite easy: download the package tarball from [0] and change [1] to the version you want, then do a `makepkg -s` in the directory of the package. It will build the package in a (usually reproducible) chroot. If it builds without errors, then you'll end up with a tarball that you can `pacman -U ${pkg}.tar.zst` to install the produced files. If you need help, makepkg documentation on the wiki[2] is pretty great. And don't forget to send a patch to arch-dev-public[3] and CC the maintainer. At the very least, it'll kick off a discussion that will get the package updated. Rolling your own packages is easy in contrast to, say, Red Hat - where compiling an RPM is easy if you've done it a bunch, but really difficult to get bootstrapped on. [0]: https://archlinux.org/packages/extra/x86_64/jdk-openjdk/ https://archlinux.org/packages/extra/x86_64/jdk-openjdk/ [1]: https://github.com/archlinux/svntogit-packages/blob/packages/java-openjdk/trunk/PKGBUILD#L8 https://github.com/archlinux/svntogit-packages/blob/packages... [2]: https://wiki.archlinux.org/title/Makepkg https://wiki.archlinux.org/title/Makepkg [3]: https://lists.archlinux.org/listinfo/arch-dev-public https://lists.archlinux.org/listinfo/arch-dev-public