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.
When using offline updates, this is not possible, and it's a limitation/design choice of the PackageKit library that provides offline updates. The whole update is an atomic unit and you can't cherry-pick bits and bobs from it. However when using interactive updates, you can already skip packages (though it's not really recommended); each package has a checkbox by it and you can uncheck it. Are you asking for this to be automatic or for the UI for it to be improved or something?
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!