Showing 100 of 1948 issues
| Issue | Title | Author | Age | Action | Impact ↓ | Actionability | Quick Win | Summary |
|---|---|---|---|---|---|---|---|---|
|
snapcraft (launchpad) issue #1809475 |
Feature Request: Snapcraft should ship gitignore when running `snapcraft init` | ~brlin | 2878d | needs triage | 30 | 76 | 17 | Snapcraft still provides no .gitignore entries for `snapcraft init`; shared Craft Application support can append entries, but this 2018 feature request remains untriaged. |
|
snapcraft issue #5691 |
Proposal: Metadata Separation of Snap Versions | erik78se | 455d | keep open | 30 | 35 | 2 | Proposal to split snap 'version' metadata into separate workload-version and snap-version fields; maintainer mr-cal acknowledged and pointed to snapcraft forum thread; no implementation, still open. |
|
snapcraft pr #5974 |
feat(project): add pydantic validator for common_id field | soumyaDghosh | 290d | needs review | 30 | 25 | 6 | Adds a pydantic validator for App.common_id enforcing appstream desktop-ID format, with unit tests and docs. Successor to closed #5625 for issue #5624. Dormant 252 days, 3 unresolved review comments, 3 CI checks failing. |
|
snapcraft pr #5981 |
chore: use pathlib to interact with craft-parts | EdmilsonRodrigues | 285d | close stale | 30 | 10 | 2 | Pathlib migration for craft-parts is now redundant on main; the PR is inactive after 249 days with four unresolved comments and multiple failing checks. |
|
snapcraft (launchpad) issue #1955887 |
snapcraft npm doesn't respect npm-node-version | ~nanu | 1776d | close not a bug | 30 | 94 | 24 | Legacy npm configuration was misleading: override-build bypasses the plugin-managed Node download; current craft-parts requires npm-include-node with npm-node-version. |
|
snapcraft (launchpad) issue #1798881 |
patchelf fails on i386 vscode | ~popey | 2941d | close resolved | 30 | 70 | 9 | The i386 VS Code build hit a patchelf 0.9 ELF underrun; Snapcraft later changed its Go ELF handling, but the Launchpad issue remains open. |
|
craft-application issue #1217 |
Bad error handling for ill-formatted platforms | cmatsuoka | 29d | keep open | 30 | 80 | 22 | Crash with AttributeError when platforms is declared as a list instead of a dict in snapcraft.yaml. Triaged, with a developer interested in fixing it. |
|
craft-parts issue #196 |
Consider capturing all potentially invalid stage-packages before bailing | sergiusens | 1676d | needs triage | 30 | 72 | 14 | Requests validating all stage-packages and reporting every missing entry at once; still open, unlabelled, and awaiting maintainer triage beyond an automated Jira-sync comment. |
|
charmcraft issue #2643 |
Reorganise sample charm documentation to include the most common keys at the top. | lengau | 214d | keep open | 30 | 80 | 17 | Maintainer request to reorder the sample charmcraft.yaml so required keys (name, base, parts) appear first, and align the reference docs. Triaged; sample file currently starts with actions and ends with type. |
|
snapcraft issue #6424 |
Add `snapd-info` key for snapd snaps | mr-cal | 52d | keep open | 30 | 80 | 17 | Enhancement to add a `snapd-info` key to `snap.yaml` for `type: snapd` snaps. Issue is triaged and has a willing contributor waiting to begin work. |
|
snapcraft issue #5683 |
Investigate why `list-keys` makes repeated API calls | mr-cal | 457d | close resolved | 30 | 60 | 12 | Repeated API calls affected the legacy `list-keys` command; it is now removed, and its `keys` replacement makes one local key lookup and one account-info request. |
|
snapcraft (launchpad) issue #1852618 |
apt auto refresh sometimes interferes with my snap builds | ~pengale | 2550d | needs triage | 30 | 60 | 11 | Snapcraft build-package installation can fail when the VM's unattended apt process holds the dpkg lock; retrying inside the VM succeeds, but the report has no maintainer triage. |
|
snapcraft (launchpad) issue #1956157 |
RuntimeWarning: compiletime version 3.8 of module 'msgpack._packer' does not... | ~kenneth-loafman | 1771d | needs triage | 30 | 38 | 5 | Duplicity snap's status command against a Dropbox backend prints a Python 3.6/3.8 msgpack compiletime-vs-runtime RuntimeWarning, apparently from staging mixed python versions. Reporter worked around it recipe-side; never triaged by maintainers. |
|
craft-application issue #506 |
Allow craft tools to function inside a LXD parent container when performing... | flotter | 764d | close stale | 30 | 20 | 2 | Enhancement request for craft tools to support nested LXD managed builds inside an LXD parent container. Maintainer linked UID/idmap work in craft-providers#259 and asked for workaround details; no response in 400 days. |
|
snapcraft (launchpad) issue #1802345 |
can't build python part with C modules | ~ack | 2921d | keep open | 30 | 45 | 9 | Python plugin can't build packages with C extensions (Python.h not found). Maintainer-confirmed build-environment workaround exists, but the plugin still never sets C_INCLUDE_PATH itself. Reproducer targets core18/snapcraft 3.0 and needs re-verification on current bases. |
|
debcraft pr #197 |
fix: make build base type a union | jahn-junior | 33d | keep open | 30 | 30 | 7 | Changes BuildBaseT to include None in the union, removing the pydantic validate_default warning; under review with fast tests failing and author yet to validate. |
|
craft-store issue #244 |
Rework the API to remove repetitiveness and redundancy | lengau | 694d | keep open | 30 | 40 | 6 | Maintainer-filed API cleanup request: rename AccountModel to craft_store.models.Account for consistency with PublisherGateway. Still open, unlabelled, only a bot comment; tracked internally as CRAFT-3812. Partly addressed by aliases in craft_store.publisher. |
|
snapcraft issue #5697 |
Explain how to use local GPG keys for a repository | lengau | 451d | keep open | 30 | 82 | 19 | Triaged documentation gap remains: local GPG keys for custom package repositories lack guidance on the required key filename format and storage location. |
|
snapcraft issue #5448 |
Add deprecation warning for the `snap_daemon` system username | mr-cal | 557d | keep open | 30 | 82 | 18 | Maintainer-filed enhancement (triaged) to warn when `snap_daemon` appears in system-usernames, per snapd's deprecation. Still unimplemented on HEAD; PR #6250 exists but is open with failing CI and unresolved review comments. |
|
craft-actions issue #47 |
Docs: link to examples in each action's README | jahn-junior | 331d | keep open | 30 | 65 | 15 | Docs request by a maintainer to add real-world usage examples to each action's README (like setup-uv), also to help users choose between setup and pack actions; still open, no discussion. |
|
snapcraft (launchpad) issue #1758859 |
'snapcraft push' dies with traceback if credentials are invalid | ~romain-janvier | 3149d | close resolved | 30 | 75 | 17 | 'snapcraft push' emitted a raw UnicodeDecodeError traceback when legacy snapcraft.cfg store credentials were malformed; current code catches decoding failures and raises a handled LegacyCredentialsParseError. |
|
snapcraft pr #6169 |
docs: fix support chart colours for dark mode | Copilot | 211d | needs review | 30 | 72 | 19 | Docs-only CSS fix: adds dark-mode custom properties (--chart-pro-fill #aea79f, --chart-milestone-color #cd7c97) so Pro/Legacy bars and milestone markers in the support chart are visible; light mode unchanged. CLA passing, no reviewers yet. |
|
snapcraft issue #5275 |
docs: update build-environment for the kde-neon and kde-neon-6 extensions | mr-cal | 625d | keep open | 30 | 88 | 20 | Triaged documentation task remains open: the KDE neon extension reference still shows one build environment, although the code supports distinct core22 and core24 environments; PR #6456 was closed unmerged. |
|
snapcraft pr #6073 |
docs: add gnome-keyring example for WSL users (fixes #6049) | Dotunbey | 249d | keep open | 30 | 30 | 7 | Docs-only PR adding a gnome-keyring install/configure example for WSL users to docs/how-to/publishing/authenticate.rst, closing #6049. External contributor; one maintainer comment but 8 unresolved inline review comments and no activity for ~7 months. |
|
snapcraft issue #5257 |
Show artifact name and overall progress when uploading a snap with components | farshidtz | 633d | keep open | 30 | 58 | 8 | Enhancement request: snapcraft upload with components shows a bare 'Uploading...' bar per artifact with no artifact name or overall progress. Triaged as a UX improvement (JIRA SNAPCRAFT-1033); still unimplemented in snapcraft/commands/upload.py. |
|
snapcraft issue #5244 |
"Edit this page on Github" links give a 404 not found on Github | Sophie-Pages | 638d | close resolved | 30 | 90 | 22 | Snapcraft documentation edit links were traced to an upstream canonical-sphinx path bug; the current docs stack requires canonical-sphinx 0.6+, incorporating the 0.4.0 fix. |
|
snapcraft issue #4958 |
Recommend using newer versions of snapcraft | mr-cal | 817d | keep open | 30 | 88 | 22 | Enhancement to emit a warning recommending a newer Snapcraft for older bases; rescoped by maintainer to 8.x recommending 9.x for core22/core24/core26, contributor assigned, open PR #6240 stalled with failing CI. |
|
rockcraft issue #898 |
Hello world tutorial doesn't work when using 24.04 base | seb128 | 513d | close resolved | 30 | 80 | 22 | Tutorial fails when base changed from 22.04 to 24.04 (bare + build-base); current docs use ubuntu@26.04, so the reported doc issue is resolved. |
|
snapcraft (launchpad) issue #1674124 |
trying to push with the wrong macaroon return non user-friendly error | ~elopio | 3520d | close stale | 30 | 55 | 9 | Legacy enable-ci should explain macaroon permission 403s, but the command is absent from the current codebase and the report needs reassessment against today's authentication flow. |
|
fetch-service pr #671 |
ci: switch to public runners | lengau | 4d | needs review | 30 | 80 | 22 | Switches CI workflows from self-hosted runners to public GitHub-hosted runners. Small config change (+8/-7, 1 file). CI passing, awaiting review. |
|
craft-parts issue #610 |
Utility function to format partition names | lengau | 1060d | keep open | 30 | 80 | 22 | Consolidate duplicated partition name formatting logic in executor/environment.py and utils/partition_utils.py into a shared utility function. |
|
rockcraft issue #1388 |
maven/ant plugins: `create_usr_bin_java` creates a stray `./java` link;... | javierdelapuente | 24d | keep open | 30 | 80 | 19 | Maven/Ant plugins fail on second `rockcraft pack` because `create_usr_bin_java` uses `test -f` which returns false for symlinks, causing `ln -s` to fail with 'Already exists'. |
|
rockcraft issue #513 |
Missing craft-parts plugins in reference | alnvdl-work | 964d | keep open | 30 | 60 | 16 | Documentation gap: rockcraft plugin reference doesn't explain that plugins come from craft-parts. Maintainer confirmed work is in progress upstream. |
|
starflow issue #118 |
Contributors script sometimes adds @unknown to the thank-you section. | lengau | 246d | keep open | 30 | 62 | 12 | starflow's tools/contributors.py emits a bogus '@unknown' entry in the thank-you section when a contributor's GitHub username can't be resolved; reported by a maintainer with a reproducer command, labeled Type: Bug, still open and unfixed. |
|
snapcraft (launchpad) issue #1668242 |
"snapcraft gated" output doesn't have a clear order | ~ara | 3540d | keep open | 30 | 88 | 22 | snapcraft gated still emits validations in store-response order; requested ordering is snap name A-Z and revisions by descending validation timestamp |
|
rockcraft issue #510 |
Cannot easily skip `go mod download` with the `go` plugin | alnvdl-work | 967d | needs triage | 30 | 65 | 13 | Feature request: the `go` plugin (craft-parts go_plugin.py) unconditionally runs `go mod download all`, with no key to skip it for vendored deps; overriding the whole build script is the only workaround. Unlabelled, no maintainer reply. |
|
snapcraft issue #5211 |
Docs: Cover the minimum versions for build providers | medubelko | 656d | keep open | 30 | 35 | 6 | Docs request to list minimum LXD/Multipass build provider versions in system requirements. Valid and triaged, but maintainer says it can't start until craft-providers documents and exposes those versions to all craft apps. |
|
rockcraft pr #1413 |
fix(ci): replace managerFilePatterns with fileMatch in renovate config | LoweRAM | 3d | needs review | 30 | 80 | 23 | Fixes Renovate config validation error by replacing deprecated managerFilePatterns with fileMatch in .github/renovate.json5. Verified locally; CI mostly passing. |
|
snapcraft (launchpad) issue #1918998 |
Crash when key in snap/keys is not ascii armored | ~racb | 2066d | needs triage | 30 | 78 | 16 | A binary snap/keys asset triggers a UTF-8 decode error instead of a clear validation message; the report is open, unlabeled, and lacks maintainer triage or a confirmed resolution. |
|
charmcraft issue #1886 |
Make 2.x version of Charmcraft docs on RTD | lengau | 789d | keep open | 30 | 55 | 8 | Maintainer request to publish a versioned 2.x copy of Charmcraft docs on Read the Docs so users can compare 2.x and 3.x behavior. Still open with no comments or implementation. |
|
snapcraft (launchpad) issue #1899033 |
Passing --store has weird syntax/requirements and user-facing error is not... | ~roadmr | 2221d | close not a bug | 30 | 55 | 12 | A copied zero-width space in the --store value caused the 400 response; clean input succeeds. Clearer API errors and store-aware output are separable UX enhancements. |
|
craft-application issue #458 |
Emit a warning when the fetch-service integration is enabled | tigarmo | 786d | close resolved | 30 | 80 | 23 | Requests a warning when the experimental fetch-service integration is enabled; already implemented in craft_application/services/fetch.py and covered by a unit test. |
|
craft-providers issue #970 |
Test on Python 3.14 and Ubuntu 26.04 (Resolute) | lengau | 157d | needs triage | 30 | 60 | 14 | Request to add Python 3.14 and Ubuntu 26.04 testing to CI. A previous PR (#971) failed and was closed, leaving the tracking issue open without maintainer review or labels. |
|
snapcraft issue #4360 |
Add "--base=core2x"" option to "snapcraft extensions" | unknown | 1156d | keep open | 30 | 80 | 19 | Add --base option to 'snapcraft extensions' for parity with 'plugins --base'. Triaged, unimplemented, with open PR #6214. |
|
craft-parts issue #1214 |
Configure maven to ignore missing checksums for the repositories we define | tigarmo | 442d | keep open | 30 | 85 | 20 | Add <checksumPolicy>ignore</checksumPolicy> to the craft-parts-defined Maven repositories (backstage maven-use repo and /usr/share/maven-repo mirror) to silence noisy missing-checksum warnings. Triaged, linked to CRAFT-4709, still unimplemented at HEAD. |
|
charmcraft pr #2666 |
tests: add reproducer for fetch-lib unhelpful error message (#2204) | lengau | 200d | close superseded | 30 | 25 | 5 | Adds failing unit test reproducing #2204's 'Library None not found' error; Copilot comment claims fix in commit 4a4d0d4 but PR remains test-only and inactive 163 days. |
|
snapcraft (launchpad) issue #1719348 |
meson plugin builds to /usr/local by default | ~popey | 3330d | keep open | 30 | 70 | 16 | Requests the meson plugin default to --prefix=/usr instead of meson's /usr/local. Still unimplemented: craft-parts MesonPlugin passes only user meson-parameters; the plugin moved out of snapcraft, so fix must be upstream. |
|
snapcraft (launchpad) issue #1660302 |
foreign architecture builds doesn't work with classic snaps | ~popey | 3568d | close not a bug | 30 | 35 | 1 | The classic-snap --target-arch build is unsupported because architecture selection is plugin-specific; the sole maintainer response said general support required Debian cross-compilation, and the issue remains open. |
|
craft-parts issue #1158 |
"unknown argument ignored: lazytime" in overlay operations | tigarmo | 492d | keep open | 30 | 82 | 18 | Triaged bug: old fuse-overlayfs versions emit noisy “unknown argument ignored: lazytime” warnings during overlay mounts; it remains open without a craft-parts fix. |
|
craft-application pr #1003 |
docs: Add reference documentation for the RemoteBuildService | lengau | 282d | needs review | 30 | 82 | 18 | Adds RemoteBuildService reference documentation; all 15 listed CI checks pass, but after 210 days without activity it still has no reviewer or review feedback. |
|
snapcraft (launchpad) issue #1918968 |
Cannot automatically build a part from a Debian package source tree | ~racb | 2066d | needs triage | 30 | 35 | 4 | Wishlist request (2020) from ~racb for a 'deb' part plugin that builds a deb from a Debian source tree's debian/ directory and exposes it to stage/build-packages; no maintainer response, labels, or comments after 2029 days. |
|
snapcraft issue #6510 |
Spread tests should run review-tools on snaps | mr-cal | 17d | keep open | 30 | 80 | 14 | Enhancement to add review-tools checks to Spread tests. Triaged, with active PR #6531 implementing the first part. |
|
craft-application issue #923 |
`CraftSpreadYaml` should accept the `environment` key | lczyk | 407d | keep open | 30 | 64 | 14 | Top-level environment is still rejected in deprecated spread.yaml parsing; the enhancement was acknowledged, but no implementation or design decision is recorded and suite-level environment provides a workaround. |
|
charmcraft pr #2979 |
docs: explain how to set default charm track | CODElST | 8d | needs review | 30 | 80 | 22 | Documentation-only PR adding a section on setting the default track via Charmhub API, closing issue #2960. Awaiting maintainer review. |
|
craft-application pr #861 |
chore: prepare for Python 3.14 | lengau | 449d | keep open | 30 | 15 | 3 | Adds Python 3.14 and 3.14+freethreaded to the QA test matrix in qa.yaml; all fast/slow test jobs fail because the PR is waiting on PyO3 0.26. 412 days idle, no review. |
|
craft-application issue #552 |
Add a way for applications to customize the `InitService` | mr-cal | 730d | keep open | 30 | 70 | 16 | Enhancement: let apps customize InitService name validation and emit per-template messages. Name validation is done (constructor params name_regex/default_name/invalid_name_message, PR #567); per-template message hook still missing. |
|
snapcraft (launchpad) issue #1812435 |
python snap fails to build no such file or directory in prime/bin | ~dwoot | 2850d | needs triage | 30 | 55 | 9 | Snapcraft 2.43.1 fails while priming because apps.command references a missing prime/bin/mockpyairpulse; the supplied YAML lacks evidence about the source package's entry point. |
|
snapcraft (launchpad) issue #1704103 |
New git commits don't mark pull step dirty | ~saviq | 3405d | close not a bug | 30 | 85 | 19 | New commits intentionally do not dirty a source-type: git pull step; maintainers redirected automatic source tracking toward source-type: local. |
|
craft-application issue #485 |
Provide a better error message when loading a multi-document yaml | lengau | 778d | keep open | 30 | 80 | 18 | Requests a clearer unsupported multi-document YAML error instead of PyYAML ComposerError/internal error. Current safe_yaml_load wraps YAMLError but lacks a specific multi-document message. |
|
snapcraft (launchpad) issue #1999038 |
"snapcraft release" chokes given an invalid revision value | ~rpjday | 1431d | keep open | 30 | 75 | 12 | Confirmed parser bug: `snapcraft release mysnap fubar` reports "No such command 'release'" instead of a bad-revision error. Reproduced by mr-cal on 7.2.9, labeled craft-1532, still open with no fix. |
|
craft-cli issue #266 |
Provide a way for apps to warn users about deprecated features. | lengau | 829d | keep open | 30 | 68 | 10 | Maintainer-filed request for an Emitter deprecation-warning API (docs link, version-to-error, once-per-run, silencing). Emitter.warning() (#358) covers only basic warnings; the dedicated mechanism is unimplemented. Tracked as CRAFT-3174. |
|
craft-parts pr #1545 |
Add integration tests for the organize keyword with parametrized YAML fixtures | Copilot | 207d | needs review | 30 | 76 | 14 | Adds 11 integration cases using parametrized real-world YAML fixtures for organize mappings. Canonical CLA is green, but no maintainer review has occurred after 170 days. |
|
charmcraft issue #1433 |
Improve Documentation for 'charmcraft help analyze' Command | mateofloreza | 1062d | needs triage | 30 | 45 | 10 | Untriaged request for clearer analyze-command documentation; current source has a brief overview and a separate analyzer/linter reference, but no explicit resolution is recorded. |
|
craft-cli issue #128 |
Greeting doesn't output as expected | mr-cal | 1473d | keep open | 30 | 82 | 14 | Partially resolved: PR #301 stops duplicate greetings for repeated trace modes, but current code still prints the initial trace greeting before CLI --verbosity=quiet is parsed. |
|
snapcraft issue #6161 |
Support chart colours aren't dark-mode friendly | medubelko | 214d | keep open | 30 | 88 | 22 | Docs bug: support chart in docs/reference/support-schedule.rst uses hardcoded black/dark fills (#111, #56334b) for Pro bars and release milestones, unreadable in dark mode. Open fix PR #6169 adds CSS custom properties. |
|
snapcraft (launchpad) issue #1858020 |
export-login --acls are not documented | ~abitrolly | 2502d | keep open | 30 | 80 | 21 | export-login --acls values still undocumented: CLI help and docs only link to the macaroon API reference; no per-ACL explanation/table. Maintainer agreed in 2020 it should be in help/docs; partial link-only fix landed in e40e68f37 (#6136). |
|
snapcraft (launchpad) issue #1663233 |
Confusing error message for "organize" when source refers to multiples items... | ~didrocks | 3558d | keep open | 30 | 82 | 17 | Wildcard organize mappings can produce a misleading "foo already exists" collision for multiple matches without a trailing slash; the report remains open with a likely glob-support fix candidate. |
|
craft-parts pr #1597 |
docs(dump): add usage examples | gcomneno | 169d | needs review | 30 | 82 | 23 | Docs-only PR adding declarative Dump plugin usage examples (local dir, per-file copies, organize remapping). Approved by 2 reviewers, 0 unresolved comments; CI green except an unrelated Minimum-dependencies failure. |
|
charmcraft issue #1096 |
Spread tests should ensure that juju can correctly parse the output. | lengau | 1293d | keep open | 30 | 55 | 9 | Maintainer-filed enhancement to install juju on spread runners and verify juju can parse built charm/bundle output. No comments, labels, or resolution evidence. |
|
starbase issue #352 |
CI to check pre-commit updates from renovate | lengau | 633d | keep open | 30 | 80 | 18 | Maintainer request to add a CI check running `pre-commit run --all-files` so Renovate's pre-commit hook bumps can't break things. Still unimplemented: only an automated research comment; common.mk's format-pre-commit still just runs `pre-commit run`. |
|
starbase issue #308 |
Auto-format documentation source? | lengau | 687d | keep open | 30 | 38 | 5 | Maintainer proposal to auto-format docs source and docstrings (docstrfmt suggested); still open, with a reviewer noting it needs rigorous testing against Starter Pack conventions and RST readability concerns. |
|
fetch-service pr #660 |
fix(deps): update module github.com/elazarl/goproxy to v1.9.2 | lengau | 39d | needs review | 30 | 70 | 19 | Updates goproxy to v1.9.2 and adjusts proxy_test.go for normalized req.URL.Host behavior. Approved by 1 reviewer; most CI passing, OSV-scanner failing, snap-tests pending. |
|
starflow pr #86 |
feat: Workflow for testing setup | lengau | 429d | close superseded | 30 | 12 | 2 | Adds a 70-line setup-testing Actions workflow across two files, but main already contains the equivalent self-test workflow from #58. Inactive for 392 days with no reviews or comments, it remains open while eight Linux matrix checks fail. |
|
craft-application issue #24 |
YAML loading either needs simplification or better testing | lengau | 1248d | needs triage | 30 | 60 | 10 | YAML loader exception handling from PR #20 may be redundant with current PyYAML; no regression test exercises it, and the open issue lacks a concrete reproducer. |
|
craft-cli issue #61 |
Don't add timestamps when the subprocess already does that | facundobatista | 1738d | keep open | 30 | 70 | 18 | Feature request by maintainer to add a `sub_with_timestamps` flag to emit.open_stream() so craft-cli skips adding its own timestamp when the subprocess already emits them. Still unimplemented; open_stream has no such parameter. |
|
rockcraft issue #1343 |
bug/question: should `_daemon_` be set with `*` password field? | cjdcordeiro | 78d | keep open | 30 | 70 | 18 | Suggests setting the pebble user entry in /etc/passwd to '*' (or conditionally on /etc/shadow existing) instead of 'x' for container-oriented no-login behaviour. cmatsuoka endorsed '*'. Still open; oci.py add_user unchanged. |
|
craft-cli issue #125 |
When the Printer stops it needs to clean the last line if it was transient progress | facundobatista | 1493d | close resolved | 30 | 85 | 18 | Reporter (maintainer facundobatista) asked the Printer to clear the transient progress line when stopping or pausing. Implemented in PR #126 (commit 9f9df27, merged as 2cbced2); issue left open. |
|
charmcraft issue #1434 |
Improve Documentation for 'charmcraft help clean' Command | mateofloreza | 1062d | needs triage | 30 | 30 | 6 | Documentation request for `charmcraft clean` help text; current overview is brief and issue lacks specific gaps. Related PR #2795 was rejected as subpar; no maintainer triage on issue. |
|
snapcraft pr #6461 |
experimental: use binary craftctl | cmatsuoka | 37d | needs review | 30 | 45 | 9 | Maintainer's experimental +44/-9 change to snap/snapcraft.yaml to use a binary craftctl in the snap build. Open 1 day, 0 reviews, 4 unresolved review comments; CI fails Conventional Commits title and lint/files. |
|
charmcraft issue #1512 |
Improve error message for provider not installed. | PietroPasotti | 1005d | keep open | 30 | 80 | 18 | Improve uninformative 'Provider is required but not installed' prompt to clarify LXD init and what 'y' does; maintainers acknowledge quick fix after craft-providers PR 366. |
|
charmcraft pr #2775 |
ci: add concurrency cancellation across GitHub workflows | lengau | 120d | needs review | 30 | 65 | 15 | Maintainer-authored CI-only change adding top-level `concurrency` groups with cancel-in-progress to 10 GitHub workflows. All completed checks pass; 3 spread/store checks still pending, no reviews and one unresolved comment after 80 days idle. |
|
snapcraft (launchpad) issue #1567524 |
Support tar.lzma | ~olivier-interfasys | 3866d | keep open | 30 | 70 | 14 | Open, maintainer-acknowledged enhancement for clean tar.lzma source extraction; an old reproducer emitted errors despite eventually producing files. |
|
rockcraft issue #425 |
clarify the impact of the global rockcraft.yaml fields in the final ROCK | cjdcordeiro | 1074d | keep open | 30 | 78 | 14 | Rockcraft’s rockcraft.yaml reference does not explain how global fields populate OCI labels/annotations and internal ROCK metadata; the documentation task remains open with a contributor requesting assignment. |
|
starbase issue #211 |
Merge queues | lengau | 913d | needs triage | 30 | 40 | 8 | Maintainer tracking issue to try out GitHub merge queues (prototype in charmcraft#1676). Idle876 days: no merge_group trigger added, no documented configuration, and CI has since moved to shared starflow workflows. |
|
rockcraft pr #832 |
docs: added download pdf button | alesancor1 | 607d | keep open | 30 | 35 | 9 | Adds three lines to enable a PDF download button in Rockcraft docs; open for 571 days with no reviews, comments, or CI results. |
|
snapcraft (launchpad) issue #1666160 |
Can’t distinguish programmatically between snapcraft.yaml errors and other errors | ~mpt | 3548d | keep open | 30 | 55 | 11 | Requests a programmatic distinction (exit code) between snapcraft.yaml errors and other snapcraft failures, for build.snapcraft.io UI. Still unimplemented: errors.py subclasses set retcode in only 3 cases. Needs re-triage. |
|
charmcraft issue #1713 |
Autodocs: Updates for pydantic models | lengau | 859d | keep open | 30 | 72 | 14 | Documentation task has two concrete goals: one charmcraft.yaml schema and alphabetised schema entries. Schema generation now exists, but ordering and autodoc integration remain unverified. |
|
rockcraft issue #1291 |
Execute parts as `run_user` | sed-i | 122d | needs triage | 30 | 45 | 5 | Feature request: run all parts as the non-root UID/GID when `run_user: _daemon_` is declared, removing manual chown/chmod overrides. Open, unlabelled, no maintainer response; only an outside contributor asked to work on it. |
|
rockcraft issue #991 |
Provide instructions on authentication using Skopeo when publishing rock | sinapah | 397d | needs triage | 30 | 72 | 19 | Doc request to add a --dest-creds authentication section to the 'Publish a rock to a registry' how-to. Page (now docs/how-to/crafting/publish-a-rock.rst) still has no auth guidance; no maintainer reply in ~1 year. |
|
fetch-service issue #257 |
Document how to generate captures for test data | lengau | 759d | needs triage | 30 | 65 | 16 | Open, untriaged maintainer doc request: add a how-to page describing how to generate pcap captures (tshark + SSLKEYLOGFILE git clone) used as fetch-service test data. No such docs exist yet. |
|
snapcraft (launchpad) issue #1979154 |
remote-build spams terminal | ~popey | 1602d | close stale | 30 | 94 | 25 | Legacy remote-build progress output spammed terminals in Snapcraft 7.0.7; the legacy builder was removed in Snapcraft 9.0, so the affected code path no longer exists. |
|
snapcraft (launchpad) issue #1882270 |
feature request: allow pdb tracing of snapcraft plugin code | ~dmitriis | 2346d | needs triage | 30 | 35 | 5 | 2019 request to allow pdb tracing into Snapcraft's plugin code during builds. Still open, unlabelled, no maintainer response; only workaround is unsquashing and hand-patching the snap. --debug/--shell exist but give no Python-level tracing. |
|
rockcraft issue #185 |
Support for descriptors different from rockcraft.yaml | arturo-seijas | 1370d | keep open | 30 | 58 | 9 | Custom descriptor filenames remain unsupported; maintainers cite consistency with other Craft tools, and the rocks-template repository is suggested to avoid per-rock subdirectory logic. |
|
craft-parts issue #1232 |
ant plugin: Support `disable-parallel` parameter | lengau | 431d | needs triage | 30 | 45 | 10 | Ant plugin support for disable-parallel is unimplemented; the request remains open as Needs information, with maintainers requesting a real-world case that fails under parallel builds. |
|
charmcraft issue #1842 |
Output build times for each pip package built | sed-i | 806d | needs triage | 30 | 55 | 7 | Feature request (untriaged, no labels/comments): print per-package pip build times when packing with --no-binary so charm authors can see which deps (e.g. pydantic_core) dominate build time. |
|
charmcraft issue #2112 |
doc: Unexpected None values in CLI description | alex-ramanau | 652d | needs triage | 30 | 70 | 17 | Generated CLI reference docs show `<None>` for positional args (e.g. `close`'s `name` and `channel`) because the doc generator uses `action.metavar`, which is unset for those args. Unlabelled and untriaged. |
|
snapcraft (launchpad) issue #1778530 |
rust plugin. failed build with RUST ver. 1.27 | ~general-beck | 3057d | needs triage | 30 | 45 | 6 | An old core18 Rust-plugin report says Rust 1.27 fails to execute rustc -vV while 1.26.2 succeeds; no triage comments or resolution are recorded. |
|
snapcraft (launchpad) issue #1739473 |
Add support for pipenv/Pipfile | ~oddbloke | 3244d | needs triage | 30 | 40 | 5 | Feature request to add pipenv/Pipfile support to snapcraft. Still open and unimplemented; snapcraft's Python plugins remain python, poetry and uv with no Pipfile handling. |
|
craft-cli pr #504 |
fix: raise TypeError for non-string items in humanize_list | Shahzeb-DataEngineer | 24d | needs review | 30 | 60 | 16 | Adds TypeError check to humanize_list for non-string items, addressing issue #413. Clean diff awaiting review; only CI failure is Canonical CLA. |
|
snapcraft issue #6484 |
Bad error handling for ill-formatted platforms | cmatsuoka | 29d | keep open | 30 | 90 | 22 | Crash when platforms is incorrectly specified as a list instead of a mapping; requests a user-friendly error message instead of an AttributeError traceback. |