[Dxspider-support] New build 532

[Dirk Koopman]

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
>