bcookatpcsd
commented
1 month ago This seems to have no problems..
cd /tmp
fetch https://static.adguard.com/adguardhome/release/AdGuardHome_freebsd_amd64.tar.gz
tar xvf AdGuardHome_freebsd_amd64.tar.gz
/usr/local/bin/adguardhome --version
/usr/local/etc/rc.d/adguardhome stop
cp /tmp/AdGuardHome/AdGuardHome /usr/local/bin/adguardhome
/usr/local/etc/rc.d/adguardhome start
/usr/local/bin/adguardhome --version
rm -rf /tmp/AdGuardHome
Prerequisites
[X] I have checked the Wiki and Discussions and found no answer
[X] I have searched other issues and found no duplicates
[X] I want to report a bug and not ask a question or ask for help
[X] I have set up AdGuard Home correctly and configured clients to use it. (Use the Discussions for help with installing and configuring clients.)
Platform (OS and CPU architecture)
FreeBSD, AMD64 (aka x86_64)
Installation
Other (please mention in the description)
Setup
Standalone machine for a network for tailscale
AdGuard Home version
v0.107.51
Action
Put up a FreeBSD machine for a project and installed adguardhome from pkg.
Not sure why 107.51 is in pkg and in ports.. is there a reason 107.52 isn't there?
getting the github release for 107.52 and cp'ing the AdGuardHome binary to adguardhome and everything seems just fine..
(but is there something that I don't know about yet..? )
Expected result
FreeBSD pkg and ports would have the stable release found in github..
Actual result
one version behind, but just confused why
https://cgit.freebsd.org/ports/tree/www/adguardhome
.. any ideas?
possibly related to golang ver or npm ver?
Additional information and/or screenshots
thank you in advance as always..