| Summary: | Discover unable to proceed when some small changes found in APT sources | ||
|---|---|---|---|
| Product: | [Applications] Discover | Reporter: | Daniel Duris <kdebugs> |
| Component: | discover | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED UPSTREAM | ||
| Severity: | major | CC: | aleixpol, nate |
| Priority: | NOR | ||
| Version First Reported In: | 6.3.5 | ||
| Target Milestone: | --- | ||
| Platform: | Neon | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Daniel Duris
2025-05-19 08:58:26 UTC
This is a limitation in the APT PackageKit plugin, which Discover uses for this. Because the PackageKit library intentionally does not support showing multiple-choice UI prompts to the user, there are two remaining options for how the APT plugin can handle this situation: 1. Automatically proceed, assuming you're okay with whatever changes it needs to make 2. Automatically fail, showing you an ugly error message and leaving you to figure it out It chose #2. The only practical way for this to be improved is to stop using PackageKit, and to write a custom APT backend specially for Discover, which could then handle situations like this better. However that's something that would really need initiative from people in the APT packaging world. All the custom backends in Discover that do exist (e.g. for SteamOS, Kinoite, Alpine Linux, and KDE Linux) were contributed by the people working on those distros. It would have to be the same for any hypothetical custom APD backend in Discover. It's a sucky situation, but it is what it is. (In reply to Nate Graham from comment #1) > This is a limitation in the APT PackageKit plugin, which Discover uses for > this. Because the PackageKit library intentionally does not support showing > multiple-choice UI prompts to the user, there are two remaining options for > how the APT plugin can handle this situation: > 1. Automatically proceed, assuming you're okay with whatever changes it > needs to make > 2. Automatically fail, showing you an ugly error message and leaving you to > figure it out > [...snip...] > It's a sucky situation, but it is what it is. Thanks for the explanation, I appreciate you taking time to do that. What I forgot to post was my solution was simply running: `apt-get update --allow-releaseinfo-change` Once that was finished, Discover works OK again. I found some (old) kdialog use in PackageKit sources. Maybe this could work? ``` kdialog --title "Some repositories changed" --warningcontinuecancel "Some repos have changed their info. Fix the distro changes?" ``` That would be something to bring up with the PackageKit folks. But I doubt they would accept that solution for multiple reasons (objection to the concept of offering user interactivity; objection to the use of a CLI program rather than a proper API; objection to the use of a KDE-specific tool rather than something cross-platform). |