Iain and Adam confirmed on IRC that this is fine, and splitting out
shared libraries into separate binary packages is good packaging
practice either way.
** Changed in: iptables (Ubuntu)
Status: New => In Progress
** Changed in: iptables (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
--
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/1616437
Title:
FFE: split out libiptc library
Status in iptables package in Ubuntu:
In Progress
Bug description:
I would like to get iptables merged from sid. 1.6.0-3
(https://tracker.debian.org/news/788344) split out the libiptc library
so that it doesn't drag in the full 4 MB of "iptables". With this we
can finally enable libiptc support in systemd [1] so that nspawn
containers with a private network will finally have working network
(this needs to set up masquerading).
For iptables this is just a package split without actual new features.
For systemd this only affects nspawn (and there it is a bug fix as it
unbreaks the default machinectl configuration and nspawn with -n), not
LXC/LXD or other container solutions. So overall this is a low-risk
change. But without the package split we would enlarge the base system
by ~ 4 MB.
Note: My main concern is to keep the systemd package in sync with
Debian. Disabling iptc support in Ubuntu would be the only (and
annoying) packaging delta.
[1] https://anonscm.debian.org/cgit/pkg-
systemd/systemd.git/commit/?id=26187cfaa
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1616437/+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
