Hi, On 17 February 2010 15:26, Blakeman, Murray J <blakeman.murray.j at edumail.vic.gov.au> wrote: > My guess is that you have both release and dev repositories setup and > enabled. > > Wouldn't that be an issue?
Possibly, although it's possible that the origin search order stuff (or at least whatever default are applied) may avoid that. I'm thinking of the --search-after and --search-before options (and their defaults) to pkg set-publisher. Another guess would be that Alan ran foul of a new requirement that came about in the late 120's builds - that the origin identify itself as a publisher for packages from a publisher that exactly matches the original publisher. This should be "opensolaris.org" for the regular OpenSolaris packages. You do this in the config file you nominate: [feed] description = authority = opensolaris.org window = 4368 logo = ../_themes/pkg-block-logo.png icon = ../_themes/pkg-block-icon.png name = opensolaris.org Build 130 Development Feed [publisher] alias = prefix = opensolaris.org .... some waffle cut .... name = OpenSolaris Build 130 Development Repository origins = http://192.168.254.86:10000/ I can't remember if it is the [feed] or [publisher] bit that has to match - suspect the latter. The config file is nominated as a property on the SMF service (the following from my desktop - will do it a little differently tonight): (gavinm at enogas:/etc )-> svcprop svc:/application/pkg/server:default | grep cfg pkg/cfg_file astring /etc/osol_dev_cfg_cache Gavin
