Bug 438129 - Arch: Discover fails to update package moved to another repository
Summary: Arch: Discover fails to update package moved to another repository
Status: RESOLVED UPSTREAM
Alias: None
Product: Discover
Classification: Applications
Component: Updates (other bugs)
Version First Reported In: 5.21.90
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Dan Leinir Turthra Jensen
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-06-05 18:26 UTC by Patrick Silva
Modified: 2021-06-09 17:09 UTC (History)
2 users (show)

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


Attachments
screenshot (63.16 KB, image/png)
2021-06-05 18:26 UTC, Patrick Silva
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Patrick Silva 2021-06-05 18:26:52 UTC
Created attachment 139025 [details]
screenshot

SUMMARY
Discover said "Dependency resolution failed..." (see the attached screenshot) when I tried to update my Arch Linux. pacman -Syu gave me this output in Konsole:

:: Synchronizing package databases...
 core is up to date
 kde-unstable is up to date
 extra is up to date
 community is up to date
 multilib is up to date

:: Starting full system upgrade...
:: Replace libcanberra-pulse with extra/libcanberra? [Y/n] 

I just pressed Enter and my system was successfully updated.

EXPECTED RESULT
Discover should be able to update Arch even if I a package was moved to another repo.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux
KDE Plasma Version: 5.21.90
KDE Frameworks Version: 5.82.0
Qt Version: 5.15.2
Graphics Platform: X11
Comment 1 Nate Graham 2021-06-09 17:09:17 UTC
That question that it's asking you is the problem, because PackageKit doesn't have a generic method to bubble up questions that the user needs to respond to so that they can be presented in the UI.

There are three ways this could be fixed:
1. the alpm PacMan PackageKit plugin selects a default choice of "Yes" for this action when tihs situation is encountered.
2. PackageKit adds an API to expose these sorts of questions to client apps, and then those client apps display a UI to the user. This is more technically correct, but would require changes to PackageKit, packaging plugins, and client apps.

Either way there is sadly nothing we can do about this in Discover.

See https://bugzilla.opensuse.org/show_bug.cgi?id=1163737 for the same issue in openSUSE Tumbleweed.