sFlow PDU data not correctly displayed

We shouldn't pull a prerelease version of tcpdump from experimental into precise.

The upstream patch in question also does not apply cleanly to tcpdump 4.1.1 which we currently have, so more investigation is needed to see whether this can be backported.

4.2.1 was uploaded to Debian yesterday: http://packages.qa.debian.org/t/tcpdump/news/20120102T195759Z.html

I'm testing a merge now, if it looks good I'd probably recommend going with 4.2.1 in Precise

This bug was fixed in the package tcpdump - 4.2.1-1ubuntu1

---------------
tcpdump (4.2.1-1ubuntu1) precise; urgency=low

  * Resynchronise with Debian. Remaining changes (LP: #892285):
    - Add enforcing AppArmor profile.
  * Refreshed manpage patch to apply to new upstream.

tcpdump (4.2.1-1) unstable; urgency=low

  * New upstream release.
  * Upload to unstable.

tcpdump (4.2.0~rc1-2) experimental; urgency=low

  * Make sure OpenSSL support gets enabled: since it moved to multiarch
    paths, the configure script doesn't find libcrypto.so and disables
    crypto support. To fix this, simplify detection logic in configure.in
    and run autoconf before configuring.
  * Redo build flags handling:
    + Enable hardening flags via dpkg-buildflags, not hardening-includes.
    + Switch to debhelper compat level 9 to have build flags exported
      automatically.
    + Adjust build-depends accordingly.
  * Enable parallel build in debhelper.

tcpdump (4.2.0~rc1-1) experimental; urgency=low

  * New upstream beta release (closes: #636806); now switches to the -Z
    user before opening the first output file (closes: #434603).
  * debian/control: Set Standards-Version to 3.9.2.
 -- Stephane Graber <email address hidden> Wed, 04 Jan 2012 10:33:48 +0100