From owner-freebsd-ports@FreeBSD.ORG Mon Jun 4 01:52:24 2007 Return-Path: X-Original-To: freebsd-ports@freebsd.org Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2BCBC16A488 for ; Mon, 4 Jun 2007 01:52:24 +0000 (UTC) (envelope-from parv@pair.com) Received: from mta10.adelphia.net (mta10.adelphia.net [68.168.78.202]) by mx1.freebsd.org (Postfix) with ESMTP id DFE6F13C4DB for ; Mon, 4 Jun 2007 01:52:18 +0000 (UTC) (envelope-from parv@pair.com) Received: from default.chvlva.adelphia.net ([24.126.17.68]) by mta10.adelphia.net (InterMail vM.6.01.05.02 201-2131-123-102-20050715) with ESMTP id <20070604015218.WEMN15873.mta10.adelphia.net@default.chvlva.adelphia.net>; Mon, 4 Jun 2007 01:52:18 +0000 Received: by default.chvlva.adelphia.net (Postfix, from userid 1000) id C9AA9B6B4; Sun, 3 Jun 2007 21:52:54 -0400 (EDT) Date: Sun, 3 Jun 2007 21:52:54 -0400 From: Parv To: Ivan Voras Message-ID: <20070604015254.GA3746@holestein.holy.cow> Mail-Followup-To: Ivan Voras , freebsd-ports@freebsd.org References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Cc: freebsd-ports@freebsd.org Subject: Re: sed errors through portupgrade X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Jun 2007 01:52:24 -0000 (Updated the otherwise highly misleading subject of only "sed errors".) in message , wrote Ivan Voras thusly... > > I've recently started getting these errors while running portupgrade: > > sed: 1: "s|^\(@comment[": unbalanced brackets ([]) > sed: 1: "s|^\(@comment[": unbalanced brackets ([]) > sed: 1: "s|^\(@comment[": unbalanced brackets ([]) > sed: 1: "s|^\(@comment[": unbalanced brackets ([]) > > The above lines are displayed twice: once when portupgrade starts and > once when it finishes. What version of portupgrade is producing the error message? What command did/do you issue? - Parv --