AUR (en) - elasticsearch

Search Criteria

Package Details: elasticsearch 8.13.3-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:	8
Popularity:	0.150994
First Submitted:	2022-01-08 16:30 (UTC)
Last Updated:	2024-05-03 17:49 (UTC)

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:

Popularity:

0.150994

First Submitted:

2022-01-08 16:30 (UTC)

Last Updated:

2024-05-03 17:49 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 .. 13 Next › Last »

bjo commented on 2024-02-08 10:47 (UTC) (edited on 2024-02-08 10:59 (UTC) by bjo)

"aur sync" from aurtools still has this issue, running "makepkg -rsi" still leads to:

BUILD SUCCESSFUL in 4m 25s
556 actionable tasks: 500 executed, 56 up-to-date
==> Entering fakeroot environment...
==> Starting package()...
error: package 'jdk-openjdk' was not found
==> ERROR: A failure occurred in package().
    Aborting...

And jdk-openjdk is not installed and conflicts with jdk17-openjdk.

ipaqmaster commented on 2024-02-08 04:15 (UTC)

Odd, I couldn't reproduce the build issue today in a fresh environment (An Arch root in a docker container). All deps fetched correctly and it built. Could this have been a transient issue with the official packaging of jdk-openjdk?

ipaqmaster commented on 2024-02-08 02:57 (UTC) (edited on 2024-02-08 03:07 (UTC) by ipaqmaster)

Sorry for not getting to this sooner. I kept cloning it and getting started only to get distracted by other alerts this week. Will fix that up now.

It already has jdk17-openjdk set as makedepends due to an inability to be built with newer versions but once built, it can be run with jdk-openjdk just fine.

The variable jdk_openjdk_version is to help dynamically figure out what the latest version number path for /usr/lib/jvm/java-##-openjdk/ is going to be for symlinking in the package without erroring as time goes on. This is in there because jdk-openjdk's directory above will change despite the package name being static.

Perhaps this can all just be dropped for jdk17-openjdk as a make and regular dependency though the merit was to avoid installing older versions of Java permanently where the latest was still acceptable. Keeping other applications in mind which do not have problems with whatever the latest java version happens to be.

bjo commented on 2024-02-07 21:02 (UTC)

Seems like jdk_openjdk_version=$(pacman -Ql jdk-openjdk | grep -Pom1 '(?<=jdk-openjdk )/usr/lib/jvm/java-[0-9]+-openjdk/') is broken. And a dependency on jdk17-openjdk would be better as it's broken with jdk-openjdk 21.

nonZero commented on 2024-02-06 20:09 (UTC)

==> Entering fakeroot environment...
==> Starting package()...
error: package 'jdk-openjdk' was not found
==> ERROR: A failure occurred in package().
    Aborting...
 -> error making: elasticsearch-exit status 4
 -> Failed to install the following packages. Manual intervention is required:
elasticsearch - exit status 4

ipaqmaster commented on 2024-01-23 22:55 (UTC)

I'm checking https://github.com/elastic/elasticsearch/releases and can't seem to find any indication of this being a prerelease despite evidently being built as one. It may be possible it were tagged and compiled as a pre-release before elastic gave it the green light as a proper release. In which case I have no means of filtering out prereleases right this second as the releases page doesn't seem to show any recently.

Please let me know if it happens again and I will check the github releases api again to see if it hints to a pre-release or not. If it does, I can modify ./autoUpdate to ignore them.

ipaqmaster commented on 2024-01-20 00:14 (UTC) (edited on 2024-02-08 03:17 (UTC) by ipaqmaster)

Sorry, seems like a bricked that myself ;)

All good no worries

BTW, 8.12 seems not for production?

I suspect that's how this AUR package has always been. But I will make note to have it get its version number either a different non-beta way or to filter out 'SNAPSHOT' releases when I get a chance today. [This has not yet been done*]

bjo commented on 2024-01-19 22:25 (UTC)