On 07/05/2013 03:14 PM, Adam Conrad wrote:
Package: netexpect Version: 0.20-3 Followup-For: Bug #714535 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu saucy ubuntu-patchIn Ubuntu, I've applied the following naive patch to port to the wireshark 1.10 API. It looks like the _set_unset calls can probably just go away, as they're setting members that no longer exist. As for the frame_data_{reset,destroy} mangling, I made a best-effort guess as to which to use in which situation, but input from someone more familiar with the source would probably not be a bad plan. * fix-libwireshark110-build.patch: Track wireshark 1.10 API (closes: #714535) Thanks for considering the patch.
Thanks for the effort, Adam; it's really appreciated. And thanks Scott for filing the FTBS bug.
Network Expect is tightly coupled with libwireshark, so any changes to libwireshark internals will create problems for Network Expect. That's what happened here during the Wireshark 1.8 to 1.10 transition. Unfortunately, libwireshark is tightly integrated into Wireshark and Tshark, and the API is not documented so each major Wireshark release I struggle a bit with the changes to Network Expect that are needed to be able to use the updated libwireshark API in the new Wireshark release.
I'm looking closely at the problem and should be able to upload new, fixed packages soon (hopefully by the end of this week). I was able to build after making a few minor changes but I need to test that things work as they should before uploading. I am also not positive about the frame_data_cleanup() to frame_data_reset()/frame_data_destroy() changes so I need to look into that as well.
Cheers, Eloy Paris.- netexpect.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
