From owner-freebsd-ports-bugs@FreeBSD.ORG  Mon Jun 13 06:13:13 2005
Return-Path: <owner-freebsd-ports-bugs@FreeBSD.ORG>
X-Original-To: freebsd-ports-bugs@FreeBSD.org
Delivered-To: freebsd-ports-bugs@FreeBSD.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id DEE7816A41C;
	Mon, 13 Jun 2005 06:13:12 +0000 (GMT)
	(envelope-from linimon@lonesome.com)
Received: from mail.soaustin.net (mail.soaustin.net [207.200.4.66])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 98EC143D49;
	Mon, 13 Jun 2005 06:13:12 +0000 (GMT)
	(envelope-from linimon@lonesome.com)
Received: by mail.soaustin.net (Postfix, from userid 502)
	id B230327AB; Mon, 13 Jun 2005 01:13:11 -0500 (CDT)
Date: Mon, 13 Jun 2005 01:13:11 -0500
To: Patrick Li <pat@FreeBSD.org>
Message-ID: <20050613061311.GA5506@soaustin.net>
References: <200506130500.j5D50WJr065884@freefall.freebsd.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200506130500.j5D50WJr065884@freefall.freebsd.org>
User-Agent: Mutt/1.5.9i
From: linimon@lonesome.com (Mark Linimon)
Cc: freebsd-ports-bugs@FreeBSD.org
Subject: Re: ports/82145: www/mambo missing dep. on devel/php4-pcre
X-BeenThere: freebsd-ports-bugs@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Ports bug reports <freebsd-ports-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports-bugs>, 
	<mailto:freebsd-ports-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports-bugs>
List-Post: <mailto:freebsd-ports-bugs@freebsd.org>
List-Help: <mailto:freebsd-ports-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports-bugs>, 
	<mailto:freebsd-ports-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Jun 2005 06:13:13 -0000

On Mon, Jun 13, 2005 at 05:00:32AM +0000, Patrick Li wrote:
>  Maintainer email bounces. Maybe it's just me.

Hmm, well, the maintainer last submitted an update on June 7th,
so pehaps this is a transient error?