Date: Thu, 15 Jan 2004 17:12:27 +0000 From: Matthew Seaman <m.seaman@infracaninophile.co.uk> To: "Scott I. Remick" <scott@sremick.net> Cc: freebsd-questions@freebsd.org Subject: Re: Problems using portupgrade to recompile all ports Message-ID: <20040115171227.GB26860@happy-idiot-talk.infracaninophile.co.uk> In-Reply-To: <1lwz10b51pvyx$.iwa53nx2kix.dlg@40tude.net> References: <1lwz10b51pvyx$.iwa53nx2kix.dlg@40tude.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--at6+YcpfzWZg/htY
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Thu, Jan 15, 2004 at 10:03:31AM -0500, Scott I. Remick wrote:
> So... my ultimate question is: how do you pros handle situations like thi=
s?=20
> Is there a trick I'm missing?
Work out what went wrong, fix it and then just run:
# portupgrade -af '<2004-01-15'
which does a forced update of all packages installed before the given
date. (Note: -R and -r are unnecessary with -a). Rinse,
repeat. Until all your ports are up to date.
Usually ports problems are either inability to download the required
distfiles or a temporary SNAFU by the port maintainer/committer. In
most cases it suffices to wait a few hours or days, re-cvsup the ports
tree and start the portupgrade job again.
Cheers,
Matthew
--=20
Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks
Savill Way
PGP: http://www.infracaninophile.co.uk/pgpkey Marlow
Tel: +44 1628 476614 Bucks., SL7 1TH UK
--at6+YcpfzWZg/htY
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (FreeBSD)
iD8DBQFABsn7dtESqEQa7a0RAoBLAJ9g1DO7LWVNPzMOH3t0JXiFGvho7ACeIq3X
2M5l0s71QXhfzg5wP2f2vck=
=L6zn
-----END PGP SIGNATURE-----
--at6+YcpfzWZg/htY--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040115171227.GB26860>