| Summary: | "Packages to Remove" pop-up should communicate why packages need to be removed and what will replace them | ||
|---|---|---|---|
| Product: | [Applications] Discover | Reporter: | Nate Graham <nate> |
| Component: | PackageKit | Assignee: | Aleix Pol <aleixpol> |
| Status: | RESOLVED FIXED | ||
| Severity: | wishlist | CC: | bugseforuns |
| Priority: | NOR | Keywords: | usability |
| Version: | 5.11.4 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | https://commits.kde.org/discover/66bd5e3935db2bb3cfdd08bcd182b9bf5f279e58 | Version Fixed In: | |
| Sentry Crash Report: | |||
| Attachments: | "Packages to Remove" pop-up that doesn't really tell you what's happening | ||
I don't think PackageKit offers us this information... I'm afraid we'll have to go with it. We could show also the list of newly installed packages too, do you think that would help? Yes, that would be an improvement. Even if Discover couldn't logically connect the removals with the additions, presenting both at least lets the user make that connection. Git commit 66bd5e3935db2bb3cfdd08bcd182b9bf5f279e58 by Aleix Pol. Committed on 31/05/2018 at 01:59. Pushed by apol into branch 'master'. Make update warning about removal more verbose M +10 -6 libdiscover/backends/PackageKitBackend/PackageKitUpdater.cpp M +1 -1 libdiscover/backends/PackageKitBackend/PackageKitUpdater.h https://commits.kde.org/discover/66bd5e3935db2bb3cfdd08bcd182b9bf5f279e58 |
Created attachment 109388 [details] "Packages to Remove" pop-up that doesn't really tell you what's happening When an update needs to remove packages, it only tells you about the removal, and doesn't mention any new packages that will (likely) replace them. See attached screenshot. What's going on there is that my nightly build VLC 3.0.0 packages are being replaced by new VLC 3.0.0-rc1 packages. As a software guy, I can guess this based on what showed up in the original list of updates, but to my wife or mother, what's shown in the screenshot would have no meaning without at least some follow-up text that shows the packages that will replace them. This would also be useful for Kernel upgrades where packages are removed and replaced with new ones that have different names.