From owner-freebsd-ports@FreeBSD.ORG Sun Aug 24 10:28:29 2014 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 10408F3 for ; Sun, 24 Aug 2014 10:28:29 +0000 (UTC) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C400D3E8C for ; Sun, 24 Aug 2014 10:28:28 +0000 (UTC) Received: from pi by home.opsec.eu with local (Exim 4.82 (FreeBSD)) (envelope-from ) id 1XLV2A-000MsT-W0 for freebsd-ports@freebsd.org; Sun, 24 Aug 2014 12:28:26 +0200 Date: Sun, 24 Aug 2014 12:28:26 +0200 From: Kurt Jaeger To: ports-list freebsd Subject: Re: HEADS UP: Berkeley DB 4...4.7 port removals/upgrades may require manual preparation Message-ID: <20140824102826.GB9400@home.opsec.eu> References: <53F640EF.7000200@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <53F640EF.7000200@FreeBSD.org> X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Aug 2014 10:28:29 -0000 Hi! > If you have further questions, please ask them on the freebsd-ports@ > mailing list, and feel free to Cc: me, but do make sure your mailer does > not break threading, and do keep the Subject line intact. For devel/ice: If I run portupgrade, it says: cannot install: no eligible BerkeleyDB version. Requested: 6, incompatible: 40 41 42 43 44 46 47 48 6. Try: make debug-bdb while the makefile says: USE_BDB= 5 INVALID_BDB_VER= 40 41 42 43 44 46 47 48 6 and pkg info | grep ^db says: db48-4.8.30.0_2 The Berkeley DB package, revision 4.8 db5-5.3.28_1 The Oracle Berkeley DB, revision 5.3 db6-6.1.19 The Oracle Berkeley DB, revision 6.1 Any idea on how to fix this ? -- pi@opsec.eu +49 171 3101372 6 years to go !