Currently, building lagrange 1.19.4-1 fails due to recent changes in glibc.

why is this not in the Arch package repo yet? It's great.

I think this happens because you interrupted a previous build and got a partial download.

Try running:

$ rm *.part

and try again

Seems to no longer build, I get the following error:

curl: (33) HTTP server does not seem to support byte ranges. Cannot resume.
==> ERROR: Failure while downloading https://git.skyjake.fi/skyjake/lagrange/releases/download/v1.18.3/lagrange-1.18.3.tar.gz

@Roshless: Since the maintainer likes to belittle anyone commenting here and project, I'll just post my improved PKGBUILD.

@yochananmarqos people like you are the single biggest reason there is always maintainer shortage.

What account? Did you really bother to type all this text into aur before checking what mailing list really is? You only need mail account and git installed- that's the point, no need for account on gitlab/sourcehut

Flagging package out of date is not contribution, sending a patch with updated version is. Yes I have rss feeds, but there is this thing called real life that can take some time off my non-paid time keeping packages up to date.

I don't need your high horse spiel about out of date flag purpose and aur helpers- I know, Ive been around for ~10y on this site.

Instead of being all smart in your comment, maybe next time send a patch? If you know what you are doing, it takes comparable amount of time to flagging package out of date and copy pasting link to release.

On topic: libunistring is required- it's specified multiple times in README and cmakelist. if pcre is fine I don't see the reason to change it.

This is missing the libwebp dependency. I'm not sure that libunistring is required.

It looks for pcre first and if it can't find it then it looks for pcre2. I would change the dependency to the latter.