From owner-freebsd-questions@FreeBSD.ORG Wed May 21 18:45:51 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 88F5AAD8 for ; Wed, 21 May 2014 18:45:51 +0000 (UTC) Received: from fep14.mx.upcmail.net (fep14.mx.upcmail.net [62.179.121.34]) by mx1.freebsd.org (Postfix) with ESMTP id C631D23AA for ; Wed, 21 May 2014 18:45:50 +0000 (UTC) Received: from edge03.upcmail.net ([192.168.13.238]) by viefep14-int.chello.at (InterMail vM.8.01.05.05 201-2260-151-110-20120111) with ESMTP id <20140521184543.ZHPJ20421.viefep14-int.chello.at@edge03.upcmail.net> for ; Wed, 21 May 2014 20:45:43 +0200 Received: from [192.168.1.160] ([86.101.30.243]) by edge03.upcmail.net with edge id 4ilj1o00E5EjbRA03iljnq; Wed, 21 May 2014 20:45:43 +0200 X-SourceIP: 86.101.30.243 Message-ID: <537CF453.7090105@shopzeus.com> Date: Wed, 21 May 2014 20:45:39 +0200 From: =?UTF-8?B?TmFneSBMw6FzemzDsyBac29sdA==?= User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: freebsd-questions@freebsd.org Subject: Re: pkg upgrade not working properly [was: pkgng messed up] References: <5374C16E.6000000@shopzeus.com> <44k39n2kg1.fsf@lowell-desk.lan> <5375B772.2050700@shopzeus.com> <537C4D66.6010306@shopzeus.com> <537C53E9.50905@FreeBSD.org> <537CD47A.6050802@shopzeus.com> <537CD7E3.6020501@freebsd.org> In-Reply-To: <537CD7E3.6020501@freebsd.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 May 2014 18:45:51 -0000 > You need to identify every package generating these sort of conflicts, > and then tell pkg that it should use a different port (identified by > port origin) for any upgrades using 'pkg set' like so: > > pkg set -o category/old-port:category/new-port > > So in the case of replacing postgresql93-client with postgresql90-client > you run: > > pkg set -o databases/postgresql93-client:databases/postgresql90-client > > Now when you run your 'pkg upgrade' it will tell you it is upgrading > (sic) postgresql93-client to postgresql90-client. Thank you. It is funny I have already tried this but in the other direction e.g. pkg set -o databases/postgresql90-client:databases/postgresql93-client I guess I did that because it was that way with the old portmaster. This trick helped me with postgresql, but not with perl. Here is the problem: pkg set -o lang/perl5.16:lang/perl5.12 pkg upgrade Then I still get these messages: pkg: WARNING: locally installed perl-5.12.4_4 conflicts on /usr/local/man/man1/xsubpp.1.gz with: - perl5-5.16.3_9 Which is silly because the locally installed perl is NOT 5.12 but 5.14: root@backup:/usr/ports # perl -version This is perl 5, version 14, subversion 4 (v5.14.4) built for amd64-freebsd And hey, perl5.12 is not under ports/lang anymore. What can I do with this? (And still don't understand that if this conflict is an error, then why am I getting warnings only?)