fix(ci): sign arm64 rpm packages.

[FedeDP]

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind design

/kind documentation

/kind failing-test

/kind feature

If contributing rules or changes to rules, please make sure to also uncomment one of the following line:

/kind rule-update

/kind rule-create

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area build

/area engine

/area rules

/area tests

/area proposals

What this PR does / why we need it:

Which issue(s) this PR fixes:

Fixes #2064

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

NONE

[vjjmiras]

Despite the change directory statement, the execution of the sign script, and the verification of the signature, wouldn't it make more sense to add the rest to Prepare like:

• Create a ~/sign script instead of ./sign, and grant it permissions
• Import the GPG_KEY only once (I believe the GPG ring will be the same in both run: sections and the second time it'll complain it was already imported)

And on the signing run: sections:

• Execution would be ~/sign *.rpm

This way there'd be less duplicity of code but still 2 independent stages.

[FedeDP]

@vjjmiras should be ok now, right?
Thanks for the suggestion!!

[vjjmiras]

LGTM

[FedeDP]

/hold

[FedeDP]

/unhold

[leogr]

/milestone 0.32.1

/approve

[poiana]

LGTM label has been added.

Git tree hash: 82dd4c78c548cf74ab56456acf675ffaa481db05

[jasondellaluce]

/approve

[poiana]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: FedeDP, jasondellaluce, leogr

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• .circleci/OWNERS [jasondellaluce,leogr]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[vjjmiras]

We forgot to change the location of the ~/sign file when creating it.
I opened a new PR to fix it (and I hope it also cleans up the code a bit).