From owner-freebsd-questions@FreeBSD.ORG Sat Oct 25 13:37:40 2014 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 8308F3EA for ; Sat, 25 Oct 2014 13:37:40 +0000 (UTC) Received: from avasout07.plus.net (avasout07.plus.net [84.93.230.235]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client CN "Bizanga Labs SMTP Client Certificate", Issuer "Bizanga Labs CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id E16E385C for ; Sat, 25 Oct 2014 13:37:39 +0000 (UTC) Received: from curlew.milibyte.co.uk ([84.92.153.232]) by avasout07 with smtp id 7RaR1p008516WCc01RaT66; Sat, 25 Oct 2014 14:34:27 +0100 X-CM-Score: 0.00 X-CNFS-Analysis: v=2.1 cv=bMiYIZOZ c=1 sm=1 tr=0 a=lfSX4pPLp9EkufIcToJk/A==:117 a=lfSX4pPLp9EkufIcToJk/A==:17 a=D7rCoLxHAAAA:8 a=0Bzu9jTXAAAA:8 a=GIpPufGBusUA:10 a=8nJEP1OIZ-IA:10 a=1nsQxCYdjchPj7veZdYA:9 a=wPNLvfGTeEIA:10 Received: from sedbergh.lan ([192.168.1.13] helo=curlew.lan) by curlew.milibyte.co.uk with esmtp (Exim 4.84) (envelope-from ) id 1Xi1U9-0001L1-DN for freebsd-questions@freebsd.org; Sat, 25 Oct 2014 14:34:25 +0100 From: Mike Clarke To: freebsd-questions@freebsd.org Date: Sat, 25 Oct 2014 14:34:24 +0100 Message-ID: <1745632.OG3xRRcUAb@curlew.lan> User-Agent: KMail/4.14.2 (FreeBSD/10.1-RC1-p1; KDE/4.14.2; amd64; ; ) In-Reply-To: <544B2C36.6080600@hiwaay.net> References: <544B2C36.6080600@hiwaay.net> MIME-Version: 1.0 X-SA-Exim-Connect-IP: 192.168.1.13 X-SA-Exim-Mail-From: jmc-freebsd2@milibyte.co.uk X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on curlew.lan X-Spam-Level: X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham autolearn_force=no version=3.4.0 Subject: Re: More info on last post .... Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="iso-8859-1" X-SA-Exim-Version: 4.2 X-SA-Exim-Scanned: Yes (on curlew.milibyte.co.uk) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Oct 2014 13:37:40 -0000 On Friday 24 Oct 2014 23:51:02 William A. Mahaffey III wrote: > i.e. nspluginwrapper seems to be locked in on linux-f10, rather > than linux-c6 .... Since linux-c6 is supposed to be supplanting > linux-f10, this might be a bug .... TIA for any help .... The problem is that linux-c6 is not yet the default. Packages in the repository which depend on linux are still being built against linux- f10 - there's no mechanism for the repository to provide 2 different builds of the same package. As a workaround until c6 becomes the default you could lock your version of nspluginwrapper using the command "pkg lock nspluginwrapper". This will prevent "pkg upgrade" from replacing it with the f10 version. The downside of the workaround is that if a newer version of nspluginwrapper is available in the repository "pkg upgrade" will work through the list of packages to upgrade until it reaches nspluginwrapper and then fail with a message saying that nspluginwrapper is locked. At this stage you should use portmaster to rebuild nspluginwrapper and then run "pkg upgrade" again. If some c6 dependencies are still in need of upgrading after the first "pkg upgrade" run fails then portmaster will rebuild them so you might wish to save some time by using pkg to upgrade them before running portmaster. The command below should upgrade your out of date c6 packages. pkg info -x 'linux.*c6' | xargs pkg rquery %n | xargs pkg upgrade This command creates a list of all your linux c6 packages, filters it through pkg rquery to get a list of only those packages which are available from the repository and then passes it through to pkg upgrade. -- Mike Clarke