Date: Wed, 09 Jan 2013 12:26:46 +0000 From: Matthew Seaman <matthew@freebsd.org> To: freebsd-ports@freebsd.org Subject: Re: portupgrade/portversion and detecting lower versions Message-ID: <50ED6206.8040907@freebsd.org> In-Reply-To: <20130109130701.Horde.04qRvYW-EppBXlzb5GrM8A5@avocado.salatschuessel.net> References: <20130109130701.Horde.04qRvYW-EppBXlzb5GrM8A5@avocado.salatschuessel.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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=
Cheers,
Matthew
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?50ED6206.8040907>