packages.arasaka.software is published from its own repository; the release only signs the rpm

thepra/packages.arasaka.software now reads this repository's releases and publishes
them with every other joined app, so the daily packages and F-Droid jobs, their
scripts and the repository's F-Droid settings leave this repository. The release
still signs the rpm on its own page with the Arasaka key, as the README promises,
and the F-Droid listing stays in packaging/fdroid/metadata, read at each tag.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

.gitea/workflows/release.yml

@@ -43,21 +43,14 @@ jobs:
           MEWEB_KEYSTORE_PASS: ${{ secrets.MEWEB_KEYSTORE_PASS }}
         run: .gitea/scripts/android.sh
 
-      - name: The deb and rpm on packages.arasaka.software, the rpm signed
+      - name: The rpm signed with the Arasaka packages key
         if: ${{ github.ref_type == 'tag' }}
         env:
           PACKAGES_SIGNING_KEY: ${{ secrets.PACKAGES_SIGNING_KEY }}
-        run: .gitea/scripts/packages.sh "$VERSION"
+        run: .gitea/scripts/sign-rpm.sh "$VERSION"
 
       - name: Publish the release
         if: ${{ github.ref_type == 'tag' || inputs.publish == 'true' }}
         env:
           RELEASE_TOKEN: ${{ secrets.GITEA_TOKEN }}
         run: .gitea/scripts/release.sh "v$VERSION" releases/"$VERSION"/*
-
-      - name: The APK in the F-Droid repository on packages.arasaka.software
-        if: ${{ github.ref_type == 'tag' }}
-        env:
-          MEWEB_KEYSTORE_B64: ${{ secrets.MEWEB_KEYSTORE_B64 }}
-          MEWEB_KEYSTORE_PASS: ${{ secrets.MEWEB_KEYSTORE_PASS }}
-        run: .gitea/scripts/fdroid.sh "$VERSION"