From owner-freebsd-questions@FreeBSD.ORG Thu Jan 5 18:51:47 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 3E04116A41F for ; Thu, 5 Jan 2006 18:51:47 +0000 (GMT) (envelope-from dennyboy@cableone.net) Received: from S3.cableone.net (s3.cableone.net [24.116.0.229]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9398E43D5E for ; Thu, 5 Jan 2006 18:51:46 +0000 (GMT) (envelope-from dennyboy@cableone.net) Received: from badboybox.cableone.net (unverified [69.92.7.117]) by S3.cableone.net (CableOne SMTP Service S3) with ESMTP id 42011187 for multiple; Thu, 05 Jan 2006 12:14:53 -0700 Date: Thu, 5 Jan 2006 12:51:31 -0600 (CST) From: Denny White To: Dave In-Reply-To: <009401c6119d$9b774360$0900a8c0@satellite> Message-ID: References: <006901c61154$725e1010$0900a8c0@satellite> <43BC2D6A.6090408@voidmain.net> <009401c6119d$9b774360$0900a8c0@satellite> X-GPG-PUBLIC_KEY: http//wwwkeys.nl.pgp.net X-GPG-FINGERPRINT: D0A9 AD44 1F10 E09E 0E67 EC25 CB44 F2E5 1644 E79A MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-NotAscii: charset=us-ascii; X-IP-stats: Incoming Last 2, First 2, in=1, out=0, spam=0 X-External-IP: 69.92.7.117 X-Abuse-Info: Send abuse complaints to abuse@cableone.net Cc: freebsd@voidmain.net, FreeBSD Questions Subject: Re: portupgrade freezing X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Jan 2006 18:51:47 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > ----- Original Message ----- From: "Tom Grove" > To: "Dave" > Cc: > Sent: Wednesday, January 04, 2006 3:17 PM > Subject: Re: portupgrade freezing > > >> Dave wrote: >> >>> Hello, >>> Last portupgrade i did showed portupgrade itself was in need of >>> updating. I ran portupgrade -arR and i got portupgrade v2.01,1, now when i >>> run a portupgrade command the system just sits there. I don't get any >>> output at all. I have uninstalled portupgrade and reinstalled it, no >>> change. Any help welcome. >>> Thanks. >>> Dave. >>> >>> _______________________________________________ >>> freebsd-questions@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-questions >>> To unsubscribe, send any mail to >>> "freebsd-questions-unsubscribe@freebsd.org" >>> >>> >> Do you have to power off the system before it will be responsive again or >> just kill portupgrade? Have you looked through the logs for any messages? >> portupgrade v2.01,1...are you sure; that doesn't seem to correspond with my >> versioning scheme? What does pkg_info say about portupgrade and it's >> version? What does portversion -l "<" say about portupgrade? >> >> -Tom > > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" > On Jan 4 Dave contributed the following: > Hi, > I don't have to kill the system, just portupgrade. When i run portversion > -l "<" it just hangs as well. A pkg_info shows portupgrade version 2.0.1,1. > Dave. > > Been watching this thread. Ran my usual maintenance script which ends up with portversion -l "<" and, if needed, portupgrade -arR and portsclean -DP. It showed portupgrade needed upgrading again from 2.0.0,1 to 2.0.1,1 & upgraded it. Afterward, I had a couple of stale dependencies, but not related to portupgrade. Fixed them. Ran portversion again and, though it wasn't needed, portupgrade, both with no problems. Since, at that point, nothing needed upgrading, I still can't say for sure if the same problem described originally, exists or not on my system, but I'm sure within a couple of days, something will need upgrading. If portupgrade screws up, I'll reply to this thread again. BTW, running FreeBSD_5_4 on an old HP Netserver. I didn't see in this thread what version of FreeBSD the problem was happening on. Wondering if it'd help on the system in question to run portsdb -uUF and pkgdb -fu and try portversion and portupgrade again. Hope some of this helps. Denny White GnuPG key : 0x1644E79A | http://wwwkeys.nl.pgp.net Fingerprint: D0A9 AD44 1F10 E09E 0E67 EC25 CB44 F2E5 1644 E79A -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (OpenBSD) iD8DBQFDvWq6y0Ty5RZE55oRAoSeAKC/Z8c0yK/e2iHkr0IvYpPbJwlCUQCffk1l x7DcHPCiOseg7TQNbDZ9W2I= =lyvH -----END PGP SIGNATURE-----