|
Bugzilla – Full Text Bug Listing |
| Summary: | zypper lp output nearly useless | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 12.1 | Reporter: | Christian Boltz <suse-beta> |
| Component: | Maintenance | Assignee: | E-mail List <zypp-maintainers> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Critical | ||
| Priority: | P1 - Urgent | CC: | coolo, dmacvicar, dmueller, maintenance |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| Found By: | Beta-Customer | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Christian Boltz
2011-11-28 21:10:32 UTC
Looks like maintenance changed the naming schema and I suppose they are not going to change it back. We could try to inject the summary somewhere, but it's sometimes short Update for gbrainy update for bind sometimes long "yast2 kerberos" and "yast2 ldap" do not generate valid sssd.conf for multiple servers update for NetworkManager-gnome, NetworkManager, wpa_supplicant, gnome-control-center Given this, I'd tend to add it at the end after the status rather than embeding it somewhere in the inner table. Repository | Name | Version | Category | Status | Summary ------------+------------------+---------+-------------+--------+--------------- update-12.1 | openSUSE-2011-16 | 1 | recommended | needed | aaa_base: re.. update-12.1 | openSUSE-2011-17 | 1 | recommended | needed | xfce4-sessio.. Why not make it closer to a search result: who needs the "Repository"? Why is the status not a single letter? What is the point in showing "Version"? I also think it should be similar to a zypper "search" output (or even zypper search -s). - "Repository" is there because people requested it. - "Version" was interesting because we used to release multiple versions of a patch @Dirk: Will we have the same problem on SLE11-SP2 too? Who is "people"? People also request that the repository is shown when doing a 'zypper search'. Please aim for consistency. (I also think 'Version' should stay for the same reason) Consistency, yes. We need to separate data retrieval and it's representation in the table. Currently the zypper query code knows about the table layout and also fills in the data. Without cleaning this any changes to the layout are painfull and error-prone. No, at the moment the changes in patch naming are only planned for SLE12 and beyond. Quick fix in zypper-1.6.18. Summary appended. . *** Bug 592968 has been marked as a duplicate of this bug. *** |