snapcraft: self.run() is inconsistent in providing
Metadata
Current evaluation
Closed as expired/stale on 20 February 2017 after 60 days without activity; no fix, documentation update, or superseding change was recorded.
Resolution: closed stale
Reason: Maintainer @janitor closed the report as expired after the requested clarification received no follow-up for 60 days.
Evaluated by: mr-cal-bot
No scores available.
Issue body
in a snapcraft plugin:
self.run(['pwd'])
self.run(['pwd'], '.')
make pwd run in different work directories, which is highly irritating. Thus should be consistent or at least be very explicitly documented -- or both.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed stale | Closed as expired/stale on 20 February 2017 after 60 days without activity; no fix, documentation update, or superseding change was recorded. | |
| stealth/space-bunny-alpha | — | closed stale | Closed as expired/stale by ~janitor in Feb 2017 after ~60 days of inactivity. Maintainer ~kyrofa had asked for clarification (Dec 2016) on the reported self.run() working-directory inconsistency; reporter never responded. | |
| stealth/space-bunny-alpha | — | closed stale | Closed as stale after 60 days without activity; no fix, documentation change, or superseding work was recorded. | |
| stealth/space-bunny-alpha | — | closed stale | Closed without a fix after years of inactivity; no resolving PR, commit, or maintainer explanation was recorded. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without implementation. The self.run() directory inconsistency remains unresolved and undocumented, likely abandoned due to inactivity. | |
| qwen/qwen3.6-35b-a3b | — | — | Inconsistent working directory behavior in snapcraft's self.run() was reported but closed without resolution or comments, indicating the report was abandoned. No fix or documentation update was implemented. | |
| qwen/qwen3.6-35b-a3b | — | — | Abandoned due to prolonged inactivity. The reported inconsistency in snapcraft's self.run() working directory behavior remains unfixed and undocumented. | |
| qwen/qwen3.6-35b-a3b | — | — | Abandoned and closed without resolution. The reported inconsistency in snapcraft plugin self.run() working directory handling received no comments or developer response. No code changes or documentation updates were implemented. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Inconsistent working directory behavior in snapcraft's self.run() was closed without resolution or comments, indicating the report was abandoned. No fix or documentation update was implemented. |
Update history
| Date | Change |
|---|---|
| created |
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1498140 snapcraft run should only run from the project directory | snapcraft (launchpad) | closed | Closed without a documented resolution or linked implementation after four days of activity. | |
| #1666013 Snapcraft reports an error if the executable for a command is provided by a content interface | snapcraft (launchpad) | closed | Snapcraft #1666013 was closed as expired after 60 days of inactivity; no fix or superseding work was recorded. | |
| #1988858 snapcraft trying to install extra package causing conflict | snapcraft (launchpad) | closed | Expired and closed without a fix after 60 days of inactivity; maintainers could not reproduce the conflict and suspected a transient archive state. | |
| #1734231 SnapcraftEnvironmentError is too generic | snapcraft (launchpad) | closed | Closed as stale after 3,235 days without an implementation; maintainer ~mr-cal closed it on 2026-08-14 with no linked fix. | |
| #1686484 snapcraft fails when two parts have the same file in the stage keyword | snapcraft (launchpad) | closed | Closed as stale in August 2026 after nearly nine years without a fix; the discussion provided no confirmed workaround. | |
| #1662658 snapcraft namespace is getting crowded with store methods | snapcraft (launchpad) | closed | Closed as expired on 2017-04-16 after 60 days of inactivity; no namespace migration PR or commit was recorded on the issue. |