snapcraft run should only run from the project directory
Metadata
Current evaluation
Closed without a documented resolution or linked implementation after four days of activity.
Resolution: closed stale
Reason: No comments, resolving PR, commit, or maintainer explanation were recorded, with no activity for 4,025 days. With no verifiable technical change, the closure is best classified as stale.
Evaluated by: mr-cal-bot
No scores available.
Issue body
run seems to be able to work from any localtion, this can be bad for regular users.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed stale | Closed without a documented resolution or linked implementation after four days of activity. | |
| stealth/space-bunny-alpha | — | closed stale | Launchpad #1498140 was closed without implementation or explanation; the proposal to restrict snapcraft run to project directories was abandoned after 4,029 days. | |
| stealth/space-bunny-alpha | — | closed stale | Closed without implementation; no resolving commit, PR, or maintainer explanation was recorded for restricting `snapcraft run` to project directories. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without implementation. The request to restrict snapcraft run to the project directory was abandoned or superseded by later design changes, with no discussion or resolution details provided. | |
| qwen/qwen3.6-35b-a3b | — | — | Restricting snapcraft run to the project directory was closed without resolution. Zero comments and no implementation notes indicate the request was abandoned. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed without resolution. The report noted snapcraft run executes from arbitrary directories, creating risks for regular users. Zero comments and no linked pull requests indicate the issue was abandoned. |
Update history
| Date | Change |
|---|---|
| created |
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1597711 snapcraft: self.run() is inconsistent in providing | snapcraft (launchpad) | closed | Closed as expired/stale on 20 February 2017 after 60 days without activity; no fix, documentation update, or superseding change was recorded. | |
| #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. | |
| #5843 Snapcraft uses the wrong project model for non-app snaps | snapcraft | closed | Closed without a documented resolution; the only follow-up was automated creation of internal ticket SNAPCRAFT-1252, with no linked PR or commit. | |
| #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. | |
| #4300 snapcraft fails for python projects if there is no setup.py | snapcraft | closed | Closed as stale in April 2025 without a Snapcraft fix. The reproducer declared bin/cos-alerter, but its packaging metadata did not define a console script; no resolving PR or commit was linked. |