Date: Mon, 26 Nov 2012 07:30:51 +0000 From: Matthew Seaman <matthew@FreeBSD.org> To: Tim Daneliuk <tundra@tundraware.com> Cc: freebsd-questions@freebsd.org Subject: Re: When Is The Ports Tree Going To Be Updated? Message-ID: <50B31AAB.6000903@FreeBSD.org> In-Reply-To: <50B2BEE1.9030903@tundraware.com> References: <50B2A57A.3050500@tundraware.com> <50B2A8D8.90301@FreeBSD.org> <50B2AA07.8090103@tundraware.com> <201211251856.40381.lumiwa@gmail.com> <50B2BEE1.9030903@tundraware.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig723C70F5461EB3ACB219252E Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 26/11/2012 00:59, Tim Daneliuk wrote: >> I use portsnap fetch update and it works... >=20 > Ah, maybe that was the problem. That works for me as well. >=20 Ummm... how long have you been using portsnap? If you haven't been running 'portsnap fetch' or 'portsnap cron' then you won't have received any updates to your ports tree, ever. This is all explained quite clearly in the portsnap(8) man page. Cheers, Matthew --=20 Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey --------------enig723C70F5461EB3ACB219252E Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.16 (Darwin) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iEYEARECAAYFAlCzGrUACgkQ8Mjk52CukIwlUACZAcH6RaqVdI7u+GfFLodi8NZj Z/sAn1cd8CTeTDZUmVKhEsiDsV8CUL/S =R4UG -----END PGP SIGNATURE----- --------------enig723C70F5461EB3ACB219252E--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?50B31AAB.6000903>