using an invalid architecture in stage-packages causes a mess
Metadata
Current evaluation
Closed. The issue was abandoned due to lack of comments or resolution details.
Suggested action: —
No scores available.
Issue body
Adding a stage package like this one:
stage-packages: ['hello:invalid']
results in the following suggestion:
You may need to add support for this architecture with 'dpkg --add-architecture invalid'.
If you actually go ahead an run that command, dpkg will not complain about the invalid architecture, which leaves you with invalid apt sources. You won't be able to run apt update, and thus you won't be able to run snapcraft.
I think we should only suggest to add the architecture if it is a valid one.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Closed. The issue was abandoned due to lack of comments or resolution details. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
15
Confidence:
85
Support Request:
5
|
close stale | Snapcraft suggests running dpkg --add-architecture for invalid stage-package architectures, breaking apt. Unlabeled, zero comments, inactive for over 9 years. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
10
Confidence:
85
Support Request:
5
|
close stale | Specifying an invalid architecture in stage-packages triggers a dpkg suggestion that breaks apt sources. Unlabeled, zero comments, inactive for ~9 years. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
98
Complexity:
20
Confidence:
85
Support Request:
5
|
close stale | Issue reports that suggesting dpkg --add-architecture for invalid stage-packages architectures corrupts apt sources. No maintainer response or activity in over 9 years. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
98
Complexity:
20
Confidence:
85
Support Request:
10
|
close stale | Using invalid architectures in stage-packages triggers a dpkg suggestion that corrupts apt sources and breaks snapcraft. Validate architectures before suggesting dpkg commands. Issue is open, unassigned, and awaiting triage. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1686481 stage-packages does not handle unmet dependencies | snapcraft (launchpad) | closed | stage-packages ignored target architectures, downloading dependencies for the build host instead. Closed without comments or resolution after 288 days, effectively abandoned. | |
| #1655797 Set arch for stage packages | snapcraft (launchpad) | closed | Closed without resolution. Snapcraft rejected architecture qualifiers in stage-packages, causing download failures. With zero comments and no fix, the report was abandoned. | |
| #1637282 Allow for architecture-specific stage packages | snapcraft (launchpad) | closed | The request for architecture-specific or optional stage packages was abandoned. No implementation or resolution was provided, and the issue closed after over nine years without activity. | |
| #1664141 Set arch for build-packages | snapcraft (launchpad) | closed | Closed without implementation or comments, indicating the architecture support feature request was abandoned or superseded. | |
| #4542 When cross-compiling incorrect architecture `stage-packages` are fetched | snapcraft | closed | Closed without resolution. Internal ticket CRAFT-2620 tracks the bug where cross-compilation fetches host architecture stage-packages instead of the target. Manual repository configuration and explicit architecture variables work around it. | |
| #1767 stage-packages does not respect architectures | snapcraft | closed | Superseded by PR #1788, which addresses related functionality but does not fully resolve the architecture handling bug. The core issue remains unfixed and requires a dedicated follow-up report. |