Re: [Wireshark-dev] Random "#" in issues - cross references

2020-10-28 Thread Pascal Quantin
Le mer. 28 oct. 2020 à 17:17, Pascal Quantin  a
écrit :

> Hi Chuck,
>
> Le mer. 28 oct. 2020 à 17:00, chuck c  a écrit :
>
>> https://gitlab.com/wireshark/wireshark/-/issues/16844
>> "Compiled (64-bit) with Qt 5.14.2, with libpcap, with GLib 2.52.3, with
>> zlib
>> 1.2.11, with SMI 0.4.8, with c-ares 1.15.0, with Lua 5.2.4, with GnuTLS
>> 3.6.3
>> and PKCS #11 (closed) support, ..."
>>
>> The #11 gets flagged as an issue and cross reference made.
>>
>> https://gitlab.com/wireshark/wireshark/-/issues/11
>>
>
> presumably putting the build description in``` quotes would have prevented
> this. We should update our bug template.
>

See https://gitlab.com/wireshark/wireshark/-/merge_requests/765


> Best regards,
> Pascal.
>
>
>>
>>
>> Austin Knutson @AustinKnutsonSprint mentioned in issue #16805 (closed) 2
>> months ago
>> Chuck Craft @chuckcraft mentioned in issue #16834 1 month ago
>> Allen Lee @BigFatCat mentioned in issue #16837 1 month ago
>> Chuck Craft @chuckcraft mentioned in issue #16844 (closed) 1 month ago
>> Georg Kneringer @EggisEgg mentioned in issue #16846 (closed) 1 month ago
>> lemur117 @lemur117 mentioned in issue #16859 1 month ago
>> John Thacker @johnthacker mentioned in issue #16872 1 month ago
>> Dmitry @dpl94 mentioned in issue #16881 (closed) 4 weeks ago
>> Ori Inbar @oriinbar mentioned in issue #16889 (closed) 3 weeks ago
>> Elvis Presley @phikus mentioned in issue #16904 (closed) 2 weeks ago
>> Haxthausen @Haxthausen mentioned in issue #16905 2 weeks ago
>> Guy Harris @guyharris mentioned in issue #16906 2 weeks ago
>> John Thacker @johnthacker mentioned in issue #16909 (closed) 1 week ago
>> Gerald Combs @geraldcombs mentioned in issue #16911 1 week ago
>> Tomáš Szaniszlo @tomaxuser mentioned in issue #16925 1 week ago
>> Jaap Keuter @JaapKeuter mentioned in issue #16940 1 week ago
>> Christopher Maynard @cjmaynard mentioned in issue #16957 14 hours ago
>> Jaap Keuter @JaapKeuter mentioned in issue #16961 (closed) 5 hours ago
>>
>> ___
>> 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
>
>
___
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] Random "#" in issues - cross references

2020-10-28 Thread Pascal Quantin
Hi Chuck,

Le mer. 28 oct. 2020 à 17:00, chuck c  a écrit :

> https://gitlab.com/wireshark/wireshark/-/issues/16844
> "Compiled (64-bit) with Qt 5.14.2, with libpcap, with GLib 2.52.3, with
> zlib
> 1.2.11, with SMI 0.4.8, with c-ares 1.15.0, with Lua 5.2.4, with GnuTLS
> 3.6.3
> and PKCS #11 (closed) support, ..."
>
> The #11 gets flagged as an issue and cross reference made.
>
> https://gitlab.com/wireshark/wireshark/-/issues/11
>

presumably putting the build description in``` quotes would have prevented
this. We should update our bug template.

Best regards,
Pascal.


>
>
> Austin Knutson @AustinKnutsonSprint mentioned in issue #16805 (closed) 2
> months ago
> Chuck Craft @chuckcraft mentioned in issue #16834 1 month ago
> Allen Lee @BigFatCat mentioned in issue #16837 1 month ago
> Chuck Craft @chuckcraft mentioned in issue #16844 (closed) 1 month ago
> Georg Kneringer @EggisEgg mentioned in issue #16846 (closed) 1 month ago
> lemur117 @lemur117 mentioned in issue #16859 1 month ago
> John Thacker @johnthacker mentioned in issue #16872 1 month ago
> Dmitry @dpl94 mentioned in issue #16881 (closed) 4 weeks ago
> Ori Inbar @oriinbar mentioned in issue #16889 (closed) 3 weeks ago
> Elvis Presley @phikus mentioned in issue #16904 (closed) 2 weeks ago
> Haxthausen @Haxthausen mentioned in issue #16905 2 weeks ago
> Guy Harris @guyharris mentioned in issue #16906 2 weeks ago
> John Thacker @johnthacker mentioned in issue #16909 (closed) 1 week ago
> Gerald Combs @geraldcombs mentioned in issue #16911 1 week ago
> Tomáš Szaniszlo @tomaxuser mentioned in issue #16925 1 week ago
> Jaap Keuter @JaapKeuter mentioned in issue #16940 1 week ago
> Christopher Maynard @cjmaynard mentioned in issue #16957 14 hours ago
> Jaap Keuter @JaapKeuter mentioned in issue #16961 (closed) 5 hours ago
> ___
> 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
___
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] Random "#" in issues - cross references

2020-10-28 Thread chuck c
https://gitlab.com/wireshark/wireshark/-/issues/16844
"Compiled (64-bit) with Qt 5.14.2, with libpcap, with GLib 2.52.3, with zlib
1.2.11, with SMI 0.4.8, with c-ares 1.15.0, with Lua 5.2.4, with GnuTLS
3.6.3
and PKCS #11 (closed) support, ..."

The #11 gets flagged as an issue and cross reference made.

https://gitlab.com/wireshark/wireshark/-/issues/11

Austin Knutson @AustinKnutsonSprint mentioned in issue #16805 (closed) 2
months ago
Chuck Craft @chuckcraft mentioned in issue #16834 1 month ago
Allen Lee @BigFatCat mentioned in issue #16837 1 month ago
Chuck Craft @chuckcraft mentioned in issue #16844 (closed) 1 month ago
Georg Kneringer @EggisEgg mentioned in issue #16846 (closed) 1 month ago
lemur117 @lemur117 mentioned in issue #16859 1 month ago
John Thacker @johnthacker mentioned in issue #16872 1 month ago
Dmitry @dpl94 mentioned in issue #16881 (closed) 4 weeks ago
Ori Inbar @oriinbar mentioned in issue #16889 (closed) 3 weeks ago
Elvis Presley @phikus mentioned in issue #16904 (closed) 2 weeks ago
Haxthausen @Haxthausen mentioned in issue #16905 2 weeks ago
Guy Harris @guyharris mentioned in issue #16906 2 weeks ago
John Thacker @johnthacker mentioned in issue #16909 (closed) 1 week ago
Gerald Combs @geraldcombs mentioned in issue #16911 1 week ago
Tomáš Szaniszlo @tomaxuser mentioned in issue #16925 1 week ago
Jaap Keuter @JaapKeuter mentioned in issue #16940 1 week ago
Christopher Maynard @cjmaynard mentioned in issue #16957 14 hours ago
Jaap Keuter @JaapKeuter mentioned in issue #16961 (closed) 5 hours ago
___
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] MATE not extracting fields as requested

2020-10-28 Thread Harald Welte
On Wed, Oct 28, 2020 at 11:30:03AM +0100, Jaap Keuter wrote:
> I've created issue 16961[1] on your behalf.

thanks, I was just about to create an issue myself, but then discovered 12182 
[1]
and thought it might be the same symptom.

In any case, I also saw you just submitted a patch.  my local build is running. 
Thanks.

Regards,
Harald

[1] https://gitlab.com/wireshark/wireshark/-/issues/12182

-- 
- Harald Weltehttp://laforge.gnumonks.org/

"Privacy in residential applications is a desirable marketing option."
  (ETSI EN 300 175-7 Ch. A6)
___
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] MATE not extracting fields as requested

2020-10-28 Thread Jaap Keuter
Hi Harald,

I've created issue 16961[1] on your behalf.

Thanks,
Jaap

[1] https://gitlab.com/wireshark/wireshark/-/issues/16961

On 24-10-2020 18:43, Harald Welte wrote:
> Hi Jaap,
> 
> thanks for your insight into the matter.  As you confirm there is an actual 
> bug, I will raise
> it in gitlab, together with extracts of your findings here.

___
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