From owner-freebsd-ports@FreeBSD.ORG Sun May 1 20:23:43 2005 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 67A2816A4CE for ; Sun, 1 May 2005 20:23:43 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.194.102.111]) by mx1.FreeBSD.org (Postfix) with ESMTP id 107AC43D2F for ; Sun, 1 May 2005 20:23:43 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 1D085513A7; Sun, 1 May 2005 13:23:42 -0700 (PDT) Date: Sun, 1 May 2005 13:23:42 -0700 From: Kris Kennaway To: Bjarne Wichmann Petersen Message-ID: <20050501202341.GA29716@xor.obsecurity.org> References: <200504271653.35873.freebsd.nospam@mekanix.dk> <20050427200916.GA38219@xor.obsecurity.org> <200505011046.56630.freebsd.nospam@mekanix.dk> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="cWoXeonUoKmBZSoM" Content-Disposition: inline In-Reply-To: <200505011046.56630.freebsd.nospam@mekanix.dk> User-Agent: Mutt/1.4.2.1i cc: freebsd-ports@freebsd.org cc: Kris Kennaway Subject: Re: Upgrading packages using binaries X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 May 2005 20:23:43 -0000 --cWoXeonUoKmBZSoM Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, May 01, 2005 at 10:46:55AM +0200, Bjarne Wichmann Petersen wrote: > > > My question: is there any way to upgrade packages to the latest avail= able > > > version on the mirrors > > Yes, you're using it. >=20 > In theory, yes. But in practice, no. I've just spend an entire day upgrad= ing=20 > my ports/packages, constantly keeping my eye on portupgrade so I could fi= x=20 > the many stumblingblocks that came during the process.=20 >=20 > Portupgrades "fallback" to download from ../Latest/. Several times the la= test=20 > port didn't meet the version requirement, that portupgrade demanded, so= =20 > portupgrade bails out. I had to build several ports before portupgrade wo= uld=20 > continue with the binary upgrade. >=20 > Less than optimal, and a waste of bandwith, since portupgrade repeatedly= =20 > downloaded "outdated" packages from the mirrors. BTW, this is presumably because you upgraded some of your ports from source recently (to versions newer than those on the ftp site at the time) and then wanted to update the rest from packages. If you'd been using packages only I'd expect it to be satisfied with the packages on the ftp site. > > > and/or a way to cvsup the portstree to the version the > > > binary packages have been built from? > > No, sorry. Usually the -stable packages don't get so far behind, > > except around release time when all the build activity goes there. I > > just finished a build and updated them though, so you should be able > > to retry once your favourite mirror has updated. >=20 > Would it be possible to check the version of the available package=20 > in ../Latest/ BEFORE downloading? Because then one could compare it with = the=20 > local installed version and download and install if it were a newer versi= on? You'd have to talk to the portupgrade author (or submit a patch), although he seems to be MIA. Kris --cWoXeonUoKmBZSoM Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFCdTrNWry0BWjoQKURAmbmAKC2yAewwiqsfRMa9NKiQI2FmExs/QCgq1HL pVk+UPVALC72lgIGKamGI6Y= =ZFDD -----END PGP SIGNATURE----- --cWoXeonUoKmBZSoM--