From owner-freebsd-questions@FreeBSD.ORG Sun Oct 24 18:51:13 2004 Return-Path: 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 D19D416A4CF for ; Sun, 24 Oct 2004 18:51:13 +0000 (GMT) Received: from fep2.cogeco.net (smtp.cogeco.net [216.221.81.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9038643D2D for ; Sun, 24 Oct 2004 18:51:11 +0000 (GMT) (envelope-from bbobowski@cogeco.ca) Received: from [24.150.215.98] (d150-215-98.home.cgocable.net [24.150.215.98]) by fep2.cogeco.net (Postfix) with ESMTP id 1B6D6535D; Sun, 24 Oct 2004 14:51:11 -0400 (EDT) Message-ID: <417BF9A6.90409@cogeco.ca> Date: Sun, 24 Oct 2004 14:51:18 -0400 From: Brian Bobowski User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040626 Thunderbird/0.7.1 Mnenhy/0.6.0.104 X-Accept-Language: en-us, en MIME-Version: 1.0 To: John Adams References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: FreeBSD User Questions List Subject: Re: First cvsup in sometime, and now I'm hosed X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Oct 2004 18:51:14 -0000 John Adams wrote: > Hi, folks, > > I ran a cvsup against my supfile, then a portupgrade -a, and now > I'm hosed. For starts, ruby is complaining about an insecure version > of OpenSSL, and will not install, leaving me without, well, portupgrade. > > What have I done to myself, and how do I recover? Is this, by > Hobson's choice, a good time to upgrade from 4.9? What should I > provide to help tell what's going on with my box? > > All the best, > > John A Other people have mentioned what needs to be done in future(reading /usr/*/UPDATING and portupgrade syntax). For now, you're probably going to need to get your hands dirty: go to OpenSSL in the ports tree, do a "make install" there, try again with Ruby... Basically, try to make the new version of portupgrade, and whenever it complains about a different port, go and fix it; you may need to do more than a few "make deinstall && make reinstall" to deal with version changes. Also, you could try pkg_add -r [portname] for some of these to cut down compile time at least until you can get portupgrade back. -BB