If there's something I can help with (especially the first issue seems
trivial to fix), I would gladly do. Just please point me to the
"regular" way of doing that.
Yea, regarding 1, that would be great, if you can send a pull request that
includes the new locations that would be great. Can you also install Java 7
on 12.04 while you are at it and see if its path has changed as well? Just
send a pull request would be happy to get it in.
If there's something I can help with (especially the first issue seems
trivial to fix), I would gladly do. Just please point me to the
"regular" way of doing that.
I have just done a setup on Ubuntu 12.04 and did not run into issues. I
suspect the problem is that Ubuntu does not come with Java anymore because
of Oracle policies.
I've sent the pull request. I hope it's allright, because it's my
first
regarding the errors and warnings of lintian, is there something I
can help with?
@Jordi: yes, I saw that Ubuntu doesn't come with Java, but the ES
debian package has a dependency on openjdk-6-jre-headless, so it
should work out of the box. The problem is that the path has changed
from 11.10.
If you didn't experience this issue (eg: ES started without having
Java installed before), then maybe this only happens on 64-bit
installations? Or did you have JAVA_HOME set already?
I have just done a setup on Ubuntu 12.04 and did not run into issues. I
suspect the problem is that Ubuntu does not come with Java anymore because
of Oracle policies.
Usinghttps://github.com/flexiondotorg/oab-java6to install the java
package worked well for me, and the latest ES deb installed/runs smoothly.
On Wednesday, May 9, 2012 3:18:45 PM UTC+2, Radu Gheorghe wrote:
@Jordi: yes, I saw that Ubuntu doesn't come with Java, but the ES
debian package has a dependency on openjdk-6-jre-headless, so it
should work out of the box. The problem is that the path has changed
from 11.10.
If you didn't experience this issue (eg: ES started without having
Java installed before), then maybe this only happens on 64-bit
installations? Or did you have JAVA_HOME set already?
I had JAVA_HOME set I guess since I installed the sun-java6-jre package
before the ES one. I'm on 64bit too by the way.
Maybe we should remove the dep on: openjdk-6-jre-headless | sun-java6-jre?
As they seem to change names, and just require people to install the JDK
before?
On Wed, May 9, 2012 at 4:56 PM, Jordi Boggiano j.boggiano@seld.be wrote:
On Wednesday, May 9, 2012 3:18:45 PM UTC+2, Radu Gheorghe wrote:
@Jordi: yes, I saw that Ubuntu doesn't come with Java, but the ES
debian package has a dependency on openjdk-6-jre-headless, so it
should work out of the box. The problem is that the path has changed
from 11.10.
If you didn't experience this issue (eg: ES started without having
Java installed before), then maybe this only happens on 64-bit
installations? Or did you have JAVA_HOME set already?
I had JAVA_HOME set I guess since I installed the sun-java6-jre package
before the ES one. I'm on 64bit too by the way.
Maybe we should remove the dep on: openjdk-6-jre-headless | sun-java6-jre?
As they seem to change names, and just require people to install the JDK
before?
On Wed, May 9, 2012 at 4:56 PM, Jordi Boggiano j.boggi...@seld.be wrote:
On Wednesday, May 9, 2012 3:18:45 PM UTC+2, Radu Gheorghe wrote:
@Jordi: yes, I saw that Ubuntu doesn't come with Java, but the ES
debian package has a dependency on openjdk-6-jre-headless, so it
should work out of the box. The problem is that the path has changed
from 11.10.
If you didn't experience this issue (eg: ES started without having
Java installed before), then maybe this only happens on 64-bit
installations? Or did you have JAVA_HOME set already?
I had JAVA_HOME set I guess since I installed the sun-java6-jre package
before the ES one. I'm on 64bit too by the way.
Maybe we should remove the dep on: openjdk-6-jre-headless |
sun-java6-jre? As they seem to change names, and just require people to
install the JDK before?
I think the best way would be to add a dependency on java-runtime,
because that is provided by all the java/openjdk packages I've checked.
Then if nothing is installed it will install the system default, but if
you have something already it should use it happily.
Where have you seen java-runtime? I missed that I think... . I added
dependency on openjdk-7 first, and then 6 later, one of the main problems
we have is that the openjdk 6 version is really old...
On Thu, May 10, 2012 at 10:47 AM, Jordi Boggiano j.boggiano@seld.be wrote:
On 09.05.2012 21:58, Shay Banon wrote:
Maybe we should remove the dep on: openjdk-6-jre-headless |
sun-java6-jre? As they seem to change names, and just require people to
install the JDK before?
I think the best way would be to add a dependency on java-runtime,
because that is provided by all the java/openjdk packages I've checked.
Then if nothing is installed it will install the system default, but if
you have something already it should use it happily.
Where have you seen java-runtime? I missed that I think... . I added
dependency on openjdk-7 first, and then 6 later, one of the main
problems we have is that the openjdk 6 version is really old...
java-runtime is not a real package, it's just a virtual package, if you
require it it should select & view a package that provides it as valid.
Both those package list java-runtime as provided:
On Fri, May 11, 2012 at 10:29 AM, Jordi Boggiano j.boggiano@seld.be wrote:
On 10.05.2012 22:24, Shay Banon wrote:
Where have you seen java-runtime? I missed that I think... . I added
dependency on openjdk-7 first, and then 6 later, one of the main
problems we have is that the openjdk 6 version is really old...
java-runtime is not a real package, it's just a virtual package, if you
require it it should select & view a package that provides it as valid.
Both those package list java-runtime as provided:
I believe it uses default-jre which is a virtual package they can point
to anything that's deemed the best choice at the time. At the moment it
seems to be openjdk6 http://packages.ubuntu.com/precise/default-jre
In any case, it gives the choice to the end user to install whatever
java they want before installing your package. While if you require one
package explicitly, you take this away.
I believe it uses default-jre which is a virtual package they can point
to anything that's deemed the best choice at the time. At the moment it
seems to be openjdk6 http://packages.ubuntu.com/precise/default-jre
In any case, it gives the choice to the end user to install whatever
java they want before installing your package. While if you require one
package explicitly, you take this away.
I know this message wasn't for me, but I have a related question.
I'd like to contribute with fixes for the .deb package (see issue 2
from the original post), but I don't know how to do it (as in "where
to submit patches"). I've seen on github at Elasticsearch that
the .deb packages was "moved to maven" or something. Even with
Google's help, I couldn't find how to contribute to the
Elasticsearch .deb package.
Excuse my noobness, do you have any hints? I'd really love to help.
I believe it uses default-jre which is a virtual package they can point
to anything that's deemed the best choice at the time. At the moment it
seems to be openjdk6http://packages.ubuntu.com/precise/default-jre
In any case, it gives the choice to the end user to install whatever
java they want before installing your package. While if you require one
package explicitly, you take this away.
I know this message wasn't for me, but I have a related question.
I'd like to contribute with fixes for the .deb package (see issue 2
from the original post), but I don't know how to do it (as in "where
to submit patches"). I've seen on github at Elasticsearch that
the .deb packages was "moved to maven" or something. Even with
Google's help, I couldn't find how to contribute to the
Elasticsearch .deb package.
Excuse my noobness, do you have any hints? I'd really love to help.
I believe it uses default-jre which is a virtual package they can point
to anything that's deemed the best choice at the time. At the moment it
seems to be openjdk6http://packages.ubuntu.com/precise/default-jre
In any case, it gives the choice to the end user to install whatever
java they want before installing your package. While if you require one
package explicitly, you take this away.
I know this message wasn't for me, but I have a related question.
I'd like to contribute with fixes for the .deb package (see issue 2
from the original post), but I don't know how to do it (as in "where
to submit patches"). I've seen on github at Elasticsearch that
the .deb packages was "moved to maven" or something. Even with
Google's help, I couldn't find how to contribute to the
Elasticsearch .deb package.
Excuse my noobness, do you have any hints? I'd really love to help.
I believe it uses default-jre which is a virtual package they can point
to anything that's deemed the best choice at the time. At the moment it
seems to be openjdk6http://packages.ubuntu.com/precise/default-jre
In any case, it gives the choice to the end user to install whatever
java they want before installing your package. While if you require one
package explicitly, you take this away.
Just ran into the same issue... Had run aptitude install openjdk-6- jre-headless on a plain, 32 bit Ubuntu 12.04 LTS installation before
installing the elasticsearch deb package. To fix this, I had to create
this link:
Just ran into the same issue... Had run aptitude install openjdk-6- jre-headless on a plain, 32 bit Ubuntu 12.04 LTS installation before
installing the elasticsearch deb package. To fix this, I had to create
this link:
Its actually using $JAVA_HOME by default in the bin/elasticsearch script. The deb init.d script tries to find it automatically, based on a list of common locations, and if its not found, it will use the regular $JAVA_HOME one.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.