Your message dated Fri, 8 May 2015 14:11:51 +0200 with message-id <CAK0OdpxWp2mX45FL=f5k2Ejhq8T6zuQsPCCQ4nwx=dz170v...@mail.gmail.com> and subject line Re: Bug#784727: tshark doesn't recognise BPF filter at the end of the line has caused the Debian Bug report #784727, regarding tshark doesn't recognise BPF filter at the end of the line to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 784727: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784727 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: tshark Version: 1.12.1+g01b65bf-4 Severity: important Tags: upstream Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Install latest tshark * What exactly did you do (or not do) that was effective (or ineffective)? Run tshark tcp where 'tcp' is a BPF, as per tshark(1) * What was the outcome of this action? tshark dumped the usage message and terminateb * What outcome did you expect instead? The same as when running tshark -f tcp Note: this bugs seems to be a superset of #782245. *** End of the template - remove these template lines *** -- System Information: Debian Release: 8.0 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.14.33.jessiemptcp (SMP w/1 CPU core) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages tshark depends on: ii libc6 2.19-18 ii libglib2.0-0 2.42.1-1 ii libpcap0.8 1.6.2-2 ii libwireshark5 1.12.1+g01b65bf-4 ii libwiretap4 1.12.1+g01b65bf-4 ii libwsutil4 1.12.1+g01b65bf-4 ii wireshark-common 1.12.1+g01b65bf-4 ii zlib1g 1:1.2.8.dfsg-2+b1 tshark recommends no packages. tshark suggests no packages. -- no debconf information
--- End Message ---
--- Begin Message ---Control: fixed -1 1.12.4+gb4861da-1 thanks 2015-05-08 10:39 GMT+02:00 Bálint Réczey <[email protected]>: > Control: severity -1 minor > Control: tags -1 upstream confirmed > Control: forwarded -1 https://code.wireshark.org/review/#/c/8350/ > > 2015-05-08 8:20 GMT+02:00 Olivier Mehani <[email protected]>: >> Package: tshark >> Version: 1.12.1+g01b65bf-4 >> Severity: important >> Tags: upstream >> >> Dear Maintainer, >> >> *** Reporter, please consider answering these questions, where appropriate >> *** >> >> * What led up to the situation? >> Install latest tshark >> * What exactly did you do (or not do) that was effective (or >> ineffective)? >> Run >> tshark tcp >> where 'tcp' is a BPF, as per tshark(1) >> * What was the outcome of this action? >> tshark dumped the usage message and terminateb >> * What outcome did you expect instead? >> The same as when running >> tshark -f tcp >> >> Note: this bugs seems to be a superset of #782245. > Please use the new syntax. I'm fixing the man page upstream. It has already been fixed in wireshark in unstable/testing. Cheers, Balint
--- End Message ---
