filter unwanted pkgs in snap creation when relying on content interface
Metadata
Current evaluation
Fixed by merged Snapcraft PR #989 (54aa0ec1b), adding no-system-libraries so parts can skip migrating system libraries into the snap.
Resolution: closed resolved
Reason: Snapcraft PR #989 was merged as commit 54aa0ec1b, adding the no-system-libraries build attribute to skip system-library migration during prime. It directly fixes LP #1639831.
Evaluated by: mr-cal-bot
No scores available.
Issue body
Recently we've pulled out mir-libs into it's own snap so that servers and clients can rely on them via the content interface.
This works as expected, however we did notice that the snap process is still pulling in mir libraries into the client and server snaps even though they are not needed.
It would be great if there was a way to filter these out of the snap to avoid confusion as to which libs are being used and reduce footprint.
As a demonstration of the undesired situation, follow:
https://developer.ubuntu.com/en/snappy/guides/mir-snaps/
Then on the device navigate to /snap/mir-kiosk/current/usr/lib/x86.../
and you will notice libmir* libraries there.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Fixed by merged Snapcraft PR #989 (54aa0ec1b), adding no-system-libraries so parts can skip migrating system libraries into the snap. | |
| stealth/space-bunny-alpha | — | closed resolved | Resolved by snapcraft PR #989 (commit 54aa0ec1), which added a build-attribute `no-system-libraries` allowing parts to skip ldd system-library migration, so snaps relying on content interfaces stop pulling in mir libs. | |
| stealth/space-bunny-alpha | — | closed stale | Closed without resolution after years of inactivity; filtering content-interface mir-libs from client and server snaps remained unimplemented (Launchpad snapcraft bug 1639831). | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution. The request to filter unwanted mir-libs from snap creation via the content interface was abandoned after no comments or fixes were implemented. | |
| qwen/qwen3.6-35b-a3b | — | — | Abandoned. The request to filter unwanted mir-libs from snap creation when using the content interface was closed without resolution, leaving the packaging behavior unchanged. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution. The request to filter unused mir-libs from snapcraft builds when using the content interface was abandoned due to inactivity. No fix or workaround was implemented. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Abandoned. The request to filter unwanted mir-libs from snap creation during content interface usage was closed without resolution or comments after years of inactivity. |
Update history
| Date | Change |
|---|---|
| created |
Related work
-
Likely Fixed By:
canonical/snapcraft#989
(confidence 100%)
Merged PR adding the option and explicitly linked as the fix.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1643887 snapcraft shouldn't hardcode the list of libs to strip | snapcraft (launchpad) | closed | Resolved by PR #1234 (commit a7a5a2eae): Snapcraft derives strip exclusions from the selected base snap instead of hardcoding libraries. |