On Tue, 2017-11-07 at 13:29 +0100, Bjoern Voigt wrote:

When I run "zypper dup" with the implicit default "--no-allow-vendor-change" I often see messages like this today:

$ zypper dup [...] The following 10 NEW packages are going to be installed: accountsservice-lang gedit-lang gnome-keyring-lang grilo-lang ibus-lang kernel-default-4.13.10-1.4 libcmark0_28_3 libsecret-lang python2-xcb-proto-devel python3-xcb-proto-devel

The following 47 applications are going to be REMOVED: Activities "Activity Bar" "Analog Clock" "Application Launcher" "Application Menu" "Application Menu Bar" "Battery and Brightness" Breeze "CPU Load Monitor" Calendar Clipboard "Declarative Toolbox" "Default Panel" Desktop "Desktop Containment" "Device Notifier" "Digital Clock" "Empty Panel" "Folder View" "GStreamer Multimedia Codecs" "Global Menu" "Hard Disk I/O Monitor" "Hard Disk Space Usage" "Icons-only Task Manager" Image "Input Method Panel" "KDE Plasma Desktop" "Kate Sessions" Lock/Logout Marble "Media Player" "Memory Status" "Network Monitor" Notifications Pager "Panel Toolbox" "Plain Color" Skanlite Slideshow "Software Updates" "System Tray" "Task Manager" Trashcan Umbrello "Window list" "World Clock" "World Map"

The following 3 packages are going to be REMOVED: kernel-default-4.13.10-1.3 libcmark0_28_0 python-xcb-proto-devel [...]

The package actions are understandable. But what does "The following 47 applications are going to be REMOVED" mean? None of the displayed applications are really affected.

The repo which has the packages / applications does not have valid / complete AppStream metadata... as such, zypp has no information that the packages it has available there contain the 'applications' that are currently installed (even though they likely will remain installed) It's a long-standing issue that OBS repos don't publish AppStream metadata (or no valid metadata). If it's packages coming from openSUSE Tumbleweed directly, in most cases it's packaging bugs (one needs to check why a package would then not show up in the Appstream metadata, see http://dominique.leuenberger.net/blog/2016/07/how-to-fix-my-application -does-not-show-up-in-software-centers/ Cheers, Dominique

On Tue, 2017-11-07 at 13:29 +0100, Bjoern Voigt wrote:

When I run "zypper dup" with the implicit default "--no-allow-vendor-change" I often see messages like this today:

$ zypper dup [...] The following 10 NEW packages are going to be installed: accountsservice-lang gedit-lang gnome-keyring-lang grilo-lang ibus-lang kernel-default-4.13.10-1.4 libcmark0_28_3 libsecret-lang python2-xcb-proto-devel python3-xcb-proto-devel

The following 47 applications are going to be REMOVED: Activities "Activity Bar" "Analog Clock" "Application Launcher" "Application Menu" "Application Menu Bar" "Battery and Brightness" Breeze "CPU Load Monitor" Calendar Clipboard "Declarative Toolbox" "Default Panel" Desktop "Desktop Containment" "Device Notifier" "Digital Clock" "Empty Panel" "Folder View" "GStreamer Multimedia Codecs" "Global Menu" "Hard Disk I/O Monitor" "Hard Disk Space Usage" "Icons-only Task Manager" Image "Input Method Panel" "KDE Plasma Desktop" "Kate Sessions" Lock/Logout Marble "Media Player" "Memory Status" "Network Monitor" Notifications Pager "Panel Toolbox" "Plain Color" Skanlite Slideshow "Software Updates" "System Tray" "Task Manager" Trashcan Umbrello "Window list" "World Clock" "World Map"

The following 3 packages are going to be REMOVED: kernel-default-4.13.10-1.3 libcmark0_28_0 python-xcb-proto-devel [...]

The package actions are understandable. But what does "The following 47 applications are going to be REMOVED" mean? None of the displayed applications are really affected.

The repo which has the packages / applications does not have valid / complete AppStream metadata... as such, zypp has no information that the packages it has available there contain the 'applications' that are currently installed (even though they likely will remain installed) It's a long-standing issue that OBS repos don't publish AppStream metadata (or no valid metadata). If it's packages coming from openSUSE Tumbleweed directly, in most cases it's packaging bugs (one needs to check why a package would then not show up in the Appstream metadata, see http://dominique.leuenberger.net/blog/2016/07/how-to-fix-my-application -does-not-show-up-in-software-centers/ Cheers, Dominique