Re: [Wireshark-dev] Release lifetime and version number changes?

2019-04-12 Thread graham.shanks via Wireshark-dev
I think dropping the even/odd scheme is a good  idea.Personally I'd go down to 
2 active branches but then my group wouldn't be adversely affected by  dropping 
the "old old stable" version since we invariably use the stable version. More 
weight should be given to the opinions of people who do use old stable 
versions. I would point out that the proposed change gives no firm guarantee on 
the supported lifetime of a branch at all. Could it be as short as two months? 
Potentially,  since there would be nothing to stop us releasing a branch a 
month (unlikely,  but from the user's perspective they would have no control 
over that)Sent from Samsung tablet.
null___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] Adding sample capture

2018-03-17 Thread e-mail graham.shanks via Wireshark-dev
GrahamShanks

Regards
Graham


> On 17 March 2018 at 13:38 Jaap Keuter <jaap.keu...@xs4all.nl> wrote:
> 
> 
> 
> > > On 17 Mar 2018, at 00:28, e-mail graham.shanks via 
> Wireshark-dev < wireshark-dev@wireshark.org 
> mailto:wireshark-dev@wireshark.org > wrote:
> > 
> > 
> > How do I get permission to enable me to upload a capture file to 
> > the Sample Captures page? In particular I want to add the capture file 
> > associated with Bug: 14441 
> > https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14441
> > 
> > 
> > Regards
> > Graham
> > 
> > > Hi,
> 
> What is your Wiki user name?
> 
> 
> 
 

> ___
> Sent via: Wireshark-dev mailing list <wireshark-dev@wireshark.org>
> Archives: https://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
> mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
> 
 
___
Sent via:Wireshark-dev mailing list <wireshark-dev@wireshark.org>
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

[Wireshark-dev] Adding sample capture

2018-03-16 Thread e-mail graham.shanks via Wireshark-dev
How do I get permission to enable me to upload a capture file to the Sample 
Captures page? In particular I want to add the capture file associated with 
Bug: 14441 https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14441


Regards
Graham___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

[Wireshark-dev] git question

2017-12-02 Thread e-mail graham.shanks via Wireshark-dev
After submitting some changes to git review and getting them accepted I get the
following message when I do a git status:

C:\Development\wireshark>git status
On branch master
Your branch is ahead of 'origin/master' by 3 commits.
(use "git push" to publish your local commits)
nothing to commit, working tree clean

A search on this message suggests that I need to do a git pull --rebase, but the
documentation suggests that this will synchronise with the remote repository
(which is what I want to do) but then try to apply the commits (which I don't
want to do, I think). The git documentation on rebase doesn't seem to cover what
I think the wireshark repository is doing.

Is git pull --rebase the correct thing to do? Also did I do something wrong to
get into this state?

Regards
Graham___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] Build error with VS2013 Ultimate

2017-08-01 Thread e-mail graham.shanks via Wireshark-dev
> On 06 July 2017 at 21:44 Graham Bloice <graham.blo...@trihedral.com> wrote:
> 
> 
> 
> On 6 July 2017 at 19:37, e-mail graham.shanks via Wireshark-dev
> <wireshark-dev@wireshark.org mailto:wireshark-dev@wireshark.org > wrote:
> 
> > > 
> > I have a problem with building Wireshark on a 64-bit Windows 8
> > machine using VS2013 Ultimate. I last built Wireshark on on this machine
> > about 6 months ago, so I started a completely new development by installing
> > and preparing the sources as per the development guide. When building the
> > sources I get 8 errors, all basically as follows:
> > 
> > "C:\Development\wsbuild64\Wireshark.sln" (default target) (1) ->
> > "C:\Development\wsbuild64\wireshark.vcxproj.metaproj" (default
> > target) (69) ->
> > "C:\Development\wsbuild64\wireshark.vcxproj" (default target) (138)
> > ->
> > C:\Development\wsbuild64\image\wireshark.rc(1): fatal error RC1015:
> > cannot open include file 'winver.h'.
> > [C:\Development\wsbuild64\wireshark.vcxproj]
> > 
> > Inspecting the solution file the $(WindowsSDK_IncludePath) macro is
> > pointing to the correct system directory (i.e., it contains winver.h) and is
> > included in the VC++ Directories property.
> > 
> > Any pointers to what is wrong?
> > 
> >  
> > 
> > Regards
> > 
> > Graham
> > 
> > 
> > > 
> Some questions:
>1. Are you building from the command line with msbuild or using the
> Visual Studio IDE?
>2. Can you attach the output of the CMake configuration step, this can
> be done by redirecting the output of the command to a text file and attaching
> that file i.e. "cmake ... ">&1 >cmake.txt"
>3. Similarly, can you attach the output of the msbuild step, i.e.
> "msbuild ... 2>&1 >build.txt"
> 
> --
> Graham Bloice
> 


 The problem was that I was using cmake v3.9.0 rc5 (cmake v3.9.0 also fails).
Once I reverted to cmake v3.8.2 everything was OK.

Regards
Graham___
Sent via:Wireshark-dev mailing list <wireshark-dev@wireshark.org>
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

[Wireshark-dev] Build error with VS2013 Ultimate

2017-07-06 Thread e-mail graham.shanks via Wireshark-dev
I have a problem with building Wireshark on a 64-bit Windows 8 machine using
VS2013 Ultimate. I last built Wireshark on on this machine about 6 months ago,
so I started a completely new development by installing and preparing the
sources as per the development guide. When building the sources I get 8 errors,
all basically as follows:

"C:\Development\wsbuild64\Wireshark.sln" (default target) (1) ->
"C:\Development\wsbuild64\wireshark.vcxproj.metaproj" (default target) (69) ->
"C:\Development\wsbuild64\wireshark.vcxproj" (default target) (138) ->
C:\Development\wsbuild64\image\wireshark.rc(1): fatal error RC1015: cannot open
include file 'winver.h'. [C:\Development\wsbuild64\wireshark.vcxproj]

Inspecting the solution file the $(WindowsSDK_IncludePath) macro is pointing to
the correct system directory (i.e., it contains winver.h) and is included in the
VC++ Directories property.

Any pointers to what is wrong?

 

Regards

Graham___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe