However the networkmanager-l2tp packager decided to send --without-gtk3 which looks like it would not work for gtk3. But looking at the source I don't see anything for disabling gtk3, so I'm a bit at a loss.
Unfortunately he didn't make a replaces for networkmanager-l2tp-gtk3, networkmanager-l2tp-gtk4 so there will be another conflict if you ended up installing gtk3/4 versions, but at least upgrading from original version is now fixed (just have this short window/little blip of an issue)
@TNE Not sure what you changed, but you may consider undoing it now that the package won't conflict anymore. Also not sure how the unsplit conflict will be handled, but if there is a conflict maybe we add support for the unsplitting of the package?
I've asked. Not sure it will be possible to remove those old packages, but hopefully a valid replaces/conflicts will make the garuda updates work okay. I tried doing system update from fresh garuda install and get the following error
Failed to prepare transaction
- networkmanager-l2tp-gtk3 and networkmanager-l2tp-gtk4 are in conflict
Using garuda-update command does seem to work (after a few tries), but I do get an interesting warning (and refreshing mirrors takes forever)
:: Replace networkmanager-l2tp with community/networkmanager-l2tp-gtk3? [Y/n] y
warning: ignoring package replacement (networkmanager-l2tp-1.20.0-3 => networkmanager-l2tp-gtk4-1.20.4-3)
It does end up installing networkmanager-l2tp-gtk3 anyway.
Then running sudo pacman -Sy networkmanager-l2tp gives
looking for conflicting packages...
:: networkmanager-l2tp and networkmanager-l2tp-gtk3 are in conflict. Remove networkmanager-l2tp-gtk3? [y/N] y
Packages (2) networkmanager-l2tp-gtk3-1.20.4-3 [removal] networkmanager-l2tp-1.20.4-4