From owner-freebsd-questions@FreeBSD.ORG Wed Sep 2 13:08:39 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B71421065692 for ; Wed, 2 Sep 2009 13:08:39 +0000 (UTC) (envelope-from kstewart@owt.com) Received: from smtp.owt.com (smtp.owt.com [64.146.239.50]) by mx1.freebsd.org (Postfix) with ESMTP id 8E1B38FC08 for ; Wed, 2 Sep 2009 13:08:39 +0000 (UTC) Received: from kstewart2.owt.com (kstewart2.owt.com [64.146.237.228]) (authenticated bits=0) by smtp.owt.com (8.13.8/8.13.8) with ESMTP id n82D8aG7029338; Wed, 2 Sep 2009 06:08:37 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=owt.com; s=default; t=1251896917; bh=V4QhwQBDArMe0ois5N+pBpPnOj+fskgTCNaF9CmAkvw=; h=From:To:Subject:Date:References:In-Reply-To:MIME-Version: Content-Type:Content-Transfer-Encoding:Message-Id; b=sL/ffnwiNQNFa /Xy1cXRyJIlK3FSSu43lpLe6zDtiMPvDeZUOesh8QX2cujaOOFwutx5a6J6DnUREgdH 3grKh98FPNwFxLu0ITq75cpWdr4Jru8mzYigbgin08p0tz+bpc+KAiYnVEqAHWCGHm9 ulYmxNc/tFJglqArgiig85yA= From: Kent Stewart To: freebsd-questions@freebsd.org, d.forsyth@ru.ac.za Date: Wed, 2 Sep 2009 06:08:36 -0700 User-Agent: KMail/1.9.10 References: <4A9E476D.13800.3D61987B@d.forsyth.ru.ac.za> In-Reply-To: <4A9E476D.13800.3D61987B@d.forsyth.ru.ac.za> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200909020608.36523.kstewart@owt.com> Cc: Subject: Re: portupgrade broken, and apr won't build 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: Wed, 02 Sep 2009 13:08:39 -0000 On Wednesday 02 September 2009 01:22:37 am DA Forsyth wrote: > Hiya all > > Something weird going on with portypgrade (and maybe ports in > general) here. Somewhere between last months upgrade and this month, > portupgrade has started to ignore ports that are reported by > portversion as needing upgrading. The result is I have to force each > one, one at a time. Big schlep. > > For example > > > portversion -v | grep samba > > samba-3.0.35,1 < needs updating (port has 3.0.36,1) > > > portupgrade -vr samba > > ---> Session started at: Wed, 02 Sep 2009 10:18:47 +0200 > ** None has been installed or upgraded. > ---> Session ended at: Wed, 02 Sep 2009 10:18:47 +0200 (consumed > 00:00:00) > > The other thing is that devel/apr will not build. The make stops > with this > ... > checking whether it is safe to define __EXTENSIONS__... yes > checking for library containing strerror... none required > checking whether system uses EBCDIC... no > performing libtool configuration... > ./configure: 9753: Syntax error: word unexpected (expecting ")") > *** Error code 2 > > Stop in /usr/ports/devel/apr. > *** Error code 1 > > Stop in /usr/ports/devel/apr. > > I cvsup every Monday morning. I tried the upgrades last week but got > these failures and decided to wait a week and see if there are fixes. > Apparently not. I also had to manually fix the openssl distfile > (missing MD5 and SH256) so that it would actually download the > missing patch and confirm it. I have never had so much trouble with > the port system, who broke it? <-: > > Any ideas? My experience with portupgrade problems like this is that your INDEX-? and INDEX-?.db aren't being created properly after cvsuping. Portversion doesn't depend on them but portupgrade does. The INDEX-? that you download is always out of date. I use p5-FreeBSD-Portindex to keep them incrementally up todate, which is much faster then building the INDEX from scratch. After awhile, you have a mess and things don't build because the dependencies haven't been built. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html