Include usability/volume fixes and add AUR release automation#6
Include usability/volume fixes and add AUR release automation#6
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: a34ef949c7
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
OneNoted
changed the title
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 4f38c27ab6
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| install -Dm644 LICENSE "$stage_dir/$archive_root/LICENSE" | ||
|
|
||
| tar -C "$stage_dir" -czf "$archive_path" "$archive_root" | ||
| sha256sum "$archive_path" > "$checksum_path" |
There was a problem hiding this comment.
Computing the checksum with sha256sum "$archive_path" records the runner’s absolute path inside the published .sha256 file. That makes sha256sum -c fail for users who download the release assets, because the embedded path (for example under /home/runner/...) does not exist on their machine. Generate the checksum using the archive basename (or from within output_dir) so the checksum file can be verified locally.
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 20d7c2ef24
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 3189475f28
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| "${repo_root}/scripts/aur/generate_srcinfo.sh" "$PWD/PKGBUILD" > .SRCINFO | ||
| git config user.name "$packager_name" | ||
| git config user.email "$packager_email" | ||
| git add PKGBUILD .SRCINFO *.install |
There was a problem hiding this comment.
rsync --delete mirrors the entire package directory into the temp repo, but the subsequent git add PKGBUILD .SRCINFO *.install only stages a narrow subset of paths. If packaging later adds/removes any other tracked artifact (for example patch files or helper sources referenced by source=()), those changes are left unstaged, so the pushed AUR repo can become stale and diverge from the mirrored content.
Useful? React with 👍 / 👎.
1 participant
Summary
orators,oratorsctl,oratorsd, and the packaged user service unitorators-binandorators-gitAUR package sources, install messaging, maintainer docs, and AUR sync automationWhy
We want Orators to be installable from the AUR with a stable
-binpackage driven by GitHub tagged releases and a-gitpackage that tracks the latest GitHub branch state, while also carrying forward the outstanding usability and volume fixes that were still only local.Commit order
feat: improve tui usabilityfix: investigate volume reset to zerochore: add GitHub release bundlingchore: add AUR package definitionschore: automate AUR publishingfix: address AUR review feedbackfix: address CI and review follow-upfix: trigger aur-git sync on srcinfo changesfix: stage all AUR package filesReview and CI follow-up
orators-gitno longer usescargo build --frozen, so first-time AUR builds can fetch crates from the lockfile in a clean environmentscripts/release/build-release-archive.shnow passes the requested--targetthrough to Cargo and stages binaries from the matching target directory.sha256files are portable to end-user machines./scripts/validate_packaging.shnow checks both target propagation and checksum portability, and it uses plaingrepinstead of requiringrgon the CI runner.github/workflows/aur-git.ymlnow also triggers whenscripts/aur/generate_srcinfo.shchanges, so.SRCINFOgeneration fixes propagate to the AUR automation without a manual workflow runscripts/aur/publish_aur_package.shnow stages the full mirrored AUR repository state withgit add -A, so future helper files, patch files, and deletions cannot drift out of sync with the rsynced package directoryUser impact
orators-binfrom release artifacts ororators-gitfrom source/usr/lib/systemd/user/oratorsd.serviceunit over writing a user unit by defaultorators-binautomatically once the repository AUR SSH key secret is configuredNotes
bluez-alsa-git, because that is the BlueALSA package currently available in the AURmasterif the AUR git repo does not exist yetValidation
cargo test --workspacecargo clippy --workspace --all-targets -- -D warnings./scripts/validate_packaging.sh