From owner-freebsd-questions@FreeBSD.ORG Sun Jan 15 15:33:36 2012 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 635A8106566B for ; Sun, 15 Jan 2012 15:33:36 +0000 (UTC) (envelope-from jerry@seibercom.net) Received: from mail-yx0-f182.google.com (mail-yx0-f182.google.com [209.85.213.182]) by mx1.freebsd.org (Postfix) with ESMTP id 151368FC0C for ; Sun, 15 Jan 2012 15:33:35 +0000 (UTC) Received: by yenl12 with SMTP id l12so935803yen.13 for ; Sun, 15 Jan 2012 07:33:35 -0800 (PST) Received: by 10.236.128.242 with SMTP id f78mr12419288yhi.7.1326641615320; Sun, 15 Jan 2012 07:33:35 -0800 (PST) Received: from scorpio.seibercom.net (cpe-076-182-104-150.nc.res.rr.com. [76.182.104.150]) by mx.google.com with ESMTPS id o27sm41668412ani.17.2012.01.15.07.33.33 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 15 Jan 2012 07:33:34 -0800 (PST) Received: from scorpio (localhost [127.0.0.1]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: jerry@scorpio.seibercom.net) by scorpio.seibercom.net (Postfix) with ESMTPSA id 3TR1th5PBpz2CG4h for ; Sun, 15 Jan 2012 10:33:32 -0500 (EST) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.97.3 at scorpio.seibercom.net Date: Sun, 15 Jan 2012 10:33:32 -0500 From: Jerry To: FreeBSD Message-ID: <20120115103332.09d5f2ca@scorpio> In-Reply-To: <40F552CF734E955EB7878763@mac-pro.magehandbook.com> References: <40F552CF734E955EB7878763@mac-pro.magehandbook.com> Organization: seibercom.net X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.6; amd64-portbld-freebsd8.2) Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAHlBMVEUAAABYRlwJCw4FAgAIBwKprDkBAQFQLR0BAgCir7VRttp8AAACAUlEQVQ4jZWUTYvbMBCGTVl8V2hX6Gg5G5FbWQdBj0lEfE7BhN4cyzi5Wt1E5L70roWy6N92xok/skkP+5IYrMcz78xIduDWpNM3vFzuA/jX5EY1AI6KHFwW/CzFuQAwqUBbV12p+CzIh6Awq7sg33pn5D64SQXAexffeuQlA/L35RrkaB551OjGfP/cAO8mCNaDcgvfky5ijoD0pAXlCQCnljiAjsJD9Ax05Ko5sZxbnLQcmM+dZg5IjREfZrWIHK0JuwU68pAGwHvfRxBundRzTxxz3r9dNUikPsEihjz2Dc4kjp1hKsJGuot4EDxaxzMoC7XqhxhOSfZrTS6gSX1JVdjp+o1PvWfekXgw3WL0g70nDEwA0H0HQsEZc8sTmFMTkWUfYWC/vdR1zQy3xLQgLwzu90QnlnFLjeiGWBjwhb4Sa42IqOg2qqS4O1/zhKokFUb1Q8Rj4Eb69WVflXEehJ35DgChVTE5n50eaGyMLOfH8AOodoSM4PVYAQgQdBulOa+knklYks3vAuQ+uX492lTl+A+e8qBV2AKoXalVKFfyuUp0pUp1ARaUHh82lv9MN+Ig7CZtgE6FNYvjlywT2VP2dMgOG46gTIWcqdfvuwyXNz0oMJNd/N5lh1YNiJt19ADTUo3VuFSNeQwVqRSrGjSCp53fk2g+Mvfk/gfoPxHeUS8MH9vRAAAAAElFTkSuQmCC Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Subject: Re: Portmanager Status Report Gone X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: FreeBSD List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Jan 2012 15:33:36 -0000 On Sun, 15 Jan 2012 10:09:06 -0500 Daniel Staal articulated: > I was trying out portmaster to see if it worked better than my > current tool of choice for keeping my ports up to date (portmanager) > and when I went back to portmanager I can no longer get it to give me > a 'Port Status Report', or to update anything. It just collects the > installed port data, and stops. > > Any ideas on what I may have messed up? I'd like to upgrade my ports > to the latest versions before upgrading to 9.0 (and I'd want > portmanager working afterwards to help me fix any port-related > problems that come up.) I'm on 8.2. Exactly how are you invoking "portmanager"? Usually, just give it it the "-s" flag will get you a list of port and there status as you probably know. If you just want to update everything before updating FreeBSD itself, I would suggest running it as: "portmanager -u -l -p -y" Obviously, update your ports tree prior to running that command. At the very least, you will end up with a log file telling you what failed to update properly. I use portmanager myself because it "just works" when other port management tools fail. -- Jerry ♔ Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __________________________________________________________________