From owner-freebsd-ports@FreeBSD.ORG Sat Apr 26 11:13:43 2008 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0FEBB1065673 for ; Sat, 26 Apr 2008 11:13:43 +0000 (UTC) (envelope-from kamikaze@bsdforen.de) Received: from mail.bsdforen.de (bsdforen.de [212.204.60.79]) by mx1.freebsd.org (Postfix) with ESMTP id C0EDA8FC15 for ; Sat, 26 Apr 2008 11:13:42 +0000 (UTC) (envelope-from kamikaze@bsdforen.de) Received: from mobileKamikaze.norad (unknown [92.116.88.96]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.bsdforen.de (Postfix) with ESMTP id D27FD8A0858 for ; Sat, 26 Apr 2008 13:13:36 +0200 (CEST) Message-ID: <48130E54.2080400@bsdforen.de> Date: Sat, 26 Apr 2008 13:13:24 +0200 From: Dominic Fandrey User-Agent: Thunderbird 2.0.0.12 (X11/20080422) MIME-Version: 1.0 To: freebsd-ports@freebsd.org References: <1209166740.90447.42.camel@ikaros.oook.cz> <20080426063955.6e8117eb@scorpio> In-Reply-To: <20080426063955.6e8117eb@scorpio> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: help requested with fixing after ImageMagick update X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Apr 2008 11:13:43 -0000 Gerard wrote: > On Sat, 26 Apr 2008 01:39:00 +0200 > Pav Lucistnik wrote: > >> Hi folks, >> >> we had a rather intrusive ImageMagick update recently, which left some >> ports broken. Since it's quite a task for a single guy to fix them >> all, I'd like to ask you folks to help out with this. >> >> This is a list of known breakages: >> >> science/gnudatalanguage >> textproc/htmltolatex >> graphics/kallery >> graphics/php-magickwand >> lang/q >> graphics/reallyslick >> graphics/ruby-rmagick > > > Usually, I have no major problems updating ports. I use 'portupgrade' > as my usually ports maintenance tool. However, in case like this I > prefer 'portmanager'. It seems to correct problems with dependencies > much better than 'portupgrade'. I would recommend that you do something > like this: > > 1) If portmanager is not installed, install it. > 2) Update your ports tree > 3) Run: portmanager -u -l -p -y > > That should update all of your ports and force a rebuild of any port > using an old or out dated dependency. It will also create a log file > in: '/var/log/portmanager.log'. This usually works for me. > > Good luck! Portmanager cannot work around changed library names either. The ports have to be fixed.