Actually this isn't as bad as I first thought, but it can be. Let me illustrate how/why.
iptables changed its -dev packaging. Then strongswan adapted by changing iptables-dev to libip4tc-dev + libip6tc-dev. If strongswan would have stayed as-is it woul still work. But due to adapting to the former change in 1.8.4-1 for debian #939243 it now after 1.8.4-2 for #947176 is an FTBFS. While we could merge the newer iptables in general (therefore leaving this bug open, but change to 1.8.4 merge request) I think I can fix the current issue in strongswan by adding a build-dependency to get the old libiptc.pc installed. Yep gets me back to checking for libiptc... yes Adding a Strongswan task ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861975 Title: libiptc.pc non-functional To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1861975/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
