http://bugzilla.novell.com/show_bug.cgi?id=498875 User poeml@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=498875#c1 --- Comment #1 from Peter Poeml 2009-04-28 09:36:40 MDT --- The package was in fact deleted in the repository, during my ongoing update. 2009/04/28 17:05:24 [5687] buildservice2.suse.de del. suse/ppc/yast2-2.18.14-1.1.ppc.rpm 0 0 The PPC Factory doesn't have the staging, and keeping of old packages, that the x86 Factory has, so the problem is inevitable. Closing as wontfix... -- 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.

http://bugzilla.novell.com/show_bug.cgi?id=498875 User jkupec@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=498875#c3 Ján Kupec changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Major |Enhancement --- Comment #3 from Ján Kupec 2009-04-28 09:48:14 MDT --- eh. forgot to change to enhancement (and you forgot to wontfix :O) -- 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.

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 2009-04-28 09:58:46 MDT --- (In reply to comment #2)

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.

http://bugzilla.novell.com/show_bug.cgi?id=498875 User jkupec@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=498875#c7 --- Comment #7 from Ján Kupec 2009-04-29 02:35:34 MDT --- (In reply to comment #5)

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.

Michael Andres already works on this IIRC - this will be one (the default, i guess) mode of operation. The current mode being the other. With the current mode there is always this risk.

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.

Yup, that's what i would do here....

If so, it should refresh and restart.

.. but i would only print a hint ("repo is out of date, do zypper refresh, and run the original command again."), instead of doing it automatically. @zypp people: what about the idea from comment #2? -- 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.

http://bugzilla.novell.com/show_bug.cgi?id=498875 User ma@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=498875#c9 Michael Andres changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |ma@novell.com Resolution| |FIXED --- Comment #9 from Michael Andres 2009-09-18 13:47:15 MDT --- libzypp-6.16.0 has a commit.downloadMode option in zypp.conf. Using downloadInAdvance should solve this bug. -- 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.