← Back to issue list

Local key assets are not used in package-repositories for core24

View original Github issue

Metadata

Project
snapcraft
Number
#4743
Type
issue
State
closed
Author
tigarmo
Labels
—
Created
Updated
Closed

Current evaluation

Fixed in merged PR #4758 (commit b8ff64b89), enabling core24 package repositories to use local signing keys instead of only a keyserver.

Resolution: closed resolved

Reason: The maintainer comment states “Fixed via #4758.” PR #4758 was merged as commit b8ff64b89 into hotfix/8.2, changing core24 package repositories to use local keys.

Evaluated by: mr-cal-bot

No scores available.

Issue body

### Bug Description Local key assets are not used in package-repositories for core24 (only the keyserver is supported) ### To Reproduce . ### Environment . ### snapcraft.yaml ```shell . ``` ### Relevant log output ```shell . ``` ### Additional context _No response_

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha — closed resolved Fixed in merged PR #4758 (commit b8ff64b89), enabling core24 package repositories to use local signing keys instead of only a keyserver.
stealth/space-bunny-alpha — closed resolved Fixed in merged PR #4758 (commit b8ff64b89), enabling core24 package repositories to use local signing keys instead of relying only on a keyserver.
stealth/space-bunny-alpha — closed resolved Fixed core24 package-repositories to use local signing keys by merging PR #4758 as commit b8ff64b89.
stealth/space-bunny-alpha — closed resolved Fixed by merged PR #4758 (commit b8ff64b89), making core24 package repositories use local signing keys.
qwen/qwen3.6-35b-a3b — — Resolved the bug where local key assets were ignored for core24 package-repositories. Fixed via pull request #4758 and closed.
qwen/qwen3.6-35b-a3b — — Resolved the bug where local key assets were ignored for core24 package-repositories. The fix was merged via pull request #4758.
qwen/qwen3.6-35b-a3b — — Fixed via PR #4758. Local key assets are now properly utilized in package-repositories for core24, replacing the previous keyserver-only limitation.
qwen3.6-35b-a3b-mtp-q6 — — Fixed local key assets not being used in package-repositories for core24. Resolved via merged pull request #4758.

Update history

No update history recorded yet.

Related work

  • Likely Fixed By: snapcraft#4758 (confidence 100%)

    Merged fix titled “use local keys for package-repos in core24,” commit b8ff64b89.

Related issues

Issue Project State Summary Similarity
#4758 fix: use local keys for package-repos in core24 snapcraft merged Merged PR #4758 (commit b8ff64b89) into hotfix/8.2, making core24 package-repositories use local signing keys; fixes issue #4743 where local key assets were ignored.
86%
#313 Support local key assets for package-repositories craft-application open Feature request to support local key assets (e.g. snap/keys) in package-repositories instead of hardcoding /dev/null. Resolved by merged PR #317 (071ad272), which added a local_keys_path parameter and an overridable _get_local_keys_path() hook.
73%
#4740 `package-repositories` fail with the core24 base due to missing packages snapcraft closed Fixed in merged PR #4754 (commit 712626448) and released in Snapcraft 8.2.1: core24 remote builds now install GPG/dirmngr before configuring package repositories.
71%