http://bugzilla.novell.com/show_bug.cgi?id=545258 User dave.plater@yahoo.co.uk added comment http://bugzilla.novell.com/show_bug.cgi?id=545258#c545242 Summary: zypper dup exits silently when package is skipped using DownloadInAdvance Classification: openSUSE Product: openSUSE 11.2 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: libzypp AssignedTo: zypp-maintainers@forge.provo.novell.com ReportedBy: dave.plater@yahoo.co.uk QAContact: qa@suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.3) Gecko/20090909 SUSE/3.5.3-1.4 Firefox/3.0.6, Ant.com Toolbar 1.3 zypper dup doesn't even inform the user what is happening if a package is skipped when using the DownloadInAdvance option and the user has to guess that nothing has been installed and zypper dup needs to be restarted. I would expect at least a message that states a zypper refresh is required and zypper dup needs to be rerun. Reproducible: Always Steps to Reproduce: 1.zypper dup 2.MPlayer from packman repo fails to download completely and times out 3.Tell zypper to ignore Actual Results: zypper dup exits without installing any packages Expected Results: The ideal situation:- the solver runs again to check for failed dependencies and installs what it can The minimum situation:- zypper displays a message that a package has failed to download and the user must rerun zypper dup after refreshing In my case I was updating 2.1 GiB of packages on a beta trial internet connection and due to a very bad connection and bug #545242 I deliberately skipped MPlayer and used aria2c to download it directly into the packman package cache. It would have been a nice surprise if zypper had rechecked the package cache and completed the installation but instead it left me wondering whether the new feature was working at all. When I reran zypper dup without a refresh, it completed the process. DownloadInAdvance is a nice feature but what happens when a package is skipped needs a lot of thought. See https://bugzilla.novell.com/show_bug.cgi?id=545242 for logs -- 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.