http://bugzilla.novell.com/show_bug.cgi?id=542754 Martin Vidner changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.pr |wolfgang@rosenauer.org |ovo.novell.com | -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=542754 User gfarrell@netspeed.com.au added comment http://bugzilla.novell.com/show_bug.cgi?id=542754#c3 Geoff Farrell changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW CC| |gfarrell@netspeed.com.au Info Provider|gfarrell@netspeed.com.au | --- Comment #3 from Geoff Farrell 2009-10-06 03:09:56 MDT --- Thanks Wolfgang, the acceptance of the patch behaved exactly as you predicted: mozilla-xulrunner190 was updated to version 1.9.0.14-0.1.1.x86_64, and the Updater icon is now green once more. It was easier to understand after your explanation, but I would not have worked that out for myself from the information presented. I found the situation to be confusing. For a start, the Warning dialog mentions 'patch:MoxillaFirefox-1312.noarch', which I couldn't find on the updates website, nor by searching in YaST itself (in the 'noarch' directory in both cases). I couldn't understand why 'MozillaFirefox-1312' needed updating if it didn't exist on my system. The fact that it 'conflicts with mozilla-xulrunner190.x86_64 < 1.9.0.14-0.1.1 provided by mozilla-xulrunner190-1.9.0.13-1.2.x86_64' made little headway in clearing up the matter. Perhaps if it had said that 'patch:MoxillaFirefox-1312.noarch provides an updated version of mozilla-xulrunner190-1.9.0.14-0.1.1.x86_64', it might have given me a clue. So the expression in that dialog could stand improvement. The other source of confusion was the announced 'Conflict Resolution', which was to 'install mozilla-xulrunner190-1.9.0.14-0.1.1.x86_64' (that part was clear enough) but '(with vendor change)' to 'openSUSE Build Service' really threw me. Because, from the Technical Data tab, the Vendor for the Installed Version was 'openSUSE Build Service' and the Vendor for the Alternate Version was 'openSUSE'. That is, the existing version was 'openSUSE Build Service' and it needed a vendor change to 'openSUSE Build Service' (??). That seemed like a mistake to me, so I wasn't happy proceeding with the update (thus this bug report). It's certain that there is no problem with the Updater Applet code, but the display of the information, to me, prompts for the wrong version (as per this bug title) to be updated, causing confusion. Changing the way the information is presented could fix that. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=542754 zhu rensheng changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rszhu@novell.com AssignedTo|bnc-team-screening@forge.pr |tgoettlicher@novell.com |ovo.novell.com | -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=542754 https://bugzilla.novell.com/show_bug.cgi?id=542754#c6 Marcus Meissner changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #6 from Marcus Meissner 2010-11-14 10:27:45 UTC --- we updated to 3.6 in the meantime and this problem should be gone (as we have now the same version in OBS and Update) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.