From owner-freebsd-stable@FreeBSD.ORG Thu Nov 10 17:53:03 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2BC5C16A41F for ; Thu, 10 Nov 2005 17:53:03 +0000 (GMT) (envelope-from ringworm01@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3F0AD43D48 for ; Thu, 10 Nov 2005 17:53:01 +0000 (GMT) (envelope-from ringworm01@gmail.com) Received: by wproxy.gmail.com with SMTP id i5so140910wra for ; Thu, 10 Nov 2005 09:53:01 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:from:to:subject:date:user-agent:references:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:message-id; b=XVX58D95jWYFA/J+yDCgf/XJeflnVT3N5D30RAfebSu1L0lAeWzUGsCRlt8Yzl91wgBDU6MpO7My+WWDJp2AhJTwfuxf97CeUn7Jf+pyfyHcnOxfN8lIi8IDOUBlALYoqxeQ9lEshOhJTy/Qv4AQfZEpJRHIhw1Ex6L3VTNvqrg= Received: by 10.54.154.17 with SMTP id b17mr178718wre; Thu, 10 Nov 2005 09:53:01 -0800 (PST) Received: from ?192.168.1.10? ( [71.102.14.129]) by mx.gmail.com with ESMTP id 14sm1020928wrl.2005.11.10.09.53.00; Thu, 10 Nov 2005 09:53:01 -0800 (PST) From: "Michael C. Shultz" To: "Paul T. Root" , freebsd-stable@freebsd.org Date: Thu, 10 Nov 2005 09:43:29 -0800 User-Agent: KMail/1.8.3 References: <43726E40.3090701@iaces.com> <200511091832.45341.ringworm01@gmail.com> <4373868C.4010108@iaces.com> In-Reply-To: <4373868C.4010108@iaces.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200511100943.30024.ringworm01@gmail.com> Cc: Subject: Re: gnome-upgrade.sh X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Nov 2005 17:53:03 -0000 On Thursday 10 November 2005 09:42, Paul T. Root wrote: > I moved the machine to a DSL line here, and am running > portmanager. It seems to be working. > > We're going to investigate issues with this beta Cisco > ASA machine. I am very interested at how things go with your upgrade, please keep me informed. Just to let you know, the current version of portmanager is 0.3.3_2 if anything goes wrong check that first "portmanager -v". If any problems arise I am more than happy to work with you in solving them quickly. -Mike > > Michael C. Shultz wrote: > > *********************** > > This message has been scanned by the InterScan for CSC-SSM and found to > > be free of known security risks. ***********-*********** > > > > On Wednesday 09 November 2005 18:26, Paul Root wrote: > >>Michael C. Shultz wrote: > >>>*********************** > >>>This message has been scanned by the InterScan for CSC-SSM and found to > >>>be free of known security risks. ***********-*********** > >> > >>port and install or restart gnome-upgrade.sh > >> > >>>>I'm now assuming that since all gnome has been wiped off the > >>>>disk, that the thing to do is build/install the port directly. > >>>>Starting that up, I seem to be having the same downloading > >>>> difficulties. > >>> > >>>As an alternative to gnome-upgrade.sh you may want to consider > >>>using sysutils/portmanager, all you need do is run > >>> > >>>portmanager x11/gnome2 > >>> > >>>It'll do the upgrade no problem, tested it twice now myself. > >> > >>Interesting. The web page said specifically don't do portupgrade. > > > > I didn't say portupgrade, it is sysutils/portmanager > > > >>My main problem is it's having trouble downloading, I think. I'm > >>not sure why. We found problems on our Pix (actually the new > >>ASA firewall) and the port the machine is on. We were getting half > >>duplex, but those are all fixed now. Curiously, command line ftp > >>never has a problem downloading, it's fetch (I think it's using fetch), > >>that can't seem to download. > > > > While your problem has nothing to do with gnome-upgrade.sh, portmanager > > is designed to automatically pickup from where it left off, so stopping > > and starting isn't a problem, and it won't remove a port until its > > replacement is successfully built so if the port didn't fetch you won't > > lose anything, portmanager will just move on to the next port that can be > > upgraded, it is very fail safe. > > > > -Mike > > > > Note: I removed stable@freebsd.org from the return address as it is a > > dupe of freebsd-stable@freebsd.org.