From owner-freebsd-questions@FreeBSD.ORG Fri Apr 17 15:09:54 2015 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3BFE74F5 for ; Fri, 17 Apr 2015 15:09:54 +0000 (UTC) Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C7803EC5 for ; Fri, 17 Apr 2015 15:09:53 +0000 (UTC) Received: from [192.168.0.143] ([95.91.226.254]) by mail.gmx.com (mrgmx001) with ESMTPSA (Nemesis) id 0LZiLk-1ZCwOh0xBM-00lT0o; Fri, 17 Apr 2015 17:09:51 +0200 Message-ID: <5531223E.8020208@gmx.de> Date: Fri, 17 Apr 2015 17:09:50 +0200 From: "lokadamus@gmx.de" User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 MIME-Version: 1.0 To: Mike Clarke , freebsd-questions@freebsd.org Subject: Re: pkg upgrade Solver problem References: <4256565.sTWNKMh4Pq@curlew.lan> In-Reply-To: <4256565.sTWNKMh4Pq@curlew.lan> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:XEcEg5Dihp9NDla8OJGGco+wsKaaWtpQgLJRCsNCxg4F8x7HE8d 9W1EtUPTufQcgd7PsSvQCsL8hd3x3lab95C5wGOfs+beMZwl5s3Dbosn6SZgehE3e0CtYZU x0sVYiliCHI9+DsBIu4KfRzWkTUI1htYhjTNulV5n9wGwYiGH+HiKmV1CTdzF+ZNnDJSruo aBOPNf4P6f1fr1HWeFMMw== X-UI-Out-Filterresults: notjunk:1; X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Apr 2015 15:09:54 -0000 On 04/17/15 17:00, Mike Clarke wrote: > > Prior to the update there had been conflicting requirements for mysql55 and > mysql56 which I'd got round by building p5-DBD-mysql from ports to use > mysql55-client. > > After deleting p5-DBD-mysq I was able to complete the upgrade without errors > and then reinstall p5-DBD-mysq as a package. > > I was able to work round these errors but am wondering if the solver ought to > have been able to handle them or perhaps produce less cryptic error messages? > How do you rebuild your ports? Do you use portupgrade or portmaster? Sometimes a "portsnap fetch extract" help resolve some issues. Greetings