https://bugs.kde.org/show_bug.cgi?id=448745
Bug ID: 448745
Summary: Wish: Update subset of packages when complete update
is not possible
Product: Discover
Version: 5.23.4
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
Severity: wishlist
Priority: NOR
Component: Updates (interactive)
Assignee: lei...@leinir.dk
Reporter: bu...@mightytikigod.com
CC: aleix...@kde.org
Target Milestone: ---
Whenever you have a list of packages to update -- but one of them has some kind
of problem -- you will see the toast message: "Please make sure that appstream
is properly setup."
You can't move beyond that within Discover itself.
You need to drop back to some other tool -- perhaps dnf -- find out what
package is having the problem, and then decide what you're going to do about
it.
My wish is that Discover might offer to update the packages that /can/ be
updated, and indicate the packages that cannot.
For example, if I use the command-line "dnf" tool, I might fail with an error
like this:
"GPG key at file:///etc/pki/rpm-gpg/RPM-GPG-KEY-mysql (0x5072E1F5) is already
installed
The GPG keys listed for the "MySQL Tools Community" repository are already
installed but they are not correct for this package.
Check that the correct key URLs are configured for this repository.. Failing
package is: mysql-workbench-community-8.0.28-1.fc35.x86_64"
At that point, I can grumble, "typical," about this particular vendor's
commitment to security (this is not the first time they've done this), and then
do "dnf upgrade --exclude=mysql-workbench-community" and do a partial update.
Ideally, this sort of feature would never be necessary.
Alas, I feel like it might be practical anyway.
--
You are receiving this mail because:
You are watching all bug changes.
