The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release
** Changed in: iptables (Ubuntu Precise)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
lucid has seen the end of its life and is no longer receiving any
updates. Marking the lucid task for this ticket as Won't Fix.
** Changed in: iptables (Ubuntu Lucid)
Status: Triaged = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
quantal has seen the end of its life and is no longer receiving any
updates. Marking the quantal task for this ticket as Won't Fix.
** Changed in: iptables (Ubuntu Quantal)
Status: Triaged = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
raring has seen the end of its life and is no longer receiving any
updates. Marking the raring task for this ticket as Won't Fix.
** Changed in: iptables (Ubuntu Raring)
Status: Triaged = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Branch linked: lp:ubuntu/saucy-proposed/iptables
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1187177
Title:
iptables calls setsockopt(2) incorrectly, fails when it should not
To manage
This bug was fixed in the package iptables - 1.4.18-1.1ubuntu1
---
iptables (1.4.18-1.1ubuntu1) saucy; urgency=low
* Merge changes from Debian, version 1.4.18-1.1 to fix FTBFS
in package perlipq due to missing dependecy: (LP: #1228525)
- debian/control
-
** Branch linked: lp:ubuntu/iptables
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1187177
Title:
iptables calls setsockopt(2) incorrectly, fails when it should not
To manage notifications about
** Branch linked: lp:~ari-
tczew/ubuntu/saucy/iptables/lp-1228525-1134554-1187177
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1187177
Title:
iptables calls setsockopt(2) incorrectly, fails when
** Changed in: iptables (Debian)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1187177
Title:
iptables calls setsockopt(2) incorrectly, fails when it should not
** Changed in: iptables (Ubuntu Lucid)
Status: New = Triaged
** Changed in: iptables (Ubuntu Precise)
Status: New = Triaged
** Changed in: iptables (Ubuntu Quantal)
Status: New = Triaged
** Changed in: iptables (Ubuntu Raring)
Status: New = Triaged
** Changed in:
@lamont
I would consider posting this patch to the upstream iptables project so they
can review this patch. If it get accepted into upstream, it would be useful to
then backport to affected series.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Bug watch added: Debian Bug tracker #710997
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710997
** Also affects: iptables (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710997
Importance: Unknown
Status: Unknown
--
You received this bug notification because
** Also affects: iptables (Ubuntu Lucid)
Importance: Undecided
Status: New
** Also affects: iptables (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: iptables (Ubuntu Quantal)
Importance: Undecided
Status: New
** Also affects: iptables (Ubuntu
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1187177
Title:
iptables calls setsockopt(2) incorrectly, fails when it should not
To manage notifications about this bug go to:
** Changed in: iptables (Debian)
Status: Unknown = New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1187177
Title:
iptables calls setsockopt(2) incorrectly, fails when it should not
To
15 matches
Mail list logo
