https://bugzilla.novell.com/show_bug.cgi?id=346014 Summary: zypper: sluggish dependence resolution Product: openSUSE 10.3 Version: Final Platform: i686 OS/Version: openSUSE 10.3 Status: NEW Severity: Minor Priority: P5 - None Component: libzypp AssignedTo: dmacvicar@novell.com ReportedBy: estellnb@gmail.com QAContact: dmacvicar@novell.com Found By: Community of Practice If zypper is used to install multiple packages at once (zypper -in pkg1 pkg2 ..), a singleton package can cause the dependence resolution process to fail. Nonetheless removing that package from the install list for the first run and installing it solely per se afterwards has worked well in two different cases (pressing retry multiple times had no effect). complaints: 'package XY can not be installed because of missing dependences' 'can not find unique solution when using the best architecture only' Why does Zypper not simply leave the offending package(s) out for the first run in order to try to install them/it in a second run under the assumption that all other packages have already been installed? As long as the number of packages remaining left for the next round (why not enter a second, third iteration, etc.) this procedure should perhaps be repeated without prompting the user for retry/abort. To me a warning would be fully sufficient to tell the user that dependence resolution is not working straight forward an that zypper is still working and does not hang (aborting by keybord-intr always possible during dep. resolution; isn`t it). In its current state the abort/retry loop does not seem to have any effect. Examples:
zypper in $(cat suse-inst.lis) ~~ failed even after multiple retries zypper in $(cat suse-inst.lis|grep -v python-twisted-xish) ~~ has worked (complaints about python-twisted-xish before)
zypper in $(cat Packman-inst.lis) ~~ failed even after multiple retries zypper in $(cat Packman-inst.lis|grep -v csound-python) ~~ has worked (complained about csound-python)
-- 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.