|
Bugzilla – Full Text Bug Listing |
| Summary: | problems with one-click installation and keys of third-party repositories | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.3 | Reporter: | Ulrich Windl <Ulrich.Windl> |
| Component: | YaST2 | Assignee: | Ladislav Slezák <lslezak> |
| Status: | RESOLVED FIXED | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Normal | ||
| Priority: | P4 - Low | CC: | dmacvicar |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | x86 | ||
| OS: | openSUSE 11.3 | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Bug Depends on: | 713068 | ||
| Bug Blocks: | |||
|
Description
Ulrich Windl
2011-05-17 08:45:30 UTC
For zypper you should use trust temporarily. Sadly YaST changed the dialogs in a way that IMO is not right: removed trust now, and changed it to "Import". This has to be fixed. Users not even know what import means. And import is an implementation detail. The real concept is trust: now, forever, or just don't. (In reply to comment #1) > The real concept is trust: now, forever, or just don't. IIRC there was a (feature?) request to simplify the selection, so there is "import" (forever) and "cancel" (never). ad 2) this is a different problem (either in gnome applet or in packagekit), please create a separate bug report for it. Ulrich, the title says "one-click installation", could you provide the URL for reproducing the problem? How can I reproduce it (step-by-step)? Even if you keep the two (forever) (never), the wording "Import" is an implementation detail of the "Trust" action. As a non technical user "Trust" something makes sense to me, but "Import" does not. The label has been fixed in yast2-2.21.11. Moreover I have slightly improved the layout and look in ncurses UI. Resolving as FIXED (the second problem needs to be solved separately, see comment #2). Reopening, as the fix seems to introduce bug #713068. Bug #713068 has been fixed in yast2-2.21.13, closing this bug. |