update ejabberd to v21.01

[hgy59]

Motivation: Ejabberd does not build since some time
Linked issues: #4214. closes #3770, closes #2397, closes #2260, closes #2095

Checklist

• Build rule all-supported completed successfully
• Package upgrade completed successfully
• New installation of package completed successfully

Remarks

• update erlang to v23.2.5
• update ejabberd to v21.01
• ppc853x is not supported anymore
• use generic service setup
• activate install wizard

[willemb2]

@hgy59 On my DS216+II with DSM 6.2.3-25426 Update 3 the Package Center - Community still shows ejabberd 2.1.13-1. But I don't know what the route is between GitHub and the Package Center, so maybe I'm too impatient.

[hgy59]

@hgy59 On my DS216+II with DSM 6.2.3-25426 Update 3 the Package Center - Community still shows ejabberd 2.1.13-1. But I don't know what the route is between GitHub and the Package Center, so maybe I'm too impatient.

There is no automatic update of the synocommunity Package Center from github builds.
And there are no updates from Pull-Requests. The Package Center is updated manually by maintainers after a PR is merged back to the master branch. Before upload to the package center such builds are verified, and after upload it takes up to 48 hours until the package is visible in the DSM package center.

For manual installation you can use the build artifacts of successful github build actions on each PR.

• click Details on one of the build tasks under All checks have passed
• Open the popup menu under Artifacts
• Click packages

This will download packages.zip containing all successfully built packages.

The packages containing x64-6.1, aarch64-6.1 and armv7-6.1 in the name are builds for generic architectures. You will find the matching generic (or regular) arch for your device on the wiki page Package Archs.
Extract the spk matching your Diskstation Model and use it for manual installation.

HINT: Version 6.1 is compatible with DSM 6.1, 6.2, ... 6.2.3 (but not for DSM 7+)

[hgy59]

A dedicated erlang package is on the way with #4437. This should be used here too.