Date: Mon, 12 Mar 2012 11:54:41 -0700 (PDT) From: Jakub Lach <jakub_lach@mailplus.pl> To: freebsd-ports@freebsd.org Subject: Re: portaudit pubkey Message-ID: <1331578481212-5558739.post@n5.nabble.com> In-Reply-To: <4F5E42F9.809@FreeBSD.org> References: <1331544507726-5557072.post@n5.nabble.com> <4F5DCD20.4050707@infracaninophile.co.uk> <1331575594146-5558587.post@n5.nabble.com> <4F5E42F9.809@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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. best regards, - Jakub Lach -- View this message in context: http://freebsd.1045724.n5.nabble.com/portaudit-pubkey-tp5557072p5558739.html Sent from the freebsd-ports mailing list archive at Nabble.com.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1331578481212-5558739.post>