portupgrade/portversion and detecting lower versions

Matthew Seaman matthew at freebsd.org
Wed Jan 9 12:27:13 UTC 2013

On 09/01/2013 12:07, Oliver Lehmann wrote:
> Hi,
> I regulary use portversion to check if I have outdated ports installed.
> Since some time I'm now getting false matches:
>> portversion -v | grep '<'
> horde-imp-6.0.2             <  needs updating (port has 4.3.11_1,1) (=>
> 'mail/horde3-imp')
> horde-ingo-3.0.1            <  needs updating (port has 1.2.6_1,1) (=>
> 'mail/horde3-ingo')
> horde-kronolith-4.0.2       <  needs updating (port has 2.3.6_1,1) (=>
> 'deskutils/horde3-kronolith')
> Why are they reported and how can I avoid this?

Two possibilities:

i) You've switched to pkgng but portversion still thinks you're using
pkg_tools for whatever reason.

How does the portversion output compare with:

    pkg version -vIL=
    pkg version -vPL=

(the first uses /usr/ports/INDEX-?, the second looks at port directories
un ${PORTSDIR}, which takes a bit longer but is more accurate.)

ii) You're still using the old-stlye pkg_tools, but you've got an
out-of-date INDEX file?  How does the portversion output compare with:

   pkg_version -vIL=
   pkg_version -vL=



More information about the freebsd-ports mailing list