On Sun, 2009-08-23 at 16:05 -0700, Danek Duvall wrote:
> Joanmarie Diggs wrote:
> 
> > $ pkg info virtualbox
> >           Name: virtualbox
> >        Summary: Sun VirtualBox
> >       Category: System/Virtualization
> >          State: Installed
> >      Publisher: extra
> >        Version: 3.0.2
> >  Build Release: 5.11
> >         Branch: 0.101
> > Packaging Date: July 14, 2009  6:32:00 PM 
> >           Size: 185.39 MB
> >           FMRI: pkg://extra/[email protected],5.11-0.101:20090714T183200Z
> 
> The latest version of virtualbox is 3.0.4, so it's not surprising that
> pkg(5) wants to update it.  Not sure about opera, though.  I imagine it's
> the same sort of thing.
> 
> Why do you think that these packages shouldn't be updated?

I don't think Opera should be updated because I went into PM, marked it
to be updated, and updated it. According to Contrib's web interface:

[email protected],5.11-0.101:20090428T172804Z
          Name: opera
       Summary: Web Browser
     Publisher: contrib.opensolaris.org
       Version: 9.64
 Build Release: 5.11
        Branch: 0.101
Packaging Date: Tue Apr 28 17:28:04 2009
          Size: 40.05 MB
          FMRI: pkg:/[email protected],5.11-0.101:20090428T172804Z

$ pkg info opera
          Name: opera
       Summary: Web Browser
      Category: Applications/Internet
         State: Installed
     Publisher: contrib
       Version: 9.64
 Build Release: 5.11
        Branch: 0.101
Packaging Date: April 28, 2009  5:28:04 PM 
          Size: 40.05 MB
          FMRI: pkg://contrib/[email protected],5.11-0.101:20090428T172804Z

These two things look the same to me. What is there to be updated? If
nothing, then why does pkg, pm, and um keep trying? And why does it only
keep trying on one machine rather than on both machines in question?

As for Virtualbox, that's slightly more grey as to what *should* be
taking place. However, I don't think Virtualbox should be updated
because I have since disabled the Extra authority. If disabling an
authority is not sufficient to stop it from being used (and packages
from it being updated), then what is? And even if, hypothetically, the
answer/intended user experience is that once you install a package from
Foo, Foo will forever more be checked for updates for that package, then
why is only one box insisting on updating Virtualbox; shouldn't both
boxes be trying?

--joanie

_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss

Reply via email to