From owner-freebsd-ports@FreeBSD.ORG  Tue Apr 17 16:59:04 2007
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
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 B3E5916A401
	for <freebsd-ports@freebsd.org>; Tue, 17 Apr 2007 16:59:04 +0000 (UTC)
	(envelope-from sem@FreeBSD.org)
Received: from mail.ciam.ru (ns.ciam.ru [213.247.195.75])
	by mx1.freebsd.org (Postfix) with ESMTP id 7210C13C44C
	for <freebsd-ports@freebsd.org>; Tue, 17 Apr 2007 16:59:04 +0000 (UTC)
	(envelope-from sem@FreeBSD.org)
Received: from [87.240.16.199] (helo=[192.168.0.4])
	by mail.ciam.ru with esmtpa (Exim 4.x)
	id 1Hdr2R-000AxB-Ud; Tue, 17 Apr 2007 21:00:20 +0400
Message-ID: <4624FC9B.8000001@FreeBSD.org>
Date: Tue, 17 Apr 2007 20:58:03 +0400
From: Sergey Matveychuk <sem@FreeBSD.org>
User-Agent: Thunderbird 1.5.0.9 (X11/20070124)
MIME-Version: 1.0
To: James <james@hicag.org>
References: <abd3d3c20704170824t607d6d23pae00bfadad0e32@mail.gmail.com>
In-Reply-To: <abd3d3c20704170824t607d6d23pae00bfadad0e32@mail.gmail.com>
Content-Type: text/plain; charset=KOI8-R
Content-Transfer-Encoding: 7bit
Cc: FreeBSD-ports <freebsd-ports@freebsd.org>
Subject: Re: portupgrade -s broken in portupgrade 2.2.6
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Apr 2007 16:59:04 -0000

James wrote:
> hihi.  Is portupgrade -s still supported and/or known to be working in
> portupgrade 2.2.6?  Currently I have two machines using portupgrade
> 2.2.6 all my others are using pre-2.0 versions.  The new machines show
> this problem.  The old ones work fine.
> 

Well, I don't know where this regression has happened but it has. I'll
add a note in my TODO list.

-- 
Dixi.
Sem.