Hi, I think some things are a bit blurred here: On Mon, Feb 23, 2009 at 01:13:55PM +0100, Adrian Schröter wrote:

Am Montag, 23. Februar 2009 13:04:23 schrieb Lars Marowsky-Bree:

...

Hi,

when running a largeish "zypper dup", it can easily happen that one of the repos is refreshed on the server side, causing the packages which zypper wants to pull to disappear.

This then needs interactive resolution during the upgrade process, which is mightily annoying.

Could the build service at least keep the packages from the last hour or so?

this about to get implemented atm.

That was Factory. Would theoretically work for the build service too, but feasibility is limited by the sheer number of projects x build targets (59.000 directories), and size of the tree (679G), and we would need to keep old packages (albeit out of reach of the mirrors) which is a little bit out of scope with our capacities.

...

Or does zypper need to be modified to 'retry smarter', ie by refreshing the repo and applying the same choices to the solver, ...?

I do not think that it is wanted that you suddenly need to redo the solving during the process.

I agree with Lars, zypper should really "retry smarter", by checking for updated metadata (after prompting the user, or after several retries), before giving up. The short-living repositories have comparatively small metadata, typically, so it could be quick download, and I'd expect that libzypp is rather fast in calculating again. Thus automating the manual "retry" that the user needs to do otherwise.

However, zypper could fail smarter, Peter is already testing some new implementation of zypper.

The smarter zypper (which will arrive in Factory shortly) fixes only the half of the problem -- it requires that the packages are known and available on download.opensuse.org. For Factory, this will both be the case soon; a large "zypper dup" there should no longer run into this refresh problem. It *is* conceivable that download.opensuse.org returns a mirror list for files that are no longer there and would yield a 404 normally. Once I have some other more essential things working I could look into that... This is a bit error-prone because mirrors might already be "loosing" such files (because they are syncing). But with the "smarter zypper" there would be some chance to find the old package. -Tracking of mirror syncs is another direction in which I want to look further, once we have a better mirror push. Peter -- Contact: admin@opensuse.org (a.k.a. ftpadmin@suse.com) #opensuse-mirrors on freenode.net Info: http://en.opensuse.org/Mirror_Infrastructure SUSE LINUX Products GmbH Research & Development -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org