Bug 395945 - Discover displays and allows updating packages that apt says have been intentionally held back
Summary: Discover displays and allows updating packages that apt says have been intent...
Status: RESOLVED DUPLICATE of bug 396288
Alias: None
Product: Discover
Classification: Applications
Component: PackageKit (show other bugs)
Version: 5.12.5
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Aleix Pol
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-06-28 05:22 UTC by Nate Graham
Modified: 2018-10-11 16:23 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Packages held back marked as upgradeable (420.33 KB, image/png)
2018-06-28 05:22 UTC, Nate Graham 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Nate Graham 2018-06-28 05:22:03 UTC 
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?).
Comment 1 Aleix Pol 2018-06-28 11:36:17 UTC 
Possibly a bug in PackageKit. Can you check with "pkcon update"?
Comment 2 Christoph Feck 2018-07-18 16:55:51 UTC 
If you can provide the information requested in comment #1, please add it.
Comment 3 Christoph Feck 2018-08-02 17:25:23 UTC 
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.
Comment 4 Nate Graham 2018-08-03 13:58:09 UTC 
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.
Comment 5 Aleix Pol 2018-10-11 16:23:51 UTC 
*** This bug has been marked as a duplicate of bug 396288 ***