ELK source tar balls


(Tomasz Kloczko) #1

Hi,

On http://www.elasticsearch.org/overview/elkdownloads/ I see only binary
packages and tar balls with jar files.

Q: Where I can find source code ELK tar balls and for example rpm spec
files used on build noarch.rpm packages?

Tomasz

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/efaf1648-553f-4246-becb-d39cc82604b0%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


(Mark Walkom) #2

There are rpm/deb repos


Otherwise you can find the sources on github.

Regards,
Mark Walkom

Infrastructure Engineer
Campaign Monitor
email: markw@campaignmonitor.com
web: www.campaignmonitor.com

On 5 March 2014 14:53, Tomasz Kloczko kloczko.tomasz@gmail.com wrote:

Hi,

On http://www.elasticsearch.org/overview/elkdownloads/ I see only binary
packages and tar balls with jar files.

Q: Where I can find source code ELK tar balls and for example rpm spec
files used on build noarch.rpm packages?

Tomasz

--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/efaf1648-553f-4246-becb-d39cc82604b0%40googlegroups.comhttps://groups.google.com/d/msgid/elasticsearch/efaf1648-553f-4246-becb-d39cc82604b0%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAEM624bC0FZdqEeV1%3DyhftbN%2BKtY83Lg3pRTUFMFhyMV1zWEjg%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.


(Tomasz Kloczko) #3

On Wednesday, 5 March 2014 03:58:41 UTC, Mark Walkom wrote:

There are rpm/deb repos
http://www.elasticsearch.org/blog/apt-and-yum-repositories/
Otherwise you can find the sources on github

rpm packages cannot be build from github repo so this is why I'm asking
where are source tar balls.
Someone created these tar balls before rpm packages have been created ..

In above yum repo there is no any traces of source rpm packages.
In github repo there is no spec files which can be used on build rpm
packages.
(If in source tar ball is .spec file such tar ball can be used to
build rpm package by for example "rpmbuild -ta -.tar.gz")

Don't get me wrong but lack of officially released tar balls, files used on
build binary packages is some kind of contradiction to claim "this project
is open source" :wink:
Someone build rpm packages available on download page. Question is only who
did this and why these source packages are not published on official pages?
:slight_smile:

I'm not paranoid but I don't see reasons why I should trust official rpm
packages specially when I see that official rpm packages are noarch and
some of these packages contains shared object files which never should be
packaged into noarch.rpm packages.

Tomasz

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/df95d569-924b-433c-9295-fd4774bdf589%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


(David Pilato) #4

Are you looking for this? https://github.com/elasticsearch/elasticsearch/blob/master/pom.xml#L779

--
David :wink:
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 5 mars 2014 à 05:42, Tomasz Kloczko kloczko.tomasz@gmail.com a écrit :

On Wednesday, 5 March 2014 03:58:41 UTC, Mark Walkom wrote:

There are rpm/deb repos http://www.elasticsearch.org/blog/apt-and-yum-repositories/
Otherwise you can find the sources on github

rpm packages cannot be build from github repo so this is why I'm asking where are source tar balls.
Someone created these tar balls before rpm packages have been created ..

In above yum repo there is no any traces of source rpm packages.
In github repo there is no spec files which can be used on build rpm packages.
(If in source tar ball is .spec file such tar ball can be used to build rpm package by for example "rpmbuild -ta -.tar.gz")

Don't get me wrong but lack of officially released tar balls, files used on build binary packages is some kind of contradiction to claim "this project is open source" :wink:
Someone build rpm packages available on download page. Question is only who did this and why these source packages are not published on official pages? :slight_smile:

I'm not paranoid but I don't see reasons why I should trust official rpm packages specially when I see that official rpm packages are noarch and some of these packages contains shared object files which never should be packaged into noarch.rpm packages.

Tomasz

You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/df95d569-924b-433c-9295-fd4774bdf589%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/442EDC65-6073-48A1-8F9E-2CA6FA22F1CA%40pilato.fr.
For more options, visit https://groups.google.com/groups/opt_out.


(Jörg Prante) #5

Tomasz, Elasticsearch source tarballs are available at github
https://github.com/elasticsearch/elasticsearch/releases and the RPM should
be automatically built, just by issuing the command "mvn install".

