24.05.22 16:32 - Arjen de Korte:
Citeren Marcus Meissner
: Hi,
The main problem with this transition that I had was that "zypper dup" updated NetworkManager first which restarted itself immediately, which lost the wifi network.
NetworkManager-wifi would probably have been the next package to update, but my Laptop had lost the network already.
Happens if you do "download on demand" strategy, like everyone with small disks.
In my case, 'zypper dup' downloads all packages first, yet NetworkManager-wifi was not downloaded and connection was lost after all downloaded packages were installed. So somehow the mechanism to install the recommended package failed for me, despite the default '/etc/zypp/zypp.conf' file.
'zypper dup' will not download newly added recommends. Even if 'solver.onlyRequires = false" is set in '/etc/zypp/zypp.conf'. One would have to call 'zypper install-new-recommends' to get newly added recommends. 'man zypper' says: "install-new-recommends (inr) [options] Install newly added packages recommended by already installed ones. This command basically re-evaluates the recommendations of all installed packages and fills up the system accordingly. You don’t want to call this unconditionally on small or minimal systems, as it may easily add a large number of packages. Called as zypper inr --no-recommends, it restricts the command to just look for packages supporting available hardware, languages or filesystems. Usefull after having added e.g. new hardware or driver repos. This is also the default behavior if you have set [zypp.conf:solver.onlyRequires]." Regards Hagen