在错误目录中查找Java的流浪汉

在错误目录中查找Java的流浪汉,java,macos,vagrant,vagrantfile,Java,Macos,Vagrant,Vagrantfile,我正在使用Vagrant运行VM。当我尝试启动(配置)虚拟机时,它不断给我以下错误: ==> default: The following packages have unmet dependencies: ==> default: openjdk-8-jdk : Depends: openjdk-8-jre (= 8u141-b15-2~14.04) but it is not going to be installed ==> default:

我正在使用Vagrant运行VM。当我尝试启动(配置)虚拟机时,它不断给我以下错误:

==> default: The following packages have unmet dependencies:
==> default:  openjdk-8-jdk : Depends: openjdk-8-jre (= 8u141-b15-2~14.04) but it is not going to be installed
==> default:                  Depends: openjdk-8-jdk-headless (= 8u141-b15-2~14.04) but it is not going to be installed
==> default: E: Unable to correct problems, you have held broken packages.
==> default: update-java-alternatives: directory does not exist: /usr/lib/jvm/java-1.8.0-openjdk-amd64
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.
这意味着什么,因为我的机器上有Java1.8。正在进行中

/Library/Java/JavaVirtualMachines/jdk1.8.0_91.jdk/Contents/Home
我在terminal$
/usr/libexec/java_home-v1.8


如何修复此问题?

问题不是因为它在错误的目录中查找。Vagrant正在尝试安装OpenJdk8,但由于某些原因,它无法安装openjdk依赖项(apt get问题)。我之所以知道这一点,是因为我们两小时前就开始遇到相同的问题。

在AWS上使用CodeBuild运行自动生成时,我们遇到了完全相同的问题:

The following packages have unmet dependencies:
openjdk-8-jdk : Depends: openjdk-8-jre (= 8u141-b15-2~14.04) but it is not going to be installed
Depends: openjdk-8-jdk-headless (= 8u141-b15-2~14.04) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
这是我们正在运行的buildspec.yml中的一个片段:

  - apt-get update
  - apt-get -y install software-properties-common
  - apt-get update
  - add-apt-repository -y ppa:openjdk-r/ppa
  - apt-get update
  - apt-get -y install openjdk-8-jdk

现在一切正常。我猜构建是自动推送的,需要一些时间才能完成。现在构建完成了,一切都恢复了正常

几小时前这里也发生了同样的事情<代码>apt get install-y——强制是openjdk-8-jdk在我的2个Ubuntu 14.04设备上产生了完全相同的错误。我要说的是,<代码> APT获得来修复它。同样的问题对我自己来说,看起来包在中间。事实上,新的amd64版本刚刚开始,看起来“卡住了”。希望这很快就能准备好,一些构建似乎需要几个小时!更新:新版本已经推出,一切正常