I'm not sure if this is really the best place to bring this up, but it might get the eyes of a few openSUSE developers. I've noticed a problem with Leap upgrades, certainly for 15.5 and 15.4 but I'm not sure how far back it goes. I know it was never an issue I had in the past and I've been upgrading oS installs for nearly twenty years. When using the Leap 'Upgrade' option via a USB stick or DVD, if I go into the Package Selection category of the installation overview (I've been obliged to do so with the last release because of one or two conflicts that needed resolving), I've discovered that there are a large number of packages that remain in the 'Keep' state with a black tick on an empty background. Hundreds or more. They are not marked for upgrade even though a version from the latest Leap release exists on either the upgrade media or the online repos. In some or maybe all cases the version number can be precisely the same, which may be the source of the problem. I've observed this on three separate machines in three different locations with different owners, although I'm the administrator in each case and have chosen a roughly similar configuration and package selection, so that could still mean it's a rare situation that I unfortunately trigger with my choices. One thing I tend to do prior to the upgrade is go into my software repositories and make sure they're all updated to the next release, or use $releasever in the path. During the upgrade process I flip the state of the few non-official repos I want to preserve to prevent them being deleted. In case it's relevant, all my repos have a priority of 99 except Packman which is 98. I find it hard to believe that it could either be a bug not already acted upon or that it potentially affects large swathes of Leap users and nobody has raised it, but I've not found a bug report about it from my albeit non-extensive searches. It could potentially cause a lot of incompatibility or dependency problems from Leap users who accept the defaults and are unaware they're still running packages from an older oS version. However, if the package versions are the same, I suspect in most cases nobody will notice any major problems. I first noticed this had happened on a system I'd already upgraded, and it was only afterwards I had to find a way to filter all packages that came from the previous release and forcibly upgrade them. When you want to do it during the install/upgrade with the YaST-based interface, it's not obvious how. The only way I know is to deselect all the package categories from the boxes in the left column, and leave selected only 'Keep'. Then right-click one of the packages, go to 'All in this list...' and then 'Upgrade unconditionally'. I can't pinpoint the exact release where this began to occur.. gumb