fix: inject aliased snaps into build environment
Metadata
Current evaluation
Merged PR #467 (77a3582b) injects snaps under their aliased names, fixing #411 and the Snapcraft #4683 reproducer.
Resolution: closed resolved
Reason: PR #467 was merged as commit 77a3582b and changed snap injection to use aliased names. The fix was tested against the reproducer in Snapcraft #4683.
Evaluated by: mr-cal-bot
No scores available.
Issue body
- [x] Have you followed the guidelines for contributing?
- [x] Have you signed the [CLA](http://www.ubuntu.com/legal/contributors/)?
- [x] Have you successfully run `tox`?
-----
Inject snaps into the build environment using their aliased name.
I tested and confirmed this works with the reproducer in https://github.com/canonical/snapcraft/issues/4683.
However, I tested with a locally built snap, so it had no assertions. The secondary failure in craft-providers with [`snap ack`](https://github.com/canonical/snapcraft/issues/4683#issuecomment-2344242230) will probably start occurring when testing with a signed snap from the store.
The craft-providers fix is probably changing [this line](https://github.com/canonical/craft-providers/blob/262978901d49e5c16668d8f0bc251b185837cee9/craft_providers/actions/snap_installer.py#L262) to `snap_name.split('_')[0]`.
Fixes #411
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Merged PR #467 (77a3582b) injects snaps under their aliased names, fixing #411 and the Snapcraft #4683 reproducer. | |
| stealth/space-bunny-alpha | — | closed resolved | Merged PR canonical/craft-application#467 (77a3582b) installs injected snaps under their aliased names, fixing #411 and addressing the snapcraft#4683 reproducer. | |
| qwen/qwen3.6-35b-a3b | — | — | Merged fix to inject aliased snaps into the build environment, resolving issue #411. Snaps are now referenced by their alias during setup. A related craft-providers update is noted for handling signed snaps with snap ack. |
Update history
No update history recorded yet.
Related work
-
Likely Fixed By:
canonical/craft-application#411
(confidence 100%)
PR #467 explicitly states that it fixes issue #411.
-
Related To:
canonical/snapcraft#4683
(confidence 95%)
The PR author tested the alias-injection change against this Snapcraft reproducer.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #670 fix: get assertions for aliased snaps | craft-providers | merged | Merged PR #670 fixed aliased-snap assertion retrieval by querying snapd with the canonical snap name; the fix is in commit 4fbc046 and resolves #622. | |
| #671 fix: get assertions for aliased snaps | craft-providers | merged | Merged PR #671 fixed declaration-assertion lookup for aliased snaps by using the snap name. It resolves #622 and is the 1.20 counterpart of #670. | |
| #1064 fix: skip injecting snaps from host when cross-building | craft-application | closed | Closed as redundant after the same cross-build snap-injection fix merged in canonical/craft-application#1037 via commit 16bd7ac3. | |
| #4683 Cannot use parallel installations of snapcraft if a non-aliased version is not installed | snapcraft | closed | Fixed by merged PR #5085 (main) and backported via #5087 to hotfix/7.5 (7.5.7); craft-providers now inject the aliased snapcraft snap correctly. Upstream bug tracked in craft-application#411. | |
| #5085 fix: allow parallel installations of signed snapcraft snaps | snapcraft | merged | Merged PR #5085 fixed parallel installation of signed Snapcraft snaps, resolving #4683 and #4927; #5087 backported the fix to hotfix/7.5. |