portversion and pkg_version have different opinions on current versions

[Thomas Backman]

First off: not subscribed to this list, please make sure to Cc me or I  
won't see your answers! :)

Oh, and I use portsnap, in crontab:
0 19 * * *  portsnap -I cron update

So, long story short:

[root at chaos ~]# pkgdb -aF
--->  Checking the package registry database
[root at chaos ~]# portversion -l '<'
dnsmasq                     <
ezm3                        <
libtool                     <
python26                    <
[root at chaos ~]# pkg_version | awk '$2 !~ /=/'
[root at chaos ~]# portupgrade -a
[root at chaos ~]#

... How do I figure out which is correct, and which/what should I use  
in my crontab to check for out-of-date packages? I'm pretty new to  
FreeBSD (testing use since May, but I've used it briefly before), but  
have almost 10 years of Linux experience, mostly Gentoo, so I'm not  
new to *nix-like OS's, not to mention that Gentoo's portage is based  
on FreeBSD ports - except that it has an official interface (i.e.  
emerge), rather than portupgrade, portmaster, portmanager, etc. A bit  
of a mess in my outsider opinion. ;)

I don't care overly much about having the bleeding-edge version, but  
I'd rather not, as I currently have, use packages with known  
vulnerabilities (I do know about portaudit, though, and will give that  
a check). For instance, I just noticed yesterday that I needed to  
upgrade apr, among about 6-7 other packages; the apr vulnerability had  
been known for a while before I updated.

Regards,
Thomas