Package Details: jre 14-1

Git Clone URL: (read-only, click to copy)
Package Base: jre
Description: Oracle Java Runtime Environment
Upstream URL:
Keywords: java-runtime java-runtime-headless java-runtime-headless-jre java-runtime-jre
Licenses: custom
Provides: java-runtime=14, java-runtime-headless=14, java-runtime-headless-jre=14, java-runtime-jre=14
Submitter: td123
Maintainer: dbermond
Last Packager: dbermond
Votes: 603
Popularity: 3.30
First Submitted: 2011-08-27 17:57
Last Updated: 2020-03-19 22:20

Required by (1000)

Sources (1)

Pinned Comments

dbermond commented on 2019-03-29 01:05

@archer_linux Build jre normally with makepkg, then build jdk with makepkg -d, and then install both with pacman -U. Or you can build each one in a chroot and then install both with pacman -U.

Latest Comments

1 2 3 4 5 6 ... Next › Last »

dbermond commented on 2020-03-20 17:14

@hugegameartgd jre does not need to be removed for upgrading. Please read the pinned comment.

hugegameartgd commented on 2020-03-20 14:07

jdk needs to be removed and installed again when upgrading because of jre<14 and jre>=15 dependency of jdk.

cuevaskoch commented on 2019-09-27 18:03

Here's the script I used for updating this on my various workstations, in case it helps anybody else.

cd $YAY_CACHE/jre
git latest
cd $YAY_CACHE/jdk
git latest
makepkg -d
sudo pacman -U ./jdk/jdk-13-2-x86_64.pkg.tar.xz ./jre/jre-13-2-x86_64.pkg.tar.xz

MrArgoNavis commented on 2019-09-22 05:59

I think that there shouldn't be that kind of version constraint.

With every single install, I am forced to uninstall previous version of Java 8+ (such as Java 10, 11, 12...) but as far as I can tell, Arch is perfectly capable of handling multiple versions of Java in parallel.

dbermond commented on 2019-09-19 20:27

@xuanruiqi @zor1984qq @cytodev @zrhoffman Upstream changed the source file without notice. Checksum of the current source file is now updated.

cytodev commented on 2019-09-19 18:01

Heads up to everyone trying to upgrade the package; the PKGBUILD contains an invalid SHA256 checksum. The correct one can be found here:

zrhoffman commented on 2019-09-19 15:04

jdk-13_linux-x64_bin.tar.gz has a SHA-256 of 095fe9ee73bfa8d594b6bf63ae8c750144670a676ba4331ffd2d06b5ae4d5af1.

[zrhoffman@computer jre]$ makepkg
==> Making package: jre 13-1 (Thu 19 Sep 2019 09:58:57 AM CDT)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Found jdk-13_linux-x64_bin.tar.gz
==> Validating source files with sha256sums...
    jdk-13_linux-x64_bin.tar.gz ... FAILED
==> ERROR: One or more files did not pass the validity check!

zor1984qq commented on 2019-09-19 09:03

Yes. How to fix checksum problem? Well I just enabled editing in yay AUR wrapper and edit sha256 checksumm to 095fe9ee73bfa8d594b6bf63ae8c750144670a676ba4331ffd2d06b5ae4d5af1

to enable editing in yay:

Yay is not asking me to edit PKGBUILDS, and I don't like the diff menu! What can I do?

yay --editmenu --nodiffmenu --save

Thats it. You can calculate sha256checksum with the same name following utility if it changes once more.

And archlinux-java status or archlinux-java get to check it. I have defaulted to 13 after package installation.

xuanruiqi commented on 2019-09-19 04:15

The checksum seems out of date?

dbermond commented on 2019-04-19 15:35

Package updated guys.