A bit of testing confirms that I'm right, Yast is deleting the installed files first. For example, I just tried to upgrade a few rpms, including libbz2. So the installer deletes libbz2, then tries to install the new rpm, but fails because libbz2.so.1 is missing so it can't unpack it. Ouch! Also, the full error message when the delete fails makes it clear that it is an rpm error from trying to remove the actual package files. John. --- John Layt <johnlayt@yahoo.com.au> wrote:
Up to this morning, Yast would happily apply upgrades as rpm upgrades. After applying the latest Yast version, it now appears to be applying upgrades as a delete then an install. I'm basing this on what I think is the new appearance in the Yast update progress listing of lines of 'Deleting xxx' that delete all the packages selected for upgrade, followed by the downloads and installs. Now, that could just be deleting the rpm files from cache, in which case the message needs to be changed to something less scary, but I think it does delete the installed package. Trouble here is that if there is then a problem with the download or install, like I had 3 times running, your system can be seriously borked with important files deleted and not yet replaced. It's also not helped by the Abort and Cancel buttons not working properly when a problem is reported, or that network issues don't even return an error message and give you the chance to skip, your install is automatically aborted and you're dumped back to Yast with a borked system, or that trying to reapply failed installs re-downloads everything again (this was a problem yesterday, today you don't get there as you get error messages that the delete failed, and the skip abort buttons get all random on you).
Has anyone else seen this, or am I way off-base here?
Send instant messages to your online friends http://au.messenger.yahoo.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org