From owner-freebsd-ports@FreeBSD.ORG Thu May 20 00:07:38 2004 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 6597F16A4CE; Thu, 20 May 2004 00:07:38 -0700 (PDT) Received: from smtp02.mrf.mail.rcn.net (smtp02.mrf.mail.rcn.net [207.172.4.61]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4677643D2F; Thu, 20 May 2004 00:07:38 -0700 (PDT) (envelope-from adam.mclaurin@gmx.net) Received: from 146-115-126-186.c3-0.arl-ubr1.sbo-arl.ma.cable.rcn.com ([146.115.126.186] helo=jake) by smtp02.mrf.mail.rcn.net with smtp (Exim 3.35 #7) id 1BQhe2-0001t4-00; Thu, 20 May 2004 03:07:10 -0400 Date: Thu, 20 May 2004 03:07:10 -0400 From: Adam McLaurin To: ports@freebsd.org, kris@obsecurity.org, knu@FreeBSD.org Message-Id: <20040520030710.448ae885.adam.mclaurin@gmx.net> In-Reply-To: <20040520070136.GA62040@xor.obsecurity.org> References: <20040520025535.41b274ac.adam.mclaurin@gmx.net> <20040520070136.GA62040@xor.obsecurity.org> X-Mailer: Sylpheed version 0.9.9-gtk2-20040229 (GTK+ 2.4.1; i386-portbld-freebsd5.2.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: portupgrade misbehavior 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: Thu, 20 May 2004 07:07:38 -0000 On Thu, 20 May 2004 00:01:36 -0700 Kris Kennaway wrote: > On Thu, May 20, 2004 at 02:55:35AM -0400, Adam McLaurin wrote: > > > -# uname -a > > FreeBSD jake 5.2.1-RELEASE-p4 FreeBSD 5.2.1-RELEASE-p4 #0: Tue Mar > > 30 > > 01:07:47 EST 2004 root@jake:/usr/obj/usr/src/sys/ESKI i386 > > > > > > Why the h*ll did portupgrade try to recompile zsh? I can't think of > > any > > logical explanation for this behavior. Perhaps I am missing > > something > > simple here; or perhaps I stumbled across a bug in portupgrade (or > > even > > ruby) ? > > Is your INDEX out of date? portupgrade assumes it is up-to-date and > bases its upgrade decisions on the contents. Compare the output of > portversion and pkg_version. > > Kris -# ls -al /usr/ports/INDEX* -rw-r--r-- 1 root wheel 5089899 May 1 08:57 /usr/ports/INDEX -rw-r--r-- 1 root wheel 4947853 Mar 15 18:20 /usr/ports/INDEX-5 -rw-r--r-- 1 root wheel 10911744 Apr 6 01:21 /usr/ports/INDEX.db Looking at http://www.freshports.org/shells/zsh , the zsh port hasn't been modified since March 23rd, so I should be OK on that front. And portversion does also report that zsh is up-to-date: -# portversion -v |grep -i zsh zsh-4.2.0 = up-to-date with port -- Adam "satyam, shivam, sundaram"