On Mon, May 30, 2022 at 1:59 PM Martin Wilck <martin.wilck@suse.com> wrote:
This update turns out to have more fallout. I'm running an openvswitch setup here, which ended up with no network connectivitiy after this update. Note that installing with --recommends wouldn't have prevented this:
It would.
apollon:~ # zypper se --requires NetworkManager-ovs
You should always use --pkg-requires, --pkg-recommends etc. The above looks only for literal strings in Requires, it will not catch packages that Require something that is Provided by NetworkManager-ovs (not this case, but still ...)
Loading repository data... Reading installed packages... No matching items found. apollon:~ # zypper se --recommends NetworkManager-ovs Loading repository data... Reading installed packages... No matching items found. apollon:~ # zypper se --suggests NetworkManager-ovs Loading repository data... Reading installed packages... No matching items found.
%package ovs Summary: Open vSwitch device plugin for NetworkManager Group: System Environment/Base Requires: %{name} = %{version} Requires: openvswitch Supplements: (NetworkManager and openvswitch)
Apparently OVS users are expected to figure this out by themselves, and install NetworkManager-ovs manually. Perhaps the changelog could have at least mentioned openvswitch, or in general listed _which_ subpackages had been split out?
Anyway, something like
Requires: (NetworkManager-ovs if openvswitch)
Where? In NetworkManager? Why should NetworkManager Require NetworkManager-ovs? Maybe the user is not going to control ovs with NetworkManager at all ...
in the split NetworkManager package would have saved me trouble. IMO conditional requirements like this are the solution to issues like this.
Martin