I think that there is a problem with the licenses. This caused me to have file conflicts when updating this package.
It looks like license files are both installed in /usr/share/licenses/jdk and /usr/share/licenses/java8-jdk but only the files in /usr/share/licenses/java8-jdk are tracked.
Here's what I have:
[boris@boris-desktop licenses]$ pacaur -Ql jdk | grep licenses 0
jdk /usr/share/licenses/
jdk /usr/share/licenses/java8-jdk/
jdk /usr/share/licenses/java8-jdk/COPYRIGHT
jdk /usr/share/licenses/java8-jdk/LICENSE
jdk /usr/share/licenses/java8-jdk/THIRDPARTYLICENSEREADME-JAVAFX.txt
jdk /usr/share/licenses/java8-jdk/THIRDPARTYLICENSEREADME.txt
jdk /usr/share/licenses/jdk
[boris@boris-desktop licenses]$ ls /usr/share/licenses/jdk 0
COPYRIGHT LICENSE THIRDPARTYLICENSEREADME-JAVAFX.txt THIRDPARTYLICENSEREADME.txt
Search Criteria
Package Details: jre 23.0.1-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/jdk.git (read-only, click to copy) |
---|---|
Package Base: | jdk |
Description: | Oracle Java Runtime Environment |
Upstream URL: | https://www.oracle.com/java/ |
Licenses: | LicenseRef-custom |
Conflicts: | jdk |
Provides: | java-runtime, java-runtime-headless, java-runtime-headless-jdk, java-runtime-jdk23, jre23-jdk, jre23-jdk-headless |
Submitter: | td123 |
Maintainer: | dbermond |
Last Packager: | dbermond |
Votes: | 1086 |
Popularity: | 0.119396 |
First Submitted: | 2011-08-27 17:56 (UTC) |
Last Updated: | 2024-11-16 14:08 (UTC) |
Dependencies (12)
- ca-certificates-utils
- freetype2 (freetype2-qdoledAUR, freetype2-macosAUR, freetype2-gitAUR)
- java-runtime-common
- libx11 (libx11-gitAUR)
- libxext (libxext-gitAUR)
- libxi (libxi-gitAUR)
- libxrender
- libxtst
- python-html2text (make)
- alsa-lib (optional) – for basic sound support
- gtk2 (gtk2-maemoAUR, gtk2-patched-filechooser-icon-viewAUR) (optional) – for the Gtk+ 2 look and feel - desktop usage
- gtk3 (gtk3-no_deadkeys_underlineAUR, gtk3-classicAUR, gtk3-classic-xfceAUR, gtk3-patched-filechooser-icon-viewAUR) (optional) – for the Gtk+ 3 look and feel - desktop usage
Required by (1730)
- 2009scape (requires java-runtime)
- 2009scape-git (requires java-runtime)
- 2p-kt (requires java-runtime)
- abchr (requires java-runtime)
- abcl-git (requires java-runtime)
- abdownloadmanager-bin (requires java-runtime)
- acodec-bin (requires java-runtime)
- acronis-cyber-protect-bin (requires java-runtime)
- activemq (requires java-runtime)
- aechoterm-bin (requires java-runtime)
- ahmyth-bin (requires java-runtime)
- aio-remote (requires java-runtime)
- airsonic (requires java-runtime-headless)
- airsonic-advanced-bin (requires java-runtime-headless)
- airsonic-advanced-git (requires java-runtime-headless)
- airsonic-git (requires java-runtime-headless)
- aladin (requires java-runtime)
- alchemist (requires java-runtime)
- alda (requires java-runtime)
- alda-bin (requires java-runtime)
- Show 1710 more...
Sources (9)
Latest Comments
« First ‹ Previous 1 .. 29 30 31 32 33 34 35 36 37 38 39 .. 81 Next › Last »
dotboris commented on 2014-09-09 19:01 (UTC)
Det commented on 2014-09-09 16:10 (UTC)
Well, because the path for OpenJDK was chosen as '/usr/lib/jvm/java-8-openjdk' (java-<major version>-<project name>), I simply preferred making mine 'java-8-jdk' (not 'java-8-oracle'). The actual name of the project is 'JDK', not 'Oracle JDK', and it also creates consistency with the man pages:
$ man java-openjdk8
$ man java-jdk8
Instead of:
$ man java-openjdk8
$ man java8-oracle
Which also made me change the following dependencies:
- java-runtime-headless-oracle
- java-runtime-oracle
- java-web-start-oracle
- java-environment-oracle
to:
- java-runtime-headless-jre
- java-runtime-jre
- java-web-start-jre
- java-environment-jdk (a JDK component)
Even if all of those end up being '-jdk' for simplicity, I'd still prefer that setup, than the whole excessive "Oracle" tagging.
> By the way, shouldn't jdk-devel and jre-devel also be changed to make usage of the java-common package?
I suppose you didn't have a look. They both do.
russo79 commented on 2014-09-09 10:41 (UTC)
@Jristz
Nowhere in the Java Package Guidelines [1], it is specified that the package JREs/JDKs must follow a given name convention.
Also "the guy in jdk7" as you named it just said that he'd *like* to follow the convention used by the packages provided officially :)
(which seams to be "<jdk/jre><majorversion>-<vendor>").
@Det
Although you are free to follow the naming convention you want (since officially there is none), it would be nice for all the JDKs and JREs provided both in AUR and on the official repositories to follow the same naming convention.
What do you think about renaming your jdk and jre packages to jdk8-oracle and jre8-oracle respectively?
To ease the transition you could even add a "provides" entry in your PKGBUILDs so that packages depending on this one can keep working without having their PKGBUILDs modified.
I know this is a bit PITA, but what do you think?
By the way, shouldn't jdk-devel and jre-devel also be changed to make usage of the java-common package?
[1] https://wiki.archlinux.org/index.php/Java_Package_Guidelines
<deleted-account> commented on 2014-09-08 21:00 (UTC)
Is not the new Java guideliness say that this package need to be namd jdk-oracle (and the dev: jdk-devel-oracle)?
The guy in jdk7 is claiming that and the request on jdk7-oracle -> jdk7 claim that the new scheme name is jdk7-oracle and this package need to be changed too.
stativ commented on 2014-09-06 21:06 (UTC)
kkl2401: fair enough.
As for the missing symlink problem I'm having, you can use $SRCDEST instead of $srcdir. It's not a nice solution, but it's guaranteed to contain the downloaded sources.
Regarding the wrong ownership: there's a typo in the PKGBUILD - you are missing "g" in "$pkgdir" on the line where you call chown.
leonardof commented on 2014-09-05 04:09 (UTC)
The package update pulled java-common, which conflicted with existing /etc/profile.d/jre.{,c}sh. Removing the files made it work.
Det commented on 2014-09-04 10:40 (UTC)
You people.
@klingt.net, yes, as I already told you, the old $JAVA_HOME from /etc/profile.d/jdk.sh (without rebooting) was the problem.
@lots0logs, yes, as I already told you, the upgrade process is:
1) # rm -r /usr/share/licenses/jdk/
2) install 8u20-2
klingt.net commented on 2014-09-04 09:13 (UTC)
@simonorono
I switched back to jdk8-openjdk from extra. But I think the problem was a wrong $JAVA_HOME, the old value was /opt/java and the new one is /usr/lib/jvm/default. This was changed due to the java-common update and maybe I overlooked the message to logout/login, so the old value was still present.
lots0logs commented on 2014-09-04 03:25 (UTC)
I got this error when I attempted to update:
error: failed to commit transaction (conflicting files)
unable to --force directory-file conflicts
jdk: /usr/share/licenses/jdk exists in filesystem
Errors occurred, no packages were upgraded.
For a quick fix I edited the PKGBUILD by removing the line that attempts to create a symlink over the /usr/share/licenses/jdk directory (that already existed on my system.)
Det commented on 2014-09-03 20:35 (UTC)
It's automatically set by /etc/profile.d/jdk.sh or /etc/profile.d/jre.sh (to let apps know where Java is located).
/etc/profile.d/jre.sh is now owned by 'java-common' and shouldn't be installed by Java packages anymore.
Pinned Comments
dbermond commented on 2024-03-19 19:54 (UTC)
As was made with the java packages in the official repositories, jdk now provides the jre alongside it, and both packages conflict with each other. During the package upgrade to version 22, act accordingly to your needs. For example, if you have both jdk and jre installed, only jdk will be sufficient, as it now also contains the runtime environment, and jre can be uninstalled. If you have only jre installed, no action is required.