https://bugzilla.novell.com/show_bug.cgi?id=637764 https://bugzilla.novell.com/show_bug.cgi?id=637764#c1 Michael Andres changed: What |Removed |Added ---------------------------------------------------------------------------- Component|libzypp |GNOME AssignedTo|zypp-maintainers@forge.prov |bnc-team-gnome@forge.provo. |o.novell.com |novell.com --- Comment #1 from Michael Andres 2010-09-08 13:04:27 CEST --- This seems to be an issue of the applet, not a libzypp one. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=637764 https://bugzilla.novell.com/show_bug.cgi?id=637764#c3 Michael Andres changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW CC| |mmeeks@novell.com InfoProvider|ma@novell.com | --- Comment #3 from Michael Andres 2010-09-08 13:49:26 CEST --- Sorry, but I don't understand - which setting? (allow_vendor_change?) A I understand it, it's about pk-backend now listing officially released patches _and_ newer packages, while it formerly just displayed the patches. @allow_vendor_change, in case displaying packages is intended: This depends on how you determine the packages. If you ask zypp to suggest an update candidate, it should respect the setting. But if you just ask for the one with the highest version, there's of course no vendor check. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=637764 https://bugzilla.novell.com/show_bug.cgi?id=637764#c5 Rastislav Krupansky changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rastislav.krupansky@gmail.c | |om --- Comment #5 from Rastislav Krupansky 2010-09-30 09:29:58 UTC --- I´d appreciate, if i´m informed about all available updates/upgrades (included allow_vendor_change). Why couldn´t users install the highest/newest version, if it would be officially released? It's on them, which one update/upgrade they want to install. Of course not the bleeding edge, just officially released. Let´s have a look e.g. Firefox. In update repo http://download.opensuse.org/update/11.3/ all the time will be officially released patches/updates for Firefox 3.6.x, but in Mozilla repo http://download.opensuse.org/repositories/mozilla/openSUSE_11.3/ will be available Firefox 4 in the future. And Firefox 4 will be official released. How will i be informed about new version? @Atri: You have probably enabled factory repositories, if the updater applet shows all available the bleeding edge updates/upgrades. Disable them. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=637764 https://bugzilla.novell.com/show_bug.cgi?id=637764#c7 --- Comment #7 from Atri Bhattacharya 2010-11-12 11:12:04 UTC --- Milestone 3 and counting. Is certainly one of the more scary bugs for me :( -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=637764 https://bugzilla.novell.com/show_bug.cgi?id=637764#c9 --- Comment #9 from Michael Meeks 2011-01-06 10:55:38 UTC --- This problem is a side-effect of showing package updates in addition to patch updates. That is IMHO a big usability win - since we can see updated build-service, and volunteer packages - whose users typically never build patch repositories / descriptions. Personally I don't want to loose that feature. We currently elide all package updates for packages that are mentioned in a patch (so we prefer the patch) in packagekit/backends/zypp/zypp-utils.c (zypp_get_updates) Clearly that is not quite enough. If we want to exclude vendor changes, it should be fairly trivial to scan all the packages to see if their vendor does not match the installed vendor - and since these are updates there should be no un-known / new packages that are not already installed in the system to get that info from - right ? Another ten lines to the above method by someone who understands libzypp, and some half hour of testing pain required. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=637764 https://bugzilla.novell.com/show_bug.cgi?id=637764#c11 --- Comment #11 from Sven Burmeister 2011-01-06 19:55:00 UTC --- I think both of you are right. Showing only official updates by default does make sense but has a flaw because most people do use 3rd party packages, i.e. at a minimum packman. So if some package from that repo has a security issue its update is not shown in the update applet. This is a security issue. Thus IMHO one has to acknowledge that most users do use 3rd party repos and hence need updates from those repos. As a result an update applet has to show these updates. If a user chooses to change vendor for a package, I think it is ok to assume that he wants updates for that package from that repo as well. So the update applet should be set by default to only show updates that do not require a vendor change. The user might change that to show all updates. An option to only show official patches does not make sense IMO since if a user does not use 3rd party repos he will only get security updates anyway and if he chooses to change vendor for a package he needs those updates because they might be security fixes. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=637764 https://bugzilla.novell.com/show_bug.cgi?id=637764#c13 --- Comment #13 from Martin Schlander 2011-01-09 12:58:51 UTC --- Me? Or there's another Martin? Unfortunately I barely have enough skillz to write "hello world" in bash :-) If I did have some skills I probably wouldn't spend time playing catch-up with one of RedHat's maintenance nightmares, instead I'd probably try to bring SUSEwatcher back to life, like in the good old days before openSUSE became an insane asylum for updater applets (starting when zen-updater replaced SUSEwatcher in 10.1) one more crazy and dysfunctional than the other :-( -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=637764 https://bugzilla.novell.com/show_bug.cgi?id=637764#c15 --- Comment #15 from Michael Meeks 2011-01-10 16:05:49 UTC ---

