Arch Linux User Repository

@ipaqmaster With the fifth maintenance release of this AUR package, I updated the build function,
and it is building from source, maybe you want to try if this current fifth release works for you, and we go from there.

Thanks. I think you're right - elasticsearch-bin already exists and this package was doing the same thing. We could use this one to build the source instead then

@ipaqmaster I added you as co-maintainer, feel free to update as you see fit.
To update sums, I use updpkgsums, so it is quite automatic.
My opinion is for elasticsearch, on GitHub, you only have the sources,
and on Elastic.co, you have the binaries (prebuilt deliverables) as well.
The source is by definition compatible with both aarch64 and x86_64.
Now changes have been made, I do advise to keep using the source and not the binaries,
as this package, if it uses the binaries, requires the -bin suffix in its name, and this name is taken on the AUR.

https://github.com/ipaqmaster/elasticsearch-aur/tree/autoUpdate

This branch on my github now contains the original 8.8.1 commit then a commit of the new ./autoUpdate which works against the original PKGBUILD. Plus a commit on top of its version bump.

I was able to makepkg the resulting 8.9.0 version bump from the above branch and start the elasticsearch service without any trouble. This change retains support for different architectures as the AUR package did originally.

I'm not sure how this AUR package gathered b2sums before this script. Did you grab both the x86_64 and aarch64 b2sums manually? I can imagine aarch64 will still fail with this change due to an unchanged b2sum.

I'd be happy to co-maintain this though I must apologise for assuming the tar.gz on the project's releases page were identical to the tar.gz on their downloads page. I had a workaround for this locally however even with that, the file strucutre is wildly different.

That said, it's not a source package and does contain the bins, but under different paths than the regular tarball download.

I think we should rollback to the original 8.8.1 release and change autoUpdate to still check github for a release number, but fetch that release number using the original artifacts.elasticsearch.co URL scheme this repo was using. That way, the rest of the PKGBUILD can remain as it were while still receiving version bumps.

For the next maintainer, here are the systemd timer & service:

update-elasticsearch.timer:

[Unit]
Description=Run update-elasticsearch every day at midnight

[Timer]
OnCalendar=*-*-* 00:00:00
Unit=update-elasticsearch.service

[Install]
WantedBy=timers.target

update-elasticsearch.service:

[Unit]
Description=Update Elasticsearch Script

[Service]
ExecStart=/home/hlfh/elasticsearch/autoUpdate

I updated the package. Please tell me if that works for you and I'll update accordingly.

According to the AUR submission guidelines:

Packages that use prebuilt deliverables, when the sources are available, must use the -bin suffix. An exception to this is with Java.
The AUR should not contain the binary tarball created by makepkg, nor should it contain the filelist.

I must say after taking over the elasticsearch package in November 22, I quickly changed the PKGBUILD source from the source to the binary.
In fact, building the source was breaking my server resources and it was unbearable.
So the package name became noncompliant with the AUR submission guidelines (which I did not know at the time).

In addition to providing an autoupdate maintenance script (that needs to be further checked),
what @ipaqmaster did, was the switch back to using the source rather than the binary.
I updated the build() function accordingly in this third release of 8.9.0.
I was not able to test it thoroughly on my server, please do if you want.

I suggest people to migrate to elasticsearch-bin because it is far quicker to build.

I would prefer to request elasticsearch for deletion (!) as it is not very useful compared to elasticsearch-bin
but if you guys want to maintain this kinda elasticsearch-src package, be my guest, I'm not a Gentoo kind of guy ;)
I can start by adding a co-maintainer (@^^@). Any volunteer?
This person would have to run the autoupdate script or any equivalent for quicker maintenance.

Standby. I had a workaround for this locally but it seems I forgot to commit it.

Despite that - While github is a great way to programmatically fetch the latest version number I forgot to factor in the major directory structure differences between the github release and the artifacts.elasticsearch.co tar.gz. After doing so, things still aren't quite right.

E: Will need to change the scrip tomorrow

• Pull the 8.8.1 PKGBUILD
• makepkg with the skipchecksum (this pulls the latest 8.9.* ES into the 8.8.1 build)
• In pkg, edit .BUILDINFO, .PKGINFO, .MTREE correcting the ES version
• Repackage with makepkg:

  git checkout -f ffefe39e2a46b3afced23b6ff6d672a6c6d43ae1
  makepkg --skipchecksum
  nano .BUILDINFO, .PKGINFO, .MTREE etc
  makepkg -Rf
  

Possibly you could update the PKGBUILD with the new ES version... Try it :) But the above is how I came to a solution.

@aurtechnosf:
Where have you added --skipchecksum ? I have the same issue and tried with yay or makepkg but nothing works