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 Peter
-----Original Message----- From: Duncan Mac-Vicar Prett [mailto:dmacvicar@suse.de] Sent: Tuesday, January 26, 2010 9:34 PM To: zypp-devel@opensuse.org Subject: Re: [zypp-devel] zypp backend for PackageKit
On Tuesday 26 January 2010 13:27:25 Zhu, Peter J wrote:
Thanks Reeves.
But I still have issue getting it running correctly. 'zypper list-updates' does get a list of updates(yes, I do have them) but 'pkcon get-updates' said "There are no updates available at this time". Any idea?
We implement get-updates as zypper lp which list official patches released as updates.
-- Duncan Mac-Vicar P. - Novell® Making IT Work As One™ SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg)
-- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org