armv5 rust version frozen for no-atomic support

[th0ma7]

Description

armv5 rust version frozen for no-atomic support

Fixes #

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)

[th0ma7]

@hgy59 would you mind giving this a look? As expected changes where relatively minor for this to work out (or at least seems to be ok at first glance).

[hgy59]

@th0ma7 LGTM, alas the build artifacts are strange. Build 6603 shows 12 Artifacts but only one file for "Packages for aarch64-6.2.4" is available.
Similar result for Build 6602 of sabnzbd: 11 Artifacts but only one file for "Packages for comcerto2k-7.1".
Before, build 6601 was correct (11 artifacts for jellyfin).

[th0ma7]

alas the build artifacts are strange. Build 6603 shows 12 Artifacts but only one file for "Packages for aarch64-6.2.4" is available.

Interestingly the aarch64 showed as canceled so I force-run failed builds, which in turn worked out.

Similar result for Build 6602 of sabnzbd: 11 Artifacts but only one file for "Packages for comcerto2k-7.1".

Similar again, build was marked as skipped (not failed) so i forced-run it as well.

Before, build 6601 was correct (11 artifacts for jellyfin).

I would presume it's something else with the github-action that doesn't manage forced-run artifacts correctly whereas older artifacts somehow disapear.