http://bugzilla.novell.com/show_bug.cgi?id=492261 User jkupec@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=492261#c2 --- Comment #2 from Ján Kupec 2009-07-31 06:35:03 MDT --- I don't see much benefit in this. What's wrong with simply restarting the operation? You'll need to do that at least once to proceed anyway. Or did you have something else in mind? If the user wants to run non-interactively e.g. from cron, to get the system updated and avoid failure because of temporary network problem, s/he can repeat the operation in the script until it succeeds. -- 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=492261 http://bugzilla.novell.com/show_bug.cgi?id=492261#c4 Jon Nelson changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|WONTFIX | --- Comment #4 from Jon Nelson 2010-08-10 21:26:40 UTC --- I'm reopening this bug because I do feel the functionality is worth having. Frequently, when internet connectivity is poor (as it frequently is for many people) it's convenient to be able to ignore failed or bad downloads (like checksum failures). Therefore I'd like to propose a --batch or --continue mode where zypper ignores non-fatal errors and continues on to the next download. Today, todayloading KDE 4.5.0, at least a half-dozen times I had to tell zypper to ignore the error and continue. However, that also meant that I had to sit and observe zypper for over an hour. It seems to me that people that want a --batch or --continue mode are somewhat more advanced users and are willing to live with the *possibility* (unlikely) that couple of failed downloads out of many will hose a system -- especially since a --batch mode would likely report at the end of the operation "Unable to download: foo bar and baz". Asking the user to simply repeat the operation isn't necessarily a feasible one. -- 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=492261 http://bugzilla.novell.com/show_bug.cgi?id=492261#c6 --- Comment #6 from Jon Nelson 2010-08-11 13:42:41 UTC --- While using DownloadAsNeeded (the default) combined with a batch-like mode is very slightly less "safe" (in a real but statistically unlikely way), I've generally found that the other modes all essentially behave like DownloadInAdvance (I've never actually seen DownloadInHeaps behave differently than DownloadInAdvance - although I admit that it's been a month or two since I tried). Given the scenario I was faced with last night - downloading over 100 packages from a seemingly slow and problematic server (checksum errors) - I would have much preferred to just tell zypper "do what you can" and walk away, come back a hour or two later, and fix anything that went wrong. Given that most users that would use a batch-like mode are more advanced, it seems to me that such actions are within the realm of expectations. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=492261 https://bugzilla.novell.com/show_bug.cgi?id=492261#c8 Michael Andres changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|ma@novell.com | --- Comment #8 from Michael Andres 2010-09-06 13:09:03 CEST --- It should. Downloading leaves the package in the cache until it actually gets installed. Only the attempt to install will remove it if 'keeppackages=0'. (yes, you may have a nonempty cache even if 'keeppackages=0') -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=492261 https://bugzilla.novell.com/show_bug.cgi?id=492261#c10 Michael Andres changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Normal |Enhancement --- Comment #10 from Michael Andres 2013-01-24 11:31:39 CET --- There's still no --continue option which would cause to download as much as possible if used together with --non-interactive. -- Configure bugmail: https://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=492261 Eberhard Kümmerle changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |E.Kuemmerle@fz-juelich.de --- Comment #11 from Eberhard Kümmerle --- I'm managing a number of desktop systems and I use cron.daily/opensuse.org-online_update to patch them. Currently, this fails because a minor important repository is not available: File '/repodata/repomd.xml' not found on medium 'http://download.videolan.org/pub/videolan/vlc/SuSE/13.2' Abort, retry, ignore? [a/r/i/? shows all options] (a): ABORT request: Aborting requested by user I would indeed very much appreciate if the major updates from the opensuse repo would still be installed automatically in such a situation. So I think some kind of --continue or --ignore-minor-errors would be very helpful here! -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=492261 --- Comment #13 from Eberhard Kümmerle --- For those, who want an immediate solution and accept the risks described by Michael Andres: I wrote the following script 'zypper-ignore-errors' that calls zypper in interactive mode and provides the needed answers automatically: ################## #!/usr/bin/perl use Expect; # needs package 'perl-Expect' use strict; my $exp = Expect->spawn('zypper', @ARGV); while ($exp->expect(36000, [ qr|Abort, retry, ignore\? \[a/r/i.*\):|, sub {$exp->send("i\n");}], [ qr|Do you want to disable the repository .* permanently\?|, sub {$exp->send("no\n");}], [ qr|\? \[.*\):|, sub {$exp->send("\n");}] )) {} ################## You can call it like that (important: WITHOUT --non-interactive): zypper-ignore-errors --quiet up -t patch --auto-agree-with-licenses Best regards, Eberhard -- You are receiving this mail because: You are on the CC list for the bug.