From owner-freebsd-ports@FreeBSD.ORG Tue Jul 19 13:55:50 2005 Return-Path: X-Original-To: freebsd-ports@freebsd.org Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CF16616A41F for ; Tue, 19 Jul 2005 13:55:50 +0000 (GMT) (envelope-from legalois@acm.org) Received: from smtp4.wanadoo.fr (smtp4.wanadoo.fr [193.252.22.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0E12243D55 for ; Tue, 19 Jul 2005 13:55:49 +0000 (GMT) (envelope-from legalois@acm.org) Received: from me-wanadoo.net (localhost [127.0.0.1]) by mwinf0409.wanadoo.fr (SMTP Server) with ESMTP id 8FF9C1C003BB for ; Tue, 19 Jul 2005 15:55:48 +0200 (CEST) Received: from [192.168.0.4] (ADijon-151-1-107-195.w83-203.abo.wanadoo.fr [83.203.223.195]) by mwinf0409.wanadoo.fr (SMTP Server) with ESMTP id 104741C003A6; Tue, 19 Jul 2005 15:55:47 +0200 (CEST) X-ME-UUID: 20050719135548668.104741C003A6@mwinf0409.wanadoo.fr Message-ID: <42DD0472.7060902@acm.org> Date: Tue, 19 Jul 2005 15:47:30 +0200 From: Jake Lloyd User-Agent: Mozilla Thunderbird 1.0.5 (X11/20050714) X-Accept-Language: en-us, en MIME-Version: 1.0 To: legalois@acm.org References: <42D7AB39.30803@acm.org> In-Reply-To: <42D7AB39.30803@acm.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-ports@freebsd.org Subject: Re: portupgrade problems on 4.x X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: legalois@acm.org List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Jul 2005 13:55:50 -0000 Jake Lloyd wrote: > portupgrade on my two 4.x boxes seems to have gone wrong, starting just > today. The last successful of run of portupgrade (on only one of those > systems) was to upgrade thunderbird on 14.07.2005. But today > #portupgrade > outputs the following: > > [Failed `Inappropriate file type or format'] [Updating the portsdb > in /usr/ports ... - 13190 port entries found > .........1000.........2000.........3000.........4000.........5000.........6000.........7000.........8000.........9000.........10000.........11000........./usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:613: > [BUG] Segmentation fault > ruby 1.8.2 (2004-12-25) [i386-freebsd4] > > Abort (core dumped) > > and, indeed, there is a ruby18.core file of some 10 Mb. > Naturally, the is not upgraded. > > Most mystifying is, there has been change neither to any ruby ports nor > to portupgrade itself, since the most recent uses of the portupgrade. > > Output from relevant pkg_info is as follows: > > # pkg_info | grep ruby > ruby-1.6.8.2004.07.28_1 An object-oriented interpreted scripting language > ruby-1.8.2_4 An object-oriented interpreted scripting language > ruby18-bdb1-0.2.2 Ruby interface to Berkeley DB revision 1.8x with > full featu > ruby18-programmingruby-0.4 The source of the Programming Ruby > ("pick-axe") book in XML > > # pkg_info | grep portupgrade > portupgrade-20041226_5 FreeBSD ports/packages administration and > management tool s > > (ruby-1.6 is on only one system; some cruft i haven't taken time to > clean out, but it hasn't caused any problem, so don't think that's related) > > This problem does *not* appear today on my 5.x system. > > Thanks for any help, advice. > > - Jake > > _______________________________________________ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" > The work-around suggested by Anton Berezen did not fix the problem on these two systems, but following his second suggestion did work - I deinstalled portupgrade, ruby and bdb ports, and reinstalled portupgrade.* I was previously put off opting for the bdb4 back end to portupgrade because of a warning comment from the portupgrade port maintainer about it, some time ago, indicating some 'lack of support' for this option. I don't know what it was about, and may not be true any more. Thanks to everyone who responded to my original post. - Jake *In case anyone else is following this and wants to do the same, remember to delete /var/db/ports/portupgrade/options before (re)installing portupgrade.