On 02/24/10 04:24 AM, Pavel Heimlich wrote: >> On 02/24/10 08:03, Pavel Heimlich wrote: >>> are at http://solaris.bionicmutton.org:10001 >>> >>> They are built on b132. I'd expect them to behave >> fine on b133, but I >>> was unable to verify that as the pkg tool ate all >> my limited VirtualBox >>> RAM during all attempts. >> >> there's another hitch: from b133 onwards, pkg >> performs some check which >> requires you to use the name for the repository >> that's specified in the >> repo itself: >> >>> $ pkg set-publisher -g >> http://solaris.bionicmutton.org:10001 bionicmutton >>> pkg set-publisher: >>> One or more of the repository origin(s) listed >> below contains package data for mypkgs; not >> bionicmutton: >>> >>> http://solaris.bionicmutton.org:10001/ >>> >>> This is either because one of the repository >> origins is not valid for this publisher, or because >> the list of known publishers retrieved from the >> repository origin does not match the client. >> >> >> this isn't a severe limitation, but looks a little >> strange. > > wow, if this is not a bug then what else is one? > Yet the message indicates it was brought in as a feature. > > This pkg stuff keeps on ... surprising me.
This was done to simplify client configuration, read more here: http://blogs.sun.com/srw/entry/simplifying_publisher_configuration The short version is, users can now add your repository with a shorter command: pfexec pkg set-publisher -p http://solaris.bionicmutton.org:10001/ ...that will automatically add a new publisher to their system with the origins and mirrors that are specified in your $REPO/cfg_cache file. So be certain you've set the *origins* property as well as the publisher prefix, etc. ! Cheers, -- Shawn Walker
