Package Details: elasticsearch 8.17.4-1

Git Clone URL: https://aur.archlinux.org/elasticsearch.git (read-only, click to copy)
Package Base: elasticsearch
Description: Free and Open, Distributed, RESTful Search Engine
Upstream URL: https://www.elastic.co/elasticsearch/
Licenses: custom:Elastic-2.0
Conflicts: elasticsearch-bin, elasticsearch7
Provides: elasticsearch
Submitter: hashworks
Maintainer: ipaqmaster
Last Packager: ipaqmaster
Votes: 11
Popularity: 0.22
First Submitted: 2022-01-08 16:30 (UTC)
Last Updated: 2025-03-25 16:49 (UTC)

Dependencies (2)

Required by (18)

Sources (9)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 .. 14 Next › Last »

ipaqmaster commented on 2023-10-02 21:37 (UTC) (edited on 2023-10-03 02:15 (UTC) by ipaqmaster)

Sorry I didn't see these earlier. I'll try to correct this.

It seems jre-openjdk-headless has started shipping java-21-openjdk which experiences warnings as errors during the build.

My machine has its archlinux-java set to java-17-openjdk (default) but a brand new docker container which only has jre-openjdk-headless (java-21-openjdk) can't build it due to the warning errors.

I was able to build it with java-20-openjdk in the container after downgrading to these three together: jdk-openjdk-20.0.2.u9-3 jre-openjdk-20.0.2.u9-3 jre-openjdk-headless-20.0.2.u9-3

Because Java 8,11,17 and 21 are the currently supported versions on Archlinux perhaps this AUR package could be changed to build using 17 until 21 doesn't error on warn?

prwood commented on 2023-10-02 19:22 (UTC)

I'm having the same issue as @bjo:

1: Task failed with an exception.

  • What went wrong: Execution failed for task ':libs:elasticsearch-core:compileJava'.

    error: release version 17 not supported

  • Try:

    Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Get more help at https://help.gradle.org.

bjo commented on 2023-09-21 20:06 (UTC)

Building fails with error: release version 17 not supported - not sure what it complains about.

ipaqmaster commented on 2023-09-10 03:50 (UTC)

Understandable HLHF. This being changed to a source build certainly knocks out the build time.

The latest elastic 'release' for 7.17.13 caused the package to version-bump downwards, this has been corrected and logic has been added to avoid autoUpdating to lower version numbers.

HLFH commented on 2023-08-31 12:49 (UTC) (edited on 2023-08-31 12:50 (UTC) by HLFH)

I migrated to elasticsearch-bin as elasticsearch source takes too much resources (and time) to build.
I am leaving my maintainer role, and giving it to @ipaqmaster, you can therefore replace the Maintainer line in the PKGBUILD either for the current or the next version.

ipaqmaster commented on 2023-08-31 03:42 (UTC)

The package continues to fall out of date so I've added ./autoUpdate to my own pipelines.

Updated ./audoUpdate to reset the pkgrel variable with updates. And had to set the tarball url to match the one in PKGBUILD as github's project/repo/archive/vXXX.tar.gz endpoint returns a different archive than the the api's tarball_url value repos/elastic/elasticsearch/tarball/vXXX with no other references to latch onto.

HLFH commented on 2023-08-20 22:39 (UTC)

@ipaqmaster, when you push for a change to the same package version, you should normally update pkgrel, here pkgrel should be 6.

ipaqmaster commented on 2023-08-18 07:39 (UTC) (edited on 2023-08-21 07:53 (UTC) by ipaqmaster)

Whoops, good catch anonfunc that flag has been added to both gradlew calls.

E: Apologies. Forgot to bump pkgrel in a hurry. Also pushed.

anonfunc commented on 2023-08-17 09:47 (UTC) (edited on 2023-08-17 09:48 (UTC) by anonfunc)

Could you please add --no-daemon to the gradle-wrapper commands, so that there is no gradle daemon running after building this? The deamon is not needed for the build, its main purpose, as far as I understand, is to speed up subsequent builds, which should be way out of scope for an AUR package.

ipaqmaster commented on 2023-08-06 09:25 (UTC) (edited on 2023-08-06 12:44 (UTC) by ipaqmaster)

I believe this is what I already did in the initial commits. I'll add those again and test a build, install and service start.

I haven't had to build from the tar.gz before but after gradle runs the output seems to be at pkgdir subdir distribution/archives/linux-tar/build/install/${pkgname}-${pkgver}-SNAPSHOT. I've adjusted the script to refer to this build dir instead of the path relevant for artifact downloads and it seems to be working.

I'll push this for now as it builds successfully but will need to be made aware of any aarch64 compatibility issues.

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 .. 14 Next › Last »