This behavior was changed without thinking much on the consecuences.

Which is a shame, since it was discussed on the list, and approved by the zypp guys :-)

PackageKit applets were never intended to be notifier of newer versions of the package but newer versions of the package you have installed.

Sure - but then, this is not what patches do for you for most non-distro repositories :-)

The right solution should be selecting relevant patches, and then using the solver system update to select the relevant packages. This protect against vendor changes and also conflicting packages.

Unfortunately, that only yields updates that stem from patches; and not updates to the majority of community / build-service repositories which have no patchinfo (right) ? And, yes - I would love this functionality to be in libzypp itself ;-) -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=637764 https://bugzilla.novell.com/show_bug.cgi?id=637764#c16 --- Comment #16 from Will Stephenson 2011-01-19 14:28:04 UTC --- Can someone point me to the discussion on zypp-devel? I am trying to understand the rationale for this change. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=637764 https://bugzilla.novell.com/show_bug.cgi?id=637764#c Stephan Kulow changed: What |Removed |Added ---------------------------------------------------------------------------- Flag| |SHIP_STOPPER+ -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=637764 https://bugzilla.novell.com/show_bug.cgi?id=637764#c18 Atri Bhattacharya changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|badshah400@gmail.com | --- Comment #18 from Atri Bhattacharya 2011-02-15 23:38:20 UTC --- (In reply to comment #17)

Please test PackageKit on home:dmacvcar which supports hiding packages and when showing them it uses the zypper lu algorithm.

See http://lists.opensuse.org/opensuse-factory/2011-02/msg00586.html

Works! Thanks a lot for fixing this, Duncan! Testing method: * Start LiveCD with default repos added * Install packages from repo mentioned above. * Add factory-oss (same vendor as default repos) and X11:Compiz (different vendor) * Start gnome-packagekit ("software update" in control-centre) Result:- Shows exactly the result from zypper lu, i.e. packages from the different vendor (X11:Compiz) are not shown, but all packages from factory-oss are shown. Using "zypper lu -a" also shows updates from X11:Compiz, confirming that packagekit's behaviour is now indeed "zypper lu". So this solves the main problem in my report, namely: not respecting version stickiness. Remarks:- For me however the expected behaviour of packagekit, in consistency with earlier versions of openSUSE (<= 11.3), is as a front-end to "zypper list-patches" as I described in the report. So I tried what was suggested in the message in the earlier comment, i.e. " Now you can disable packages as well, just create /etc/PackageKit/ZYpp.conf and set: [Updates] HidePackages=true " Then running gnome-packagekit shows just the patches from the default update repository. So this works too :) I would suggest that this be done by default, i.e., update packages be hidden and only patches shown in the packagekit interface by default. For those interested in seeing also update "package candidates", perhaps some information in the release notes regarding removing the ZYpp.conf file will help. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=637764 https://bugzilla.novell.com/show_bug.cgi?id=637764#c20 --- Comment #20 from Vincent Untz 2011-02-16 08:30:28 UTC --- (In reply to comment #19)

(I guess it's zypp.conf, not ZYpp.conf, right?)

Just read the patch, where I saw it's indeed ZYpp.conf. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=637764 https://bugzilla.novell.com/show_bug.cgi?id=637764#c22 Duncan Mac-Vicar changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED AssignedTo|bnc-team-gnome@forge.provo. |dmacvicar@novell.com |novell.com | --- Comment #22 from Duncan Mac-Vicar 2011-02-18 12:08:06 UTC --- It is indeed ZYpp.conf as it is in /etc/PackageKit and it is indeed specific to the PackageKit glue, so I followed the KitFashionCamelCase convention. zypp.conf is libzypp confuration and it is on /etc/zypp/zypp.conf. I will submit this to factory today and I leave up to Coolo to set the HidePackages as default (you will need to add the config file in the package). -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=637764 https://bugzilla.novell.com/show_bug.cgi?id=637764#c24 Vincent Untz changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED InfoProvider|wstephenson@novell.com | Resolution| |FIXED --- Comment #24 from Vincent Untz 2011-02-18 13:39:30 UTC --- Pushed the change, and added /etc/PackageKit/ZYpp.conf to PackageKit-branding-openSUSE. It doesn't change the default setting, but having the file makes it easier for people to change it. FWIW, I didn't change HidePackages in ZYpp.conf, after a very quick discussion on #opensuse-factory. But the file is there and is documented, so it's easy to change. Thanks Duncan! -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=637764 https://bugzilla.novell.com/show_bug.cgi?id=637764#c26 Marcus Meissner changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |meissner@novell.com --- Comment #26 from Marcus Meissner 2011-06-07 09:22:30 UTC --- http://download.opensuse.org/update/11.4-test/ has test PackageKit packages, if you want to test. please report back if it fixes this issue. (if you see new or different issue, please open new bugs, cc maintenance opensuse.org) -- 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.