From owner-freebsd-questions@FreeBSD.ORG Fri Feb 10 20:36:12 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1DD0C16A420 for ; Fri, 10 Feb 2006 20:36:12 +0000 (GMT) (envelope-from andrew.chace@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9068443D45 for ; Fri, 10 Feb 2006 20:36:11 +0000 (GMT) (envelope-from andrew.chace@gmail.com) Received: by zproxy.gmail.com with SMTP id 9so515863nzo for ; Fri, 10 Feb 2006 12:36:11 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:subject:from:to:in-reply-to:references:content-type:date:message-id:mime-version:x-mailer:content-transfer-encoding; b=nF5cVV5wki84pupIihzpvzywVzW/oXE9hDplbzjwQ9PceoJmjPfd02n4uOPLjv/FKojtP/XCqROOAQ6yDaiBZrKZj2awust63vbL/2jc3XUOLBb8S6meD2yKigx0x8NtBqCgzJ3oCKyLKVSBd35MzA/4rvYj9u93ZmD+IvED+PM= Received: by 10.36.96.18 with SMTP id t18mr3904627nzb; Fri, 10 Feb 2006 12:36:10 -0800 (PST) Received: from netvista.network ( [71.214.192.222]) by mx.gmail.com with ESMTP id c1sm1547123nzd.2006.02.10.12.36.09; Fri, 10 Feb 2006 12:36:10 -0800 (PST) From: Andrew To: roberthuff@rcn.com, donaldjoneill@gmail.com, freebsd-questions@freebsd.org In-Reply-To: <17388.62292.955134.229885@jerusalem.litteratus.org> References: <1139589051.2185.8.camel@netvista.network> <17388.49778.982280.245532@jerusalem.litteratus.org> <1139596918.58491.3.camel@netvista.network> <17388.62292.955134.229885@jerusalem.litteratus.org> Content-Type: text/plain Date: Fri, 10 Feb 2006 14:35:45 -0600 Message-Id: <1139603745.58491.27.camel@netvista.network> Mime-Version: 1.0 X-Mailer: Evolution 2.4.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: Subject: Re: stale dependencies in pkgdb 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: Fri, 10 Feb 2006 20:36:12 -0000 On Fri, 2006-02-10 at 15:11 -0500, Robert Huff wrote: > Andrew writes: > > > I guess what is unclear to me is how I go about fixing the stale > > dependencies. I was under the impression that portupgrade would > > take care of the dependencies for a particular port, and the > > "stale dependency" was just an error in the package database > > (pkgdb). Is this not the case? > > My understanding of how things work: > Consider two ports a and b, such that a-4.6 is a dependency for > b-2.2. If a updates to 4.7, and I run "portupgrade -r a", b will > also be updated. > But if I run "portupgrade a" (or there's a bug in the programs/ > scripts) b will not update ... and pkgdb will complain about about a > stale (i.e. unsatisified) dependency. This also happens when you > replace one port with another that provides the same functionality. > For example: many gnome ports depend on openldap. But I use > openldap-sasl - and every time I update one of those ports I have to > manually correct the dependency. (There's probably a way to do that > automatically, but I haven't figured out how.) > And now there's a "stale dependency". This can be expecially > frustrating if the dependant port hasn't been updated for years; the > required port may have been upgraded beyond recognition, no longer > available, absorbed into another port, etc.. > As to how, try this as a first approximation. Run [kgdb -f, > and reply "no" to all changes. Write down the port:dependency > pairs, and then anaylze the dependencies. Has it been > installed. but not registered? Replaced by a newer version? Two > useful files are /usr/ports/UPDATING and /usr/ports/MOVED. > My response here is mostly guesswork, educated by several years > of doing this and sometimes asking for help. In the case above, > fixing a-4.6 with a-4.7 is usually a no-brainer. Fixing a-4.6 with > a-5.0, however, would require reseaech (and warrant keeping a backup > of the pkgdb). Sorry; just fired off a message to the list before I got this one... Anyway, I think I've got it now. I believe I was correct in thinking that portupgrade usually takes care of dependencies; the portion that I was missing was that pkgdb catches what discrepancies do appear between what is installed and what is required. One of the ports that was giving me troubles was gamin; which I've just noticed seems to be similar to your situation with openldap-sasl (gamin/fam). Another was cdrtools (cdrtools/cjk-cdrtools). I've corrected both manually using "pkgdb -F", which I think solves my problem (for now, at least :-) ). Thank you for your help! -Andrew