add the typical environment variables to any interactive session, like with `--debug`
Metadata
Current evaluation
Feature request to include build-stage env vars (CRAFT_PART_BUILD, CRAFT_PRIME, etc.) in the interactive shell dropped on `--debug` build failure. No labels, no maintainer comments, no assignee; untriaged for ~2.7 years.
Suggested action: needs triage
Reason: The issue has zero labels, zero comments, and no assignee, with last activity 381 days ago and no maintainer acknowledgement, so it has never been triaged. It is a valid, well-scoped feature request (env vars like CRAFT_PART_BUILD are already defined in craft-parts' executor/environment.py), but the fix likely belongs in craft-parts rather than rockcraft, which needs maintainer assessment to route correctly.
Impact:
35
Quick Win:
19.25
Staleness:
78
Complexity:
45
Confidence:
62
Support Request:
10
Issue body
### What needs to get done
Whenever the user is dropped into an interactive session (for example, when a build error occurs during `rockcraft pack --debug`), include all environment variables that would normally exist at that stage in the build. For example, if debugging happens because part `xyz` failed, you should have `CRAFT_PART_BUILD=/root/parts/xyz/build`, `CRAFT_PRIME=/root/prime`, etc
### Why it needs to get done
For a user that is debugging, they want to debug exactly where the script left off. Without these environment variables, they need to set them manually to debug their own scripts. This is both tedious and leads to errors
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.8-27b |
Impact:
35
Quick Win:
19.25
Staleness:
78
Complexity:
45
Confidence:
62
Support Request:
10
|
needs triage | Feature request to include build-stage env vars (CRAFT_PART_BUILD, CRAFT_PRIME, etc.) in the interactive shell dropped on `--debug` build failure. No labels, no maintainer comments, no assignee; untriaged for ~2.7 years. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
90
Complexity:
20
Confidence:
80
Support Request:
10
|
close stale | Request to automatically populate standard environment variables in interactive debug shells to simplify script debugging. The issue remains unlabelled and has seen no maintainer engagement or comments in over two years. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
90
Complexity:
20
Confidence:
85
Support Request:
10
|
needs triage | Request to automatically populate typical build environment variables when entering interactive debug sessions. Currently unlabelled and awaiting maintainer assessment. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
90
Complexity:
20
Confidence:
85
Support Request:
10
|
close stale | Feature request to automatically populate standard build environment variables when entering interactive debug sessions. Currently unlabelled and inactive for over two years with no maintainer feedback. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
85
Complexity:
20
Confidence:
65
Support Request:
10
|
needs triage | Automatically inject standard build environment variables into interactive debug sessions. Currently requires manual setup, causing tedious and error-prone debugging. Open, unassigned, no comments, inactive for over a year. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #435 Include appropriate craft-parts environment variables when packing with `--shell`, `--debug`, etc. | craft-application | open | Feature request to expose craft-parts environment variables (e.g. $CRAFT_STAGE) in the shell launched by --shell/--debug on lifecycle commands like pack, to speed up override-script debugging. Open, unlabelled, zero comments, no activity since ~465 days ago. |