Page MenuHomeSolus

NetworkManager libreswan/strongswan plugins should conflict
Open, Needs TriagePublicBUG

Description

Summary

The strongswan and libreswan packages are currently set to conflict with each other because both provide a same file. The network manager plugins for them, however, do not. This can lead to the case of having both plugins installed, but only one library installed, with the user only noticing something is wrong when they go to update and the backend they're using gets removed, as was recently discovered in our Matrix support channel. Or, because only one library is installed, it might be the wrong one, so someone trying to user it is left with a vague error message and no idea what's happening.

It might be a good idea for networkmanager-libreswan and networkmanager-strongswan to be marked as conflicts with each other as well, to prevent this from happening in the future.

Steps to reproduce:

  1. Install networkmanager-strongswan
  2. Install networkmanager-libreswan

Expected

networkmanager-strongwan should be uninstalled.

Actual

Both network plugins are installed, even though strongswan is removed.

Event Timeline

I suppose we would expect both libreswan and networkmanager-libreswan as conflicts for networkmanager-strongswan? Also, should we add the conflict for libreswan and networkmanager-libreswan in the other direction as well?