Package Details: futhark-bin 0.26.1-1

Git Clone URL: https://aur.archlinux.org/futhark-bin.git (read-only, click to copy)
Package Base: futhark-bin
Description: A data-parallel functional programming language.
Upstream URL: https://futhark-lang.org/
Licenses: LicenseRef-ISC
Conflicts: futhark
Provides: futhark
Submitter: mbloms
Maintainer: mieszkodrewicz
Last Packager: tippfehlr
Votes: 5
Popularity: 0.116099
First Submitted: 2020-04-22 07:10 (UTC)
Last Updated: 2026-06-11 17:25 (UTC)

Dependencies (3)

Required by (0)

Sources (2)

Latest Comments

sebastianprehn commented on 2026-03-12 09:37 (UTC)

I was unable to replicate the issue you ran into, installing without issue even when I tried from a new machine. I found your specification of license to be a useful addition nonetheless and added it. Please let me know if that helped!

Eirikr commented on 2026-03-03 00:30 (UTC) (edited on 2026-03-03 00:31 (UTC) by Eirikr)

1) aur/futhark-bin fails to install with AUR helpers with a "LICENSE NOT FOUND" message...

Messy interpretation is that makepkg does not follow HTTP redirects for https:// sources by default when the URL points to GitHub release assets, because GitHub returns a 302 to a time-limited signed S3/Azure URL. It sends a Range: bytes=0- header on the redirect which the Azure CDN rejects with a 416 "Requested Range Not Satisfiable", causing curl to exit non-zero and makepkg to report "error downloading sources".


So... after chasing that ghost... it might also have been that the original PKGBUILD names the second source just LICENSE which is a generic name and if SRCDEST is doing... something wrong... who knows what... then suddenly there are licensing ghosts of unknown origin. makepkg saw "Found LICENSE", checked the hash, got a mismatch, and reported it as a download error.


What worked for me in the PKGBUILD = rename LICENSE to LICENSE-${pkgname}-${pkgver} via the filename::url source syntax.... "LICENSE-${pkgname}-${pkgver}::https://raw.githubusercontent.com/diku-dk/futhark/v${pkgver}/LICENSE") and then update the SHA256