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 Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/1861975 Title: libiptc.pc non-functional Status in iptables package in Ubuntu: Invalid Status in strongswan package in Ubuntu: New Bug description: Hi, I found this by trying to merge a newer strongswan which was an FTFBS. I wondered what happened and found: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947176 This is exactly my issue and we might face FTBFS in strongswan, systemd and probably others as well. The fix seems to be to merge iptables 1.8.4-2 from Debian. Could someone usually looking after iptables do that please? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1861975/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
