[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Accepted wireshark 1.2.10-2+squeeze1 (source i386)

2010/9/30 Adam D. Barratt <adam@adam-barratt.org.uk>:
> On Wed, 2010-09-29 at 23:28 +0200, Bálint Réczey wrote:
>> There would be another path to go with wireshark.
>> Would you like the idea of allowing 1.2.11-2 to go to testing if I fix
>> the regression introduced by 1.2.11?
> Which of the fixes in 1.2.11 aren't (or are, if that's easier) including
> in the t-p-u package?
I referenced the source patch for the changes in 1.2.10-2+squeeze1's changelog:

* Backport changes from 1.2.11
  - Fix segmentation fault (Closes: #597703)
    -> 0004-Revert-rev-33697-it-s-not-necessary-check_col-is-NOT.patch

  - Fix inifinite loop in Bootstrap Protocol dissector
    -> 0015-Pick-up-change-from-trunk.patch -
  - Fix crash in RTSP dissector
    -> 0020-Copy-over-revisions-from-the-trunk.patch,
      (fix crash in RTSP dissector)
  - Fix crash when filtering packets based on expert info
    -> 0020-Copy-over-revisions-from-the-trunk.patch,
      (fix crash in ftype-tvbuff.c)
  - Fix crash when generating PostScript output\
    -> 0022-Copy-over-revisions-from-the-trunk.patch

The difference between 1.2.10-2+squeeze1 and 1.2.11-1 is still
significant, but I think those are low-risk changes.

I have uploaded  1.2.11-2 in the meantime:


wireshark (1.2.11-2) unstable; urgency=low
 * 25_fix-libsmi-workaround.patch:
   Fix the libsmi workaround by adding missing brackets.
 * backport fix for IP header checksum calculation regression introduced
   in 1.2.10
 * [Debconf translation updates]
   - Vietnamese (Clytie Siddall). (Closes: #598498).
 [ Daniel T Chen ]

 * 22_lp606063-fix-assertion-capture_start.patch:
   Handle event handler being invoked recursively.  Fix backported from
   upstream SVN r33906.  Thanks, Gregor Beck!
   (LP: #606063)

I reverted the regression and added important fixes.
(22_lp606063-fix-assertion-capture_start.patch is in squeeze already).
I think 1.2.11-2 is a good candidate for being included in Squeeze and
we could return to the unstable -> testing migration path.


Reply to: