http://bugzilla.novell.com/show_bug.cgi?id=498875
User poeml@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=498875#c5
--- Comment #5 from Peter Poeml
This is intended. You should run 'zypper refresh' before updating, or you should enable autorefresh for the repo(s). Whichever suits you. (still it can happen if a repo changes during the download/install process).
But yes, we could check for the files before actually starting with downloading (& installing). So that the apps could tell the user 'the repo is out of date, do a refresh'. I don't see why not (the additional does-file-exist requests should not harm, as long as we provide also progress reporting).
(not a bug, though, changing to enhancement)
zypper refreshes by itself, if it hasn't run for some (unknown to me) time. This is what happened in my case. So there was no point in running 'zypper refresh' before updating in my case. Thus, the repository was not outdated when I started the update. It became outdated during the update (as proven by the rsync log line which shows the deletion of the requested package shortly before my powerbook attempted to download it). zypper should a) NOT ruin your system by an incomplete update, and it should NOT start the update before all needed packages have been downloaded. b) (if you ask me) if it encounters a 404 (from the server, not after a redirect) for a package, it should do a quick check on the timestamp of the repository to see whether it has changed since zypper was started. If so, it should refresh and restart. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.