From owner-freebsd-questions@FreeBSD.ORG Mon Feb 21 05:06:16 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3931716A4CE for ; Mon, 21 Feb 2005 05:06:16 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.199.47.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id D977F43D55 for ; Mon, 21 Feb 2005 05:06:15 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id AB987512F2; Sun, 20 Feb 2005 21:06:14 -0800 (PST) Date: Sun, 20 Feb 2005 21:06:14 -0800 From: Kris Kennaway To: Eric Schuele Message-ID: <20050221050614.GA9135@xor.obsecurity.org> References: <42196AF5.9030302@computer.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="gKMricLos+KVdGMg" Content-Disposition: inline In-Reply-To: <42196AF5.9030302@computer.org> User-Agent: Mutt/1.4.2.1i cc: FreeBSD Questions Subject: Re: Trouble with upgrading ports... X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Feb 2005 05:06:16 -0000 --gKMricLos+KVdGMg Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Feb 20, 2005 at 11:00:37PM -0600, Eric Schuele wrote: > Hello, >=20 > I am having difficulty upgrading ports on all my freebsd 5.3-stable=20 > machines. They all have been cvsup'd and built within the last few days. >=20 > But for the last week, maybe two... something strange has been (not)=20 > happening. Portversion no longer correctly reports what ports need=20 > updating. But if I do a 'portupgrade -arR', the appropriate things get= =20 > upgraded.... and then later it says they 'succeed' the port!?! It feels= =20 > like the INDEX is not getting update at all, or something. Correct: the machine that builds fetchindex hasn't been getting cvs updates since last week some time. I'm in the process of trying to fix this. In the meantime, you can build your own index ('make index') if you need to update, but this is quite resource-intensive. Kris --gKMricLos+KVdGMg Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFCGWxGWry0BWjoQKURAsPSAKCPYxGBVM/mstH8B42fb69iTj+i2wCfa/cv 3ukg7khdHpSi3CQazyNLCcg= =3vXq -----END PGP SIGNATURE----- --gKMricLos+KVdGMg--