libiptc.pc non-functional

Bug #1861975 reported by Christian Ehrhardt 
6
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://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?

Related branches

Changed in iptables (Ubuntu):
importance: Undecided → High
Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

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 ...

Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

Actually the merge of 1.8.4 and the FTBFS are so different - closing the iptables tasks to live in a different place if needed.

no longer affects: iptables (Debian)
Changed in iptables (Ubuntu):
status: New → Invalid
Changed in strongswan (Ubuntu):
status: New → In Progress
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package strongswan - 5.8.2-1ubuntu1

---------------
strongswan (5.8.2-1ubuntu1) focal; urgency=medium

  * Merge with Debian unstable (LP: #1861971). Remaining changes:
    - d/control: Transition from strongswan-tnc-* being in extra packages
      to libcharon-extra-plugins (drop after 20.04)
    - d/control: Transition from former Ubuntu only libcharon-standard-plugins
      to common libcharon-extauth-plugins (drop after 20.04)
    - d/control: strongswan-starter hard-depends on strongswan-charon,
      therefore bump the dependency from Recommends to Depends. At the same
      time avoid a circular dependency by dropping
      strongswan-charon->strongswan-starter from Depends to Recommends as the
      binaries can work without the services but not vice versa.
  * Added Changes
    - d/control: build-depend on libiptc-dev to avoid FTBFS (LP: #1861975)
      This is needed due to changes in regard to Debian bug 947176 and 939243
      and can later be dropped again.

strongswan (5.8.2-1) unstable; urgency=medium

  [ Jean-Michel Vourgère ]
  * README.Debian: Fixed typo

  [ Yves-Alexis Perez ]
  * d/control: replace iptables-dev b-dep by libip{4,6}tc-dev (Closes: #946148)
  * d/watch: use uscan special strings
  * New upstream version 5.8.2
  * d/control: update dh compat level to 12
  * strongswan-nm: update path for dbus service file
  * install DRBG plugin to libstrongswan
  * d/control: add ${misc:Pre-Depends} to strongswan-starter

 -- Christian Ehrhardt <email address hidden> Wed, 05 Feb 2020 08:28:30 +0100

Changed in strongswan (Ubuntu):
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.