From owner-freebsd-questions@FreeBSD.ORG Mon Feb 12 22:14:06 2007 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B5DD316A401 for ; Mon, 12 Feb 2007 22:14:06 +0000 (UTC) (envelope-from fbsd06@mlists.homeunix.com) Received: from mxout-03.mxes.net (mxout-03.mxes.net [216.86.168.178]) by mx1.freebsd.org (Postfix) with ESMTP id 9294313C471 for ; Mon, 12 Feb 2007 22:14:06 +0000 (UTC) (envelope-from fbsd06@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 7542451979 for ; Mon, 12 Feb 2007 17:14:04 -0500 (EST) Date: Mon, 12 Feb 2007 22:13:57 +0000 From: RW To: freebsd-questions@freebsd.org Message-ID: <20070212221357.7ed10c33@gumby.homeunix.com> In-Reply-To: <45CEF35F.4060707@passagen.se> References: <45CEF35F.4060707@passagen.se> X-Mailer: Claws Mail 2.7.2 (GTK+ 2.10.9; i386-portbld-freebsd6.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: DJBDNS missing from ports? 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: Mon, 12 Feb 2007 22:14:06 -0000 On Sun, 11 Feb 2007 11:43:43 +0100 Roger Olofsson wrote: > Dear Mailing List, > > After a recent buildworld (6.2-STABLE FreeBSD) and portsnap fetch > portversion reported djbdns as being in need of an upgrade, however > portupgrade just exits like so: > > # portupgrade -Rr djbdns-ipv6 > # > > ie, nothing happens. > > A quick locate djbdns | grep ports gave the results that it might be > on the move from ports/dns to ports/net but there are no files for it > in net and the one in dns looks to be the one I have installed. pkg_info -o "*djbdns*" will tell you the full package name and origin However a similar thing recently happened to me, after the move of portupgrade to a new category. I tried to run portupgrade on a port and nothing happened. I'm not sure why it worked, because I didn't get "Command not found", but typing rehash fixed it.