ps3netsrv updated

[Hirador]

Updated to v1.47.45 with ps3netsrv 20220813 for DSM's versions: DSM-6.2.4 -> DSM-7.1

Description

1 - Updated the variables found on "spksrc/spk/ps3netsrv" and " spksrc/cross/ps3netsrv" to match the current version (v1.47.45 with ps3netsrv 20220813) of aldostools's ps3netsrv

2 - made "make all-supported",

3 - created .spk for my Architecture (arch-armada370)

4 - Made some tests with the updated version of the ps3netsrv

5 - Cleaned everything up for the pull request (make clean on both spksrc/spk/ps3netsrv and spksrc/cross/ps3netsrv)

Closes #5751

Checklist

• Build rule all-supported completed successfully
• New installation of package completed successfully
• Package upgrade completed successfully (Manually install the package again)
• Package functionality was tested
• Any needed documentation is updated/created

Type of change

• Bug fix
• New Package
• Package update
• Includes small framework changes
• This change requires a documentation update (e.g. Wiki)

[hgy59]

@Hirador thanks for providing this update.

What do you think about changing the port for this package? (see #5751)

[hgy59]

@Hirador please have a look at the file /spksrc/cross/p3netsrv/digests

It is not a valid digests file.

you should be able to create the correct file with make clean && make digests in cross/ps3netsrv folder

[Hirador]

@Hirador thanks for providing this update.

What do you think about changing the port for this package? (see #5751)

Hey I’ve thought about giving the chance to the user to set a custom port to the server, with a disclaimer where they can check which port is used in other Synocommunity’s packages (I know that this package has a port conflict with the Synology Calendar CalDAV). The fact is, the default port that the clients use to connect to this server is 38008, but can be changed with a custom one, so I’m planning to do it in the near future but for this update, I’m just leaving the default one set

[Hirador]

@Hirador please have a look at the file /spksrc/cross/p3netsrv/digests

It is not a valid digests file.

you should be able to create the correct file with make clean && make digests in cross/ps3netsrv folder

My fault, I’ve actually made the make digest command but something may have got wrong in the process

[Hirador]

@Hirador please have a look at the file /spksrc/cross/p3netsrv/digests

It is not a valid digests file.

you should be able to create the correct file with make clean && make digests in cross/ps3netsrv folder

Fixed the issue with the digests file

[hgy59]

Hey I’ve thought about giving the chance to the user to set a custom port to the server, with a disclaimer where they can check which port is used in other Synocommunity’s packages (I know that this package has a port conflict with the Synology Calendar CalDAV). The fact is, the default port that the clients use to connect to this server is 38008, but can be changed with a custom one, so I’m planning to do it in the near future but for this update, I’m just leaving the default one set

It is not possible to make the port configurable. Each package has to use exclusive ports. As port 38008 conflicts with the synology calendar package, we should change this port now.

[Hirador]

Hey I’ve thought about giving the chance to the user to set a custom port to the server, with a disclaimer where they can check which port is used in other Synocommunity’s packages (I know that this package has a port conflict with the Synology Calendar CalDAV). The fact is, the default port that the clients use to connect to this server is 38008, but can be changed with a custom one, so I’m planning to do it in the near future but for this update, I’m just leaving the default one set

It is not possible to make the port configurable. Each package has to use exclusive ports. As port 38008 conflicts with the synology calendar package, we should change this port now.

@hgy59 If it is strictly necessary, I agree with the port changing even if I would really prefer to leave the default one, just because the clients need to be modified so is no more “plug and play”.

Confirm to me that the port 14167 is usable and I’m going to edit the package in few minutes setting the default port to 14167

Also, where you think i can insert a warning to the users telling them to change the port client side? in the DESCRIPTION field?

[Hirador]

Hey I’ve thought about giving the chance to the user to set a custom port to the server, with a disclaimer where they can check which port is used in other Synocommunity’s packages (I know that this package has a port conflict with the Synology Calendar CalDAV). The fact is, the default port that the clients use to connect to this server is 38008, but can be changed with a custom one, so I’m planning to do it in the near future but for this update, I’m just leaving the default one set

It is not possible to make the port configurable. Each package has to use exclusive ports. As port 38008 conflicts with the synology calendar package, we should change this port now.

Please confirm me what I’ve said so that we can go live as soon as possible

[Hirador]

Hey I’ve thought about giving the chance to the user to set a custom port to the server, with a disclaimer where they can check which port is used in other Synocommunity’s packages (I know that this package has a port conflict with the Synology Calendar CalDAV). The fact is, the default port that the clients use to connect to this server is 38008, but can be changed with a custom one, so I’m planning to do it in the near future but for this update, I’m just leaving the default one set

It is not possible to make the port configurable. Each package has to use exclusive ports. As port 38008 conflicts with the synology calendar package, we should change this port now.

Changed the port, please continue the checks

[hgy59]

LGTM