Date: Fri, 4 Apr 2014 16:52:37 -0700 From: Anton Afanasyev <aasoft@gmail.com> To: sindrome <sindrome@gmail.com> Cc: "ports@freebsd.org" <ports@freebsd.org>, Robert Huff <roberthuff@rcn.com> Subject: Re: pkgng vs. portupgrade reporting ports outdated Message-ID: <CAEAhP2g62wpojpj4DFDeO2a5zq1bPCEsHKwA0TaXBCt39UOnyQ@mail.gmail.com> In-Reply-To: <000301cf505f$c86f8260$594e8720$@gmail.com> References: <533F36F0.8020803@rcn.com> <000701cf505e$d42d9a20$7c88ce60$@gmail.com> <000301cf505f$c86f8260$594e8720$@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Apr 4, 2014 at 4:44 PM, sindrome <sindrome@gmail.com> wrote: > Here's more information > > foo:107:/home/foobar# pkg update > Updating repository catalogue > > foo:108:/home/foobar# pkg upgrade > Updating repository catalogue > Nothing to do > > Now when I do a 'pkg_version -v|grep needs' I have > pkg_* tools use the old packages database, while the pkg tool uses its own, new, database. After you upgraded to pkgng and started using it for all your package needs, your old database stopped being updated (because the old pkg_* tools aren't being used to install packages anymore). This is why the old pkg_* tools are still reporting old version information - they only see what's in their old database. Anton
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAEAhP2g62wpojpj4DFDeO2a5zq1bPCEsHKwA0TaXBCt39UOnyQ>