|
Bugzilla – Full Text Bug Listing |
| Summary: | zypper loops when command line argument is (miss) given as package or capability | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.0 | Reporter: | Carlos Gonçalves <cgoncalves> |
| Component: | libzypp | Assignee: | Jan Kupec <jkupec> |
| Status: | RESOLVED FIXED | QA Contact: | Duncan Mac-Vicar <dmacvicar> |
| Severity: | Critical | ||
| Priority: | P5 - None | CC: | robin.knapp |
| Version: | Beta 3 | Flags: | coolo:
SHIP_STOPPER-
|
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | zypper logs | ||
linux:/home/beta3 # du -sh /var/log/zypper.log 1003M /var/log/zypper.log JFYI ;-) This happens if you append options after the <name> argument. I had the same when I called: zypper -v install koffice2-kword --debug-solver It loops here: 2008-05-17 14:19:34 <0> linux(7556) [zypper] zypper-misc.cc(install_remove):539 trying: =debug-solver edition: debug-solver 2008-05-17 14:19:34 <0> linux(7556) [zypper] zypper-utils.cc(preparse_cap_str):315 capstr: =debug-solver 2008-05-17 14:19:34 <0> linux(7556) [zypper] zypper-utils.cc(preparse_cap_str):320 new capstr: =debug-solver 2008-05-17 14:19:34 <0> linux(7556) [zypper] zypper-utils.cc(preparse_cap_str):325 new capstr: = debug-solver Even if our syntax is wrong, zypper shouldn't be stuck in an endless loop; maybe it's the "--" which deselects and selects a package at once (my first guess) more context: 008-05-17 14:19:34 <0> linux(7556) [zypper] zypper-misc.cc(install_remove):539 trying: -debug=solver edition: solver 2008-05-17 14:19:34 <0> linux(7556) [zypper] zypper-utils.cc(preparse_cap_str):315 capstr: -debug=solver 2008-05-17 14:19:34 <0> linux(7556) [zypper] zypper-utils.cc(preparse_cap_str):320 new capstr: -debug =solver 2008-05-17 14:19:34 <0> linux(7556) [zypper] zypper-utils.cc(preparse_cap_str):325 new capstr: -debug = solver 2008-05-17 14:19:34 <0> linux(7556) [zypper] zypper-misc.cc(install_remove):539 trying: =debug-solver edition: debug-solver 2008-05-17 14:19:34 <0> linux(7556) [zypper] zypper-utils.cc(preparse_cap_str):315 capstr: =debug-solver 2008-05-17 14:19:34 <0> linux(7556) [zypper] zypper-utils.cc(preparse_cap_str):320 new capstr: =debug-solver 2008-05-17 14:19:34 <0> linux(7556) [zypper] zypper-utils.cc(preparse_cap_str):325 new capstr: = debug-solver 2008-05-17 14:19:34 <0> linux(7556) [zypper] zypper-misc.cc(install_remove):539 trying: -debug=solver edition: solver 2008-05-17 14:19:34 <0> linux(7556) [zypper] zypper-utils.cc(preparse_cap_str):315 capstr: -debug=solver 2008-05-17 14:19:34 <0> linux(7556) [zypper] zypper-utils.cc(preparse_cap_str):320 new capstr: -debug =solver 2008-05-17 14:19:34 <0> linux(7556) [zypper] zypper-utils.cc(preparse_cap_str):325 new capstr: -debug = solver 2008-05-17 14:19:34 <0> linux(7556) [zypper] zypper-misc.cc(install_remove):539 trying: =debug-solver edition: debug-solver 2008-05-17 14:19:34 <0> linux(7556) [zypper] zypper-utils.cc(preparse_cap_str):315 capstr: =debug-solver 2008-05-17 14:19:34 <0> linux(7556) [zypper] zypper-utils.cc(preparse_cap_str):320 new capstr: =debug-solver 2008-05-17 14:19:34 <0> linux(7556) [zypper] zypper-utils.cc(preparse_cap_str):325 new capstr: = debug-solver Fixed in zypper revision r10166, passing to Jan so he can close it when the package is submitted. submitted |
Created attachment 216103 [details] zypper logs Seems that any zypper command with --no-recommends makes zypper looping, using 100% of the CPU and A LOT of disk space with its logs. Just to have an idea: leaving 'zypper in -t pattern KDE3 --no-recommends' for ~2minutes (Ctrl+C ftw!) took +700MB of space...