From owner-freebsd-ports@FreeBSD.ORG Sat Apr 5 04:00:18 2014 Return-Path: Delivered-To: ports@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 74CCA11F for ; Sat, 5 Apr 2014 04:00:18 +0000 (UTC) Received: from mail-ig0-x22a.google.com (mail-ig0-x22a.google.com [IPv6:2607:f8b0:4001:c05::22a]) (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 3F1CB8CF for ; Sat, 5 Apr 2014 04:00:18 +0000 (UTC) Received: by mail-ig0-f170.google.com with SMTP id uq10so2659475igb.1 for ; Fri, 04 Apr 2014 21:00:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-type:content-transfer-encoding:thread-index :content-language; bh=yauMhy1nl2lMRVMu5rgQOch5YF0fLzYI5pH3h9sk5Go=; b=qa+VJXxmwmPpegtJZ4aLrv1rqeRKOAi23Dcehnr/YynTsfpYKnl6anCNO43UzuR5be AJanoAmmx+v5oTC88vMdB3AAoJIEpYtd07FNiNaNUzDuuWAYh1IRWjQSBqk0LHwrBKDD yWYqDd04xP28kn3ir3tI7nhtRfdFobSktVrSOIWWuos8WozNKJRqJMIxvxYMnxxS2gG8 SpvzVZWIA5qMgju4fckkOTnc/X5a3EUurpdN51J1RUxt68y89e0m/0lBdMHBxhNh/cbr ohqa1sAIq3iDa/ZF4lozAH1N8g+NduSXKbMGDBWilw0SqP0POrEVpx75J+/W3G9jcb/p YQhw== X-Received: by 10.43.90.202 with SMTP id bj10mr15189680icc.48.1396670417678; Fri, 04 Apr 2014 21:00:17 -0700 (PDT) Received: from SINDROME (c-50-178-125-248.hsd1.il.comcast.net. [50.178.125.248]) by mx.google.com with ESMTPSA id y9sm11016410igl.7.2014.04.04.21.00.17 for (version=TLSv1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 04 Apr 2014 21:00:17 -0700 (PDT) From: "sindrome" To: "'Warren Block'" References: <533F36F0.8020803@rcn.com> <000601cf505e$d3b6bc70$7b243550$@gmail.com> In-Reply-To: Subject: RE: pkgng vs. portupgrade reporting ports outdated Date: Fri, 4 Apr 2014 23:00:15 -0500 Message-ID: <001501cf5083$8dc109d0$a9431d70$@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQFAmLT3AK3p1Tt5lpXS+3E115PjcwH+njHCAiQEknCb/sAGAA== Content-Language: en-us Cc: ports@freebsd.org, 'Robert Huff' X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Apr 2014 04:00:18 -0000 So now the way to keep ports up-to-date is to execute 'pkg update' and 'pkg upgrade'? Are you saying I shouldn't svn update the ports tree anymore? oz:132:/usr/local/etc# pkg update oz:133:/usr/local/etc# pkg upgrade -----Original Message----- From: Warren Block [mailto:wblock@wonkity.com] Sent: Friday, April 04, 2014 9:23 PM To: sindrome Cc: 'Robert Huff'; ports@freebsd.org Subject: RE: pkgng vs. portupgrade reporting ports outdated On Fri, 4 Apr 2014, sindrome wrote: > There is a major inconsistency with what pkg_version -v says is > outdated and what pkgng says. Of course. pkg_version looks at the text files in /var/db/pkg, while pkg looks at the database local.sqlite in that directory. The first step in using pkg is running pkg2ng, which imports the old information from the text files into the sqlite table. After that, pkg_version should not be used. It's getting information from an outdated database.