[Bug 268444] www/adguardhome: fails to start after go1.18.9 update

Go to: [ bottom of page ] [ top of archives ] [ this month ]

From: <bugzilla-noreply_at_freebsd.org>
Date: Sun, 18 Dec 2022 11:59:12 UTC

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268444

            Bug ID: 268444
           Summary: www/adguardhome: fails to start after go1.18.9 update
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: Individual Port(s)
          Assignee: yuri@freebsd.org
          Reporter: bsd@j-star.org
             Flags: maintainer-feedback?(yuri@freebsd.org)
          Assignee: yuri@freebsd.org

After rebuilding adguardhome today it fails to start with "[fatal] initing
hosts container: hosts container: path at index 0: stat etc/hosts: os: DirFS
with empty root".

I *think* the reason is that the version of adguardhome in ports is broken by
this commit to go
https://github.com/golang/go/commit/7dc9fcb13de7bb20b11f6a526865545cc9142c2c
fixing CVE-2022-41720 . As far as I can tell, adguardhome introduced a patch in
v0.107.20 to fix the problem:
https://github.com/AdguardTeam/AdGuardHome/blame/master/internal/aghos/os_unix.go#L13
.

So I suspect simply updating to the latest release will fix this. I tried to
test, and would send a patch, but I haven't yet been able to figure out how to
update the distfiles checksums!

-- 
You are receiving this mail because:
You are the assignee for the bug.