Date: Sun, 16 Jun 2019 09:32:31 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 238602] dns/powerdns-recursor: update to 4.1.14 Message-ID: <bug-238602-7788-xVdAPX7C7H@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-238602-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-238602-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=3D238602 Kubilay Kocak <koobs@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|New |Open Severity|Affects Many People |Affects Only Me --- Comment #3 from Kubilay Kocak <koobs@FreeBSD.org> --- Hi Ralf, thanks for the update including QA.=20 A few administrative tips: Feature updates (unless they're also security updates) are always "Affects = Only Me" in the sense that it "affects the maintainer", who aims to update the p= ort, the class of the issue. Build logs are not required, unless they are requested by someone first. Instead you can confirm QA in your comment as follows: portlint: OK (looks fine.) testport: OK (poudriere: <versions>, <archs>, <OPTIONS> tested) If you can provide a changelog URL for version updates, please do so in the URL: field, pointing to an upstream URL that is a permalink (ie; its conten= ts doesn't change over time) to the changes for that version. If it includes previous versions too that's fine. When providing logs, or anything else which is a large body of text/data, u= se attachments instead of external URL's, which can become stale or go missing entirely over time. It's better if all information is completely self-contained and available in the issue. --=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-238602-7788-xVdAPX7C7H>