This is something I've seen often, but never understood. I went to apply the y2base-2.2.7-10.i386.rpm and received the following messages: Found 0 source and 1 binary packages installing binary packages file /usr/lib/YaST2/bin/parted from install of y2base-2.2.7-10 conflicts with file from package y2client-2.2.11-0file /usr/lib/YaST2/plugin/libpy2makefs.so.2.0.0 from install of y2base-2.2.7-10 conflicts with file from package y2client-2.2.11-0file /usr/lib/YaST2/plugin/libpy2makereiserfs.so.2.0.0 from install of y2base-2.2.7-10 conflicts with file from package y2client-2.2.11-0file /usr/lib/YaST2/plugin/libpy2packager.so.2.0.0 from install of y2base-2.2.7-10 conflicts with file from package y2client-2.2.11-0file /usr/lib/YaST2/plugin/libpy2parted.so.2.0.0 from install of y2base-2.2.7-10 conflicts with file from package y2client-2.2.11-0 If I am reading things correctly, the y2base-2.2.7-10 is newer than y2client-2.2.11-0. I will admit I don't understand RPM as well as I would like. Are these messages simply the result of having files relocated from one package to another? Could the update RPM have been packaged differently so as not to generate these messages? How do I know that I'm not doing something undesierable to my system? In the past I have simply selected the replace files button - when using kpackage. And I will do so now, but I don't like the feeling I get when this happens. Any ideas? TIA, Steve