From owner-freebsd-ports@FreeBSD.ORG  Fri Apr 10 18:13:46 2009
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: freebsd-ports@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 06D72106564A
	for <freebsd-ports@freebsd.org>; Fri, 10 Apr 2009 18:13:46 +0000 (UTC)
	(envelope-from kstewart@owt.com)
Received: from smtp.owt.com (smtp.owt.com [64.146.239.50])
	by mx1.freebsd.org (Postfix) with ESMTP id CE2728FC1B
	for <freebsd-ports@freebsd.org>; Fri, 10 Apr 2009 18:13:45 +0000 (UTC)
	(envelope-from kstewart@owt.com)
Received: from kstewart2.owt.com (kstewart2.owt.com [64.146.237.228])
	(authenticated bits=0)
	by smtp.owt.com (8.13.8/8.13.8) with ESMTP id n3AIDiSH008963;
	Fri, 10 Apr 2009 11:13:44 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=owt.com; s=default;
	t=1239387225; bh=CWQxxr4mt7HN5GQJ2ksg2bvuCeadC5EC7/iM1qVoJU0=;
	h=From:To:Subject:Date:References:In-Reply-To:MIME-Version:
	Content-Type:Content-Transfer-Encoding:Message-Id; b=bma0QgG2dAbLY
	CUrvR5U2n290PWD6wo4Oe8ptEzLhh/+L43dEm3YnWppYK3CxZqHJIbe0I3AoBYeDc6y
	YIZ97CYLCV280tWiz0b545DOiwezcNPNRhEWbefF59hZe628e5VixooPh/u02KeqUkv
	cEOnj9OwmMfJABOlJmJLsUII=
From: Kent Stewart <kstewart@owt.com>
To: freebsd-ports@freebsd.org, Parv <parv@pair.com>
Date: Fri, 10 Apr 2009 11:13:42 -0700
User-Agent: KMail/1.9.10
References: <b79ecaef0904080551x74c80227h1a4ba5d2adcca905@mail.gmail.com>
	<20090410125733.GA3645@holstein.holy.cow>
	<ef8c8a880904100603tc78eeb4p35d64041787a46c@mail.gmail.com>
In-Reply-To: <ef8c8a880904100603tc78eeb4p35d64041787a46c@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Message-Id: <200904101113.43891.kstewart@owt.com>
Cc: 
Subject: Re: Portupgrade still broken?
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: Fri, 10 Apr 2009 18:13:46 -0000

On Friday 10 April 2009 06:03:54 am Torfinn Ingolfsen wrote:
> Hi,
>
> On Fri, Apr 10, 2009 at 2:57 PM,  <parv@pair.com> wrote:
> > What was the last working version? =A0It would be simpler for this
> > Ruby simpleton to generate a patch than to debug through the
> > stack trace.
>
> FWIW, my current workaround for thi problem is to portdowngrade to the
> latest portupgrade 2.4.3
> portupgrade-2.4.3_2,2 is working.
>
> HTH

I looked at the timeline using cvsweb.cgi and I think the change to the -R=
=20
option in 2.4.3 to "Exclude up-to-date packages" is when it stopped working=
=20
for me at times. I thought it was a mismatch between versions of the ruby=20
ports. I would force rebuild -fR portupgrade and it would go away. With the=
=20
changes to the port system between 4 and 6 April 2009, I could make it fail=
=20
100% trying to -rR libxcb.=20

The machine that had the archive of email I had sent in 2008 died. Now, it=
=20
looks like there is something that is being stomped on when you have too ma=
ny=20
dependancies. I looked at the version on my system but I don't speak Ruby :=
).

Kent

=2D-=20
Kent Stewart
Richland, WA

http://users.owt.com/kstewart/index.html