FS#45656 - [iptables] early start from systemd?
Attached to Project:
Arch Linux
Opened by James (thx1138) - Wednesday, 15 July 2015, 17:33 GMT
Last edited by Doug Newgard (Scimmia) - Thursday, 16 July 2015, 02:37 GMT
Opened by James (thx1138) - Wednesday, 15 July 2015, 17:33 GMT
Last edited by Doug Newgard (Scimmia) - Thursday, 16 July 2015, 02:37 GMT
|
Details
iptables 1.4.21-3
With respect to [Unit] ... Wants=network-pre.target Before=network-pre.target but there is still no such thing in the iptables.service or ip6tables.service files. What was the resolution here? |
This task depends upon
Closed by Doug Newgard (Scimmia)
Thursday, 16 July 2015, 02:37 GMT
Reason for closing: Duplicate
Additional comments about closing: FS#33478
Thursday, 16 July 2015, 02:37 GMT
Reason for closing: Duplicate
Additional comments about closing:
https://projects.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/iptables&id=2d3a57689b0a490f9d212349a4eac73d446e93ea
committer svntogit <svntogit@nymeria.archlinux.org> 2015-04-01 07:30:18 (GMT
Ok - did you look at the date? The current iptables package is
Version : 1.4.21-3
Build Date : Wed 25 Mar 2015 03:56:47 AM MDT
and today's Date is 2015 Jul 15.
It seems to me that, if the iptables package is never rebuilt from the updated source, then the source revisions are of no value. So now, the issue would be, how many months should elapse before the iptables package is rebuilt and distributed from the current source?
And incidentally, is it really appropriate that an Arch Linux bug be closed before a revision propagates to distribution?
> So now, the issue would be, how many months should elapse before the iptables package is rebuilt and distributed from the current source?
That's up to the package maintainer.
Ok - thanks - got it.
> That's up to the package maintainer.
Uhm - help me out, here. Is this not the correct place to "ping" the package maintainer? Or I should contacted the package maintainer directly, instead?