Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 15 Aug 2009 20:33:37 +0100
From:      "N.J. Mann" <njm@njm.me.uk>
To:        Thomas Backman <serenity@exscape.org>
Cc:        Doug Barton <dougb@FreeBSD.org>, Miroslav Lachman <000.fbsd@quip.cz>, freebsd-ports@FreeBSD.org
Subject:   Re: portversion and pkg_version have different opinions on current versions
Message-ID:  <20090815193336.GA79191@titania.njm.me.uk>
In-Reply-To: <6B5B7698-CCD8-48FF-A5FB-0349D4CC1143@exscape.org>
References:  <B787D58E-9157-48E7-ADF3-E8D54F8AF22F@exscape.org> <4A86FF1E.1030705@quip.cz> <6B5B7698-CCD8-48FF-A5FB-0349D4CC1143@exscape.org>

next in thread | previous in thread | raw e-mail | index | archive | help
In message <6B5B7698-CCD8-48FF-A5FB-0349D4CC1143@exscape.org>,
	Thomas Backman (serenity@exscape.org) wrote:
> 
> On Aug 15, 2009, at 20:31, Miroslav Lachman wrote:
> > Thomas Backman wrote:
> > [...]
> >> [root@chaos ~]# pkgdb -aF
> >> --->  Checking the package registry database
> >> [root@chaos ~]# portversion -l '<'
> >> dnsmasq                     <
> >> ezm3                        <
> >> libtool                     <
> >> python26                    <
> >> [root@chaos ~]# pkg_version | awk '$2 !~ /=/'
> >> [root@chaos ~]# portupgrade -a
> >> [root@chaos ~]#
> > [...]
> >
> > As was mentioned, you can use pkg_version -L =, or you can compare  
> > it with INDEX.db instead of ports tree: pkg_version -IL =. This is  
> > significantly faster.
> >
> > pkg_version -L =
> > Usr: 7.286s  Krnl: 3.984s  Totl: 0:31.77s
> >
> > pkg_version -IL =
> > Usr: 0.195s  Krnl: 0.015s  Totl: 0:00.21s
> >
> > And if you want to know the version of newer (available) port, you  
> > can use pkg_version -vIL =
> > It gives you something like this:
> >
> > png-1.2.35                   <   needs updating (index has 1.2.38)
> > postfix-2.5.6,1              <   needs updating (index has 2.6.3,1)
> > vim-lite-7.2.209             <   needs updating (index has 7.2.239)
> >
> > Miroslav Lachman
> Thanks, guys!
> However, a new issue appeared... Kind of. I know I read something  
> about portsnap and INDEX on the -current list recently, so I'm  
> guessing this is related? Maybe not, though (see later in the mail).
[...]

I am not familiar with portsnap - I use CVS (and SVN) because I like to
have ports, src, doc and www locally, just in case...  Be that as it
may, you can always do a

make index

to rebuild the INDEX-* file.


Cheers,
       Nick.
-- 




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090815193336.GA79191>