From owner-freebsd-questions@FreeBSD.ORG Sun Jan 20 19:00:43 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4EDEE16A418 for ; Sun, 20 Jan 2008 19:00:43 +0000 (UTC) (envelope-from fbsd06+SK=d329cc7e@mlists.homeunix.com) Received: from mxout-04.mxes.net (mxout-04.mxes.net [216.86.168.179]) by mx1.freebsd.org (Postfix) with ESMTP id 31EF313C447 for ; Sun, 20 Jan 2008 19:00:43 +0000 (UTC) (envelope-from fbsd06+SK=d329cc7e@mlists.homeunix.com) Received: from gumby.homeunix.com. (unknown [87.81.140.128]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTP id B0EEDD05B8 for ; Sun, 20 Jan 2008 14:00:39 -0500 (EST) Date: Sun, 20 Jan 2008 19:00:29 +0000 From: RW To: freebsd-questions@freebsd.org Message-ID: <20080120190029.58c9e3b8@gumby.homeunix.com.> In-Reply-To: <16143691-5D0B-4248-84BE-37FBDE40FEA5@mac.com> References: <70F64C4A-51CB-4301-B7C5-200FD8D5BC41@mac.com> <20080120002209.04e18225@gumby.homeunix.com> <16143691-5D0B-4248-84BE-37FBDE40FEA5@mac.com> X-Mailer: Claws Mail 3.0.2 (GTK+ 2.12.5; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: portupgrade: the -P options rarely works X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Jan 2008 19:00:43 -0000 On Sun, 20 Jan 2008 09:49:29 +0100 Giorgio Valoti wrote: >=20 > On 20/gen/08, at 01:22, RW wrote: >=20 > > On Sat, 19 Jan 2008 23:35:42 +0100 > > Giorgio Valoti wrote: > > > >> Hi all, > >> I=E2=80=99ve noticed that using the -P option with portupgrade, which > >> should try to fetch the binary version of a package rarely works. > >> Most of the times it tries to fetch the package from the freebsd > >> site, it fails and then proceed to build it from the sources. > >> While I can expect from to time that a pre-compiled version of a > >> package to be unavailable, it surprises me to see this so many > >> times. > > > > Are you aware that you need to pick-up stable packages, rather than > > release packages, for portupgrade -P to work properly? >=20 > Well, no. What is the way to distinguish between stable and release? Packages are built per branch, but packages for release security branches are not generally updated. So if someone is using, say, 6.2 and wants updated packages, they set the PACKAGESITE variable to fetch 6-Stable packages instead. Try googling for the correct setting.