Date: Mon, 12 Mar 2012 15:15:30 -0800 From: Kevin Oberman <kob6558@gmail.com> To: Jakub Lach <jakub_lach@mailplus.pl> Cc: freebsd-ports@freebsd.org Subject: Re: portaudit pubkey Message-ID: <CAN6yY1uKyR3CzHHui_ZePaFK1k8wRwE1sCnt8Sn1VZs4MGW6ug@mail.gmail.com> In-Reply-To: <1331578481212-5558739.post@n5.nabble.com> References: <1331544507726-5557072.post@n5.nabble.com> <4F5DCD20.4050707@infracaninophile.co.uk> <1331575594146-5558587.post@n5.nabble.com> <4F5E42F9.809@FreeBSD.org> <1331578481212-5558739.post@n5.nabble.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Mar 12, 2012 at 10:54 AM, Jakub Lach <jakub_lach@mailplus.pl> wrote: > Thanks for such attention. > > I'm using portsnap with main portsnap server. > >> Even after deleting everything in ports-mgmt/portaudit >> and doing a new csup with the second commit I was >> still getting the above error. > > Exactly. Now, since I've finally found pubkey (I was > looking in wrong places, and yesterday google's 0 hits > with "portaudit.pubkey" didn't help either), I have a > feeling that my problem is over, thanks for help. The easy fix is just 'portaudit -F'. then everything went fine on all of my systems. -- R. Kevin Oberman, Network Engineer E-mail: kob6558@gmail.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAN6yY1uKyR3CzHHui_ZePaFK1k8wRwE1sCnt8Sn1VZs4MGW6ug>