https://bugzilla.novell.com/show_bug.cgi?id=400773 User stbinner@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=400773#c1 Stephan Binner changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID --- Comment #1 from Stephan Binner 2008-06-17 02:37:27 MDT --- kdebase3-ksysguardd doesn't exist anymore in 11.0 and kdebase4-workspace-ksysguardd provides kdebase3-ksysguardd = 3.5.90 -- 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=400773 User jkupec@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=400773#c3 Ján Kupec changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jkupec@novell.com AssignedTo|zypp-maintainers@forge.provo.novell.com |jkupec@novell.com Status|REOPENED |ASSIGNED --- Comment #3 from Ján Kupec 2008-06-17 04:16:51 MDT --- This is intended. If the requested packages cannot be found by name, zypper falls back to search by capability. Maybe some feedback could be added here. --name forces selection by name, --capability is available too. -- 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=400773 User jkupec@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=400773#c5 Ján Kupec changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |zypp-maintainers@forge.provo.novell.com --- Comment #5 from Ján Kupec 2008-06-17 05:10:17 MDT --- Ah, OK. The difference is that with --name zypper marks the resolvable for installation on its own (poolitem.status().setToBeInstalled(zypp::ResStatus::USER )), without --name it just adds requirement (Resolver::addRequire()). I'm not sure what to do - zypper added a requirement (the package name), solver has chosen the best package providing it. I'd say that is what we want. After all it was probably one of the reasons why we were told to stop setting status of pool items on our own and just add requirements. And the user can force selection by name if he's not satisfied with the solution. Any idea what to change here? -- 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=400773 User mls@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=400773#c7 --- Comment #7 from Michael Schröder 2008-06-17 05:51:45 MDT --- Note that the current implementation of --name in zypper is bad: the solver should choose the right package, not zypper. This can't be done with current libzypp, though, you need Schubi's new interface for it. Plus, we might want to add an iterator to libzypp that returns packages that match a dependency with their NEVR instead of their provides list. (It would basically be the iterator over the provides plus filtering with libsatsolver's pool_match_nevr() function.) -- 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=400773 User mls@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=400773#c9 --- Comment #9 from Michael Schröder 2008-06-17 06:10:45 MDT --- (Actually we still use capabilities, "foo" is a capability in both cases) -- 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=400773 User schubi@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=400773#c11 --- Comment #11 from Stefan Schubert 2008-06-17 09:08:10 MDT --- The call is: /** * Resolve package dependencies: * * The solver works off the given queue and writes back the solution * to pool. * * Returns "true" on success (i.e., if there were no problems that * need user interaction) and "false" if there were problems. In * the latter case, use problems() and later applySolutions() * below. * The solution could be that the solver remove/add some entries * in the task queue. So make a new call of resolveQueue after you * have applied any solution AND check the parameter "queue" if * there has been any changes by the solver and adapt these changes * to e.g. the selectables. * **/ bool resolveQueue (solver::detail::SolverQueueItemList & queue); -- 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.