Backport xtables-addons 2.6-1 to trusty

[Patrick Domack]

Please sync xtables-addons 2.6-1 (universe) from Debian jessie (main)

Version 2.4 of xtables is required for kernel 3.13 support (current version
is 2.3)

I have had no problems compiling or running 2.6 on trusty, and have been
using 2.4 for a year now (including trusty alpha/beta versions).

I recommend going to 2.6 vs 2.4, for support of backported kernels

Changelog entries since current trusty version 2.3-1:

xtables-addons (2.6-1) unstable; urgency=medium

  * New upstream version [September 2014].
  * Standards-Version: 3.9.6.

 -- Dmitry Smirnov <email address hidden> Sat, 04 Oct 2014 00:07:46 +1000

xtables-addons (2.5-1) unstable; urgency=low

  * New upstream version [April 2014].
  * Install `iptaccount` to "/usr/sbin" instead of "/sbin".

 -- Dmitry Smirnov <email address hidden> Wed, 23 Apr 2014 16:47:32 +1000

xtables-addons (2.4-1) unstable; urgency=low

  * New upstream version [January 2014].
  * Dropped no longer needed "skip-depmod.patch".
  * Added "unzip, wget" to Recommends to satisfy `xt_geoip_dl`
    (Closes: #714654).
  * Fixed FTBFS in m-a/xtables-addons-source (Closes: #730074).
  * Standards to 3.9.5.

 -- Dmitry Smirnov <email address hidden> Mon, 10 Feb 2014 13:05:36 +1100

[Artur Rona (ari-tczew)]

xtables-addons (2.6-1) unstable; urgency=medium

  * New upstream version [September 2014].
  * Standards-Version: 3.9.6.

 -- Dmitry Smirnov <email address hidden> Sat, 04 Oct 2014 00:07:46 +1000

[Sebastien Bacher (seb128)]

Thanks, if you need a fix for the bug in previous versions of Ubuntu, please perform as much as possible of the SRU Procedure [1] to bring the need to a developer's attention.

[1]: https://wiki.ubuntu.com/StableReleaseUpdates#Procedure

[Sebastien Bacher (seb128)]

(the bug needs a description of the impact, a test case and the regression potential statement)

[Sebastien Bacher (seb128)]

unsubscribing sponsors, there is nothing to sponsor there at the moment, if you want a SRU you should follow the instructions of the previously pointed url and add a package update targetting trusty as well

[Robie Basak (racb)]

As discussed, this bug needs a justification against SRU policy to make any progress, so marking this as Incomplete for Trusty. Alternatively (sorry I failed to mention this on IRC) you can seek a backport via the backports pocket so users can opt in to using it. See https://wiki.ubuntu.com/UbuntuBackports for process details.

[Mattia Rizzolo (mapreri)]

trusty is now EOL, so I'm closing the bug.