|
Bugzilla – Full Text Bug Listing |
| Summary: | system tray updater different from "sudo zypper up" | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.0 | Reporter: | Bernhard Koenig <b.a.koenig> |
| Component: | libzypp | Assignee: | E-mail List <zypp-maintainers> |
| Status: | RESOLVED INVALID | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | dmacvicar, tgoettlicher |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | 32bit | ||
| OS: | openSUSE 11.0 | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Bernhard Koenig
2008-07-14 13:04:25 UTC
I had the "Zypp Backend" in the system tray icon, by the way. Hi. Yes, this is intented. The applet show what 'zypper lu -t package -t patch' shows (depending on how it is configured). Then executes 'zypper in <packages-you-select>', not 'zypper up'. Hmm, why does it deal with packages? That breaks our patch concept somewhat. And selecting packages from "zypper lu -t package" is dangerous, as the "zypper in" is done in forceResolv mode and "zypper lu" doesn't run the solver, so it doesn't detect if the update forces some bad changes. (In reply to comment #3 from Michael Schröder) > Hmm, why does it deal with packages? That breaks our patch concept somewhat. People wanted it. It is optional, you can configure the applet to deal with patches only (i don't know what is the default). > And selecting packages from "zypper lu -t package" is dangerous, as the "zypper > in" is done in forceResolv mode The applet runs zypper in non-interactive mode, forceResolve=false is used there. ... and it uses 'zypper in' instead of 'zypper up' because it allows you to select packages to update from the list, IIRC. (In reply to comment #4 from Ján Kupec) > People wanted it. It is optional, you can configure the applet to deal with > patches only (i don't know what is the default). Default is patches only. The option that enables packages mentions "for experts only". Closing as invalid. We are working in making the patch/package issue more clear. |