From owner-freebsd-questions@FreeBSD.ORG Fri Apr 26 21:06:24 2013 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id D2C6C560 for ; Fri, 26 Apr 2013 21:06:24 +0000 (UTC) (envelope-from russo@bogodyn.org) Received: from bogodyn.org (mail.bogodyn.org [69.49.164.40]) by mx1.freebsd.org (Postfix) with ESMTP id 855201DB5 for ; Fri, 26 Apr 2013 21:06:23 +0000 (UTC) Received: from bogodyn.org (localhost [127.0.0.1]) by bogodyn.org (8.14.6/8.14.6) with ESMTP id r3QKsxx8060634; Fri, 26 Apr 2013 14:54:59 -0600 (MDT) (envelope-from russo@bogodyn.org) Received: (from russo@localhost) by bogodyn.org (8.14.6/8.14.6/Submit) id r3QKsxNg060633; Fri, 26 Apr 2013 14:54:59 -0600 (MDT) (envelope-from russo) Date: Fri, 26 Apr 2013 14:54:59 -0600 From: Tom Russo To: freebsd-questions@freebsd.org Subject: Why is "pkg_glob" no longer working for me? Message-ID: <20130426205459.GA60584@bogodyn.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Organization: International Institute for Advanced Quantum Bogodynamical Studies User-Agent: Mutt/1.5.21 (2010-09-15) X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on bogodyn.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: russo@bogodyn.org List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Apr 2013 21:06:24 -0000 I used to be able to run "pkg_glob" to see what packages have been updated since a given date. For example, if I do a big 'portupgrade -fr somepackage' and wait overnight, then in the morning find a handful had failed, I often find it helpful to do something like: pkg_glob -r somepackage -x '>= 2013-04-24' to see what packages depend on somepackage but weren't updated when I did the portupgrade on the 24th. But now, I find that pkg_glob always returns absolutely nothing if I specify a date. I did a portupgrade -a on Thursday the 25th of April, and when I try to see which ports actually got updated with "pkg_glob '>=2013-04-24'", it prints nothing. This has been happening for a few weeks, at least, and I wonder an update to the portupgrade package busted it. I have tried rebuilding the package db and ports db using pkgdb and portsdb, with no change in behavior. I tried looking at /var/db/pkg to see if the modification times of directories there might help me answer my question, but far more directories have been touched than packages actually updated (there were, as I recall, 20 pending package upgrades when I started the process). Anyone else have this issue? Or am I the only one left still using portupgrade and its associated tools? -- Tom Russo KM5VY SAR502 DM64ux http://www.swcp.com/~russo/ Tijeras, NM QRPL#1592 K2#398 SOC#236 http://kevan.org/brain.cgi?DDTNM echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] [n-z][a-m]