New version of subversion and apache2 not indicated?

[Ryan Schmidt]

On Dec 23, 2008, at 12:14, Chris Janton wrote:

> I may just be confused.
>
> I'm running from trunk.
>
> I did my typical svn update / build
>
> I get the following results from my check for new versions of  
> things. I expect to see subversion and apache2 (upgraded on a  
> system running 1.7, not from trunk)
>
> mac 17 # port outdated
> No installed ports are outdated.
> mac 18 # port info subversion
> subversion @1.5.5 (devel)
[snip]
> mac 19 # port installed | grep subversion
>   subversion @1.5.4_0+bash_completion+mod_dav_svn+no_bdb+tools  
> (active)
>
> So, shouldn't I have a needed upgrade to subversion?
>
> Same for apache2?
>
> mac 20 # port installed | grep apache2
>   apache2 @2.2.10_0+darwin_9 (active)
>   php5 @5.2.8_0+apache2+macosx+mysql5+pear (active)
> mac 21 # port info apache2
> apache2 @2.2.11 (www)
[snip]

The only reason I can think of why the ports would not be shown as  
outdated is if your PortIndex was not up to date. Try "port sync" one  
more time. subversion and apache2 did show as outdated for me recently.