Package Details: pi-hole-ftl 5.23-1

Git Clone URL: (read-only, click to copy)
Package Base: pi-hole-ftl
Description: The Pi-hole FTL engine
Upstream URL:
Licenses: EUPL-1.2
Conflicts: dnsmasq
Provides: dnsmasq
Submitter: max.bra
Maintainer: max.bra (graysky)
Last Packager: max.bra
Votes: 53
Popularity: 0.197644
First Submitted: 2017-05-07 15:23 (UTC)
Last Updated: 2023-05-28 14:59 (UTC)

Required by (69)

Sources (7)

Pinned Comments

max.bra commented on 2018-02-09 16:46 (UTC) (edited on 2019-10-18 23:13 (UTC) by max.bra)

ArchLinux Pi-hole is not officially supported by Pi-hole project. In case of bugs and malfunctions please DO NOT file a report upstream.

First of all check if the wiki ( can help then ask here for assistance and tips.
When it will be excluded that the problem does not depend on ArchLinux we will file a bug upstream.

Latest Comments

1 2 3 4 5 6 .. 41 Next › Last »

max.bra commented on 2023-02-27 11:40 (UTC)

@loathingkernel done w/o rel bump. cleaner. i like it. opinions are welcome.

max.bra commented on 2023-02-24 12:16 (UTC)

I take advantage of the request to fix this: I always hated the date solution inserted some time ago following another request.
I think I will also implement the release number in github patch name.

loathingkernel commented on 2023-02-24 11:30 (UTC) (edited on 2023-02-24 11:33 (UTC) by loathingkernel)

I don't know how you would like to handle it, but one solution would be to statically include the patch file with the PKGBUILD. Another one would be to host a fork in github and pull the patch's commit by its url<user>/<repo>/commit/<sha>.patch

Edit: from a quick look, since the patch is already versioned, I don't see the need to append the date too. Unless I am missing something, wouldn't it be easier to just omit the date altogether?

max.bra commented on 2023-02-24 11:23 (UTC)

@loathingkernel do you have any suggestion?

loathingkernel commented on 2023-02-24 11:19 (UTC) (edited on 2023-02-24 11:31 (UTC) by loathingkernel)

Please find a proper versioning scheme for the customization patch. Using date +%N makes .SRCINFO perpetually invalid. Not only this is incorrect for the AUR but causes issues for anyone that might want to cross-reference the .SRCINFO file against the PKGBUILD for validation reasons.

Antiz commented on 2023-02-16 08:12 (UTC)

@DGUERRERO patch is a member of the base-devel meta package which is assumed installed when building AUR packages, so it shouldn't be added as a make dependency.

See and

DGUERRERO commented on 2023-02-16 08:03 (UTC)

please add patch as dependency

 ==> Extracting sources...
 -> Extracting pi-hole-ftl-v5.21.tar.gz with bsdtar
 ==> Starting prepare()...
 /home/dguerrero/pi-hole-ftl/PKGBUILD: line 39: patch: command not found
 ==> ERROR: A failure occurred in prepare().

gmiske commented on 2023-01-01 05:41 (UTC) (edited on 2023-01-01 05:42 (UTC) by gmiske)

mrdotx commented on 2022-12-23 04:27 (CST)
I can't build the current release 5.20-1:

I was not able to either, and I got the same error.

I was able to build 5.19.2-1 though, by doing "git checkout 9ee34", and then issuing "makepkg"

I'm not sure what problems I'll encounter because of this, but it did build, and install.

max.bra commented on 2022-12-26 22:46 (UTC)

oh i see now, I wasn't aware of the provide on xxd. i was lot, even if rautesamtr tells me, sorry.

ilpianista commented on 2022-12-26 22:05 (UTC)

why is removable vim make dependency a problem?

Even if it isn't. FS#45406 has been implemented to cover this specific use case.