From owner-freebsd-questions@FreeBSD.ORG Tue Jun 24 12:01:30 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B36B81065671 for ; Tue, 24 Jun 2008 12:01:30 +0000 (UTC) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: from be-well.ilk.org (dsl092-078-145.bos1.dsl.speakeasy.net [66.92.78.145]) by mx1.freebsd.org (Postfix) with ESMTP id 739E48FC28 for ; Tue, 24 Jun 2008 12:01:30 +0000 (UTC) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: by be-well.ilk.org (Postfix, from userid 1147) id AA60028461; Tue, 24 Jun 2008 08:01:29 -0400 (EDT) To: iwrTech@iwr.ru.ac.za References: <485F9523.3446.E15165@iwrtech.iwr.ru.ac.za> From: Lowell Gilbert Date: Tue, 24 Jun 2008 08:01:29 -0400 In-Reply-To: <485F9523.3446.E15165@iwrtech.iwr.ru.ac.za> (DA Forsyth's message of "Mon\, 23 Jun 2008 12\:20\:51 +0200") Message-ID: <44tzfjkpnq.fsf@be-well.ilk.org> User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.2 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: freebsd-questions@freebsd.org Subject: Re: portupgrade dependency loop X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-questions@freebsd.org List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Jun 2008 12:01:30 -0000 "DA Forsyth" writes: > How do I fix this? > > ===> Registering installation for horde-base-3.2_3 > pkg_create: dependency loop detected for package pear-Auth-1.6.1 > pkg_create: dependency loop detected for package pear-Auth_SASL-1.0.2 > pkg_create: dependency loop detected for package pear-Net_SMTP-1.3.1 > > I tried doing a 'pkgdb -F' and removing the dependencies in the loop, > but they just get rebuilt. Start by updating your ports tree again. You may have hit a transient issue with the dependencies in the actual makefiles. Probably not, but it's worth checking before trying to understand what's really happening. If I can let the machine alone for a while, I will generally rebuild all the ports in the dependency tree for the problem. Getting this accurate usually requires examining the ports by hand. Removing all of those ports and rebuilding them to pick up the dependency information in order will usually work, but takes the functionality offline for longer. Hope that helps...