← Back to issue list

post-stop-command not wrapped

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#1683422
Type
issue
State
open
Author
~mabnhdev
Labels
post-stop-command
Created
Updated
Closed
—

Current evaluation

2015 bug report: snapcraft copies post-stop-command verbatim into snap.yaml without shell wrapping, so $SNAP-style variables fail snapd's field regex and break snap install. No comments, no labels, no maintainer response; untriaged and unverified against current code.

Suggested action: needs triage

Reason: The issue has zero comments, no labels, and no assignee, and is 3423 days old, so it has never been assessed by a maintainer. It is a genuine bug with a concrete reproducer (external repo branch 'poststop' and the snapd error 'app description field post-stop-command contains illegal /bin/ls $SNAP/etc'), not a support question. Code inspection tools were unavailable (no pinned SHA), so it cannot be confirmed whether modern snapcraft still copies the field verbatim; a maintainer should verify current behavior before closing, since the reported failure mode may still apply.

Impact: 35 Quick Win: 21.0 Staleness: 85 Complexity: 40 Confidence: 55 Support Request: 10

Issue body

The post-stop-command is not wrapped, so not snappy variable substitution is possible. The post-stop-command is copied verbatim into the meta/snap.yaml file with insufficient syntax checking. If a variable is included it causes snap installation failure with the errror: error: cannot read snap file: app description field 'post-stop-command' contains illegal "/bin/ls $SNAP/etc" (legal: '^[A-Za-z0-9/. _#:-]*$') To reproduce: git clone http://github.com/mabnhdev/snappy-daemon-demo -b poststop cd snappy-daemon-demo snapcraft sudo snap try

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.8-27b
Impact: 35
Quick Win: 21.0
Staleness: 85
Complexity: 40
Confidence: 55
Support Request: 10
needs triage 2015 bug report: snapcraft copies post-stop-command verbatim into snap.yaml without shell wrapping, so $SNAP-style variables fail snapd's field regex and break snap install. No comments, no labels, no maintainer response; untriaged and unverified against current code.
qwen/qwen3.6-35b-a3b
Staleness: 99
Complexity: 20
Confidence: 85
Support Request: 0
close stale Improper handling of post-stop-command variables in snapcraft.yaml causes installation failures. The report is over nine years old with zero maintainer engagement.
qwen/qwen3.6-35b-a3b
Staleness: 98
Complexity: 40
Confidence: 85
Support Request: 10
close stale Report that post-stop-command lacks variable substitution and fails snap validation. Unacknowledged for ~9 years with no maintainer interaction.
qwen3.6-35b-a3b-mtp-q6
Staleness: 98
Complexity: 45
Confidence: 85
Support Request: 10
close stale Bug report stating post-stop-command lacks variable substitution and fails snapcraft validation. No maintainer activity for over 9 years.

Update history

No update history recorded yet.

Related issues

Issue Project State Summary Similarity
#1662240 post-stop-command not defined in snapcraft schema snapcraft (launchpad) closed Closed without comments or resolution. The missing post-stop-command schema definition was abandoned and never implemented.
75%