iptables no longer has --reap option

Bug #887332 reported by Jamie Strandboge on 2011-11-07
This bug affects 1 person
Affects Status Importance Assigned to Milestone
iptables (Ubuntu)
Tim Gardner
Tim Gardner

Bug Description

As of iptables 1.4.12-1ubuntu1, iptables no longer supports the --reap option. From the debian/changelog:

    - No longer apply the following:
      + 9002-xt_recent-reap.patch: this requires a rewrite of the patch. For
        now adjust series to not apply, file a bug, assigning to the kernel
        team. Once they have resubmitted upstream, we can take the new patch.

The aforementioned upload was coordinated with tgardner on the kernel team (the author of the original patch), and this is the corresponding bug.

Related branches

Changed in iptables (Ubuntu Precise):
status: New → Triaged
milestone: none → ubuntu-12.04-beta-1
importance: Undecided → Medium
assignee: nobody → Canonical Kernel Team (canonical-kernel-team)
description: updated
tags: added: regression-release rls-p-tracking
description: updated
Tim Gardner (timg-tpi) on 2011-11-08
Changed in iptables (Ubuntu Precise):
assignee: Canonical Kernel Team (canonical-kernel-team) → Tim Gardner (timg-tpi)
status: Triaged → In Progress
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package iptables - 1.4.12-1ubuntu3

iptables (1.4.12-1ubuntu3) precise; urgency=low

  * Restore support for --reap, patch submitted to upstream.
    -LP: #887332

  * Fix FTBS against linux 3.2 headers by copying linux/types.h to
    local include directory. This package unfortunately has a
    number of local kernel headers that are getting out of date.
 -- Tim Gardner <email address hidden> Wed, 30 Nov 2011 09:03:14 -0700

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

Other bug subscribers