I just did an install in vmware, x86_64 non-free netinstall and after I ran "urpmi --auto-select --auto-update", which gave me no new packages, I was presented with this list. The following packages: exo-0.12.3-1.mga7.x86_64 icewm-i18n-1.4.2-2.mga7.noarch icewm-theme-oxygen-aya-0.1-12.mga7.noarch lib64burn4-1.5.0-1.mga7.x86_64 lib64exo1_0-0.12.3-1.mga7.x86_64 lib64exo2_0-0.12.3-1.mga7.x86_64 lib64isofs6-1.5.0-1.mga7.x86_64 lib64rsvg-gir2.0-2.44.10-1.mga7.x86_64 lib64xaw7-1.0.13-2.mga7.x86_64 lib64xfce4ui1_0-4.13.4-3.mga7.x86_64 lib64xfce4ui2_0-4.13.4-3.mga7.x86_64 lib64xfce4util7-4.13.2-2.mga7.x86_64 libxfce4ui-4.13.4-3.mga7.x86_64 libxfce4util-i18n-4.13.2-2.mga7.x86_64 mageia-theme-6.5-1.mga7.noarch perl-Crypt-SSLeay-0.720.0-15.mga7.x86_64 perl-LWP-Protocol-https-6.70.0-2.mga7.noarch perl-XML-SAX-Expat-0.510.0-7.mga7.noarch perl-XML-Simple-2.250.0-2.mga7.noarch plymouth-plugin-label-0.9.4-1.mga7.x86_64 plymouth-plugin-script-0.9.4-1.mga7.x86_64 plymouth-system-theme-0.9.4-1.mga7.x86_64 x11-data-bitmaps-1.1.1-11.mga7.noarch xdg-compliance-0.1-22.mga7.x86_64 xdg-compliance-autostart-0.1-22.mga7.x86_64 xdg-compliance-menu-0.1-22.mga7.x86_64 are now orphaned, if you wish to remove them, you can use "urpme --auto-orphans" I did "Unselect Everything" during installation, chose the Mate Desktop, unselected a few tidbits here and there and added a few things. To me, this is not supposed to happen on a fresh system.
Created attachment 10622 [details] report.bug.xz
Created attachment 10623 [details] ddebug.log.xz
This isn't new or unusual for Mageia. It's a product of how it maintains the list of packages to install in the backend as you select/deselect things. Ideally it shouldn't create the list until you've made your final selections, but instead it makes a list based on the initial selections, then removes things you uncheck, resulting in orphans.
CC: (none) => marja11Assignee: bugsquad => mageiatools
So this is simply something to document in or manuals then?
CC: (none) => doc-bugs, fri