Repository navigation
Conversation
Adds an apt-repo job to the release workflow that collects the .deb installers (amd64 + arm64), builds a standard Debian archive layout (pool/ + dists/stable with Packages, Packages.gz, Release), signs it (Release.gpg + InRelease) with a GPG key from the APT_REPO_GPG_PRIVATE_KEY and APT_REPO_GPG_PASSPHRASE secrets, exports the public key as jmonkeyengine-repo.asc and deploys everything to GitHub Pages. Users can then install and update the SDK with the commands documented in readme.md. One-time setup required: enable GitHub Pages (source: GitHub Actions) and create the two secrets. Relates to jMonkeyEngine#449 Co-authored-by: neph1 <neph1@users.noreply.github.com>
| echo ">> Architectures: $archs" | ||
|
|
||
| for arch in $archs; do | ||
| arch_dir="$out_dir/dists/$suite/$component/binary-$arch" |
There was a problem hiding this comment.
Looks great! Using an APT repository is a fantastic improvement for Debian/Ubuntu users.
One quick question regarding installers/publish-apt-repo.sh: Is there a reason you chose stable as the suite name? Often, it's common to use stable or main depending on the project's release model, but I wanted to make sure this aligns with the team's plans for distribution. Also, have you verified if the repository path handles potential future versions (e.g., testing, unstable) gracefully, or are we intentionally keeping it simple for now?
There was a problem hiding this comment.
I think it makes sense to only release stable versions to apt. We mostly do stable releases, anyway.
There was a problem hiding this comment.
That makes total sense! Keeping it focused on stable releases is super clean and fits the workflow well. Thanks for clarifying!
jaime-jmebot
left a comment
There was a problem hiding this comment.
- Added a signed APT repository publishing workflow and GitHub Pages deployment.
- Provided clear installation documentation for Debian/Ubuntu users.
- Verified packaging layout and script mechanics.
jaime-jmebot
left a comment
There was a problem hiding this comment.
I have replied to neph1's comment on the PR discussion thread.
Summary
Adds the "future step" from #449: distribute the SDK as a real APT repository so Debian/Ubuntu users can
sudo apt install jmonkeyengine-sdkand get updates viaapt upgrade.installers/publish-apt-repo.sh— collects the.debfiles fromdist/installers, builds a standard Debian archive layout (pool/main,dists/stable/main/binary-<arch>/Packages[.gz],Release), signs it (Release.gpg+InRelease) with a GPG key provided via secrets, exports the public key asjmonkeyengine-repo.asc, and stages everything for Pages..github/actions/publish-apt-repo/action.yml— composite action: installsdpkg-dev/apt-utils, downloads theinstallers-Linux-*artifacts, runs the script withAPT_REPO_GPG_PRIVATE_KEY/APT_REPO_GPG_PASSPHRASEsecrets, uploads the repo as an artifact, and deploys to GitHub Pages (configure-pages+upload-pages-artifact+deploy-pages)..github/workflows/release.yml— newapt-repojob (needspackage, environmentgithub-pages, permissionspages: write,id-token: write), running alongside the existing release job.readme.md— documents the 3-command install for end users.No changes to the .deb packages themselves are needed: they already bundle their own JRE, so there are no system dependencies to declare.
One-time setup required (maintainer)
gpg --quick-gen-key "jMonkeyEngine APT Repository <contact@jmonkeyengine.org>" rsa3072 sign 0and store the armored private key in theAPT_REPO_GPG_PRIVATE_KEYsecret and its passphrase inAPT_REPO_GPG_PASSPHRASE(repo secrets).After that, every tag push publishes/updates the repo at
https://jmonkeyengine.github.io/sdk.Verification
Tested locally in this sandbox with two dummy .debs (amd64 + arm64) and a throwaway GPG key:
installers/publish-apt-repo.shbuilds the full layout:pool/main/*.deb,dists/stable/main/binary-{amd64,arm64}/Packages{,.gz},dists/stable/{Release,Release.gpg,InRelease},jmonkeyengine-repo.asc.apt-get updateagainst the generated repo verifies theInReleasesignature and listsjmonkeyengine-sdk 3.10.0.beta2-1from the correct pool path;apt-get install --download-only jmonkeyengine-sdkfetches the .deb successfully.release.ymland the new action YAML parse cleanly.dpkg-scanpackageswas invoked with an absolute pool path, which leaked absolute paths into theFilename:fields; it now runs relative to the repo root soaptresolves packages correctly.Relates to #449