Have the `--debug` shell inform the user which part and step failed
Metadata
Current evaluation
Feature request: have rockcraft's --debug shell tell the user which part and step failed (e.g. via PS1 or /etc/issue) for quicker troubleshooting. Open, no labels, only a Jira-sync bot comment; no maintainer response or implementation found.
Suggested action: needs triage
Reason: The issue is a well-scoped feature request (add part/step context to the --debug shell) but has no labels, no assignee, and the only comment is an autogenerated Jira-sync bot message (CRAFT-2831) with no maintainer acknowledgement. No code implementing PS1 or /etc/issue context was found in rockcraft or craft-parts, so it appears unaddressed and untriaged.
Impact:
40
Quick Win:
24.0
Staleness:
70
Complexity:
40
Confidence:
60
Support Request:
10
Issue body
### What needs to get done
When rockcraft takes me into a `--debug` shell, it's not clear what went wrong and I end up poking in `../parts/` to see what's missing and where.
It could be handy if the debug shell had a means to inform the user which part and step went wrong, for example:
- PS1 envvar
- Update and display `/etc/issue`
### Why it needs to get done
Quicker troubleshooting.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.8-27b |
Impact:
40
Quick Win:
24.0
Staleness:
70
Complexity:
40
Confidence:
60
Support Request:
10
|
needs triage | Feature request: have rockcraft's --debug shell tell the user which part and step failed (e.g. via PS1 or /etc/issue) for quicker troubleshooting. Open, no labels, only a Jira-sync bot comment; no maintainer response or implementation found. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
85
Complexity:
15
Confidence:
80
Support Request:
10
|
needs triage | Feature request to display the failing part and step in the rockcraft --debug shell prompt or /etc/issue for faster troubleshooting. Currently unlabelled and inactive for over two years. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
85
Complexity:
15
Confidence:
75
Support Request:
0
|
needs triage | Feature request to show the failed part and step in rockcraft's --debug shell. Currently unlabelled with no maintainer response in over two years, awaiting project prioritization. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
85
Complexity:
15
Confidence:
75
Support Request:
20
|
needs triage | Feature request to display the failing part and step in rockcraft's --debug shell for easier troubleshooting. Currently unlabelled, with a Jira sync comment from April 2024 and no maintainer engagement. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
82
Complexity:
15
Confidence:
75
Support Request:
5
|
close stale | Request to show the failed part and step in rockcraft's debug shell for faster troubleshooting. Open with Jira ticket CRAFT-2831, last active 304 days ago, awaiting triage. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #483 Summarise what has/has not been completed when failing or entering a `--debug` session | rockcraft | open | Feature request to print a summary of completed/incomplete build steps when a rockcraft pack fails or when entering a --debug session, to help users understand where they are in the build process. No maintainer response; only an automated Jira sync bot comment. No evidence of implementation in the codebase. |