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
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
