On 1/26/2010 at 07:31 AM, "Zhu, Peter J"
wrote: I'm not sure I follow what you said. So you mean it's normal and by design? With such design, as I launch gpk-update-viewer(GUI in gnome-packagekit), I can't see any updates because both "pkcon get-updates" and gpk-update-viewer uses pk_client_get_updates_async which finally call backend_get_updates_thread() in pk-backend-zypp.cpp to get updates with libzypp. I noticed below snippets from that function // get all Packages and Patches for Update std::setzypp::PoolItem *candidates = zypp_get_patches (); //std::setzypp::PoolItem *candidates2 = new std::setzypp::PoolItem (); if (!_updating_self) { // exclude the patch-repository std::string patchRepo; if (!candidates->empty ()) { patchRepo = candidates->begin ()->resolvable ()->repoInfo ().alias (); }
//candidates2 = zypp_get_updates (patchRepo);
//candidates->insert (candidates2->begin (), candidates2->end ()); }
So you use zypp_get_patches rather than zypp_get_updates to get updates? Why such design
The goals of the updaters are not the same as the goals of manual interactive package management. The updaters are designed to maintain the stability of your system - generally it should be safe to throw on any updates listed. Only approved, vetted and tested updates show up - ie as Ducan said only official patches from the update repo. Manual interactive package management is completely separate. If you have installed package foo from repo foome and a new release is made then you can if you wish install that new bleeding edge version (or pick an intermediate version, or uninstall it or ...) with zypper. But you don't want that just automatically showing up in the updaters.. -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org