From owner-freebsd-bugs Thu Jul 19 21: 5: 3 2001 Delivered-To: freebsd-bugs@freebsd.org Received: from coffee.q9media.com (coffee.q9media.com [216.94.229.19]) by hub.freebsd.org (Postfix) with ESMTP id DD22937B406 for ; Thu, 19 Jul 2001 21:05:00 -0700 (PDT) (envelope-from mike@coffee.q9media.com) Received: (from mike@localhost) by coffee.q9media.com (8.11.2/8.11.2) id f6K4Lgr57334; Fri, 20 Jul 2001 00:21:42 -0400 (EDT) (envelope-from mike) Date: Fri, 20 Jul 2001 00:21:42 -0400 From: Mike Barcroft To: Paul Richards Cc: mi@aldan.algebra.com, freebsd-bugs@FreeBSD.org Subject: Re: bin/10031: ypxfr does not work with Solaris master server(s) Message-ID: <20010720002142.A57085@coffee.q9media.com> References: <200107200228.f6K2SCQ72925@freefall.freebsd.org> <196780000.995597409@lobster.originative.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <196780000.995597409@lobster.originative.co.uk>; from paul@freebsd-services.co.uk on Fri, Jul 20, 2001 at 03:50:09AM +0100 Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Fri, Jul 20, 2001 at 03:50:09AM +0100, Paul Richards wrote: > --On Thursday, July 19, 2001 19:28:12 -0700 mike@FreeBSD.org wrote: > > Synopsis: ypxfr does not work with Solaris master server(s) > > > > State-Changed-From-To: feedback->closed > > State-Changed-By: mike > > State-Changed-When: Thu Jul 19 19:17:49 PDT 2001 > > State-Changed-Why: > > > > The originator indicated to me, in a private e-mail, that he is > > unable to test whether this has been resolved in a newer release. > > > > http://www.FreeBSD.org/cgi/query-pr.cgi?pr=10031 > > > I don't think it's right to close PRs for these reasons, the bug may still > be present. Is there any harm in leaving it open for the time being if > there's no evidence to suggest the bug is fixed? My concern is that this PR hasn't even been touched in over two years. If we leave it open it's not likely anyone will pick it up because it deals with an old version of FreeBSD, an old version of Solaris, and since it deals with interoperability between the two, it's difficult to judge whether it's a FreeBSD bug, a Solaris bug, or a misconfiguration issue. Finally, if a new person experiences this on newer versions of FreeBSD and Solaris would it really be a crime if they had to open a new PR? Having said this, if you still feel it should be left open I will, ofcourse, be glad to re-open it. Best regards, Mike Barcroft To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message