On 1/29/2009 at 10:00 AM, Eberhard Moenkeberg <emoenke@gwdg.de> wrote: But don't miss the major aspect he has pointed to:
Waiting/stopping in the middle of the update process is bad design.
No arguing there... but like you just did: it has to stay on topic, without insults. On the other hand if an rpm can't be downloaded, I'm not sure if zypper should just 'skip' this one, finish the rest of it's task and install what it downloaded. This could render your system very very unusable (think of libzypp changing so version, thus a new zypper links against it. zypper is downloaded, libzypp fails. zypper being installed and libzypp skipped. you'll not be able to start zypper anymore.). So at best the 'remainings' can be tried to be downloaded, but I would for sure not like the PM trying to install the packages which could be downloaded. Sure, make the PM very smart to skip a whole bunch of packages that depend on each other. Which would in fact mean that after every skipped package you have to run the solver. which might be as broken an idea as nothing else: repodata might have changed on the server. New conflicts appear, existing conflicts that were solved by the user invalidated.... you name them. I think the approach with more potential that was mentioned in the list is in fact to find a solution to keep packages that get replaced for 24 hours longer on the mirror. This would help against change of repodata in the middle. Dominique -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org