Re: [Wireshark-dev] Git + Gerrit: next steps
On Dec 21, 2013, at 2:39 AM, Joerg Mayer wrote: > On Wed, Dec 18, 2013 at 04:12:20PM -0800, Gerald Combs wrote: >> I'm assuming everyone has had a chance to test the Gerrit installation >> at test.code.wireshark.org If you haven't, now might be a good time. >> Unless anyone thinks that moving to Git+Gerrit is an absolutely horrific >> idea I'm going to start the process of migrating from Subversion. The >> timeline looks roughly like this: >> >> Preparation (next few days, early January): >> >> 1. Create a Gerrit instance at code.wireshark.org. > > I failed at this step. I neither have nor will I have a google/yahoo/whatever > ID. Is there another way to provide authentication? OK, I'm confused - which of the steps in those lists are things *Gerald* has to do, and which are things that all developers who want to use Git+Gerrit have to do? I'd assumed all those steps were just things Gerald was going to be doing. ___ Sent via:Wireshark-dev mailing list 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] Git + Gerrit: next steps
On 12/21/13 2:39 AM, Joerg Mayer wrote: > On Wed, Dec 18, 2013 at 04:12:20PM -0800, Gerald Combs wrote: >> I'm assuming everyone has had a chance to test the Gerrit installation >> at test.code.wireshark.org If you haven't, now might be a good time. >> Unless anyone thinks that moving to Git+Gerrit is an absolutely horrific >> idea I'm going to start the process of migrating from Subversion. The >> timeline looks roughly like this: >> >> Preparation (next few days, early January): >> >> 1. Create a Gerrit instance at code.wireshark.org. > > I failed at this step. I neither have nor will I have a google/yahoo/whatever > ID. Is there another way to provide authentication? Do you have an account with *any* OpenID provider? There are plenty of options aside from Google or Yahoo, including hosting your own: https://help.launchpad.net/YourAccount/OpenID https://fedoraproject.org/wiki/OpenID https://sourceforge.net/apps/trac/sourceforge/wiki/OpenID http://wiki.openid.net/w/page/12995226/Run%20your%20own%20identity%20server Aside from OpenID Gerrit allows for HTTP or LDAP authentication but OpenID is the easiest to use and manage by far from both a user and sysadmin perspective. ___ Sent via:Wireshark-dev mailing list 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] Is this patch to semcheck.c valid (handling FT_SYSTEM_ID) ?
There is also : ./wslua_proto.c:1261:1: error: 'ProtoField_systemid' defined but not used [-Werror=unused-function] (Fixed in revision 54397) On Mon, Dec 23, 2013 at 6:59 PM, wrote: > I believe I just missed committing that file when I added the FT_SYSTEM_ID > type. Committed (functionality) to rev 54394 and thanks for the catch! > > -Original Message- > From: Martin Mathieson > To: Developer support list for Wireshark > Sent: Mon, Dec 23, 2013 12:44 pm > Subject: [Wireshark-dev] Is this patch to semcheck.c valid (handling > FT_SYSTEM_ID) ? > > My gcc build is complaining that FT_SYSTEM_ID is missing from 3 switch > statements. I'm not sure I properly understand how it is used, so would > appreciate if someone could take a quick look at this patch? If there are > no objections I will commit it later... > > Thanks, > Martin > > ___ > Sent via:Wireshark-dev mailing list > Archives:http://www.wireshark.org/lists/wireshark-dev > Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev > mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe > > > > ___ > Sent via:Wireshark-dev mailing list > Archives:http://www.wireshark.org/lists/wireshark-dev > Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev > mailto:wireshark-dev-requ...@wireshark.org > ?subject=unsubscribe > ___ Sent via:Wireshark-dev mailing list 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] Is this patch to semcheck.c valid (handling FT_SYSTEM_ID) ?
I believe I just missed committing that file when I added the FT_SYSTEM_ID type. Committed (functionality) to rev 54394 and thanks for the catch! -Original Message- From: Martin Mathieson To: Developer support list for Wireshark Sent: Mon, Dec 23, 2013 12:44 pm Subject: [Wireshark-dev] Is this patch to semcheck.c valid (handling FT_SYSTEM_ID) ? My gcc build is complaining that FT_SYSTEM_ID is missing from 3 switch statements. I'm not sure I properly understand how it is used, so would appreciate if someone could take a quick look at this patch? If there are no objections I will commit it later... Thanks, Martin ___ Sent via:Wireshark-dev mailing list Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe ___ Sent via:Wireshark-dev mailing list Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
[Wireshark-dev] Is this patch to semcheck.c valid (handling FT_SYSTEM_ID) ?
My gcc build is complaining that FT_SYSTEM_ID is missing from 3 switch
statements. I'm not sure I properly understand how it is used, so would
appreciate if someone could take a quick look at this patch? If there are
no objections I will commit it later...
Thanks,
Martin
Index: semcheck.c
===
--- semcheck.c (revision 54393)
+++ semcheck.c (working copy)
@@ -65,6 +65,7 @@
switch (a) {
case FT_NONE:
case FT_PROTOCOL:
+ case FT_SYSTEM_ID:
case FT_FLOAT: /* XXX - should be able to compare with
INT */
case FT_DOUBLE: /* XXX - should be able to compare with
INT */
case FT_ABSOLUTE_TIME:
@@ -172,6 +173,7 @@
switch(hfinfo->type) {
case FT_NONE:
case FT_PROTOCOL:
+ case FT_SYSTEM_ID:
case FT_FLOAT:
case FT_DOUBLE:
case FT_ABSOLUTE_TIME:
@@ -304,6 +306,7 @@
case FT_NONE:
case FT_PROTOCOL:
+ case FT_SYSTEM_ID:
case FT_FLOAT:
case FT_DOUBLE:
case FT_ABSOLUTE_TIME:
___
Sent via:Wireshark-dev mailing list
Archives:http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
[Wireshark-dev] Is it possible to update the version of gcrypt?
Hi, I would like to make use of an AES mode only available in the most recent version of gcrypt (1.6). Is it possible to upgrade the version that comes as a result of running the Windows 'setup' target? My guess is that its not easy, and that we take the version that came with an old version of gnutls, whereas recent versions now use nettle as the low-level crypto library? We have 10 dissectors that use libgcrypt, so moving to nettle would take a bit of work. I'm not yet certain that nettle supports what I need (never mind the other current users of gcrypt)- I'd need to write a test program to see if it does what I need. Regards, Martin ___ Sent via:Wireshark-dev mailing list 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-users] Wireshark 1.10.5 is now available
can not connect to website http://www.wireshark.org/ ,it lasted about 1 week. damker___ Sent via:Wireshark-dev mailing list 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] Compilation failure on Fedora 20 - GTK3 issues
On 12/20/2013 12:46 PM, Joerg Mayer wrote: As Wireshark development doesn't really care about the compatibility with future GTK versions (we are migrating to Qt) I have disabled that warning for cmake builds. So either apply a similar change to the autotools build Done in SVN #54337. ___ Sent via:Wireshark-dev mailing list Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
