From owner-freebsd-questions@FreeBSD.ORG  Wed Sep  6 22:34:34 2006
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
X-Original-To: freebsd-questions@freebsd.org
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 24FCB16A4E1
	for <freebsd-questions@freebsd.org>;
	Wed,  6 Sep 2006 22:34:34 +0000 (UTC)
	(envelope-from chris@childeric.freeserve.co.uk)
Received: from smtp-out4.blueyonder.co.uk (smtp-out4.blueyonder.co.uk
	[195.188.213.7])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 6C66343D5A
	for <freebsd-questions@freebsd.org>;
	Wed,  6 Sep 2006 22:32:47 +0000 (GMT)
	(envelope-from chris@childeric.freeserve.co.uk)
Received: from [172.23.170.137] (helo=anti-virus01-08)
	by smtp-out4.blueyonder.co.uk with smtp (Exim 4.52)
	id 1GL5wt-0005sO-02
	for freebsd-questions@freebsd.org; Wed, 06 Sep 2006 23:32:47 +0100
Received: from [82.35.115.93] (helo=[192.168.10.60])
	by asmtp-out2.blueyonder.co.uk with esmtpa (Exim 4.52)
	id 1GL5ws-0004Ks-7t
	for freebsd-questions@freebsd.org; Wed, 06 Sep 2006 23:32:46 +0100
Message-ID: <44FF4C89.6070704@childeric.freeserve.co.uk>
Date: Wed, 06 Sep 2006 23:32:41 +0100
From: Chris Whitehouse <chris@childeric.freeserve.co.uk>
User-Agent: Thunderbird 1.5 (X11/20060417)
MIME-Version: 1.0
To: freebsd-questions@freebsd.org
References: <20060905035751.16474.qmail@web53407.mail.yahoo.com>	<44FDE33E.10906@childeric.freeserve.co.uk>
	<20060905174924.60F5.GERARD@seibercom.net>
In-Reply-To: <20060905174924.60F5.GERARD@seibercom.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: Various package/ports problems
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Sep 2006 22:34:34 -0000

Gerard Seibert wrote:
> Chris Whitehouse wrote:
> 
>> Dr. Jennifer Nussbaum wrote:
>>
>>> So now i can find out what version each port is, but that doesnt
>>> help me know whether these are outdated, or to update them.
>>> For that im still stuck on the Ruby core dump problem. I did 
>>> reinstall portupgrade, ruby18, and the ruby-bdb thing, but sadly
>>> i still get the same abort trap/core dump thing ive reported all
>>> along. Is there any other way i can attack this last issue?
>>>
>>> Thanks.
>>>
>>> Jen
>> Have you tried portmanager (sysutils/portmanager)? The -s option just 
>> reports on what's required to upgrade.
> 
> Assuming you have a freshly updated ports tree, you could also just run
> this little command:
> 
>      /usr/sbin/pkg_version -vIL=
> 
> It will display what needs to be updated very quickly. I think that
> 'portmanager' would be the best way to update the ports however.
> 
> 

Very useful and quick, but man pkg_version says the -I interrogates the 
INDEX file which in this case (I've lost previous posts) was corrupted 
or out of sync with the ports tree? In this case portmanager -s might 
give more accurate results even if it is a bit slow.

Chris