Issue & PR triage
Loading...
Showing 5 of 5 issues
| Issue | Title | Author | Age | Action | Impact ↓ | Actionability | Quick Win | Summary |
|---|---|---|---|---|---|---|---|---|
|
snapcraft-rocks issue #111 |
Failed to create rock (Failed to stage: parts list the same file or... | asilnov | 314d | needs triage | 55 | 62 | 14 | Rock creation on core22-8 fails during staging because the snapcraft part and its overlay disagree on Python 3.10 files; the unlabelled report has no maintainer response. |
|
snapcraft-rocks issue #98 |
Use `rockcraft test` to test the rocks | lengau | 448d | needs triage | 35 | 45 | 9 | Maintainer-filed task to replace/augment spread tests in spread.yaml and CI workflows with `rockcraft test` so built snapcraft rocks are exercised; untouched for 421 days, no labels or discussion. |
|
snapcraft-rocks issue #59 |
Add `SNAPCRAFT_BUILD_ENVIRONMENT=host` to Docker image | abitrolly | 765d | needs triage | 32 | 72 | 17 | Requests SNAPCRAFT_BUILD_ENVIRONMENT=host be set in the snapcraft rocks images so snapcraft can be run manually inside the container to troubleshoot. Untriaged, no comments; change must go on core22-7/8 and core24-8 branches. |
|
snapcraft-rocks issue #40 |
`--workdir` is ignored | VladRassokhin | 911d | needs triage | 30 | 55 | 11 | Reporter: --workdir ignored by snapcraft-rocks containers; only /project works. Full docker repro given. Doc gap conceded by reporter, but why custom dirs are rejected (entrypoint/pwdb) is still unconfirmed. No maintainer response. |
|
snapcraft-rocks issue #41 |
Arguments list is incompatible with previous official snapcraft docker image | VladRassokhin | 911d | needs triage | 25 | 30 | 6 | Notes that the new rocks-based snapcraft image wraps snapcraft in ENTRYPOINT, so scripts written for the old snapcore/snapcraft image must drop the leading `snapcraft` argument; no explicit ask, no maintainer reply. |