Date: Fri, 28 Oct 2005 16:39:04 -0500 From: Eric F Crist <ecrist@secure-computing.net> To: John DeStefano <john.destefano@gmail.com> Cc: freebsd-questions@freebsd.org Subject: Re: portupgrade stale dependencies Message-ID: <6FB767AE-D4D7-4C38-90C0-726D48AF5654@secure-computing.net> In-Reply-To: <f2160e0d0510281330g4d12c1fexb7c4baadc2c85a65@mail.gmail.com> References: <f2160e0d0510151746n28cdbb25s2150337c0c6f7cfc@mail.gmail.com> <200510271904.17908.ringworm01@gmail.com> <f2160e0d0510280553v27f96396o1314f7ed317c8fe@mail.gmail.com> <200510280640.04025.ringworm01@gmail.com> <f2160e0d0510281330g4d12c1fexb7c4baadc2c85a65@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> status report finished > ====================================================================== > == > percentDone-=>0 = 100 - ( 100 * ( QTY_outOfDatePortsDb-=>1 / > TOTAL_outOfDatePortsDb-=>1 ) ) > upgrade 0.3.0_0 info: ignoring apache-2.0.48, reason: failed during > (2) make > ---------------------------------------------------------------------- > -- > update of ports collection complete with either some errors, ignored > ports or both > > > Unfortunately, this is the most crucial of all, and ironically the one > about which I've been asking since the beginning. As I mentioned > earlier, upgrading this port bails consistently with a C callout to > PEM_F_DEF_CALLBACK. I'd really like to get this port updated, not > only to finally complete this insane goose chase of updating, but > because I know that apache-2.0.48 is chock full of vulerabilities. > > > cd /usr/ports/www/apache20 && make deinstall && make clean && make reinstall See what happens. ----- Eric F Crist Secure Computing Networks http://www.secure-computing.net
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6FB767AE-D4D7-4C38-90C0-726D48AF5654>