From owner-freebsd-questions@FreeBSD.ORG Sun Feb 5 17:33:43 2006 Return-Path: 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 AE44D16A420 for ; Sun, 5 Feb 2006 17:33:43 +0000 (GMT) (envelope-from gerard@seibercom.net) Received: from smtp4.suscom.net (smtp4.suscom.net [64.78.119.247]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1D01C43D48 for ; Sun, 5 Feb 2006 17:33:43 +0000 (GMT) (envelope-from gerard@seibercom.net) Received: from localhost (unknown [127.0.0.1]) by smtp4.suscom.net (Postfix) with ESMTP id 60B1E15005C for ; Sun, 5 Feb 2006 12:33:41 -0500 (EST) Received: from smtp4.suscom.net ([127.0.0.1]) by localhost (smtp4.suscom.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 20872-01-86 for ; Sun, 5 Feb 2006 12:33:35 -0500 (EST) Received: from seibercom.net (ip148.217.susc.suscom.net [216.45.217.148]) by smtp4.suscom.net (Postfix) with SMTP id 39284150059 for ; Sun, 5 Feb 2006 12:33:35 -0500 (EST) Received: from [192.168.0.4] (boss [192.168.0.4]) by seibercom.net (8.13.4/8.13.4) with ESMTP id k15HXZPB024074 for ; Sun, 5 Feb 2006 12:33:35 -0500 (EST) (envelope-from gerard@seibercom.net) Date: Sun, 05 Feb 2006 12:33:36 -0500 From: Gerard Seibert To: freebsd-questions@freebsd.org Sender: gerard@seibercom.net Organization: Seibercom In-Reply-To: References: <200602042201.00168.duncan.fbsd@gmail.com> X-Face: "\j?x](l|]4p?-1Bf@!wN<&p=$.}^k-HgL}cJKbQZ3r#Ar]\%U(#6}'?<3s7%(%(gxJxxcR nSNPNr*/^~StawWU9KDJ-CT0k$f#@t2^K&BS_f|?ZV/.7Q Message-Id: <20060205122602.7554.GERARD@seibercom.net> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit X-Mailer: Becky! ver. 2.24.01 [en] X-Virus-Scanned: ClamAV 0.88/1277/Sun Feb 5 08:22:21 2006 on seibercom.net X-Virus-Status: Clean X-Virus-Scanned: amavisd-new at suscom.net Subject: Re: Why does portsdb -Uu run so long? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-questions@freebsd.org List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Feb 2006 17:33:43 -0000 Xn Nooby wrote: > > I want to ask you: how long does it take you to cvsup your ports, run > > 'portsdb > > -Uu', and finish with 'portversion -l "<" '? To run 'portsnap fetch > > update', > > then 'portversion -v | grep needs', it took less then 55 seconds and I was > > off upgrading ports. The procedure I used had no errors. > > > I think it takes about 40 minutes to run portsdb -Uu on my normal P4 > desktop, and several hours inside a virtual machine. My old P3 laptop took > 2 hours. Portsnap took about 1 minute, it was very fast. > > "The procedure I used had no errors." > > Everyone that knows what they are doing never seem to have a problem. > Generally people say, "I just did a 'portsnap -AbCdDeF' and it worked > great!", but then it turns out that command was one of many that preceeded > and followed it, which they neglected to mention. > > > Both ways of upgrading work. Neither way will tell you about the conflict > > between pilot-link and libmal. You're going to have to find out about > > during > > an upgrade or, or wait and read about it on the list. So you can't be > > talking > > about that as a problem with portsnap. Just what was the problem you had > > with > > portsnap? > > > I believe I had a "stale dependency with imagemagic" that I chose to "force" > to continue. That was on a brand new install, and it happend twice (I tried > reinstalling). Maybe I can try to recreate it in a VMWare virtual machine > so I can reproduce it. > > I think I also got the ruby error, if that was the one that happend about 1 > year ago. I remember doing an upgrade which broke the system, so I > reinstalled it a few days later. > > Also, is it not possible to make a system that does not have conflicts? > Maybe OS's are simply too complex. It would seem like there should be a way > to kick off a global update and rebuild that started with the core pieces > first, and then moved up the dependency tree level-by-level. Something that > was 100% guaranteed to work, and took 1 command. You could try portmanager 'sysutils/portmanager'. The command: portmanager -u -f -l -y will rebuild all of the installed ports in a logical manner as well as creating a log file for the user to examine if necessary. I would recommend cleaning out /usr/ports/distfiles and then running: portsclean -C -D -DD -L -P -PP prior to running that command. This will ensure that all the crud from previous installations will be removed ensuring a clean start. Just my 2ยข. -- Gerard Seibert gerard@seibercom.net Man invented language to satisfy his deep need to complain. Lily Tomlin