Repository navigation
fix(mod-store): rename zima_cron entry to cron (install returns 404) - #20
Open
chicohaager wants to merge 1 commit into
Open
chicohaager wants to merge 1 commit into
chicohaager wants to merge 1 commit into
Conversation
zpkg fetches <name>.raw from the latest release of a repo entry. The module ships as cron.raw with extension-release.cron (already in v0.2.0), so the entry zima_cron resolves to releases/latest/download/zima_cron.raw -> 404 and 'zpkg install zima_cron' fails with 'bad response code: 404' (measured on ZimaOS v1.8.0-beta1). Under the name cron the same repo installs cleanly (sha256 matches the release's cron.raw.sha256). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
zpkg install zima_cronfails on ZimaOS v1.8.0-beta1:For a
repoentry, zpkg downloads<name>.rawfrom the latest release. The module ships ascron.rawand its image carriesextension-release.cron(already in v0.2.0), so the entryzima_cronresolves to a file that does not exist:curl -L)https://github.com/chicohaager/cron/releases/latest/download/zima_cron.rawhttps://github.com/chicohaager/cron/releases/latest/download/cron.rawFix
Rename the entry to
cron(name and title). The same repository listed under"name": "cron"in a second catalogue (modstore =inmod-management.conf) installs cleanly on v1.8.0-beta1:install success, the SHA-256 of the downloaded image equals the release'scron.raw.sha256, and the service starts.Adding a
zima_cron.rawasset instead would not work, because the file name must match theextension-releasename inside the image. Existing installations already carry the module namecron, so nothing installed is renamed by this change.🤖 Generated with Claude Code