Package Details: pi-hole-server 5.18.2-1

Git Clone URL: https://aur.archlinux.org/pi-hole-server.git (read-only, click to copy)
Package Base: pi-hole-server
Description: The Pi-hole is an advertising-aware DNS/Web server. Arch adaptation for lan wide DNS server.
Upstream URL: https://github.com/pi-hole/pi-hole
Keywords: ad block pi-hole
Licenses: EUPL-1.2
Conflicts: pi-hole-standalone
Submitter: max.bra
Maintainer: max.bra (graysky)
Last Packager: max.bra
Votes: 112
Popularity: 1.50
First Submitted: 2016-01-13 12:50 (UTC)
Last Updated: 2024-04-01 18:11 (UTC)

Dependencies (18)

Required by (2)

Sources (15)

Pinned Comments

max.bra commented on 2018-02-09 16:45 (UTC) (edited on 2019-10-18 23:14 (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 (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.

Latest Comments

« First ‹ Previous 1 .. 6 7 8 9 10 11 12 13 14 15 16 .. 80 Next › Last »

starquake commented on 2022-01-04 13:09 (UTC)

@max.bra I understand building from sources is recommended. And I agree with that. But some AUR packages have a -bin package for convenience. So that's why I asked. Because I would find that convenient. But maybe that's not a concern for most people.

Swapping will help but the machine gets really slow sometimes. And then pihole gets slow. I'll see if I can do cross compiling. Or maybe upgrade.

Thanks!

max.bra commented on 2022-01-04 08:46 (UTC)

@starquake hi, FTL has compile problems on systems with less than about 800MB of free RAM.
The binaries are already made available by the original developers but archlinux policies, where possible, recommend compiling the sources.
You can brilliantly solve the problem by configuring even only 512MB of swap or if possible do a cross compiling with your other device on the network (plus: also speeding things up).

df8oe commented on 2022-01-04 08:41 (UTC)

I do not think a binary package is necessary. Simply activate swap to get rid of this problem.

starquake commented on 2022-01-04 08:27 (UTC)

My RPI 3B+ has problems compiling this package. It's running out of memory. Would you consider creating a binary package?

katoitalia commented on 2021-12-08 16:41 (UTC)

@max.bra yes, we all make mistakes but we all need to be corrected when we do. I am sorry if a simple feedback rocked your fragile self esteem, I can't help you with that.

max.bra commented on 2021-12-08 16:36 (UTC)

@katoitalia
since you insist: then simply notify that the package has problems (which can happen, we are all human beings who can be wrong) without arrogating the right to teach me how to do it since you have NOT been asked. that's it. it is a matter of respect for the person and his work.

katoitalia commented on 2021-12-08 16:31 (UTC) (edited on 2021-12-08 16:35 (UTC) by katoitalia)

@max.bra please read it carefully, in no way shape or form that article on the wiki says that a broken package with an #outdated and broken# PKGBUILD shouldn't be considered as #outdated# and marked accordingly.

First, you should flag the package out-of-date indicating details on why the package is outdated, preferably including links to the release announcement or the new release tarball.

Should you find some other wiki article that proves me wrong, please quote it I will enjoy reading it. I am deeply sorry if feedback from the community isn't encouraged as it should.

To prevent such things to happen in the future consider checking if your packages do work before pushing them to the AUR.

Thank you.

max.bra commented on 2021-12-08 16:11 (UTC) (edited on 2021-12-08 16:15 (UTC) by max.bra)

@katoitalia https://wiki.archlinux.org/title/Arch_User_Repository#Flagging_packages_out-of-date
... preferably including links to the release announcement or the new release tarball.
Nothing else to say or write.
p.s.: on forgetting on how to checksum a package: I was sarcastic :-D

katoitalia commented on 2021-12-08 15:09 (UTC) (edited on 2021-12-08 15:23 (UTC) by katoitalia)

@max.bra thank you for updating it quickly. It works just fine now. Cheers.

A broken PKGBUILD with outdated sha256sums is an outdated PKGBUILD.

Please consider building your packages locally with makepkg (and/or automating checks with a custom script) before pushing them to the AUR to avoid such issues.

Thanks

max.bra commented on 2021-12-08 15:06 (UTC) (edited on 2021-12-08 15:13 (UTC) by max.bra)

@katoitalia hi, thanks for your explanation on a correct checksumming. after 5 years of packages maintaining i was forgetting it.
package updated with corrected sums. you can remove your post.
oh, and more: DO NOT flag package as outdated for a problem on it. simply posting the problem will notify me (and graysky) of everything.