Arch Linux User Repository

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 (https://wiki.archlinux.org/index.php/Pi-hole) 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.

to update to pi-hole 6, please use pi-hole-core pi-hole-ftl and pi-hole-web packages.

Deleting the patches (or just clean building) does fix the checksum issue.

However, an even better solution (imo), since you already have to update this package with the new checksums, is to just copy the patches into this package instead of having them source from github. This comes with the added benefit that it's easy to see a diff between the versions.

and more:

[Aur: 1]  pi-hole-server-4.3.2-5

  1 pi-hole-server                   (Build Files Exist)
==> Packages to cleanBuild?
==> [N]one [A]ll [Ab]ort [I]nstalled [No]tInstalled or (1 2 3, 1-3, ^4)
==>

this appear a clear question to me. or not? it's just a matter of not pressing <enter> blindly...

@all sorry but, i need to change the PKGBUILD because of yay build caching? am i understanding well? this is not normal and the use of an aur helper is not mandatory.

cat .config/yay/config.json 
{
"buildDir": "/tmp",
"editor": "",
    ...

the issue isn't that the checksums are wrong it's that arch-server-admin-4.3.2.patch and arch-server-core-4.3.2.patch change with each pkgrel bump but their url doesn't, so although the server is different than your downloaded version because they share the same name they don't get updated, and then fail the checks.

solutions would be to update https://github.com/max72bra/pi-hole-server-archlinux-customization/ to name the patches like arch-server-core-4.3.2-5.patch, or to update the PKGBUILD to download them and save them by pkgrel, so the sources would look like:

source=(...
        admin-$_wwwpkgver-$pkgrel.tar.gz::https://github.com/$_pkgname/$_wwwpkgname/archive/v$_wwwpkgver.tar.gz
        arch-server-core-$pkgver-$pkgrel.patch::"https://raw.githubusercontent.com/max72bra/pi-hole-server-archlinux-customization/master/arch-server-core-$pkgver.patch"
        arch-server-admin-$_wwwpkgver-$pkgrel.patch::"https://raw.githubusercontent.com/max72bra/pi-hole-server-archlinux-customization/master/arch-server-admin-$_wwwpkgver.patch"
        )

...

prepare() {
  cd "$srcdir"/"$_pkgname"-"$pkgver"
  patch -Np1 -i "$srcdir"/arch-server-core-$pkgver-$pkgrel.patch
  cd "$srcdir"/"$_wwwpkgname"-"$_wwwpkgver"
  patch -Np1 -i "$srcdir"/arch-server-admin-$_wwwpkgver-$pkgrel.patch
}

or just configure your AUR helper to either cleanbuild (as stated several times) or your build directory into a temp dir, yay e.g. supports both... -.-

Current easy workaround(for yay) yay -G pi-hole-server , cd pi-hole-server , makepkg -g >> PKGBUILD , makepkg , sudo pacman -U pi-hole-server-4.3.2-5-any.pkg.tar.xz

pi-hole-server-4.3.2-5-any.pkg.tar.xz is current version change it accordingly to it version and file it created

Dear max.bra

I appreciate your work but if I get ==> ERROR: One or more files did not pass the validity check! there is no use of your repo if I had to download and compile it myself, Kind regards

Hi gecko, dns servers list and adblocks list are taken manually from upstream basic-install.sh. It happens that something can be lost especially for the informations extrapolated from basic-insall.sh precisely. In fact, the AUR community never fails to notice what others do. And this is very good.

Given that pi-hole on archlinux is not supported by the original developers and the use of AUR packages is at the user's own risk, the update details are all opensource. You can find all the installation files here in the git repository of this package (FTL details on the respective page) and the patch generator on the respective github repos (https://github.com/max72bra?tab=repositories).

Updating adblock list... done!! Thanks for reporting, as usual. ;-)

@max.bra

Firstly, let me preface by saying thank you for the work you do on maintaining this aur package. It’s great work you’re doing and you make it very convenient for a lot of people, so I’m sure I’m not alone in saying thank you - we appreciate your effort and hard work :) May I ask, how does your package work exactly when updates are applied upstream? Because I noticed in the pihole 4.3.2 release notes (https://pi-hole.net/2019/09/21/pi-hole-4-3-2-release-notes/) that the zeustracker blocklist has been removed from the default blocklists contained in adlists.list file. This was to fix PR#2843 (https://github.com/pi-hole/pi-hole/issues/2843).

However, upon installing your package fresh (ie not an upgrade, full uninstall and removal of /etc/pihole/ folder then reinstall) I find that the zeustracker is still contained in the default blocklist adlists.list file. I assumed that all changes made upstream are automatically applied to this package when there is an update, but this appears to not be the case. So I was wondering if you would mind going into some detail as to what happens when you update this package to reflect an upstream update?

Thanks again for your work :)

@nealc99 try a clean build