From owner-freebsd-questions@FreeBSD.ORG Sun Jul 27 15:12:06 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 284DD8F1 for ; Sun, 27 Jul 2014 15:12:06 +0000 (UTC) Received: from mail-wi0-x233.google.com (mail-wi0-x233.google.com [IPv6:2a00:1450:400c:c05::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B57642490 for ; Sun, 27 Jul 2014 15:12:05 +0000 (UTC) Received: by mail-wi0-f179.google.com with SMTP id f8so3168279wiw.0 for ; Sun, 27 Jul 2014 08:12:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=date:from:to:subject:message-id:in-reply-to:references:mime-version :content-type:content-transfer-encoding; bh=umrMgJEtt9Tx1D1+5ywl+4fcTYqA/BSey/DauJm3qgg=; b=JQNW2xbVu+VLOwCbZoQJxCqrhhyNSNi0EXfZpSy4NbzlXd+th34k2XAevWpvSBIJV4 dhALazYJTQRGl05gjOQAilLJZzqMEhPkHag+aIQiyvM92zAy2STj9Cyz4jHgZwuLjXgj JrhHxTXDM9HcUeiJVgryw4Zraxx34WODwdVGuA8LWoO67uUHE1p9mzXqSpitWsad2srN BwEOrayxg5kNBb9dFptUTVMKrFLQkc8ieCmAHonlqms8x8jH66KaTdmtaKrjOCATZucl nzcK70PbJ6Jqam/fGgMBCl0atE1fpDDy6QZEiAoOSZ9nKMgCqPHS7GUDztdSkX9mug3O YDXA== X-Received: by 10.180.81.234 with SMTP id d10mr21945805wiy.79.1406473922674; Sun, 27 Jul 2014 08:12:02 -0700 (PDT) Received: from gumby.homeunix.com ([94.195.197.42]) by mx.google.com with ESMTPSA id de5sm20217571wib.18.2014.07.27.08.12.01 for (version=SSLv3 cipher=RC4-SHA bits=128/128); Sun, 27 Jul 2014 08:12:01 -0700 (PDT) Date: Sun, 27 Jul 2014 16:12:00 +0100 From: RW To: freebsd-questions@freebsd.org Subject: Re: portversion doesn't seem to know what's out of date Message-ID: <20140727161200.01eec19d@gumby.homeunix.com> In-Reply-To: References: X-Mailer: Claws Mail 3.10.1 (GTK+ 2.24.22; amd64-portbld-freebsd10.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Jul 2014 15:12:06 -0000 On Sun, 27 Jul 2014 20:51:56 +1000 Jason Birch wrote: > I built FreeBSD for my Beaglebone Black a couple of weeks ago, and > went to do an update just then. After updating /usr/ports, I ran > `portversion | grep \<` to see a list of what could be updated. > Knowing that this takes a bit longer and needing to run out the door, > I also type `portupgrade -aF` afterwards, to fetch anything that > might need upgrading. > > When I returned, I found that portversion seemed to think everything > was up to date, but ... > > root@beaglebone:/usr/home/jbirch # portsnap fetch > ... > root@beaglebone:/usr/home/jbirch # uname -a > FreeBSD beaglebone 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r268309: > Sun Jul 6 22:13:49 EST 2014 > jbirch@267801:/usr/home/jbirch/crochet-freebsd/work/obj/arm.armv6/usr/src/sys/BEAGLEBONE > arm > > > Has anyone seen this behaviour before, or can point me forward? Try running portsdb -Fu. I don't think portsnap fetches an INDEX file for current. portupgrade -aF doesn't need to know about versions, so it's not affected.