More info on last post ....

[Mike Clarke]

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