Re: [Wireshark-dev] [Wireshark-announce] Wireshark 1.12.0rc3 is now available
The x86 CMake build now completes :-) The x64 build is failing due to the lack of an acceptable Python and some dumpcap link errors. On 1 August 2014 00:28, Gerald Combs ger...@wireshark.org wrote: On 7/31/14 2:19 PM, Graham Bloice wrote: On 31 July 2014 22:14, Graham Bloice graham.blo...@trihedral.com mailto:graham.blo...@trihedral.com wrote: On 31 July 2014 17:34, Gerald Combs ger...@wireshark.org mailto:ger...@wireshark.org wrote: On 7/31/14 6:08 AM, Graham Bloice wrote: On 31 July 2014 11:42, Bálint Réczey bal...@balintreczey.hu mailto:bal...@balintreczey.hu mailto:bal...@balintreczey.hu mailto:bal...@balintreczey.hu wrote: +1 for dropping autotools in favor of CMake. CMake already covers all my use cases. Same here except for Windows. I've been doing most of my Qt development using Qt Creator + CMake. It doesn't have all the conveniences of Qt Creator + QMake but it works well enough. I also support dropping nmake, but since I'm not building on Windows I can't tell if CMake is complete enough. Not yet. Working on it though. I added msbuild steps to the Windows buildslaves after the cmake steps. The 32-bit build succeeds although I haven't tried running it. The 64-bit build passes /MACHINE:X86 to the linker which then fails. The buildslaves are failing to build the solution. I think the arguments to the msbuild step should be modified to be msbuild /m /p:Configuration=RelWithDebInfo Wireshark.sln. Done. And the x86 buildslave CMake still isn't locating a viable Python Interpreter. The machine has the official Python 2.6 installed in c:\Python26 and Cygwin's Python 2.7 installed in c:\cygwin\usr\bin. According to http://www.cmake.org/pipermail/cmake/2010-February/035404.html CMake looks for numbered Pythons executables (python2.7, python2.6, ...) before looking for the plain executable. In our case this means it's finding Cygwin's Python before the official version. The version detection then fails for some reason. I'm going to try installing the official Python 2.7. Hopefully it will be found before Cygwin's. ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org ?subject=unsubscribe -- Graham Bloice Software Developer Trihedral UK Limited ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] [Wireshark-announce] Wireshark 1.12.0rc3 is now available
On Jul 31, 2014, at 1:18 AM, Bálint Réczey bal...@balintreczey.hu wrote: Since the files stored in git are enough for building Wireshark on every platform we support, ...as long as the user has Flex and Perl and Python and automake and autoconf and libtool (and possibly other tools) installed. Do we want to require that? ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] [Wireshark-announce] Wireshark 1.12.0rc3 is now available
On Jul 31, 2014, at 1:18 AM, Bálint Réczey bal...@balintreczey.hu wrote: Since the files stored in git are enough for building Wireshark on every platform we support So we shouldn't bother generating or shipping tarballs at all, just say check out this from git if you want the 1.X.Y source? ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] [Wireshark-announce] Wireshark 1.12.0rc3 is now available
2014-07-31 10:32 GMT+02:00 Guy Harris g...@alum.mit.edu: On Jul 31, 2014, at 1:18 AM, Bálint Réczey bal...@balintreczey.hu wrote: Since the files stored in git are enough for building Wireshark on every platform we support So we shouldn't bother generating or shipping tarballs at all, just say check out this from git if you want the 1.X.Y source? Functionally a signed git tag is as good as a signed tarball, but serving .xz compressed relesea tarballs are cheaper in terms of CPU and bandwidth consumption, so I would go with that. Cheers, Balint ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] [Wireshark-announce] Wireshark 1.12.0rc3 is now available
On Wednesday 30 July 2014 14:35:06 Gerald Combs wrote: After comparing the tarballs generated by make dist and git-export-release.sh I have to agree. Both have issues but the dist tarball will build according to our documentation on Linux, Windows, and OS X. make dist is missing: - Quite a bit under asn1. asn1/*/CMakeLists.txt, gnm, gprscdr, and other assorted files. - Several CMake modules - Many files under debian - Many docbook files - Several READMEs in doc - Many files in plugins - Most (all?) files in tools git-export-release.sh is missing: - ./configure, install-sh, other Autotoolery - Files generated using Bison/Flex - help/faq.txt - packaging/macosx/Info.plist - plugins/*/plugin.c - ui/*/*shark-tap-register.c It looks like you can't build from a dist tarball using CMake which is something we should fix. Instead of relying on autotools to generate the distribution tarball, one could also (temporarily) add all generated files to git and use git to build the tarball. Something like this (ensure that you have no other files in your git tree!): git clean -xfd # Ensure clean working dir (destructive!) ./autogen.sh ./configure find -name Makefile* -print0 | xargs -0 git add -f git add ... configure, config.status, bison, flex, etc... git commit -q -m Release git archive --prefix=... HEAD | xz -9 tar.gz git reset --hard HEAD~ # Return to previous version Another thing to consider is the availability of cmake which does not require additional files in a distribution tarball like autotools. If all platforms support cmake, what about dropping the autotools-generated stuff? Kind regards, Peter https://lekensteyn.nl ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] [Wireshark-announce] Wireshark 1.12.0rc3 is now available
2014-07-31 12:34 GMT+02:00 Peter Wu pe...@lekensteyn.nl: On Wednesday 30 July 2014 14:35:06 Gerald Combs wrote: After comparing the tarballs generated by make dist and git-export-release.sh I have to agree. Both have issues but the dist tarball will build according to our documentation on Linux, Windows, and OS X. make dist is missing: - Quite a bit under asn1. asn1/*/CMakeLists.txt, gnm, gprscdr, and other assorted files. - Several CMake modules - Many files under debian - Many docbook files - Several READMEs in doc - Many files in plugins - Most (all?) files in tools git-export-release.sh is missing: - ./configure, install-sh, other Autotoolery - Files generated using Bison/Flex - help/faq.txt - packaging/macosx/Info.plist - plugins/*/plugin.c - ui/*/*shark-tap-register.c It looks like you can't build from a dist tarball using CMake which is something we should fix. Instead of relying on autotools to generate the distribution tarball, one could also (temporarily) add all generated files to git and use git to build the tarball. Something like this (ensure that you have no other files in your git tree!): git clean -xfd # Ensure clean working dir (destructive!) ./autogen.sh ./configure find -name Makefile* -print0 | xargs -0 git add -f git add ... configure, config.status, bison, flex, etc... git commit -q -m Release git archive --prefix=... HEAD | xz -9 tar.gz git reset --hard HEAD~ # Return to previous version Please don't do that. Another thing to consider is the availability of cmake which does not require additional files in a distribution tarball like autotools. If all platforms support cmake, what about dropping the autotools-generated stuff? +1 for dropping autotools in favor of CMake. CMake already covers all my use cases. I also support dropping nmake, but since I'm not building on Windows I can't tell if CMake is complete enough. Cheers, Balint ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] [Wireshark-announce] Wireshark 1.12.0rc3 is now available
On 31 July 2014 11:42, Bálint Réczey bal...@balintreczey.hu wrote: 2014-07-31 12:34 GMT+02:00 Peter Wu pe...@lekensteyn.nl: On Wednesday 30 July 2014 14:35:06 Gerald Combs wrote: After comparing the tarballs generated by make dist and git-export-release.sh I have to agree. Both have issues but the dist tarball will build according to our documentation on Linux, Windows, and OS X. make dist is missing: - Quite a bit under asn1. asn1/*/CMakeLists.txt, gnm, gprscdr, and other assorted files. - Several CMake modules - Many files under debian - Many docbook files - Several READMEs in doc - Many files in plugins - Most (all?) files in tools git-export-release.sh is missing: - ./configure, install-sh, other Autotoolery - Files generated using Bison/Flex - help/faq.txt - packaging/macosx/Info.plist - plugins/*/plugin.c - ui/*/*shark-tap-register.c It looks like you can't build from a dist tarball using CMake which is something we should fix. Instead of relying on autotools to generate the distribution tarball, one could also (temporarily) add all generated files to git and use git to build the tarball. Something like this (ensure that you have no other files in your git tree!): git clean -xfd # Ensure clean working dir (destructive!) ./autogen.sh ./configure find -name Makefile* -print0 | xargs -0 git add -f git add ... configure, config.status, bison, flex, etc... git commit -q -m Release git archive --prefix=... HEAD | xz -9 tar.gz git reset --hard HEAD~ # Return to previous version Please don't do that. Another thing to consider is the availability of cmake which does not require additional files in a distribution tarball like autotools. If all platforms support cmake, what about dropping the autotools-generated stuff? +1 for dropping autotools in favor of CMake. CMake already covers all my use cases. I also support dropping nmake, but since I'm not building on Windows I can't tell if CMake is complete enough. Not yet. Working on it though. -- Graham Bloice ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] [Wireshark-announce] Wireshark 1.12.0rc3 is now available
On Thu, Jul 31, 2014 at 12:34:18PM +0200, Peter Wu wrote: Another thing to consider is the availability of cmake which does not require additional files in a distribution tarball like autotools. If all platforms support cmake, what about dropping the autotools-generated stuff? Oh no! Now you have uncovered my evil masterplan - and you know what happens to evil master plans once they are revealed? :-) Jörg -- Joerg Mayer jma...@loplof.de We are stuck with technology when what we really want is just stuff that works. Some say that should read Microsoft instead of technology. ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] [Wireshark-announce] Wireshark 1.12.0rc3 is now available
On 07/31/14 06:42, Bálint Réczey wrote: 2014-07-31 12:34 GMT+02:00 Peter Wu pe...@lekensteyn.nl: Another thing to consider is the availability of cmake which does not require additional files in a distribution tarball like autotools. If all platforms support cmake, what about dropping the autotools-generated stuff? +1 for dropping autotools in favor of CMake. CMake already covers all my use cases. There's still a long list of pretty important things listed under what needs to be done in README.cmake. ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] [Wireshark-announce] Wireshark 1.12.0rc3 is now available
On 7/31/14 6:08 AM, Graham Bloice wrote: On 31 July 2014 11:42, Bálint Réczey bal...@balintreczey.hu mailto:bal...@balintreczey.hu wrote: +1 for dropping autotools in favor of CMake. CMake already covers all my use cases. Same here except for Windows. I've been doing most of my Qt development using Qt Creator + CMake. It doesn't have all the conveniences of Qt Creator + QMake but it works well enough. I also support dropping nmake, but since I'm not building on Windows I can't tell if CMake is complete enough. Not yet. Working on it though. I added msbuild steps to the Windows buildslaves after the cmake steps. The 32-bit build succeeds although I haven't tried running it. The 64-bit build passes /MACHINE:X86 to the linker which then fails. Once we get CMake working on Windows we can drop the requirement for QMake and remove ui/qt/Qtshark.pro. ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] [Wireshark-announce] Wireshark 1.12.0rc3 is now available
On 31 July 2014 17:34, Gerald Combs ger...@wireshark.org wrote: On 7/31/14 6:08 AM, Graham Bloice wrote: On 31 July 2014 11:42, Bálint Réczey bal...@balintreczey.hu mailto:bal...@balintreczey.hu wrote: +1 for dropping autotools in favor of CMake. CMake already covers all my use cases. Same here except for Windows. I've been doing most of my Qt development using Qt Creator + CMake. It doesn't have all the conveniences of Qt Creator + QMake but it works well enough. I also support dropping nmake, but since I'm not building on Windows I can't tell if CMake is complete enough. Not yet. Working on it though. I added msbuild steps to the Windows buildslaves after the cmake steps. The 32-bit build succeeds although I haven't tried running it. The 64-bit build passes /MACHINE:X86 to the linker which then fails. I'm not that happy about CMake's handling of x86/amd64 issues. It should be able to emit a VS .sln that handles both types of builds, but I haven't yet looked into what's needed to make that work. -- Graham Bloice ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] [Wireshark-announce] Wireshark 1.12.0rc3 is now available
On 31 July 2014 17:34, Gerald Combs ger...@wireshark.org wrote: On 7/31/14 6:08 AM, Graham Bloice wrote: On 31 July 2014 11:42, Bálint Réczey bal...@balintreczey.hu mailto:bal...@balintreczey.hu wrote: +1 for dropping autotools in favor of CMake. CMake already covers all my use cases. Same here except for Windows. I've been doing most of my Qt development using Qt Creator + CMake. It doesn't have all the conveniences of Qt Creator + QMake but it works well enough. I also support dropping nmake, but since I'm not building on Windows I can't tell if CMake is complete enough. Not yet. Working on it though. I added msbuild steps to the Windows buildslaves after the cmake steps. The 32-bit build succeeds although I haven't tried running it. The 64-bit build passes /MACHINE:X86 to the linker which then fails. The buildslaves are failing to build the solution. I think the arguments to the msbuild step should be modified to be msbuild /m /p:Configuration=RelWithDebInfo Wireshark.sln. -- Graham Bloice ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] [Wireshark-announce] Wireshark 1.12.0rc3 is now available
On 31 July 2014 22:14, Graham Bloice graham.blo...@trihedral.com wrote: On 31 July 2014 17:34, Gerald Combs ger...@wireshark.org wrote: On 7/31/14 6:08 AM, Graham Bloice wrote: On 31 July 2014 11:42, Bálint Réczey bal...@balintreczey.hu mailto:bal...@balintreczey.hu wrote: +1 for dropping autotools in favor of CMake. CMake already covers all my use cases. Same here except for Windows. I've been doing most of my Qt development using Qt Creator + CMake. It doesn't have all the conveniences of Qt Creator + QMake but it works well enough. I also support dropping nmake, but since I'm not building on Windows I can't tell if CMake is complete enough. Not yet. Working on it though. I added msbuild steps to the Windows buildslaves after the cmake steps. The 32-bit build succeeds although I haven't tried running it. The 64-bit build passes /MACHINE:X86 to the linker which then fails. The buildslaves are failing to build the solution. I think the arguments to the msbuild step should be modified to be msbuild /m /p:Configuration=RelWithDebInfo Wireshark.sln. And the x86 buildslave CMake still isn't locating a viable Python Interpreter. -- Graham Bloice ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] [Wireshark-announce] Wireshark 1.12.0rc3 is now available
On 7/31/14 2:19 PM, Graham Bloice wrote: On 31 July 2014 22:14, Graham Bloice graham.blo...@trihedral.com mailto:graham.blo...@trihedral.com wrote: On 31 July 2014 17:34, Gerald Combs ger...@wireshark.org mailto:ger...@wireshark.org wrote: On 7/31/14 6:08 AM, Graham Bloice wrote: On 31 July 2014 11:42, Bálint Réczey bal...@balintreczey.hu mailto:bal...@balintreczey.hu mailto:bal...@balintreczey.hu mailto:bal...@balintreczey.hu wrote: +1 for dropping autotools in favor of CMake. CMake already covers all my use cases. Same here except for Windows. I've been doing most of my Qt development using Qt Creator + CMake. It doesn't have all the conveniences of Qt Creator + QMake but it works well enough. I also support dropping nmake, but since I'm not building on Windows I can't tell if CMake is complete enough. Not yet. Working on it though. I added msbuild steps to the Windows buildslaves after the cmake steps. The 32-bit build succeeds although I haven't tried running it. The 64-bit build passes /MACHINE:X86 to the linker which then fails. The buildslaves are failing to build the solution. I think the arguments to the msbuild step should be modified to be msbuild /m /p:Configuration=RelWithDebInfo Wireshark.sln. Done. And the x86 buildslave CMake still isn't locating a viable Python Interpreter. The machine has the official Python 2.6 installed in c:\Python26 and Cygwin's Python 2.7 installed in c:\cygwin\usr\bin. According to http://www.cmake.org/pipermail/cmake/2010-February/035404.html CMake looks for numbered Pythons executables (python2.7, python2.6, ...) before looking for the plain executable. In our case this means it's finding Cygwin's Python before the official version. The version detection then fails for some reason. I'm going to try installing the official Python 2.7. Hopefully it will be found before Cygwin's. ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] [Wireshark-announce] Wireshark 1.12.0rc3 is now available
On 7/28/14 7:34 AM, Jeff Morriss wrote: On 07/27/14 13:34, Bálint Réczey wrote: 2014-07-25 23:49 GMT+02:00 Jeff Morriss jeff.morriss...@gmail.com: On 07/22/14 16:27, Wireshark announcements wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I'm proud to announce the release of Wireshark 1.12.0rc3. This is a public release candidate for Wireshark 1.12.0. Hmm, the source tarball isn't in the expected directory (rc2 is still there): http://wiresharkdownloads.riverbed.com/wireshark/src/ The all-versions directory does have it though. Fixed. It also did not contain quite some files. Could release tarballs please be made using tools/git-export-release.sh? I had to use the tagged git-snapshot for the Debian packages. It worked well for me. What files were missing? I think changing to git-snapshot would be too significant a change this late in the game: it means a lot of the auto-generated files (like ./configure) would not be delivered, right? After comparing the tarballs generated by make dist and git-export-release.sh I have to agree. Both have issues but the dist tarball will build according to our documentation on Linux, Windows, and OS X. make dist is missing: - Quite a bit under asn1. asn1/*/CMakeLists.txt, gnm, gprscdr, and other assorted files. - Several CMake modules - Many files under debian - Many docbook files - Several READMEs in doc - Many files in plugins - Most (all?) files in tools git-export-release.sh is missing: - ./configure, install-sh, other Autotoolery - Files generated using Bison/Flex - help/faq.txt - packaging/macosx/Info.plist - plugins/*/plugin.c - ui/*/*shark-tap-register.c It looks like you can't build from a dist tarball using CMake which is something we should fix. Git-export-release picks up everything in images. I'm not sure if this is desired or not but it's something we haven't done in the past. ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] [Wireshark-announce] Wireshark 1.12.0rc3 is now available
On Jul 30, 2014, at 2:35 PM, Gerald Combs ger...@wireshark.org wrote: git-export-release.sh is missing: - ./configure, install-sh, other Autotoolery - Files generated using Bison/Flex - help/faq.txt - packaging/macosx/Info.plist - plugins/*/plugin.c - ui/*/*shark-tap-register.c Can that be rewritten as: git-export-release.sh is missing: - Everything not checked into Git This means its output is unacceptable for a release tarball (one purpose of which is to allow people running on a platform for which there's no binary Wireshark distribution to build a given release of Wireshark from source with as few extra tools installed as possible, so it should include a number of things built *from* source checked into Git). ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] [Wireshark-announce] Wireshark 1.12.0rc3 is now available
On 07/27/14 13:34, Bálint Réczey wrote: 2014-07-25 23:49 GMT+02:00 Jeff Morriss jeff.morriss...@gmail.com: On 07/22/14 16:27, Wireshark announcements wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I'm proud to announce the release of Wireshark 1.12.0rc3. This is a public release candidate for Wireshark 1.12.0. Hmm, the source tarball isn't in the expected directory (rc2 is still there): http://wiresharkdownloads.riverbed.com/wireshark/src/ The all-versions directory does have it though. It also did not contain quite some files. Could release tarballs please be made using tools/git-export-release.sh? I had to use the tagged git-snapshot for the Debian packages. It worked well for me. What files were missing? I think changing to git-snapshot would be too significant a change this late in the game: it means a lot of the auto-generated files (like ./configure) would not be delivered, right? ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] [Wireshark-announce] Wireshark 1.12.0rc3 is now available
On 07/22/14 16:27, Wireshark announcements wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I'm proud to announce the release of Wireshark 1.12.0rc3. This is a public release candidate for Wireshark 1.12.0. Hmm, the source tarball isn't in the expected directory (rc2 is still there): http://wiresharkdownloads.riverbed.com/wireshark/src/ The all-versions directory does have it though. ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
