From owner-freebsd-ports Sun Sep 8 13:39:45 2002 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 6ED0037B405; Sun, 8 Sep 2002 13:39:40 -0700 (PDT) Received: from gate.volant.org (gate.volant.org [207.111.218.246]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0A77743E42; Sun, 8 Sep 2002 13:39:40 -0700 (PDT) (envelope-from patl+freebsd@volant.org) Received: from 64-144-229-193.client.dsl.net ([64.144.229.193] helo=[192.168.0.13]) by gate.volant.org with asmtp (TLSv1:DES-CBC3-SHA:168) (Exim 3.33 #1) id 17o8qD-000I3D-00; Sun, 08 Sep 2002 13:39:34 -0700 Date: Sun, 08 Sep 2002 13:39:32 -0700 From: Pat Lashley To: Joe Marcus Clarke Cc: ports@FreeBSD.org Subject: Re: [CONCLUSION] What to do about Mozilla Message-ID: <191405408.1031517571@mccaffrey.phoenix.volant.org> In-Reply-To: <1031511512.60099.6.camel@shumai.marcuscom.com> References: <1031382538.46865.1.camel@shumai.marcuscom.com> <3703892704.1031440015@mccaffrey.phoenix.volant.org> <1031465323.644.13.camel@gyros.marcuscom.com> <4150422704.1031478579@mccaffrey.phoenix.volant.org> <1031511512.60099.6.camel@shumai.marcuscom.com> X-Mailer: Mulberry/2.2.1 (Linux/x86 Demo) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="==========1906472324==========" Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org --==========1906472324========== Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline --On Sunday, September 08, 2002 02:58:32 PM -0400 Joe Marcus Clarke=20 wrote: > On Sun, 2002-09-08 at 05:49, Pat Lashley wrote: >> --On Sunday, September 08, 2002 02:08:38 AM -0400 Joe Marcus Clarke >> wrote: >> >> > ... >> > This problem should be fixed now if you make sure the origin pointed = to >> > in your +CONTENTS file is correct. Both pkg_version and portupgrade >> > report no problems on my mozilla laptop, or my mozilla-devel desktop. >> >> I hand edited the +CONTENTS files, but then after a cvsup and index >> rebuild, portversion showed my 1.1 mozilla ports as being downrev of the >> 1.0_2,1 ports. >> And when I upgraded the XFree86 ports to 4.2.0 the recursive update >> downgraded >> my mozilla ports back to 1.0_2,1. >> >> I had written a section outlining how I was only seeing one copy of the >> mozilla ports in the INDEX and what I thought the problem was; but it >> turns out that somehow my INDEX.db was noticably newer than the INDEX >> itself. I've re-cvsupp'd and re-built the indexes and now I see both. >> So I'll retract my claim that the split is unfinished. >> >> >> >> But now I've got the old versions installed; and don't see any clean way >> to upgrade to the new ones. (I do not consider manual pkg_deinstall and >> portinstall to be clean.) I've tweaked the origin in the +CONTENTS >> files; but that doesn't seem to make any difference at this point. (And >> is, I suspect, actually counter-productive.) I have a feeling that no >> matter what I do, I'll wind up with both versions installed... > > Can you explain the "old" and "new" versions. Are you referring to > mozilla-embedded-devel and mozilla-headers-devel If so, I committed a > fix yesterday to correct their split. That may be what you were seeing > previously. I meant the 1.0 versions vs the 1.1 versions. I have all three ports (mozilla, -headers, and -embedded) installed. I had updated them to the 1.1 versions when that change was committed. When you posted that you were backing that out, I avoided further updates until the dust had settled a bit and the -devel versions were available. Then I added '-devel' to the origins of the installed ports. Even then, I did not try to directly update the mozilla ports; they were caught in a -recursive on the XFree86 ports. The unexpected downgrade was probably caused by whatever went silently wrong with the index updates after the cvsup. (There is a small but non-zero probability that I failed to run the 'portsdb --updateindex --update') The oldest files in any of /var/db/pkg/mozilla-* are timestamped Sept 5 5:51 (Pacific time). The portsupgrade would have been started right after the cvsup and (probable) index rebuild. There are no +REQUIRED_BY files in the -headers or -embedded dirs; so manual de-install and re-install should work fine for them. And, rather surprisingly, the only entry for mozilla itself is the flashplugin, which should probably be re-built anyway. Am I correct in believing that the mozilla and mozilla-headers installs should be kept in sync; but need not match mozilla-embedded ? (E.g., Install mozilla-1.1, mozilla-headers-1.1, mozilla-embedded-1.0; but not mozilla-1.1, mozilla-headers-1.0, mozilla-embedded-1.0.) -Pat --==========1906472324========== Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (FreeBSD) iD8DBQE9e7WEncYNbLD8wuMRAir/AJ9YQuqt44RoG7ygUKuXTrXWJVTiPgCeN4w/ q2udeVs9A+nLd/pbULCHKfw= =hIp4 -----END PGP SIGNATURE----- --==========1906472324==========-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message