|
Bugzilla – Full Text Bug Listing |
| Summary: | Sources Shown with Weird Number IDs in Versions Tab | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 10.2 | Reporter: | Rebecca Walter <rwalter> |
| Component: | YaST2 | Assignee: | Stefan Hundhammer <shundhammer> |
| Status: | RESOLVED FIXED | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | andreas.hanke, kkaempf, ma, ro |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | Screen shot: versions view with inst source URL | ||
|
Description
Rebecca Walter
2007-01-08 13:22:20 UTC
We should at least provide the URL. URLs would make me very happy. Currently, that versions view uses zypp::Product::summary(). Those summaries never seem to contain anything meaningful. Those numbers that get displayed may be useful for the CD makers, but for sure it doesn't mean anything to the end user. The way it is now is unsatisfactory if you have any more than one installation source. You don't even know what packages you'll get from the update server, rather than from the CD or DVD. As an end user, I'd like to see something like "openSUSE 10.2 download version" or "openSUSE update server", not "4711-0815". Klaus, Rudi, how are the products' fields defined, and how are they actually used? The product and the repository are not related. A repository can carry multiple products, a product might be available through multiple repositories. The current 1:1 interpretation of product:repository is a bug/hack since neither 'YaST-type' (on CD or DVD) nor 'repomd-type' repositories support a repository name. For the YaST-type this is acceptable since a CD/DVD usually contains a single product. There are recent (not yet in libzypp) extensions to the repomd standard which allow to name a repository. (IIRC this 'bug' is already covered in FATE) That's why the UI has a function "singleProduct()" that searches an installation source for products. Only if it contains exactly one product, this one is returned, and that's what you see in that view. It's a pragmatic approach. But it turns out that it works in all real-life use cases. But the content of those products are not really giving very much useful information. I'd happily display useful information about the repository itself if only there were any. But so far I couldn't find anything that might mean anything to the end user. The product issue does not give me any reason why my installation sources are identified by unidentifiable numeric gibberish in the package manager. I would like to know on what _SOURCE_ the different versions are available. Why is this gibberish used instead of something human-readable? I entered human-readable information about the source when I created it. Why can't I see that instead? For now I added the installation source URL. It's not much, but at least it is some giveaway where each version comes from. Created attachment 116305 [details]
Screen shot: versions view with inst source URL
I consider this a significant improvement. Thank you! |