portupgrade, packages, and same versions

[David Syphers]

I just upgraded to 5-STABLE from an older version of 5, and wanted to rebuild 
all my ports because of the ABI compatability breakage just before 5-RELEASE. 
I ran across behavior in portupgrade that I don't understand - if I force an 
upgrade because I already have the same version installed, portupgrade 
refuses to use packages. e.g.

--->  Found a package of 'net/cvsup-without-gui': cvsup-without-gui-16.1h.tbz 
(cvsup-without-gui-16.1h)
--->  Located a package version 16.1h (cvsup-without-gui-16.1h.tbz)
** Ignoring the package, which is the same version as is installed (16.1h)
** No package available: net/cvsup-without-gui

What on earth is wrong with portupgrade, and is there any way of convincing it 
to use packages in this case? If I run 'portupgrade -rafP' it will merrily  
upgrade via ports when forcing an upgrade, so why not packages?

Thanks,

-David

-- 
"To get out of the Metaphysical Void, you either have to
grasp the meaning of the universe or roll doubles twice."
 -Cecil Adams