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 <christian.ehrha...@canonical.com> Wed, 05 Feb
2020 08:28:30 +0100
** Changed in: strongswan (Ubuntu)
Status: In Progress => Fix Released
--
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:
Fix Released
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 : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
