Hi, You didn't update via YaST2 then? That should explain it. YaST2 has no way of tracking patches it did not install itself. 'Fortunately', YaST2 can be quite easily fooled. You could try this as root: cd /var/lib/YaST/patches/i386/update/7.2/patches mv aaa_base-1.<YYYYMMDD>.new aaa_base-1.<YYYYMMDD>.installed Here <YYYYMMDD> appears to be the date of download of the patch. Hereafter, YaST2 will not show aaa_base in the update list anymore. If you want to be sure that a package is installed execute the command (root privileges not required): rpm -q <package name> In my case: tim@gaia:~ > rpm -q aaa_base aaa_base-2001.8.23-0 I wonder whether the proxy is the problem. YaST2 expects to find patches in a very specific directory tree. If you change the server/harddisk download settings, make sure the patch descriptions can be found from there in the relative path i386/update/7.2/patches Good luck, Tim On Mon, Sep 10, 2001 at 08:56:40AM +0200, Ivan Sergio Borgonovo wrote:
Since I had some problem with proxy and YaST2 I decided to let YaST suggest me the update and download the rpm [1].
I've downloaded the aaa_base.rpm and installed it but when I check again with YaST2 what I should update the aaa_base.rpm is still in the list.
How can I be sure I've installed it? and how can I remove it from the "suggested download" list if I've installed it?
[1] it would be nice if YaST worked better with proxies.
TIA
-- Salve Ivan Sergio Borgonovo http://www.webthatworks.it/
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com