UM as originally designed was meant to allow you to update packages that 
might not require a reboot. The problem is that we cannot tell if this 
is the case for any given package at the minute, we also cannot tell if 
a package belongs to an incorporation. On David and Stephen's 
recommendation we only ever allow UM to do an image-update. Our 
understanding having talked to them both is that upgrades will always 
require an image-update. This may change in the future, but its what the 
design is meant to do.

The behavior you are seeing is a little odd. How did you do the update? 
Did you do it via the UM GUI launched by clicking on the UMN 
notification icon or on the command line?

If the UMN was running and detected that an update is available it will 
set a gconf key to show the update icon on startup. Clicking on the icon 
unsets this key and launched the UM GUI. If you then went and did the 
update on the command line this gconf key is still set as there is no 
communication between the CLI and the GUI. So on next reboot the icon is 
displayed and clicking on it will bring up the UM which will run and 
tell you correctly that no updates are available.

If this is not what you did then something else is going on. Certainly 
the UM GUI should ensure that the gconf key is unset when a successful 
Update All is run from it. So you could see this behavior if the UM GUI 
is launched from the menu or command line and not by clicking the icon. 
This is a bug and I'll log it. The other involving the CLI and GUI I'm 
happy to leave.

JR

Brad Hall wrote:
> On Wed, Nov 19, 2008 at 06:19:59PM -0800, Dan Price wrote:
>   
>> On Wed 19 Nov 2008 at 10:18AM, [EMAIL PROTECTED] wrote:
>>     
>>>>> This assumption seems overly simplistic.  What happens if the notifier
>>>>> determines that one package is available for upgrade, but the
>>>>> updatemanager isn't invoked until later?  Does the updatemanager
>>>>> double-check to see if more updates have arrived?  What happens in the
>>>>>   
>>>>>           
>>>> updatemanagernotifier just determines if there are updates.
>>>>
>>>> When updatemanager is run it determines what updates are available.
>>>>         
>>> Ok.  Thanks for clarifying this point.
>>>       
>> A significant bad interaction is happening here: after I updated
>> my system and rebooted, the update manager toolbar thingy told me there
>> were updates available.  Amused, I clicked it.  Update manager popped up
>> and told me that, in fact, there were no updates available.
>>
>> So, I quit the UM.  Now I also have no update notifier anymore.
>>     
>
> Same thing happened to me.
>
> -Brad
> _______________________________________________
> pkg-discuss mailing list
> [email protected]
> http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
>   

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

Reply via email to