Date: Sat, 21 Jan 2023 17:50:12 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 269083] www/adguardhome: fails to start properly after upgrading Message-ID: <bug-269083-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D269083 Bug ID: 269083 Summary: www/adguardhome: fails to start properly after upgrading Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: yuri@freebsd.org Reporter: bsd@j-star.org Assignee: yuri@freebsd.org Flags: maintainer-feedback?(yuri@freebsd.org) Commit https://cgit.freebsd.org/ports/commit/?id=3D95bf6629820c81523de4693a7c6299e= d62c7e1f6 which fixes bug https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D268890 introduces an unwanted behaviour: existing adguardhome installations do not restart properly when upgraded, but instead revert to the configuration wiz= ard. This makes sense, since the configuration files are not in the new expected location. The new behaviour of having the configuration in a more reasonable place is clearly better. I wonder whether a note should be added to UPDATING flagging that existing installations will break, and giving the steps required to update: mv /usr/local/bin/AdGuardHome.yaml /usr/local/etc/ # If adguardhome has been started since upgrade rm -rf /var/db/adguardhome/data/ mv /usr/local/bin/data/ /var/db/adguardhome/data --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-269083-7788>