Date: Fri, 17 Nov 2023 04:16:43 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 266415] dns/ddclient: Update to v3.10 RC2 Message-ID: <bug-266415-7788-rzYdmWQreB@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-266415-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-266415-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D266415 --- Comment #9 from mjl@luckie.org.nz --- I have tried out ddclient-3.11.1, according to the version in opnsense. But ddclient is still buggy: WARNING: updating <redacted>: nochg: No update required; unnecessary attem= pts to change to the current address are considered abusive This experience is not unique to me. For example, on opnsense's forum: https://forum.opnsense.org/index.php?topic=3D33267.0 https://github.com/ddclient/ddclient/issues/544 My previous suggestion in one of these ddclient tickets was for someone to create a ddclient-devel port, so that people who want to use new dynamic dns providers can use that port, without running the risk that other users of ddclient will find themselves blocked through no fault of their own. I sti= ll think that is the correct approach for the time being. I'll attach the pat= ch I used locally as evidence that I am doing the best I can to maintain this po= rt, but the patch should not be applied to this port (it is not maintainer approved). --=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-266415-7788-rzYdmWQreB>