Bugzilla – Bug 471340
change of bootloader causes change in software selection
Last modified: 2021-02-18 14:50:33 UTC
Created attachment 269099 [details] screenshot of "Installation settings" before change of bootloader User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-GB; rv:1.8.1.6) Gecko/20070730 SUSE/2.0.0.6-25 Firefox/2.0.0.6 I had prepared an installation, de/selecting packages, banning others etc. Then I changed the boot loader, and for some reason my software selection also changed. See screenshots. This appears to be KDE3.5 related, and I understand that is being deprecated - this just seemed really weird, so maybe it goes further than just the KDE packages. Reproducible: Didn't try
Created attachment 269100 [details] screenshot of "Installation settings" after change of bootloader When compared to the "before" screenshot, extra items on the list are "KDE3 desktop environment" "Graphics" "Games" "Misc. packages" The total installation size also went up from 1.3G to 1.6G.
Created attachment 269102 [details] y2logs tarred and gzipped
I guess this is already known bug - going to any proposal simply resets changes made to package selection by the user. Rather cumbersome workaround is to go to bootloader (partitioning,..) proposal first and leave software proposal (making custom changes to package selection) as the very last step before clicking on "Install". Lado, please mark as duplicate.
yast2-bootloader module should use PackagesProposal.ycp module in the first stage for selecting the needed packages. This module collects all package requests from all proposal modules.
yast2-bootloader uses PackagesProposal.ycp during installation like yast2-kdump. There is only called Pkg::IsSelected () and it is not cause of changing software proposal. Maybe I only didn't find some other function from packager which can modify software proposal and which is called in yast2-bootloader. Please return me bug back if the problem is really in yast2-bootloader.
The problem was that the desktop patterns were reselected again regardless the user decision. Fixed in factory (openSUSE-11.3) in yast2-pkg-bindings-2.19.0 and yast2-packager-2.19.2.
This is an autogenerated message for OBS integration: This bug (471340) was mentioned in https://build.opensuse.org/request/show/28175 Factory / yast2-packager https://build.opensuse.org/request/show/28176 Factory / yast2-pkg-bindings