You are not logged in.

#1 2014-08-18 18:56:37

RazZziel
Member
From: Spain
Registered: 2007-07-13
Posts: 36

Java broken after upgrade

After last upgrade, I stopped having a "java" command in my $PATH, besides having jre7-openjdk and jdk7-openjdk installed and working daily.

I uninstalled them, tried to reinstall them, but they error out like this:

08:54:57 ~$ yaourt -S jre7-openjdk jdk7-openjdk
resolving dependencies...
looking for inter-conflicts...

Packages (2): jdk7-openjdk-7.u65_2.5.1-8  jre7-openjdk-7.u65_2.5.1-8

Total Installed Size:   19.77 MiB

:: Proceed with installation? [Y/n] 
(2/2) checking keys in keyring                                                                          [-------------------------------------------------------------] 100%
(2/2) checking package integrity                                                                        [-------------------------------------------------------------] 100%
(2/2) loading package files                                                                             [-------------------------------------------------------------] 100%
(2/2) checking for file conflicts                                                                       [-------------------------------------------------------------] 100%
(2/2) checking available disk space                                                                     [-------------------------------------------------------------] 100%
(1/2) installing jre7-openjdk                                                                           [-------------------------------------------------------------] 100%
when you use a non-reparenting window manager
set _JAVA_AWT_WM_NONREPARENTING=1 in
/etc/profile.d/jre.sh
/tmp/alpm_V6wx1c/.INSTALL: line 11: /usr/bin/archlinux-java: No such file or directory
/tmp/alpm_V6wx1c/.INSTALL: line 13: /usr/bin/archlinux-java: No such file or directory
error: command failed to execute correctly
Optional dependencies for jre7-openjdk
    icedtea-web-java7: web browser plugin + Java Web Start [installed]
    alsa-lib: for basic sound support [installed]
    giflib: for gif format support [installed]
    libpulse: for advanced sound support [installed]
    gtk2: for the Gtk+ look and feel - desktop usage [installed]
    libxtst: linked in xawt/libmawt.so - desktop usage [installed]
(2/2) installing jdk7-openjdk                                                                           [-------------------------------------------------------------] 100%
/tmp/alpm_XKwvKL/.INSTALL: line 4: /usr/bin/archlinux-java: No such file or directory
/tmp/alpm_XKwvKL/.INSTALL: line 6: /usr/bin/archlinux-java: No such file or directory
08:55:07 ~$ java
bash: java: command not found

What's this "archlinux-java" script, and where do I get it?

Offline

#2 2014-08-18 19:44:15

Lone_Wolf
Administrator
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 15,089

Re: Java broken after upgrade

it's in java-common package, which should be pulled in automatically.

Try adding jre7-openjdk-headless to the install command.


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

Online

#3 2014-08-18 22:53:56

RazZziel
Member
From: Spain
Registered: 2007-07-13
Posts: 36

Re: Java broken after upgrade

Didn't try re-installing jre7-openjdk-headless, but indeed re-installing java-common did work

Offline

#4 2014-08-19 10:45:37

Wikimig
Developer
From: France
Registered: 2004-12-10
Posts: 77
Website

Re: Java broken after upgrade

The pacman output you provide shows java-common was not installed when you issued "yaourt -S jre7-openjdk jdk7-openjdk" (because 'archlinux-java' is provided by this package). To figure out why it was not installed back then we would need pacman's output of the previous upgrades (can be found in /var/log/pacman.log)

Offline

#5 2014-08-19 14:03:13

RazZziel
Member
From: Spain
Registered: 2007-07-13
Posts: 36

Re: Java broken after upgrade

Indeed looks like it was never installed:

03:49:19 ~$ cat /var/log/pacman.log |grep java-common
13214:[2014-08-19 00:52] [PACMAN] Running 'pacman --color auto -S --noconfirm extra/java-common'
13220:[2014-08-19 00:52] [PACMAN] installed java-common (1-3)

Last 5000 lines: http://pastebin.com/raw.php?i=8G0TgAWq

Offline

#6 2014-08-19 14:13:37

Wikimig
Developer
From: France
Registered: 2004-12-10
Posts: 77
Website

Re: Java broken after upgrade

[2014-08-17 22:46] [PACMAN] Running 'pacman -Sudd'                                                  
$ man pacman
[…]
       -d, --nodeps
           Skips dependency version checks. Package names are still checked. Normally, pacman will always check a
           package’s dependency fields to ensure that all dependencies are installed and there are no package
           conflicts in the system. Specify this option twice to skip all dependency checks.
[…]

Offline

#7 2014-08-19 14:34:23

RazZziel
Member
From: Spain
Registered: 2007-07-13
Posts: 36

Re: Java broken after upgrade

Hm, as far as I know, -dd only avoids dependency conflict errors, which I need to use every time the nvidia driver updates, because I use extra/nvidia-utils + aur/nvidia-dkms (and I need nvidia-dkms or aur/nvidia-pae, because I use linux-pae/linux-pae), so I either uninstall and re-install nvidia-dkms before the update, or update with -dd so nvidia-dkms won't complain about a temporal mismatch in nvidia-utils (temporal, because both packages are usually updated at the same time)

Long story short, I'd assume -dd to avoid only dependency conflict errors, not to avoid new dependencies from getting installed. When I manually installed nvidia-common, I was not warned about any dependency conflict nor package substitution.

But looks like I'm wrong, so let this thread serve as a public lesson for the rest of the noobs!

Offline

#8 2014-08-20 08:51:23

Wikimig
Developer
From: France
Registered: 2004-12-10
Posts: 77
Website

Re: Java broken after upgrade

RazZziel wrote:

Hm, as far as I know, -dd only avoids dependency conflict errors

Well, read again what the man excerpt says:

Specify this option twice to skip all dependency checks.

Anyway: 'pacman -Sdd <ONE_PKG>' is all right if you know what you are doing but 'pacman -Sudd' is a very bad idea.

Offline

Board footer

Powered by FluxBB