For the RPM, I agree with you. I'm also disappointed by the RPM package
offer so far. It seems to me the ES team misunderstands RPM as a solely
binary distribution format, and used a simplified Maven RPM plugin build in
pom.xml.

I have installed a RHEL7 Beta yesterday to start a rebuild of Elasticsearch
with Maven according to Fedora rules
http://fedoraproject.org/wiki/How_to_create_an_RPM_package

This will include src.rpm, spec file, correct target architecture, and
dependencies, like in the Solr RPM at
https://bugzilla.redhat.com/show_bug.cgi?id=1025904

I hope it will be useful.

Jörg

On Wed, Mar 5, 2014 at 5:42 AM, Tomasz Kloczko kloczko.tomasz@gmail.comwrote:

On Wednesday, 5 March 2014 03:58:41 UTC, Mark Walkom wrote:

There are rpm/deb repos http://www.elasticsearch.org/blog/apt-
and-yum-repositories/
Otherwise you can find the sources on github

rpm packages cannot be build from github repo so this is why I'm asking
where are source tar balls.
Someone created these tar balls before rpm packages have been created ..

In above yum repo there is no any traces of source rpm packages.
In github repo there is no spec files which can be used on build rpm
packages.
(If in source tar ball is .spec file such tar ball can be used to
build rpm package by for example "rpmbuild -ta -.tar.gz")

Don't get me wrong but lack of officially released tar balls, files used
on build binary packages is some kind of contradiction to claim "this
project is open source" :wink:
Someone build rpm packages available on download page. Question is only
who did this and why these source packages are not published on official
pages? :slight_smile:

I'm not paranoid but I don't see reasons why I should trust official rpm
packages specially when I see that official rpm packages are noarch and
some of these packages contains shared object files which never should be
packaged into noarch.rpm packages.

Tomasz

--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/df95d569-924b-433c-9295-fd4774bdf589%40googlegroups.comhttps://groups.google.com/d/msgid/elasticsearch/df95d569-924b-433c-9295-fd4774bdf589%40googlegroups.com?utm_medium=email&utm_source=footer
.

For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAKdsXoF2sMOPLVfma%2B35x2ocR7eP%2BR5FGsWjB6nfFGEHfjM0qQ%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.


(Lukáš Vlček) #6

Jörg,

how are you going to approach shaded deps?
Also, it might be interesting to you, RPM for Lucene 4.7 is available in
Fedora (Rawhide) now: https://apps.fedoraproject.org/packages/lucene/ so
you may not need to rebuild it.

Lukas

On Wed, Mar 5, 2014 at 9:15 AM, joergprante@gmail.com <joergprante@gmail.com

wrote:

Tomasz, Elasticsearch source tarballs are available at github
https://github.com/elasticsearch/elasticsearch/releases and the RPM
should be automatically built, just by issuing the command "mvn install".

For the RPM, I agree with you. I'm also disappointed by the RPM package
offer so far. It seems to me the ES team misunderstands RPM as a solely
binary distribution format, and used a simplified Maven RPM plugin build in
pom.xml.

I have installed a RHEL7 Beta yesterday to start a rebuild of
Elasticsearch with Maven according to Fedora rules
http://fedoraproject.org/wiki/How_to_create_an_RPM_package

This will include src.rpm, spec file, correct target architecture, and
dependencies, like in the Solr RPM at
https://bugzilla.redhat.com/show_bug.cgi?id=1025904

I hope it will be useful.

Jörg

On Wed, Mar 5, 2014 at 5:42 AM, Tomasz Kloczko kloczko.tomasz@gmail.comwrote:

On Wednesday, 5 March 2014 03:58:41 UTC, Mark Walkom wrote:

There are rpm/deb repos http://www.elasticsearch.org/blog/apt-
and-yum-repositories/
Otherwise you can find the sources on github

rpm packages cannot be build from github repo so this is why I'm asking
where are source tar balls.
Someone created these tar balls before rpm packages have been created ..

