portupgrade stale dependencies

[John DeStefano]

On 10/28/05, Eric F Crist <ecrist at secure-computing.net> wrote:
> > 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.
>

Talk about strange:

# cd /usr/ports/www/apache20/
# make deinstall
===>  Deinstalling for www/apache20
===>   apache not installed, skipping

# make -V PKGNAME
apache-2.0.55

# pkg_info | grep apache
apache-2.0.48       Version 2 of the extremely popular Apache http server

# apachectl -v
Server version: Apache/2.0.48
Server built:   Nov 19 2003 22:44:21