Bug 390570 - Discover sources list is not verbose enough for repositories
Summary: Discover sources list is not verbose enough for repositories
Status: RESOLVED DUPLICATE of bug 390569
Alias: None
Product: Discover
Classification: Applications
Component: discover (show other bugs)
Version: 5.12.1
Platform: Kubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Aleix Pol
Depends on:
Reported: 2018-02-16 17:09 UTC by Andrew Crouthamel
Modified: 2018-09-13 18:22 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:

Discover showing ambiguous repository sources (1.18 MB, image/png)
2018-02-16 17:09 UTC, Andrew Crouthamel

Note You need to log in before you can comment on or make changes to this bug.
Description Andrew Crouthamel 2018-02-16 17:09:12 UTC
Created attachment 110724 [details]
Discover showing ambiguous repository sources

Discover has recently changed the sources list so it no longer shows the full URL. While this has cleaned up the interface, it has made it difficult to determine the differences between the repositories listed. Please see attached screenshot. Even with the future addition of (sources) as I've been told is coming, it will still be ambiguous as to what each repository is.

A good example of this is at the very bottom of the attached screenshot. That repository is actually:

deb https://download.virtualbox.org/virtualbox/debian artful contrib

And so should have some description regarding it being for VirtualBox.

I'd like to recommend at least including the base domain name in the source description. So instead of:

Artful (contrib)

It would be:

Artful virtualbox.org (contrib)

This would work well for the default Ubuntu repos as well:

Artful updates (multiverse)

Would become:

Artful updates ubuntu.com (multiverse)

Or, put the base domain name first, whatever you think is best. Either way, it would be more descriptive, without cluttering the interface with the full URL like before.
Comment 1 Aleix Pol 2018-02-22 18:33:21 UTC

*** This bug has been marked as a duplicate of bug 390569 ***
Comment 2 Nate Graham 2018-09-13 18:22:03 UTC
*** Bug 398585 has been marked as a duplicate of this bug. ***