In above yum repo there is no any traces of source rpm packages.
In github repo there is no spec files which can be used on build rpm
packages.
(If in source tar ball is .spec file such tar ball can be used
to build rpm package by for example "rpmbuild -ta
-.tar.gz")

Don't get me wrong but lack of officially released tar balls, files used
on build binary packages is some kind of contradiction to claim "this
project is open source" :wink:
Someone build rpm packages available on download page. Question is only
who did this and why these source packages are not published on official
pages? :slight_smile:

I'm not paranoid but I don't see reasons why I should trust official rpm
packages specially when I see that official rpm packages are noarch and
some of these packages contains shared object files which never should be
packaged into noarch.rpm packages.

Tomasz

--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/df95d569-924b-433c-9295-fd4774bdf589%40googlegroups.comhttps://groups.google.com/d/msgid/elasticsearch/df95d569-924b-433c-9295-fd4774bdf589%40googlegroups.com?utm_medium=email&utm_source=footer
.

For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/CAKdsXoF2sMOPLVfma%2B35x2ocR7eP%2BR5FGsWjB6nfFGEHfjM0qQ%40mail.gmail.comhttps://groups.google.com/d/msgid/elasticsearch/CAKdsXoF2sMOPLVfma%2B35x2ocR7eP%2BR5FGsWjB6nfFGEHfjM0qQ%40mail.gmail.com?utm_medium=email&utm_source=footer
.

For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAO9cvUZyaZt_fqE6P6tjkCjhEQ-OJL%3D-cY0qRaeWafj7z48hLA%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.


(Tomasz Kloczko) #7

On Wednesday, 5 March 2014 08:15:02 UTC, Jörg Prante wrote:

Tomasz, Elasticsearch source tarballs are available at github
https://github.com/elasticsearch/elasticsearch/releases and the RPM
should be automatically built, just by issuing the command "mvn install"

Correct me if I'm wrong. These archives are not official/signed dist files.
These are on-the-fly generated archives from release label. Isn't it?

For the RPM, I agree with you. I'm also disappointed by the RPM package
offer so far. It seems to me the ES team misunderstands RPM as a solely
binary distribution format, and used a simplified Maven RPM plugin build in
pom.xml

I'm really appreciated that someone is trying to help generate regular
packages but current approach seems is waste of time.
Different distributions are using different way of packaging. Sometimes are
using different init scripts templates.
Differences between OSes are even deeper.
For example on creare Solaris (IPS) packages current init scrips used by
pom.xml does not allow use service instances. Solaris service management
consist from two files: SMF service description file and SH backend script
which is completely different than rpm based Linux distributions.

pom.xml file creates package without proper dependencies (for example has
no java package dependency).

Instead storing in elasticsearch git tree shared objects (which is quite
strange) better would be document that this software needs/depends on sigar.

I have installed a RHEL7 Beta yesterday to start a rebuild of Elasticsearch

with Maven according to Fedora rules
http://fedoraproject.org/wiki/How_to_create_an_RPM_package

This will include src.rpm, spec file, correct target architecture, and
dependencies, like in the Solr RPM at
https://bugzilla.redhat.com/show_bug.cgi?id=102590https://bugzilla.redhat.com/show_bug.cgi?id=1025904

Exactly.

On downloading dist tar archive using above release URL is not generated
-.tar.gz file but file with name only (lack of
proper tar.gz ext). So for example these URLs cannot be used in Source:
spec file field.

IMO it would be way better if ELK components will be distributed in real
dist source archives (best with official SHA checksums) and not as a git
substitutes which cannot be used straight (without additional operations)
as input files to create any type of packages.
Best will be if ELK developers will leave packaging layer to people with
proper packaging skills :slight_smile:
All what is needed here it is proper official source tar ball :slight_smile:

I can understand that currently available packages can be used on prepare
some kind of dirty POC but in the same time using such packages in real
production environments in many cases will be completely unacceptable.

Tomasz

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/449ae0d0-f6a1-4bb7-841c-1bbbfdda5321%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


(Jörg Prante) #8

Personally, as long as github is not hijacked, I trust github, so for
myself, I don't worry today about signed sources. Maybe this will change
later, after I catch some malware over corrupted Elasticsearch archives...

If you are after SHA1 signed sources, you know that Maven signs the builds
by default. When the Elasticsearch team releases a new version, they are
mirrored to Maven Central. For example, the 1.0.1 release can be found with
SHA1 and MD5 checksums at

http://search.maven.org/#artifactdetails|org.elasticsearch|elasticsearch|1.0.1|jar

or

http://repo.maven.apache.org/maven2/org/elasticsearch/elasticsearch/1.0.1/

etc.

So the path from the mirror servers to your server can be verified. The
unverified path left is from the Elasticsearch team build server to the
Maven repo. I think, all that is to do is to include the repo checksums in
the release notes at http://www.elasticsearch.org/downloads/

Jörg

On Wed, Mar 5, 2014 at 3:56 PM, Tomasz Kloczko kloczko.tomasz@gmail.comwrote:

All what is needed here it is proper official source tar ball :slight_smile:

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAKdsXoF-oaSEqGHVCkoRkUEyQC10m3myDVFQquGA1susBGzHMA%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.


(Alexander Reelsen) #9

Hey

just FYI: the RPM is not built when running 'mvn install' - the reason for
this is, that it needs the rpm binary on the system, which is not the case
for rpm-based operating sytems (the majority of developer systems
probably). You can explicitely create it by running 'mvn rpm:rpm'

--Alex

On Wed, Mar 5, 2014 at 9:15 AM, joergprante@gmail.com <joergprante@gmail.com

wrote:

Tomasz, Elasticsearch source tarballs are available at github
https://github.com/elasticsearch/elasticsearch/releases and the RPM
should be automatically built, just by issuing the command "mvn install".

For the RPM, I agree with you. I'm also disappointed by the RPM package
offer so far. It seems to me the ES team misunderstands RPM as a solely
binary distribution format, and used a simplified Maven RPM plugin build in
pom.xml.

I have installed a RHEL7 Beta yesterday to start a rebuild of
Elasticsearch with Maven according to Fedora rules
http://fedoraproject.org/wiki/How_to_create_an_RPM_package

This will include src.rpm, spec file, correct target architecture, and
dependencies, like in the Solr RPM at
https://bugzilla.redhat.com/show_bug.cgi?id=1025904

I hope it will be useful.

Jörg

On Wed, Mar 5, 2014 at 5:42 AM, Tomasz Kloczko kloczko.tomasz@gmail.comwrote:

On Wednesday, 5 March 2014 03:58:41 UTC, Mark Walkom wrote:

There are rpm/deb repos http://www.elasticsearch.org/blog/apt-
and-yum-repositories/
Otherwise you can find the sources on github

rpm packages cannot be build from github repo so this is why I'm asking
where are source tar balls.
Someone created these tar balls before rpm packages have been created ..

In above yum repo there is no any traces of source rpm packages.
In github repo there is no spec files which can be used on build rpm
packages.
(If in source tar ball is .spec file such tar ball can be used
to build rpm package by for example "rpmbuild -ta
-.tar.gz")

Don't get me wrong but lack of officially released tar balls, files used
on build binary packages is some kind of contradiction to claim "this
project is open source" :wink:
Someone build rpm packages available on download page. Question is only
who did this and why these source packages are not published on official
pages? :slight_smile:

I'm not paranoid but I don't see reasons why I should trust official rpm
packages specially when I see that official rpm packages are noarch and
some of these packages contains shared object files which never should be
packaged into noarch.rpm packages.

Tomasz

--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/df95d569-924b-433c-9295-fd4774bdf589%40googlegroups.comhttps://groups.google.com/d/msgid/elasticsearch/df95d569-924b-433c-9295-fd4774bdf589%40googlegroups.com?utm_medium=email&utm_source=footer
.

For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/CAKdsXoF2sMOPLVfma%2B35x2ocR7eP%2BR5FGsWjB6nfFGEHfjM0qQ%40mail.gmail.comhttps://groups.google.com/d/msgid/elasticsearch/CAKdsXoF2sMOPLVfma%2B35x2ocR7eP%2BR5FGsWjB6nfFGEHfjM0qQ%40mail.gmail.com?utm_medium=email&utm_source=footer
.

For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAGCwEM_4tpwUbGV2hZHm_rUwOC9xOiKeaoEVN3cPE-sqx5aYJQ%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.


(Jörg Prante) #10

I hope the shaded deps will work just by using the maven shade plugin.
AFAIK Maven itself uses shaded deps.

http://ftp.redhat.com/redhat/rhel/beta/7/x86_64/os/Packages/maven-shade-plugin-2.0-5.el7.noarch.rpm

It could be that traveling down the path with RHEL7 Beta will be dead
ended, then I'd switch to Fedora 20 / Fedora Rawhide / Fedora EPEL 7 /
whatever.

Jörg

On Wed, Mar 5, 2014 at 1:27 PM, Lukáš Vlček lukas.vlcek@gmail.com wrote:

Jörg,

how are you going to approach shaded deps?
Also, it might be interesting to you, RPM for Lucene 4.7 is available in
Fedora (Rawhide) now: https://apps.fedoraproject.org/packages/lucene/ so
you may not need to rebuild it.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAKdsXoF5og0pim%2ByFFp%2BAmyavkCpj9gE860GMEHYPWnU4burrg%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.


(Lukáš Vlček) #11

Jörg

my point about shaded deps is that if you want to deliver crystal clear RPM
from Fedora POW then you need to build source RPM first and then noarch
RPM. Which means that you would first need to have all the shaded deps as a
separate RPMs available in some RPM repo (and if they have transitive deps
then these need to be also build as a standalone RPMs as well ... etc). At
least that is how I understand this and it can be a lot of work if you want
to support it long term and according to all Linux packaging standards.

Regards,
Lukáš

On Thu, Mar 6, 2014 at 10:29 AM, joergprante@gmail.com <
joergprante@gmail.com> wrote:

I hope the shaded deps will work just by using the maven shade plugin.
AFAIK Maven itself uses shaded deps.

http://ftp.redhat.com/redhat/rhel/beta/7/x86_64/os/Packages/maven-shade-plugin-2.0-5.el7.noarch.rpm

It could be that traveling down the path with RHEL7 Beta will be dead
ended, then I'd switch to Fedora 20 / Fedora Rawhide / Fedora EPEL 7 /
whatever.

Jörg

On Wed, Mar 5, 2014 at 1:27 PM, Lukáš Vlček lukas.vlcek@gmail.com wrote:

Jörg,

how are you going to approach shaded deps?
Also, it might be interesting to you, RPM for Lucene 4.7 is available in
Fedora (Rawhide) now: https://apps.fedoraproject.org/packages/lucene/ so
you may not need to rebuild it.

--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/CAKdsXoF5og0pim%2ByFFp%2BAmyavkCpj9gE860GMEHYPWnU4burrg%40mail.gmail.comhttps://groups.google.com/d/msgid/elasticsearch/CAKdsXoF5og0pim%2ByFFp%2BAmyavkCpj9gE860GMEHYPWnU4burrg%40mail.gmail.com?utm_medium=email&utm_source=footer
.

For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAO9cvUbbymek%3DCTtoSqW4J45xpSc6NAWuVR%2BrpWNJrjNUyoC1g%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.


(Jörg Prante) #12

Yes, I'm aware of building the dependencies SRPMs too, and I agree it is a
lot of work.

Examining the Solr SRPM at
https://bugzilla.redhat.com/show_bug.cgi?id=1025904 a lot of work has been
already done regarding dependencies, and that encourages me to add the
missing ones for ES.

I think it is worth a try now that ES 1.0 is out. I'm unsure about how far
I can proceed and if I find time to provide SRPMs for all future ES
patch/bugfix versions. Maybe others are also interested in package
maintaining and jump in, I'd welcome this.

Jörg

On Thu, Mar 6, 2014 at 11:24 AM, Lukáš Vlček lukas.vlcek@gmail.com wrote:

Jörg

my point about shaded deps is that if you want to deliver crystal clear
RPM from Fedora POW then you need to build source RPM first and then noarch
RPM. Which means that you would first need to have all the shaded deps as a
separate RPMs available in some RPM repo (and if they have transitive deps
then these need to be also build as a standalone RPMs as well ... etc). At
least that is how I understand this and it can be a lot of work if you want
to support it long term and according to all Linux packaging standards.

Regards,
Lukáš

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAKdsXoH2eJZmPzDPrF%2B%2BVXJOx7dhHZ28%3DhvrUY%3DLyyKDCaFcRw%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.


(Lukáš Vlček) #13

Jörg

IMO the best approach would be to do this in context on Fedora packaging,
this means opening a ticket in appropriate system, where Fedora packaging
issues are tracked and do the work in context of such ticket. This way it
could get attention from the people that have a lot of experience in this
domain. If you are fine with that I will try to find which forum is the
right one. WDYT?

Regards,
Lukáš

On Thu, Mar 6, 2014 at 11:58 AM, joergprante@gmail.com <
joergprante@gmail.com> wrote:

Yes, I'm aware of building the dependencies SRPMs too, and I agree it is a
lot of work.

Examining the Solr SRPM at
https://bugzilla.redhat.com/show_bug.cgi?id=1025904 a lot of work has
been already done regarding dependencies, and that encourages me to add the
missing ones for ES.

I think it is worth a try now that ES 1.0 is out. I'm unsure about how far
I can proceed and if I find time to provide SRPMs for all future ES
patch/bugfix versions. Maybe others are also interested in package
maintaining and jump in, I'd welcome this.

Jörg

On Thu, Mar 6, 2014 at 11:24 AM, Lukáš Vlček lukas.vlcek@gmail.comwrote:

Jörg

my point about shaded deps is that if you want to deliver crystal clear
RPM from Fedora POW then you need to build source RPM first and then noarch
RPM. Which means that you would first need to have all the shaded deps as a
separate RPMs available in some RPM repo (and if they have transitive deps
then these need to be also build as a standalone RPMs as well ... etc). At
least that is how I understand this and it can be a lot of work if you want
to support it long term and according to all Linux packaging standards.

Regards,
Lukáš

--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/CAKdsXoH2eJZmPzDPrF%2B%2BVXJOx7dhHZ28%3DhvrUY%3DLyyKDCaFcRw%40mail.gmail.comhttps://groups.google.com/d/msgid/elasticsearch/CAKdsXoH2eJZmPzDPrF%2B%2BVXJOx7dhHZ28%3DhvrUY%3DLyyKDCaFcRw%40mail.gmail.com?utm_medium=email&utm_source=footer
.

For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAO9cvUbmrUtDS%3D56rg7SA%3DD_K4PA7RrVrJQzYMip585e-0P-9g%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.


(Leslie Hawthorn-2) #14

I heard at FOSDEM that Peter Robinson was looking at packaging
Elasticsearch for Fedora. You may want to check in with him to see if
he's moved down that path.

Cheers,
LH

--
Leslie Hawthorn
Community Manager
http://elasticsearch.com

Other Places to Find Me:
Freenode: lh
Twitter: @lhawthorn
Skype: mebelh
Voice: +31 20 794 7300

On Thu, Mar 6, 2014 at 3:00 PM, Lukáš Vlček lukas.vlcek@gmail.com wrote:

Jörg

IMO the best approach would be to do this in context on Fedora packaging,
this means opening a ticket in appropriate system, where Fedora packaging
issues are tracked and do the work in context of such ticket. This way it
could get attention from the people that have a lot of experience in this
domain. If you are fine with that I will try to find which forum is the
right one. WDYT?

Regards,
Lukáš

On Thu, Mar 6, 2014 at 11:58 AM, joergprante@gmail.com
joergprante@gmail.com wrote:

Yes, I'm aware of building the dependencies SRPMs too, and I agree it is a
lot of work.

Examining the Solr SRPM at
https://bugzilla.redhat.com/show_bug.cgi?id=1025904 a lot of work has been
already done regarding dependencies, and that encourages me to add the
missing ones for ES.

I think it is worth a try now that ES 1.0 is out. I'm unsure about how far
I can proceed and if I find time to provide SRPMs for all future ES
patch/bugfix versions. Maybe others are also interested in package
maintaining and jump in, I'd welcome this.

Jörg

On Thu, Mar 6, 2014 at 11:24 AM, Lukáš Vlček lukas.vlcek@gmail.com
wrote:

Jörg

my point about shaded deps is that if you want to deliver crystal clear
RPM from Fedora POW then you need to build source RPM first and then noarch
RPM. Which means that you would first need to have all the shaded deps as a
separate RPMs available in some RPM repo (and if they have transitive deps
then these need to be also build as a standalone RPMs as well ... etc). At
least that is how I understand this and it can be a lot of work if you want
to support it long term and according to all Linux packaging standards.

Regards,
Lukáš

--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/CAKdsXoH2eJZmPzDPrF%2B%2BVXJOx7dhHZ28%3DhvrUY%3DLyyKDCaFcRw%40mail.gmail.com.

For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/CAO9cvUbmrUtDS%3D56rg7SA%3DD_K4PA7RrVrJQzYMip585e-0P-9g%40mail.gmail.com.

For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAB5RFS8UKSn-AQQU4PYhncTEKgkjDkvtdpOkRnCZ8cWxhgqmFg%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.


(Jörg Prante) #15

Thanks Lukáš, Leslie, this is the ticket for Elasticsearch in Fedora/RHEL,
it has been open for a while

https://bugzilla.redhat.com/show_bug.cgi?id=902086

I hope I can contribute something useful in the next few weeks.

Jörg

On Thu, Mar 6, 2014 at 4:10 PM, Leslie Hawthorn <
leslie.hawthorn@elasticsearch.com> wrote:

I heard at FOSDEM that Peter Robinson was looking at packaging
Elasticsearch for Fedora. You may want to check in with him to see if
he's moved down that path.

Cheers,
LH

--
Leslie Hawthorn
Community Manager
http://elasticsearch.com

Other Places to Find Me:
Freenode: lh
Twitter: @lhawthorn
Skype: mebelh
Voice: +31 20 794 7300

On Thu, Mar 6, 2014 at 3:00 PM, Lukáš Vlček lukas.vlcek@gmail.com wrote:

Jörg

IMO the best approach would be to do this in context on Fedora packaging,
this means opening a ticket in appropriate system, where Fedora packaging
issues are tracked and do the work in context of such ticket. This way it
could get attention from the people that have a lot of experience in this
domain. If you are fine with that I will try to find which forum is the
right one. WDYT?

Regards,
Lukáš

On Thu, Mar 6, 2014 at 11:58 AM, joergprante@gmail.com
joergprante@gmail.com wrote:

Yes, I'm aware of building the dependencies SRPMs too, and I agree it
is a

lot of work.

Examining the Solr SRPM at
https://bugzilla.redhat.com/show_bug.cgi?id=1025904 a lot of work has
been

already done regarding dependencies, and that encourages me to add the
missing ones for ES.

I think it is worth a try now that ES 1.0 is out. I'm unsure about how
far

I can proceed and if I find time to provide SRPMs for all future ES
patch/bugfix versions. Maybe others are also interested in package
maintaining and jump in, I'd welcome this.

Jörg

On Thu, Mar 6, 2014 at 11:24 AM, Lukáš Vlček lukas.vlcek@gmail.com
wrote:

Jörg

my point about shaded deps is that if you want to deliver crystal clear
RPM from Fedora POW then you need to build source RPM first and then
noarch

RPM. Which means that you would first need to have all the shaded deps
as a

separate RPMs available in some RPM repo (and if they have transitive
deps

then these need to be also build as a standalone RPMs as well ...
etc). At

least that is how I understand this and it can be a lot of work if you
want

to support it long term and according to all Linux packaging standards.

Regards,
Lukáš

--
You received this message because you are subscribed to the Google
Groups

"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send
an

email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit

https://groups.google.com/d/msgid/elasticsearch/CAKdsXoH2eJZmPzDPrF%2B%2BVXJOx7dhHZ28%3DhvrUY%3DLyyKDCaFcRw%40mail.gmail.com
.

For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit

https://groups.google.com/d/msgid/elasticsearch/CAO9cvUbmrUtDS%3D56rg7SA%3DD_K4PA7RrVrJQzYMip585e-0P-9g%40mail.gmail.com
.

For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/CAB5RFS8UKSn-AQQU4PYhncTEKgkjDkvtdpOkRnCZ8cWxhgqmFg%40mail.gmail.com
.
For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAKdsXoGgjsSz2Ngk6DbqVh52F_tfQDhaiEcwoE12W_GMCOqWtg%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.


(system) #16