package-repositories assumes architecture
Metadata
Current evaluation
snapcraft 7.1.3 incorrectly assumes architecture in package-repositories, hardcoding it in generated .sources files instead of omitting the field when not specified.
Suggested action: needs triage
Reason: The issue has no labels, no maintainer comments, and is 1457 days old (~4 years). Without maintainer assessment or evidence that the behavior has been fixed or changed in newer snapcraft versions, it needs triage to determine current relevance. The issue is a legitimate bug report (not support), but its age and the project's likely evolution make it uncertain whether it still applies.
Impact:
50
Quick Win:
35.0
Staleness:
90
Complexity:
30
Confidence:
50
Support Request:
20
Issue body
snapcraft: 7.1.3
base: core20
snapcraft.yaml:
package-repositories:
- type: apt
ppa: snappy-dev/image
This results in:
snapcraft-ppa-snappy-dev_image.sources with the following content:
Types: deb
URIs: http://ppa.launchpad.net/snappy-dev/image/ubuntu
Suites: focal
Components: main
Architectures: arm64
If "architectures" was not specified in "package-repositories", snapcraft should not assume it, and omit "Architectures" in the generated source file.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen3.6-35b-a3b-mtp-q6 |
Impact:
50
Quick Win:
35.0
Staleness:
90
Complexity:
30
Confidence:
50
Support Request:
20
|
needs triage | snapcraft 7.1.3 incorrectly assumes architecture in package-repositories, hardcoding it in generated .sources files instead of omitting the field when not specified. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
20
Confidence:
85
Support Request:
10
|
close stale | snapcraft 7.1.3 explicitly sets Architecture in generated apt sources files for PPAs even when unspecified, preventing multi-arch builds. Unlabelled, no maintainer response, inactive for ~4 years. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
45
Confidence:
85
Support Request:
15
|
close stale | Reports snapcraft 7.1.3 automatically assumes an architecture when generating apt source files from package-repositories, even when unspecified. No maintainer response in nearly 4 years. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
20
Confidence:
85
Support Request:
10
|
close stale | snapcraft 7.1.3 automatically adds an Architectures field to generated apt source files when package-repositories lacks an explicit architecture, contrary to expected behavior. Untriaged, inactive for nearly four years. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
25
Confidence:
85
Support Request:
15
|
needs triage | Unlabelled issue reporting that snapcraft's package-repositories directive incorrectly assumes an architecture in generated APT sources. Open for 3.5 years with no maintainer interaction or comments. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #4289 dpkg --add-architecture fails when using package-repositories | snapcraft | closed | Fixed in Snapcraft candidate channel. --root was incorrectly placed before --add-architecture. Maintainers confirmed the argument order bug and directed users to the candidate channel for the fix, pending release after other architecture issues resolve. |