| Summary: | Discover displays and allows updating packages that apt says have been intentionally held back | ||
|---|---|---|---|
| Product: | [Applications] Discover | Reporter: | Nate Graham <nate> |
| Component: | PackageKit | Assignee: | Aleix Pol <aleixpol> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version First Reported In: | 5.12.5 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | Packages held back marked as upgradeable | ||
Possibly a bug in PackageKit. Can you check with "pkcon update"? If you can provide the information requested in comment #1, please add it. To further investigate this issue, KDE developers need the information requested in comment #1. If you can provide it, or need help with finding that information, please add a comment. In order to provide the information Aleix has requested, I need another batch of updates to come in that `apt` doesn't want to apply, so I can issue `pkcon update` to see if PackageKit ignores those restrictions, or if it's Discover that ignores PackageKit (much less likely, but still possible I guess). No such problematic update has been offered, so I'm still waiting. *** This bug has been marked as a duplicate of bug 396288 *** |
Created attachment 113616 [details] Packages held back marked as upgradeable See attached screenshot. apt won't let me upgrade 100 packages, but Discover will; the held-back packages are presented normally, and clicking on the Update All button upgrades them, with unknown consequences (surely there was a reason why they were held back?).