Hi Brandon,

Update to build 128 
<http://blogs.sun.com/observatory/en_US/entry/updating_to_a_specific_build>, 
then you should be free to go forward.

Regards,
Brian

Brandon Hume wrote:
> I've got a box currently running b127 which I'd like to update.  
> Unfortunately, in between the new rules for publisher names took effect.  
> I've adjusted my publisher names, as so:
>
> # pkg publisher
> PUBLISHER                             TYPE     STATUS   URI
> opensolaris.org          (preferred)  origin   online   
> http://pkg.opensolaris.org/dev/
> contrib.opensolaris.org               origin   online   
> http://pkg.opensolaris.org/contrib/
> justplayer                            origin   online   
> http://pkglabo.justplayer.com/dev/
>
>
> But I can't do an image update:
>
> # pkg image-update -f --be-name=opensolaris-b132
> Creating Plan \pkg: Cannot remove 
> 'pkg://opensolaris.org-dev/SUNWgnome-a11y-libs-python24 at 
> 0.5.11,5.11-0.127:20091111T055042Z' due to the following packages that depend 
> on it:
>   pkg://opensolaris.org-dev/SUNWgnome-a11y-reader at 
> 0.5.11,5.11-0.127:20091111T055202Z
>
> Doing a pkg info shows the following:
>
> # pkg info SUNWgnome-a11y-reader
>           Name: SUNWgnome-a11y-reader
>        Summary: Orca screen reader/magnifier
>    Description: Orca screen reader/magnifier
>       Category: Applications/Universal Access
>          State: Installed
>      Publisher: opensolaris.org-dev
>        Version: 0.5.11
>  Build Release: 5.11
>         Branch: 0.127
> Packaging Date: November 11, 2009  5:52:02 AM 
>           Size: 4.65 MB
>           FMRI: pkg://opensolaris.org-dev/SUNWgnome-a11y-reader at 
> 0.5.11,5.11-0.127:20091111T055202Z
>
>
> Do my update problems originate from the bad publisher name in the existing 
> packages?
>   

-- 
W. Brian Leonard
Technology Evangelist
408.404.6884
http://blogs.sun.com/observatory

-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://mail.opensolaris.org/pipermail/opensolaris-help/attachments/20100210/e798e7f6/attachment.html>

Reply via email to