From owner-freebsd-ports Tue Jul 3 1: 5:27 2001 Delivered-To: freebsd-ports@freebsd.org Received: from ringworld.nanolink.com (ringworld.nanolink.com [195.24.48.13]) by hub.freebsd.org (Postfix) with SMTP id EE2AC37B403 for ; Tue, 3 Jul 2001 01:05:14 -0700 (PDT) (envelope-from roam@orbitel.bg) Received: (qmail 34861 invoked by uid 1000); 3 Jul 2001 08:09:40 -0000 Date: Tue, 3 Jul 2001 11:09:40 +0300 From: Peter Pentchev To: Dan Larsson Cc: kris@FreeBSD.org, freebsd-ports@FreeBSD.org Subject: Re: ports/25155: `ASSERTION FAILED' errors with security/pgp6 on FreeBSD-4.2 STABLE Message-ID: <20010703110940.B28604@ringworld.oblivion.bg> Mail-Followup-To: Dan Larsson , kris@FreeBSD.org, freebsd-ports@FreeBSD.org References: <200107021952.f62Jqi119478@freefall.freebsd.org> <20010703082910.G23720-100000@hq1.tyfon.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010703082910.G23720-100000@hq1.tyfon.net>; from dl@tyfon.net on Tue, Jul 03, 2001 at 08:30:01AM +0200 Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Tue, Jul 03, 2001 at 08:30:01AM +0200, Dan Larsson wrote: > On Mon, 2 Jul 2001 kris@FreeBSD.org wrote: > > | Synopsis: `ASSERTION FAILED' errors with security/pgp6 on FreeBSD-4.2 STABLE > | > | State-Changed-From-To: suspended->closed > | State-Changed-By: kris > | State-Changed-When: Mon Jul 2 12:52:14 PDT 2001 > | State-Changed-Why: > | No response from submitter > | > | http://www.FreeBSD.org/cgi/query-pr.cgi?pr=25155 > > What does this notice mean? On March 22nd, Kris Kennaway changed this PR's state from 'open' to 'suspended' with the following message: State-Changed-From-To: open->suspended State-Changed-By: kris State-Changed-When: Thu Mar 22 11:53:04 PST 2001 State-Changed-Why: Not sure exactly what you hope us to do with this: you haven't given any insight on how to replicate the problem, and besides it's not usually the job of the FreeBSD Ports team to fix bugs in ported software: that's what software vendors are for :-) Unless you can show that this is brokenness within the FreeBSD port and indicate (at the very least) how to replicate it, this issue should be taken up with the PGP authors. Apparently, you never responded with reasons why you think this is a problem with the FreeBSD port, and not with PGP per se; so Kris closed the PR. G'luck, Peter -- The rest of this sentence is written in Thailand, on To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message