Skip to content

opus-tools: Update to version 0.2-52-g5f894e9, switch source to rarewares.org - #8428

Closed
reaseno wants to merge 1 commit into
ScoopInstaller:masterfrom
reaseno:master
Closed

opus-tools: Update to version 0.2-52-g5f894e9, switch source to rarewares.org#8428
reaseno wants to merge 1 commit into
ScoopInstaller:masterfrom
reaseno:master

Conversation

@reaseno

@reaseno reaseno commented Aug 22, 2026

Copy link
Copy Markdown

Summary

  • The previous download source (archive.mozilla.org) no longer receives opus-tools updates
  • Switched to rarewares.org, which publishes current builds
  • Updated to version 0.2-52-g5f894e9 (libopus 1.6.1-11-g788cc89) with fresh hashes
  • Adjusted checkver/autoupdate to match rarewares' filename scheme via named capture groups

Test plan

  • Verified both 64bit and 32bit URLs download valid zip archives
  • Recomputed and confirmed sha256 hashes for both architectures

@coderabbitai

coderabbitai Bot commented Aug 22, 2026

Copy link
Copy Markdown

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: cda4eb53-2566-437b-88c2-f222be1508b5

📥 Commits

Reviewing files that changed from the base of the PR and between ef3713c and c835959.

📒 Files selected for processing (1)
  • bucket/opus-tools.json

Included review availability: Your plan provides up to 4 included reviews per hour; 3 remain after this review.


Summary by CodeRabbit

  • Chores
    • Updated opus-tools to a newer release.
    • Refreshed download sources and package checksums for 32-bit and 64-bit packages.
    • Improved version detection and automatic update URL generation.

Walkthrough

Changes

The opus-tools manifest now uses version 0.2-52-g5f894e9 and Rarewares-hosted 64-bit and 32-bit packages. Version checking captures the package and libopus versions, and autoupdate generates URLs from both values.

opus-tools source update

Layer / File(s) Summary
Rarewares package metadata
bucket/opus-tools.json
The manifest updates the package version, architecture-specific download URLs, and SHA-256 hashes.
Rarewares update automation
bucket/opus-tools.json
checkver scrapes Rarewares and captures the package and libopus versions. autoupdate uses these values to generate 64-bit and 32-bit package URLs.
🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Title check ✅ Passed The title clearly identifies the manifest, version update, and source change.
Description check ✅ Passed The description explains the source change, version update, manifest adjustments, and verification steps.

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@z-Fng z-Fng changed the title opus-tools: switch source to rarewares.org opus-tools: Switch source to rarewares.org Aug 23, 2026
@z-Fng z-Fng changed the title opus-tools: Switch source to rarewares.org opus-tools: Update to version 0.2-52-g5f894e9, switch source to rarewares.org Aug 23, 2026
@z-Fng

z-Fng commented Aug 23, 2026

Copy link
Copy Markdown
Contributor
  • The previous download source (archive.mozilla.org) no longer receives opus-tools updates
  • Switched to rarewares.org, which publishes current builds

From what I can tell, rarewares.org provides third-party community builds rather than official releases. Switching an existing manifest to a third-party distributor just to bump the version breaks the trust chain.

Unless there is a strong reason or clear verification of the build pipeline, we should probably stick to the official upstream binaries. If you'd like to support this build, it might be better to maintain a separate opus-tools-rarewares manifest in your personal bucket instead.

See also: https://scoop.sh/#/apps?q=rarewares&o=false&p=1

@z-Fng z-Fng closed this Aug 23, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants