From owner-freebsd-questions@FreeBSD.ORG Fri Oct 28 01:32:41 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org 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 8B3C116A41F for ; Fri, 28 Oct 2005 01:32:41 +0000 (GMT) (envelope-from john.destefano@gmail.com) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.197]) by mx1.FreeBSD.org (Postfix) with ESMTP id C9B6343D49 for ; Fri, 28 Oct 2005 01:32:40 +0000 (GMT) (envelope-from john.destefano@gmail.com) Received: by xproxy.gmail.com with SMTP id t8so137408wxc for ; Thu, 27 Oct 2005 18:32:40 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=my9u//GDCFLFRPRKz2AsA2uNQ0B43UdRDrD0bDOD4cvW0VUj0UAPFuXO0ht946nuy9JXsy1ypIAVazwbipr+MqAuiJVrJIeepqFfGxeYdt7US0TAZooTC+WnKs1dHPcX/mw0sX+xKeyc0m05yH/i+raMW7lU/LhZ2ruCDmmyg6U= Received: by 10.65.231.8 with SMTP id i8mr2049250qbr; Thu, 27 Oct 2005 18:32:40 -0700 (PDT) Received: by 10.65.154.4 with HTTP; Thu, 27 Oct 2005 18:32:40 -0700 (PDT) Message-ID: Date: Thu, 27 Oct 2005 21:32:40 -0400 From: John DeStefano To: freebsd-questions@freebsd.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: Subject: Re: portupgrade stale dependencies 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: Fri, 28 Oct 2005 01:32:41 -0000 On 10/27/05, Andrew P. wrote: > On 10/27/05, John DeStefano wrote: > > > > After clearing out the ports, updating ports (with portsnap) and > > source, and rebuilding the system and kernel... it seemed the ultimate > > problem was actually a dependency of the package to apache1.3. After I > > ran 'pkgdb -F' and "fixed" this dependency to point to apache2.1, but > > I still had trouble installing ports. > > > > 'portsdb -Uu' would not run, so I ran 'make fetchindex' and > > 'portupdate -a'. From what I've read, this _should_ create an index > > and update all out-of-date ports and their dependencies, but it never > > has worked for me. I just tried this combination again, and it > > (again) punts during portupdate. This time, 38 ports were skipped and > > 7 failed, the first failure being a strange compiler error in updating > > from apache-2.0.48. > > > > I've been fighting with ports for long enough now to have become a bit > > frustrated with them. If you have any thoughts or suggestions on how > > to troubleshoot them, please pass them on. > > > > Thanks, > > ~John > > > > Do not fix dependencies if you're not sure that they > are really broken. Don't use apache21 unless 2.0 > is absolutely inappropriate. The proper way to change > dependencies from apache1 to apache2 is to add > "WITH_APACHE2=3Dtrue" to /etc/make.conf (or to > /usr/local/etc/pkgtools.conf, but that's an advanced > topic). I wasn't really looking to upgrade to apache21, just to update my version (2.0.48) to any more current port, since other ports keep barking about it being out-of-date. I added the "WITH_APACHE2=3Dtrue" parameter, but when I try to upgrade my apache port, it seems to still be looking to the "wrong" version: ...Upgrading 'apache-2.0.48' to 'apache-2.1.4' (www/apache21) This process attempts to build and then consistently fails with the same error, which seems to my untrained eye like a C function error in httpd: ssl_engine_pphrase.c: In function `ssl_pphrase_Handle_CB': ssl_engine_pphrase.c:684: error: `PEM_F_DEF_CALLBACK' undeclared (first use in this function) ssl_engine_pphrase.c:684: error: (Each undeclared identifier is reported only once ssl_engine_pphrase.c:684: error: for each function it appears in.) *** Error code 1 Stop in /usr/ports/www/apache21/work/httpd-2.1.4-alpha/modules/ssl. *** Error code 1 Stop in /usr/ports/www/apache21/work/httpd-2.1.4-alpha/modules/ssl. *** Error code 1 Stop in /usr/ports/www/apache21/work/httpd-2.1.4-alpha/modules. *** Error code 1 Stop in /usr/ports/www/apache21/work/httpd-2.1.4-alpha. *** Error code 1 Stop in /usr/ports/www/apache21/work/httpd-2.1.4-alpha. *** Error code 1 Stop in /usr/ports/www/apache21. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade38050.3 make ** Fix the problem and try again. Apparently, this is an OpenSSL-related bug, and there's a "patch" availavble for it somewhere Is there a way to fix this without applying a patch? > If you have portsdb utility, don't use make fetchindex, > just add -F to portsdb: "portsdb -uUF" will work fine. "portsdb -uU" wasn't working for me for a while, but I finally got it going last night. Kris maintained that I should use "make fetchindex" instead of "portsdb -uU" before running "portupgrade -a", at least until my package installation dependencies were in better condition, at which time I could resume using "portsdb -uU". Problem is, "portupgrade -a" still isn't working to update all installed packages (most, but not all), regardless of whether it is preceded by "portsdb -uU" or "portupgrade -a". > You cann add -k to portupgrade, so that it doesn't > skip ports (but it won't fix the failed ones). > > John, you'll have to spend a few hours reading > ports documentation before you find them really > great (which they really are). I have no problem with reading as much documentation as I can find. Aside from the handbook (Chapter 4, which is a nice overview) and man pages (which are great for quick and complete reference), what else would you recommend for gaining a more detailed understanding? And I do already agree that the port system is great, even with all the trouble I'm having. Thanks. ~John