Having a "snap" directory with actual content causes build failures
Metadata
Current evaluation
⚠️ This summary may be outdated — the issue content or evaluation prompts have changed since this evaluation was made.
Closed without resolution or linked pull request. The proposed fix to allow alternative snap directories and update ignore rules was never implemented, indicating the issue was abandoned due to inactivity.
Suggested action: —
No scores available.
Issue body
We are currently working on the "snapd" snap.
One roadblock we discovered is that it seems like the "snap" directory is always considered to be "owned" exclusively by snapcraft. For our codebase which contains a "snap" directory with actual content (go code).
This is problematic as the pull stage will exclude the "snap" directory in internal/source/_local.py:ignore() which means the export of our source tree is incomplete. The build tree is also using a (different) ignore in pluginhandlers/__init__.py:build() which will also need updating.
One simple fix would be to allow ".snap" in addition to "snap" for putting custom plugins (which we use in the snapd snap) and if that dir exists ignore the "snap" dir.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution or linked pull request. The proposed fix to allow alternative snap directories and update ignore rules was never implemented, indicating the issue was abandoned due to inactivity. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution or comments. The proposed workaround to use a .snap directory was not implemented, and the issue appears abandoned due to prolonged inactivity. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed without resolution. The reported conflict between source directories and snapcraft's ignore rules was abandoned. No fix or alternative implementation was merged. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1660890 An empty snap directory ends up in the snap | snapcraft (launchpad) | closed | Reported unintended inclusion of the snap directory in the build output. Closed without comments or resolution, indicating the report was abandoned. | |
| #564 fix(snap): use snap bin paths if in a snap | craft-parts | closed | Addresses snap binary path resolution for snap environments. Closed without merging due to two unresolved review comments and over 300 days of inactivity, effectively abandoned. | |
| #5841 Include "build snapd snap" test in test suite | snapcraft | closed | Closed without implementation or linked resolution. The requested build test was not added, indicating the issue was abandoned or superseded by alternative testing measures. | |
| #1650686 Some symlinks not properly fixed up | snapcraft (launchpad) | closed | Abandoned. Closed without comments or resolution. The snapcraft build failure caused by unpatched absolute symlinks remains unresolved, with no fix implemented. | |
| #1558965 Snap building fails due to missing include directory | snapcraft (launchpad) | closed | Closed without documented fix. Snapcraft 2.4 failed builds by statically referencing non-existent include directories, requiring manual creation to bypass. | |
| #1791368 Warn when unexpected things are in the snap dir | snapcraft (launchpad) | closed | Closed without implementation. The request to warn on unexpected files in the snap/ directory was abandoned due to prolonged inactivity and no associated pull request. | |
| #1792203 Add support for snap/local directory | snapcraft (launchpad) | closed | Support for a snap/local directory was closed without implementation. With zero comments and nearly eight years of inactivity, the request was abandoned. |