PATH auto extended with stage paths
Metadata
Current evaluation
Auto-prepending stage bin paths to PATH breaks cross-compilation by invoking wrong-architecture binaries. Suggests disabling this for cross-builds or making it configurable. Unassigned, no comments, inactive for over 3 years.
Suggested action: needs triage
Reason: The issue has been inactive for over three years with zero maintainer comments or labels, indicating it has not yet been assessed. While it describes a valid cross-compilation concern, it requires maintainer review to verify if the behavior persists in current versions and to determine appropriate next steps before considering stale closure.
Staleness:
90
Complexity:
50
Confidence:
75
Support Request:
10
Issue body
snapcraft automatically adds <stage>/usr/bin and <stage>/usr/sbin, additionally those paths are added to the beginning.
This would usually work for native builds, but causes problems when running cross builds
e.g. including python in the snap, would make the next part fail, if it tries to use python from the stage directory, which is of the wrong architecture.
As a minimum, this should be avoided if cross-build is detected.
It is still questionable if this should be the default behaviour rather than in control of the snapcraft.yaml
e.g. staging JRE in the snap, vs using JDK from the build environment.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| 2026-06-19 08:03:45.840978+00:00 | qwen3.6-35b-a3b-mtp-q6 |
Staleness:
90
Complexity:
50
Confidence:
75
Support Request:
10
|
needs triage | Auto-prepending stage bin paths to PATH breaks cross-compilation by invoking wrong-architecture binaries. Suggests disabling this for cross-builds or making it configurable. Unassigned, no comments, inactive for over 3 years. |
| 2026-06-19 08:01:15.208456+00:00 | pending | — | — | — |