pkgng and portmaster

[Joel Dahl]

On 12-01-2013 14:02, Joel Dahl wrote:
> On 12-01-2013 10:12, Matthew Seaman wrote:
> > On 12/01/2013 09:21, Joel Dahl wrote:
> > > Hi,
> > > 
> > > # pkg version | grep "<"
> > > ca_root_nss-3.14	<
> > > git-1.8.0.2		<
> > > subversion-1.7.7_1	<
> > > 
> > > # portmaster -a
> > > ===>>> All ports are up to date
> > > 
> > > Huh?
> > > 
> > > Running HEAD from Dec 29.
> > > 
> > 
> > pkg version can use any of the ports index, checking the ports tree
> > directly or checking the configured repository catalogue to find out
> > what the current versions of ports are.  If you don't express a
> > preference by using one of the -I -P or -R arguments, then pkg version
> > will check in /usr/ports directly, or failing that, the repository
> > catalogue.
> > 
> > portmaster similarly can use the ports index, or check directly in the
> > ports tree.  Or, in fact, both.  It generally defaults to using the
> > ports index -- although settings in portmasterrc can override this.
> > 
> > So, working hypothesis: your ports index file is out of date.  Update
> > it, or tell portmaster not to use it and portmaster will find the
> > available updates.
> 
> OK. I was under the impression that portsnap would take care of that. I run
> portsnap once every night.
> 
> Anyway, so now I ran portsnap manually and it seems to have rebuilt the INDEX
> files (at least that's what the output indicates).
> 
> Trying portsnap -a still gives me "All ports are up to date" though. I seem to
> be using the tools people recommend these days (portsnap, pkgng, portmaster)
> but I'm obviously doing something wrong.

Looks like I didn't install portmaster with pkgng support on this particular
machine. Problem solved.

-- 
Joel