--debug drops me into an unexpected directory
Metadata
Current evaluation
Snapcraft 4.5.1 --debug drops the user into /root instead of the override-stage script's working directory. Reported ~5.5 years ago, zero comments, no labels, no maintainer interaction. Related Launchpad bugs 1848513 (env vars) and 1848732 (snapcraftctl) still open.
Suggested action: needs triage
Reason: The issue is a genuine bug report (not a support request) with a clear reproduction scenario (override-stage with 'exit 1' under --debug), but it has zero comments, no labels, no assignee, and no maintainer response in ~5.5 years. It has never been triaged. While very stale, there is no evidence the behavior was fixed or that the affected version is unsupported, so it should be triaged rather than closed outright.
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.8-27b |
Impact:
30
Quick Win:
18.0
Staleness:
95
Complexity:
40
Confidence:
55
Support Request:
10
|
needs triage | Snapcraft 4.5.1 --debug drops the user into /root instead of the override-stage script's working directory. Reported ~5.5 years ago, zero comments, no labels, no maintainer interaction. Related Launchpad bugs 1848513 (env vars) and 1848732 (snapcraftctl) still open. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
45
Confidence:
90
Support Request:
5
|
close stale | Reports that --debug in override-stage drops into /root instead of the script's working directory. Open for over 5 years with no maintainer response or updates. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
40
Confidence:
90
Support Request:
10
|
close stale | Bug report stating --debug flag in override-stage drops user in /root instead of the script's working directory. Issue is over 5 years old, has no maintainer interaction, and references outdated software versions. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
35
Confidence:
85
Support Request:
10
|
close stale | Reports --debug in override-stage dropping into /root instead of the script directory. Unlabeled, zero comments, and based on outdated version 4.5.1. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
30
Confidence:
90
Support Request:
10
|
close stale | --debug in snapcraft drops users into /root instead of the override-stage script's working directory. Remains open, unassigned, and inactive with no comments or labels. |
Update history
No update history recorded yet.
Related work
-
Related To:
snapcraft#1848513
(confidence 70%)
Explicitly referenced in the issue body as a companion bug for missing environment variables in the debug shell.
-
Related To:
snapcraft#1848732
(confidence 70%)
Explicitly referenced in the issue body as a companion bug for a missing snapcraftctl command in the debug shell.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1848513 --debug does not expose appropriate environment variables | snapcraft (launchpad) | open | Snapcraft --debug drops user into a shell on command failure but does not propagate the environment variables (SNAPCRAFT_* and Python-specific vars) the failing command relied on, so the failure cannot be reproduced. 7 years old, no labels, no maintainer interaction. | |
| #1989139 Duplicated /root/stage in path | snapcraft (launchpad) | open | Bug report about duplicated /root/stage in Snapcraft 7.1.3 causing build failures. Issue is 4 years old with no maintainer interaction or labels. |