Synopsis: [PATCH] Latest BIND port triggers problem in portsnap
State-Changed-From-To: feedback->open
State-Changed-By: delphij
State-Changed-When: Mon Apr 14 19:38:43 UTC 2014
State-Changed-Why:
I think we have enough information to solve this already.
Responsible-Changed-From-To: freebsd-bugs
lini...@freebsd.org wrote:
> to which part of the system does the patch pertain to?
I'm sorry it wasn't obvious from my report.
The patch pertains to src/usr.sbin/portsnap/portsnap/portsnap.sh.
___
freebsd-bugs@freebsd.org mailing list
http://lists.free
Synopsis: [PATCH] Latest BIND port triggers problem in portsnap
State-Changed-From-To: open->feedback
State-Changed-By: linimon
State-Changed-When: Sun Apr 13 23:34:37 UTC 2014
State-Changed-Why:
to which part of the system does the patch pertain to?
http://www.freebsd.org/cgi/query-pr.cgi?pr=18
The following reply was made to PR bin/186510; it has been noted by GNATS.
From: Oliver Fromme
To: bug-follo...@freebsd.org
Cc:
Subject: Re: bin/186510: [PATCH] Latest BIND port triggers problem in portsnap
Date: Thu, 6 Feb 2014 15:20:33 +0100 (CET)
Addendum:
At first I wasn't ab
>Number: 186510
>Category: bin
>Synopsis: [PATCH] Latest BIND port triggers problem in portsnap
>Confidential: no
>Severity: serious
>Priority: high
>Responsible:freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class:
