[Dxspider-support] Removal of /P and /MM
Mike G3YPP
mike at g3ypp.uk
Sun Apr 14 12:07:57 BST 2024
Fortunately I am also seeing those spots with build 533
I don’t understand why you would want to remove these suffixes which are a key part of the callsign for hunters for such things as WWFF, SOTA, POTA etc.
Mike G3YPP
Sent from Mail for Windows
From: dxspider-support-request at tobit.co.uk
Sent: 14 April 2024 12:00
To: dxspider-support at tobit.co.uk
Subject: Dxspider-support Digest, Vol 255, Issue 9
Send Dxspider-support mailing list submissions to
dxspider-support at tobit.co.uk
To subscribe or unsubscribe via the World Wide Web, visit
https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
or, via email, send a message with subject or body 'help' to
dxspider-support-request at tobit.co.uk
You can reach the person managing the list at
dxspider-support-owner at tobit.co.uk
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Dxspider-support digest..."
Today's Topics:
1. Re: New build 532 (Luigi Carlotto IK5ZUK)
2. Re: New build 532 (Keith Maton)
3. Removal of /P and /MM (Mike G3YPP)
4. Re: Removal of /P and /MM (Keith Maton)
----------------------------------------------------------------------
Message: 1
Date: Sat, 13 Apr 2024 20:18:29 +0200
From: Luigi Carlotto IK5ZUK <ik5zuk at tiscali.it>
To: The DXSpider Support list <dxspider-support at tobit.co.uk>
Subject: Re: [Dxspider-support] New build 532
Message-ID: <34677e9a-a33f-4b1e-b988-1387472553c1 at tiscali.it>
Content-Type: text/plain; charset=UTF-8; format=flowed
Hi Dirk,
I've done only "git pull".
Now I've done
git reset --hard
git pull
but the errors is still here: Spider won't starts. Please, can you give
me more help?
Thank you.
73 Luigi IK5ZUK
Il 13/04/2024 19:42, Dirk Koopman via Dxspider-support ha scritto:
> Have you done
>
> git reset --hard
> git pull
>
> On 13/04/2024 13:40, Luigi Carlotto IK5ZUK wrote:
>> Hello,
>> after upgrading the Mojo to 532, Spider won't start and I've received
>> the following errors:
>>
>> sysop at HAMRADIO-:/spider/perl$ ./cluster.pl &
>> [1] 1139
>> sysop at HAMRADIO-:/spider/perl$ Global symbol "$nossid" requires
>> explicit package name at /spider/perl/Filter.pm line 362.
>> Global symbol "$nossid" requires explicit package name at
>> /spider/perl/Filter.pm line 363.
>> Global symbol "$n" requires explicit package name at
>> /spider/perl/Filter.pm line 364.
>> Global symbol "$n" requires explicit package name at
>> /spider/perl/Filter.pm line 366.
>> Global symbol "$nossid" requires explicit package name at
>> /spider/perl/Filter.pm line 368.
>> syntax error at /spider/perl/Filter.pm line 369, near
>> "Filter::read_in($sort, $dxchan->is_user ? 'user_default'"
>> BEGIN not safe after errors--compilation aborted at
>> /spider/perl/Filter.pm line 405.
>> Compilation failed in require at /spider/perl/DXChannel.pm line 33.
>> BEGIN failed--compilation aborted at /spider/perl/DXChannel.pm line 33.
>> Compilation failed in require at ./cluster.pl line 128.
>> BEGIN failed--compilation aborted at ./cluster.pl line 128.
>>
>>
>> What I can do to start it again?
>>
>> TNX !
>>
>> 73 Luigi IK5ZUK
>>
>>
>> Il 13/04/2024 13:17, Kin via Dxspider-support ha scritto:
>>> Hi to all,
>>>
>>> I've just been informed by the Telegram bot that we have a new build in
>>> Mojo: 532
>>> This is what Dirk has done:
>>>
>>> 27Mar24=====================================================================
>>>
>>> =
>>> 1. Fix dupe PC[16]1 (spot) coming in "too fast" for dupe filter to
>>> work.
>>>
>>> ??? Probably.
>>> 25Mar24=====================================================================
>>>
>>> =
>>> 1. Make talk work. Note: this now works as the mojo branch originally
>>> ??? expected - which means that it may (and likely will) flood route
>>> talks
>>> ??? where the callsign that you want to talk to does not have a
>>> route to
>>> ??? both the callsign and any nodes that it may be connected to.
>>> 22Mar24=====================================================================
>>>
>>> =
>>> 1. Change the processing of trailing callsigns slightly so that /1
>>> /2 etc
>>> are
>>> ??? retained, but the /P /M /A /MM etc are removed.
>>> 20Mar24=====================================================================
>>>
>>> =
>>> 1. Has it really been so long since the last update?
>>> 2. Since forever, mainly because filtering was done very early on in
>>> ??? DXSpider's development, clearing a filter needed a
>>> disconnect/reconnect
>>> ??? cycle from the user/node to activate. Now clearing or changing a
>>> filter
>>> is
>>> ??? immediately effective in the current session.
>>>
>>> ??? Also things like: 'rej/spot user_default on vhf' will
>>> immediately apply
>>> ??? to all users that do not already have some other filter in
>>> place. Users
>>> ??? can override this by setting a filter.
>>>
>>> ??? The Filter system will now show the actual token that a faulty
>>> command
>>> ??? dislikes.
>>> 3. Disable the "is there a route to callsign X3XXX" test in talk.
>>> This is a
>>> ??? legacy test that should not apply at the user level. The
>>> resulting PC93
>>> is
>>> ??? flood routed unless there is a genuine direct route to that
>>> callsign.
>>>
>>> Take the opportunity to upgrade to Mojo!!!
>>>
>>> 73 de Kin EA3CV
>>>
>>> Sysop EA3CV-2, EA4URE2, 3 & 5
>>>
>>>
>>>
>>> _______________________________________________
>>> Dxspider-support mailing list
>>> Dxspider-support at tobit.co.uk
>>> https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
>>
>
>
> _______________________________________________
> Dxspider-support mailing list
> Dxspider-support at tobit.co.uk
> https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
------------------------------
Message: 2
Date: Sat, 13 Apr 2024 22:30:08 +0100
From: Keith Maton <g6nhu at me.com>
To: The DXSpider Support list <dxspider-support at tobit.co.uk>
Subject: Re: [Dxspider-support] New build 532
Message-ID: <558EC04C-0CD6-4969-B310-B9E033C606D4 at me.com>
Content-Type: text/plain; charset=us-ascii
Updated successfully here using your check_build script.
73 Keith
> On 13 Apr 2024, at 12:17, Kin via Dxspider-support <dxspider-support at tobit.co.uk> wrote:
>
> Hi to all,
>
> I've just been informed by the Telegram bot that we have a new build in
> Mojo: 532
> This is what Dirk has done:
>
> 27Mar24=====================================================================
> =
> 1. Fix dupe PC[16]1 (spot) coming in "too fast" for dupe filter to work.
>
> Probably.
> 25Mar24=====================================================================
> =
> 1. Make talk work. Note: this now works as the mojo branch originally
> expected - which means that it may (and likely will) flood route talks
> where the callsign that you want to talk to does not have a route to
> both the callsign and any nodes that it may be connected to.
> 22Mar24=====================================================================
> =
> 1. Change the processing of trailing callsigns slightly so that /1 /2 etc
> are
> retained, but the /P /M /A /MM etc are removed.
> 20Mar24=====================================================================
> =
> 1. Has it really been so long since the last update?
> 2. Since forever, mainly because filtering was done very early on in
> DXSpider's development, clearing a filter needed a disconnect/reconnect
> cycle from the user/node to activate. Now clearing or changing a filter
> is
> immediately effective in the current session.
>
> Also things like: 'rej/spot user_default on vhf' will immediately apply
> to all users that do not already have some other filter in place. Users
> can override this by setting a filter.
>
> The Filter system will now show the actual token that a faulty command
> dislikes.
> 3. Disable the "is there a route to callsign X3XXX" test in talk. This is a
> legacy test that should not apply at the user level. The resulting PC93
> is
> flood routed unless there is a genuine direct route to that callsign.
>
> Take the opportunity to upgrade to Mojo!!!
>
> 73 de Kin EA3CV
>
> Sysop EA3CV-2, EA4URE2, 3 & 5
>
>
>
> _______________________________________________
> Dxspider-support mailing list
> Dxspider-support at tobit.co.uk
> https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
------------------------------
Message: 3
Date: Sun, 14 Apr 2024 09:55:44 +0100
From: Mike G3YPP <mike at g3ypp.uk>
To: "dxspider-support at tobit.co.uk" <dxspider-support at tobit.co.uk>
Subject: [Dxspider-support] Removal of /P and /MM
Message-ID: <mailman.2.1713092401.593927.dxspider-support at tobit.co.uk>
Content-Type: text/plain; charset="utf-8"
Hi Dirk,
Is my understanding correct that the latest version removes /P and /MM from spotted callsigns or have I misread the changes file?
Regards
Mike G3YPP
Sysop for MX0NCA-2
Sent from Mail for Windows
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.tobit.co.uk/pipermail/dxspider-support/attachments/20240414/7da1024d/attachment.htm>
------------------------------
Message: 4
Date: Sun, 14 Apr 2024 11:05:00 +0100
From: Keith Maton <g6nhu at me.com>
To: The DXSpider Support list <dxspider-support at tobit.co.uk>
Subject: Re: [Dxspider-support] Removal of /P and /MM
Message-ID: <A482E639-6F47-440F-BE5B-DAE0717C00DB at me.com>
Content-Type: text/plain; charset="utf-8"
That?s how I read it but I?m still seeing spots for /P stations appearing.
73 Keith
> On 14 Apr 2024, at 09:55, Mike G3YPP via Dxspider-support <dxspider-support at tobit.co.uk> wrote:
>
> Hi Dirk,
>
> Is my understanding correct that the latest version removes /P and /MM from spotted callsigns or have I misread the changes file?
>
> Regards
>
> Mike G3YPP
> Sysop for MX0NCA-2
>
> Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for Windows
>
> _______________________________________________
> Dxspider-support mailing list
> Dxspider-support at tobit.co.uk <mailto:Dxspider-support at tobit.co.uk>
> https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.tobit.co.uk/pipermail/dxspider-support/attachments/20240414/55cc2480/attachment-0001.htm>
------------------------------
Subject: Digest Footer
_______________________________________________
Dxspider-support mailing list
Dxspider-support at tobit.co.uk
https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
------------------------------
End of Dxspider-support Digest, Vol 255, Issue 9
************************************************
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.tobit.co.uk/pipermail/dxspider-support/attachments/20240414/50cf10bf/attachment.htm>
More information about the Dxspider-support
mailing list