From owner-freebsd-bugs@FreeBSD.ORG Sun Jul 13 22:36:43 2003 Return-Path: Delivered-To: freebsd-bugs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D3D3837B41E; Sun, 13 Jul 2003 22:36:43 -0700 (PDT) Received: from obsecurity.dyndns.org (adsl-64-169-104-32.dsl.lsan03.pacbell.net [64.169.104.32]) by mx1.FreeBSD.org (Postfix) with ESMTP id EA71943F93; Sun, 13 Jul 2003 22:36:42 -0700 (PDT) (envelope-from kris@obsecurity.org) Received: from rot13.obsecurity.org (rot13.obsecurity.org [10.0.0.5]) by obsecurity.dyndns.org (Postfix) with ESMTP id 613C266B04; Sun, 13 Jul 2003 22:36:39 -0700 (PDT) Received: by rot13.obsecurity.org (Postfix, from userid 1000) id D2933BCB; Sun, 13 Jul 2003 22:36:39 -0700 (PDT) Date: Sun, 13 Jul 2003 22:36:39 -0700 From: Kris Kennaway To: Arnt Gulbrandsen Message-ID: <20030714053639.GA13767@rot13.obsecurity.org> References: <200307130607.h6D67JZS094217@freefall.freebsd.org> <20030713180548.B10110@melkebalanse.gulbrandsen.priv.no> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="xHFwDpU9dbj6ez1V" Content-Disposition: inline In-Reply-To: <20030713180548.B10110@melkebalanse.gulbrandsen.priv.no> User-Agent: Mutt/1.4.1i cc: freebsd-bugs@freebsd.org Subject: Re: bin/54278: dig misparses many IPv6 addresses X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Jul 2003 05:36:44 -0000 --xHFwDpU9dbj6ez1V Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Jul 13, 2003 at 06:05:48PM +0200, Arnt Gulbrandsen wrote: > Kris Kennaway > > Synopsis: dig misparses many IPv6 addresses > >=20 > > State-Changed-From-To: open->closed > ... > > State-Changed-Why:=20 > > BIND is not maintained by FreeBSD. Please take this up with > > the BIND developers instead. >=20 > a) Is there some predictable way of telling which parts of /usr/src are > considered suitable for bug reports? If it's a separate project with its own releases, then bug reports should go there. This third-party code is usually imported into /usr/src/contrib or /usr/src/crypto in FreeBSD. > b) Is there some suitable way of saying e.g. "the version in freebsd is > buggy -- consider upgrading"? I'm not sure what you mean here. In the case of your PR, only the BIND developers are likely to know about the status of the bug and whether it has been fixed in a later release. > c) The bind developers fixed the bug four releases ago. OK, glad to hear it. It's usually helpful to follow-up to your PRs when you solve them, to indicate that they can be closed. Kris --xHFwDpU9dbj6ez1V Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (FreeBSD) iD8DBQE/EkFnWry0BWjoQKURAjT8AJ0Vj6snbk8tQEHZ/ecCBGW7wvONpACghPJh PvU3RpSvfNGTeHnj6jagCAg= =Kzqp -----END PGP SIGNATURE----- --xHFwDpU9dbj6ez1V--