Bug 26454 - RFE: Lacking information in gpk-update-viewer
Summary: RFE: Lacking information in gpk-update-viewer
Status: RESOLVED NOTABUG
Alias: None
Product: PackageKit
Classification: Unclassified
Component: General (show other bugs)
Version: unspecified
Hardware: All All
: medium enhancement
Assignee: Richard Hughes
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-02-06 05:41 UTC by EM
Modified: 2018-08-21 15:52 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description EM 2010-02-06 05:41:20 UTC
I'd like to see the following more or less vital information be displayed somewhere in gpk-update-viewer:

1. Which version of a package to be updated that's currently installed.
("Whoa, damn, I must have had v2 of fooapp! The update went all the way to v3, which is crap/incompatible with barapp/not preferred for whatever reason!")
("Hmm, I'll read the changelog to see what's changed from my currently installed version... Wait, WHAT version?")

2. Which repository that the proposed update is coming from.
("Damn, I just updated to the official distro GPL-only version of coolaudioplayer, which doesn't include MP3-support!")

3. The verbose package description provided by e.g. "yum info" or "rpm -qi", not just the often too vague summary.
("Hm, what does 'A library for foo support' really mean? Now I have to start a terminal and check with rpm -qi... Dang, I can't, RPM database locked by packagekit!")

4. Which mirror that selected updates are being downloaded from.
("Soooo sloooow... Is it a problem with my connection or the repo mirror? Wait, WHICH mirror? Maybe I'm downloading from Uzbekistan?")
Comment 1 Richard Hughes 2010-09-20 04:49:47 UTC
(In reply to comment #0)
> 1. Which version of a package to be updated that's currently installed.
> ("Whoa, damn, I must have had v2 of fooapp! The update went all the way to v3,
> which is crap/incompatible with barapp/not preferred for whatever reason!")
> ("Hmm, I'll read the changelog to see what's changed from my currently
> installed version... Wait, WHAT version?")

We only display the changelog with the difference from the installed version to the new version. Isn't that good enough for you?

> 2. Which repository that the proposed update is coming from.
> ("Damn, I just updated to the official distro GPL-only version of
> coolaudioplayer, which doesn't include MP3-support!")

I don't think the repo should matter -- the package name should be different if the package differs in functionality between different repos.

> 3. The verbose package description provided by e.g. "yum info" or "rpm -qi",
> not just the often too vague summary.
> ("Hm, what does 'A library for foo support' really mean? Now I have to start a
> terminal and check with rpm -qi... Dang, I can't, RPM database locked by
> packagekit!")

We're redesigning the updater as I speak to display a more application-centric view of updates.

> 4. Which mirror that selected updates are being downloaded from.
> ("Soooo sloooow... Is it a problem with my connection or the repo mirror? Wait,
> WHICH mirror? Maybe I'm downloading from Uzbekistan?")

We don't know the mirror until the download starts. And if a mirror fails, then we'll be using a different mirror altogether.

I don't think adding more complexity in the UI is a good thing, when we can fix bugs (like not using the mirror in Uzbekistan at all) and make it all much simpler.

Richard.
Comment 2 Richard Hughes 2018-08-21 15:52:29 UTC
We moved the upstream bugtracker to GitHub a long time ago. If this issue still affects you please re-create the issue here: https://github.com/hughsie/PackageKit/issues
 
Sorry for the impersonal message, and fingers crossed your issue no longer happens. Thanks.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.