← Back to issue list

Automatically use source package's architectures in non-native mode

View original Github issue

Metadata

Project
debcraft
Number
#93
Type
issue
State
open
Author
lengau
Labels
—
Created
Updated
Closed
—

Current evaluation

Non-native builds still default to every standard Debian architecture instead of deriving platforms from debian/control; the feature remains open, unlabeled, and without maintainer discussion.

Suggested action: needs triage

Reason: The issue has no labels or maintainer comments, so it has not been visibly triaged. The request is valid and clear: debcraft/services/project.py still enumerates every DebianArchitecture, debcraft/control.py only provides an encoder rather than a control parser, and commit f33e349 (#94) tightened the broad defaults without deriving them from debian/control.

Evaluated by: mr-cal-bot

Impact: 54 Quick Win: 20 Complexity: 57 Confidence: 92 Actionability: 84

Issue body

Currently non-native mode doesn't check the source package's control file to determine the platforms, instead just defaulting to the standard platforms that are roughly equivalent to `any`. In non-native mode we should refer to the `debian/control` file to figure out what platforms we need. As a note, the special cases of `any all` or `<arch> all` can be taken to simply mean `any` in the platforms key, since we will build those architecture-independent packages in any build (unless a package subset is declared).

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha
Impact: 54
Quick Win: 20
Complexity: 57
Confidence: 92
Actionability: 84
needs triage Non-native builds still default to every standard Debian architecture instead of deriving platforms from debian/control; the feature remains open, unlabeled, and without maintainer discussion.
qwen/qwen3.6-35b-a3b
Impact: 60
Quick Win: 29
Complexity: 40
Confidence: 70
Actionability: 80
needs triage Feature request to read architectures from debian/control in non-native mode instead of defaulting to standard platforms
qwen/qwen3.8-27b
Impact: 50
Quick Win: 22
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.

Update history

No update history recorded yet.

Related work

  • Related To: canonical/debcraft#94 (confidence 91%)

    The latest commit touching the default-platform logic is f33e349, titled "fix: generate stricter default platforms (#94)"; it leaves broad architecture enumeration in place.

Related issues

No related issues found above the similarity threshold.