Automatically use source package's architectures in non-native mode
Metadata
Current evaluation
Feature request for debcraft non-native mode to read debian/control to determine target architectures instead of defaulting to all standard platforms. Open, unlabelled, no maintainer comments, inactive for 179 days.
Suggested action: needs triage
Reason: The issue is a well-scoped feature request from a maintainer (lengau) but has no labels, no comments, and no assignee, showing no sign of triage. The default platforms logic in debcraft/services/project.py (_app_render_legacy_platforms) still hardcodes all DebianArchitecture values, so the requested behavior is not implemented. Related commit f33e349 (#94) tightened default platforms but did not add control-file-based architecture detection.
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.8-27b |
Impact:
50
Quick Win:
22.5
Staleness:
65
Complexity:
55
Confidence:
70
Support Request:
0
|
needs triage | Feature request for debcraft non-native mode to read debian/control to determine target architectures instead of defaulting to all standard platforms. Open, unlabelled, no maintainer comments, inactive for 179 days. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
65
Complexity:
40
Confidence:
85
Support Request:
5
|
needs triage | Feature request to make non-native mode read debian/control for target architectures instead of defaulting to standard platforms. Currently unlabelled and inactive for 138 days. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
55
Complexity:
40
Confidence:
85
Support Request:
10
|
needs triage | Feature request to make non-native mode automatically detect target architectures from debian/control instead of defaulting to standard platforms. Currently unaddressed with no labels or comments. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
45
Complexity:
40
Confidence:
85
Support Request:
15
|
needs triage | Non-native mode ignores source package architectures, defaulting to standard platforms. Suggests reading debian/control for automatic detection, handling any/all cases. Open, zero comments, awaiting triage or assignment. |
Update history
No update history recorded yet.
Related work
-
Related To:
canonical/debcraft#94
(confidence 60%)
PR #94 changed default platform generation to stricter defaults, touching the same code path (_app_render_legacy_platforms) but did not implement control-file-based architecture selection.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1036 Allow grammar for `package-repositories` | rockcraft | open | Feature request to allow architecture-conditional URLs in package-repositories (e.g. amd64 vs arm64) so deb-src builds work across architectures. Open 283 days, no labels, no comments, no maintainer response. | |
| #1827067 need a way to add foreign architecture to sources.list for build-packages/stage-packages | snapcraft (launchpad) | open | Feature request (2018) to auto-add foreign-arch lines to sources.list so build-packages/stage-packages like foo:armhf install in LP chroots. Now addressable via the package-repositories feature (per-arch apt repos); issue unlabelled, 0 comments, inactive ~3 years. | |
| #5632 [Feature Request]: Different source for different architectures | snapcraft | closed | Resolved via maintainer workaround using the $CRAFT_ARCH_BUILD_FOR variable in the source path to dynamically select architecture-specific deb files. The author accepted the solution, and the issue was closed. |