libiptc.pc non-functional
Bug #1861975 reported by
Christian Ehrhardt
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
iptables (Ubuntu) |
Invalid
|
High
|
Unassigned | ||
strongswan (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Hi,
I found this by trying to merge a newer strongswan which was an FTFBS.
I wondered what happened and found:
https:/
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?
Related branches
~lucaskanashiro/ubuntu/+source/strongswan:groovy-merge
Merged
into
ubuntu/+source/strongswan:debian/sid
at
revision 9a36f8ee2983a7d33bc5f0bded47bccd7b80ae6e
- Christian Ehrhardt (community): Approve
- Canonical Server: Pending requested
-
Diff: 1745 lines (+1571/-3)4 files modifieddebian/changelog (+1562/-0)
debian/control (+5/-3)
debian/libstrongswan-extra-plugins.install (+3/-0)
debian/rules (+1/-0)
~paelzer/ubuntu/+source/strongswan:merge-5.8.2-focal
Merged
into
ubuntu/+source/strongswan:debian/sid
at
revision 0191ec297c354a9d4a04ae0e1b8b4d5c71a4ec44
- Bryce Harrington (community): Approve
- git-ubuntu developers: Pending requested
- Canonical Server packageset reviewers: Pending requested
-
Diff: 1733 lines (+1581/-5)2 files modifieddebian/changelog (+1520/-0)
debian/control (+61/-5)
Changed in iptables (Ubuntu): | |
importance: | Undecided → High |
Changed in strongswan (Ubuntu): | |
status: | New → In Progress |
To post a comment you must log in.
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 ...