snapcraft does not respect filesets of remote parts
Metadata
Current evaluation
Closed without resolution. Snapcraft failed to resolve remote part filesets, causing build errors. Likely abandoned or superseded by newer versions. The wiki label indicates the workflow was clarified via documentation.
Suggested action: —
No scores available.
Issue body
Running snapcraft 2.16 on my xenial system and getting the following error while using the networkmanager remote part
[Errno 2] No such file or directory: '/root/stage/$rdepends'
Stopping snapcraft-partly-tough-sawfly
Command '['lxc', 'exec', 'snapcraft-partly-tough-sawfly', '--', 'snapcraft', 'snap', '--output', 'canonical-se-parts_1_amd64.snap']' returned non-zero exit status 1
The part networkmanager has the strucutre
parts:
networkmanager:
...
filesets:
rdepends:
..
snap:
- $rdepends
See https://git.launchpad.net/~snappy-hwe-team/snappy-hwe-snaps/+git/network-manager/tree/snapcraft.yaml for details.
Somehow it looks like the local part can't reuse the filesets or does not carry them from the original project the part links to.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution. Snapcraft failed to resolve remote part filesets, causing build errors. Likely abandoned or superseded by newer versions. The wiki label indicates the workflow was clarified via documentation. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution. Snapcraft failed to resolve filesets from remote parts, causing missing directory errors for variables like $rdepends. Likely abandoned or superseded by newer versions. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution. Snapcraft failed to resolve filesets from remote parts, triggering a missing directory error. Labeled wiki with zero comments, the report was abandoned or documented as a known limitation. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1660696 Snapcraft is testing file collisions on unbuilt parts | snapcraft (launchpad) | closed | Closed without a merged fix. Snapcraft incorrectly checked file collisions on unbuilt parts, causing file not found errors. The author verified a local workaround, but the report was closed without upstream resolution or discussion. | |
| #1816 snapcraft update won't fetch from `SNAPCRAFT_PARTS_URI` | snapcraft | closed | Closed without resolution or comments. Likely superseded by the linked Launchpad bug report. No fixes or code changes were applied. | |
| #1531481 snapcraft should setup search paths/flags for parts built after parts | snapcraft (launchpad) | closed | Closed without resolution. The request to auto-configure search paths for dependent parts was abandoned. Later snapcraft updates added native environment propagation and part dependency handling, rendering the feature obsolete. | |
| #1799925 snapcraft gives conflicting advice for cleaning parts | snapcraft (launchpad) | closed | Closed without a fix. Snapcraft incorrectly advised running snapcraft clean with part and step flags, which were unsupported. The author worked around it with a full clean. The report appears abandoned or superseded by later updates. | |
| #2020683 snapcraft remote-build cannot use a custom version of snapcraft | snapcraft (launchpad) | closed | Request to enable custom snapcraft versions in remote-build was closed without implementation. No resolution or merge details were provided, indicating the feature was abandoned. | |
| #1448 snapcraft build using manifest.yaml | snapcraft | closed | Closed without discussion or comments. The issue appears abandoned or superseded by newer snapcraft build workflows. No resolution or merge details were recorded. | |
| #1794497 Snapcraft can't re-use build VM if anything went wrong with the initial setup | snapcraft (launchpad) | closed | Closed and likely abandoned. Snapcraft lacks automatic recovery for failed VM setups, forcing manual cleanup. No resolution was provided, suggesting the issue was superseded by updated build environment handling. | |
| #1615060 snapcraft clean is incomplete | snapcraft (launchpad) | closed | Reporting that snapcraft clean skips local .snap files was closed without comments or resolution, indicating the report was abandoned or left unresolved. | |
| #1988858 snapcraft trying to install extra package causing conflict | snapcraft (launchpad) | closed | Closed without a tracked fix or comments. The author reported a build dependency conflict caused by snapcraft pulling extra packages. The issue appears abandoned or resolved by the author. | |
| #1659085 snapcraft needs to migrate to a snap directory | snapcraft (launchpad) | closed | Closed without resolution. The proposed migration of snapcraft to a snap directory, including build artifact relocation and plugin updates, was abandoned or superseded by subsequent architecture changes. |