stage-snap causes issues when mixing cores
Metadata
Current evaluation
stage-snap staging a core16 snap into a core18 build overwrites the build environment and triggers file conflicts; reporter proposes a warning on core mismatch. No maintainer activity in ~6.8 years; core16/core18 are EOL.
Suggested action: close stale
Reason: The issue is 2503 days old with 0 comments, no labels, and no maintainer interaction, and the related Launchpad bug 1849707 confirms 'no maintainer activity in over six years.' The specific reproduction (mixing core16 into core18) targets base cores that are no longer supported, so the scenario is no longer reproducible in a current configuration. The file-conflict case is already surfaced by snapcraft with actionable hints (filesets/stage/snap/organize).
Impact:
35
Quick Win:
19.25
Staleness:
95
Complexity:
45
Confidence:
65
Support Request:
25
Issue body
I came across this issue whilst trying to stage a core16 snap into a core18.
It seems that, when mixing these cores, your build environment (during snapcraft build) is overwritten by the unpacking of the incoming stage snap. This obviously breaks build packages that you have. E.g. this yaml https://www.irccloud.com/pastebin/mxelP3CN/ gives errors like:
```
Fatal Python error: Py_Initialize: Unable to get the locale encoding
ImportError: No module named 'encodings'
```
```
fatal: unable to find remote helper for 'https
```
Even if you put this stage snap to the bottom of the build process, you will end up with an error like:
```
Failed to stage: Parts 'aws-cli' and 'docker' have the following files, but with different contents:
etc/mime.types
lib/x86_64-linux-gnu/libexpat.so.1
usr/bin/pdb3
usr/bin/py3clean
usr/bin/py3compile
usr/bin/pydoc3
usr/bin/pygettext3
usr/bin/python3
usr/bin/python3m
usr/bin/run-mailcap
usr/lib/valgrind/python3.supp
usr/lib/x86_64-linux-gnu/libexpatw.so.1
usr/lib/x86_64-linux-gnu/libffi.so.6.0.4
usr/lib/x86_64-linux-gnu/libmpdec.so.2.4.2
usr/lib/x86_64-linux-gnu/libsqlite3.so.0.8.6
usr/share/doc/libexpat1/changelog.Debian.gz
usr/share/doc/libexpat1/copyright
usr/share/doc/libffi6/changelog.Debian.gz
usr/share/doc/libmpdec2/changelog.Debian.gz
usr/share/doc/libpython3-stdlib/README.Debian
usr/share/doc/libpython3-stdlib/changelog.Debian.gz
usr/share/doc/libsqlite3-0/changelog.Debian.gz
usr/share/doc/mime-support/changelog.gz
usr/share/doc/python3-minimal/README.Debian
usr/share/doc/python3-minimal/changelog.Debian.gz
usr/share/man/man1/pdb3.1.gz
usr/share/man/man1/pydoc3.1.gz
usr/share/man/man1/pygettext3.1.gz
usr/share/man/man1/python3.1.gz
usr/share/man/man1/python3m.1.gz
usr/share/man/man1/run-mailcap.1.gz
usr/share/pixmaps/python3.xpm
usr/share/python3/debian_defaults
usr/share/python3/debpython/version.py
usr/share/python3/py3versions.py
Snapcraft offers some capabilities to solve this by use of the following keywords:
- `filesets`
- `stage`
- `snap`
- `organize`
To learn more about these part keywords, run `snapcraft help plugins`.
```
I propose that snapcraft gives a warning when pulling in the snap to be staged if the cores mismatch.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.8-27b |
Impact:
35
Quick Win:
19.25
Staleness:
95
Complexity:
45
Confidence:
65
Support Request:
25
|
close stale | stage-snap staging a core16 snap into a core18 build overwrites the build environment and triggers file conflicts; reporter proposes a warning on core mismatch. No maintainer activity in ~6.8 years; core16/core18 are EOL. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
40
Confidence:
90
Support Request:
25
|
close stale | Build environment corruption and file conflicts occur when staging core16 into core18 snaps. Reporter proposes a warning for core mismatches. No maintainer activity in over six years. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
35
Confidence:
90
Support Request:
10
|
close stale | Snapcraft stage-snap fails when mixing core16 and core18 bases due to environment overwrites and file conflicts. Author suggests adding a warning for core mismatches. Unaddressed for over 6 years. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
98
Complexity:
35
Confidence:
90
Support Request:
20
|
close stale | Reported build environment conflicts and file collisions when staging core16 snaps into core18 environments in snapcraft. No maintainer response or labels after over six years. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
98
Complexity:
45
Confidence:
90
Support Request:
10
|
close stale | Reports build environment corruption and file conflicts when staging core16 into core18 snaps. No maintainer response, no labels, inactive for over 6 years. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1987853 snapcraft terminates override-build script prematurely without error | snapcraft (launchpad) | open | Snapcraft prematurely terminates override-build scripts after core18 to core20 upgrade, with no error output. Untriaged and inactive for over 4 years. |