http://bugzilla.suse.com/show_bug.cgi?id=954117
http://bugzilla.suse.com/show_bug.cgi?id=954117#c11
--- Comment #11 from Gabriele Mohr
More details about behavior on openSUSE 13.2: - I did not tested if setting solver.allowVendorChange = true in /etc/zypp/zypp.conf is reflected in yast UI (and I do not have openSUSE 13.2 now to test). - "Allow Vendor Change" in both "Online Update" and "Software Management" modules, is persistent but independent (each module has its own setting)
My opinion/suggestion from user/usability point of view: regardless of UI (ncurses, gtk, qt) and module ("Online Update" or "Software Management") there should be only one setting (solver.allowVendorChange = true/false in /etc/zypp/zypp.conf). This setting should be read/write (persistent) from all above components.
The current (Leap42.1/Tumbleweed/SLES12 SP1) behaviour is like this: - "Online Update" and "Software Management" have/read/write same settings (should be like this also on 13.2) - The Qt and ncurses (text mode) UI respect same config files: * /etc/sysconfig/yast2 contains options which can be (persistently) set in UIs (PKGMGR_AUTO_CHECK, PKGMGR_VERIFY_SYSTEM, PKGMGR_RECOMMENDED) * /etc/zypp/zypp.conf is read (in textmode UI) to have initial value for options "Allow vendor change" and "Cleanup when deleting packages" (Qt UI is fixed now, see below). These options can be changed in UIs only for one run. This is intended because setting true for vendor change persistently (and possible forget about it) might lead to unwanted behaviour that packages from an external repo are overwritten by update packages. Also it's risky to delete all depending packages unless explicitly wanted. The bug-fix for Qt UI to respect the settings 'allowVendorChange' and 'cleandepsOnRemove' from /etc/zypp/zypp.conf will be available with libyui-qt-pkg-2.45.6.
Making the setting not persistent will force users to edit zypp.conf in terminal (and if we want to "convert" Windows users we should be able to do more things that can be done in terminal also from GUI).
As mentioned before: for an update it's not necessary to allow a vendor change, for the upgrade case it's allowed by default. -- You are receiving this mail because: You are on the CC list for the bug.