Showing 100 of 2043 issues
| Issue | Title | Author | Age | Action | Staleness ↑ | Confidence | Summary |
|---|---|---|---|---|---|---|---|
|
charmcraft issue #2006 |
Noisy output in newest charmcraft | dimaqq | 654d | needs triage | 70 | 55 | Charmcraft 3.2.2 build logs a pip cache permission warning ('/root/.cache/pip not owned or writable') during dependency install; reporter notes it appears under --verbose and hints at a real cache/permission issue. No maintainer response; last activity 381 days ago. |
|
charmcraft issue #2078 |
`charmcraft clean` does not clean all platforms for charm | carlcsaposs-canonical | 606d | needs triage | 70 | 75 | charmcraft clean only removes LXC containers for platforms currently listed in charmcraft.yaml, leaving stale containers for removed platforms. Reported with repro steps; linked to issue #1338 in Jan 2025, no further activity. |
|
charmcraft issue #2086 |
Docs: Maintenance tasks that improve consistency | lengau | 603d | keep open | 70 | 70 | Docs cleanup task to remove 'How to' from how-to guide titles for consistency. No comments or labels; last activity 381 days ago. Several how-to pages already use bare infinitive titles (e.g. 'Manage charms', 'Add an icon to Charmhub'), but the style guide still mandates the 'How to' pattern, so the task is partially done and unresolved. |
|
rockcraft issue #857 |
Missing symlinks in bare-based images built with Noble | clay-lake | 521d | needs triage | 70 | 55 | Bare-based rocks built with ubuntu@24.04 (Noble) build-base lose /lib* -> /usr/lib* symlinks, so executables fail at runtime with 'no such file or directory' due to missing /lib64/ld-linux-x86-64.so.2. Untriaged, no maintainer response, no labels. |
|
debcraft issue #146 |
[Feature] Add support for debconf config script | hector-cao | 138d | close stale | 70 | 85 | Feature request for debconf config/templates deployment in debcraft. Triaged (Jira DEBCRAFT-67), and the core functionality has since been implemented via merged installdebconf helper PRs #156 and #162. No activity for about 4 months. |
|
craft-providers issue #568 |
Images contain out-of-date packages | mr-cal | 856d | close stale | 70 | 85 | Enhancement to update packages in base images. The dist-upgrade at image setup time suggested by sergiusens has been implemented in craft-providers. |
|
craft-archives issue #82 |
gnupg-related failures possibly hide their output | tigarmo | 1199d | keep open | 70 | 70 | craft-archives should log gpg command output (stderr) on failure to improve debugging; partially addressed with log=True in install_key and stderr in error messages, but key receive path still lacks debug logging |
|
craft-parts issue #659 |
Docs: Document/cross-reference working directory and environment variables... | thp-canonical | 946d | needs triage | 70 | 75 | Docs gap: part_properties.rst override-build/prime/stage/pull entries lack cross-references to step execution environment (working directory, CRAFT_* env vars). Unlabeled, only a Jira-sync bot comment; docs still not cross-referenced. |
|
snapcraft issue #5734 |
Modifying a build-snap doesn't trigger a change | dilyn-corner | 379d | needs triage | 70 | 65 | Changing a build-snap channel (e.g. node/12/stable to node/18/stable) does not trigger a rebuild of the part in snapcraft 8.11.1. A maintainer commented that craft-parts should be tracking this, but the issue remains open with no fix or follow-up. |
|
snapcraft issue #5655 |
Use pydantic instead of jsonschema for legacy store | bepri | 409d | keep open | 70 | 80 | Enhancement to migrate legacy store response parsing (channel_map.py) from pinned jsonschema 2.6.0 to Pydantic models. Triaged by a maintainer with Jira ticket SNAPCRAFT-1203, but no activity for over a year; code at HEAD still uses jsonschema, so the work remains. |
|
craft-parts issue #921 |
`prime` and `stage` key reference should be fleshed out | lengau | 648d | needs triage | 70 | 55 | Docs gap: the `prime` and `stage` part-property reference pages lack examples and value semantics (e.g. `-` for exclusions). Filed by a maintainer, acknowledged by a second maintainer, but no labels/assignee and no doc update since. |
|
snapcraft pr #5568 |
build: correctly set version of dev builds | bepri | 448d | needs review | 70 | 55 | Small build fix (+2/-5, 2 files) by maintainer bepri to correctly set the version of dev builds. Pending with 0 reviewers and 0 comments; last activity 360 days ago. CI mostly passing but 'build' and 'OSV-scanner' checks failing. |
|
starflow issue #100 |
Use the pristine-ubuntu action on hosted runners | lengau | 280d | keep open | 70 | 60 | Feature request to use lengau/pristine-ubuntu-action on GitHub-hosted runners to prevent runner updates from breaking CI. Open 268 days, no labels, no comments; a related PR (starflow#101) exists but is open with failing CI. |
|
snapcraft issue #5432 |
Add a linter for external symlinks | mr-cal | 506d | keep open | 70 | 75 | Feature request to add a snapcraft linter that detects external symlinks (pointing outside the snap), mirroring the review-tools sr_lint check. Triaged by a maintainer, linked to internal Jira SNAPCRAFT-1071, but no implementation progress in ~16 months. |
|
craft-parts issue #1245 |
meson plugin: Support `disable-parallel` parameter | lengau | 375d | keep open | 70 | 82 | Request to add the disable-parallel part property to the meson plugin, mirroring the autotools implementation. Labeled 'Needs information' and waiting on a real-world use case; no activity for ~12 months and the feature is still unimplemented. |
|
snapcraft issue #5396 |
Export variables to testing environment | cmatsuoka | 516d | keep open | 70 | 55 | Enhancement to export SNAPCRAFT_PROJECT_DIR, SNAPCRAFT_PROJECT_VERSION, and CRAFT_ARCH_BUILD_FOR into the testing environment so test projects can reference the generated snap path. Triaged by maintainer; no implementation or PR found in repo. |
|
craft-parts issue #1252 |
uv plugin: Support `disable-parallel` parameter | lengau | 375d | keep open | 70 | 80 | uv plugin lacks disable-parallel part property support. Low-priority enhancement, labeled Needs information, blocked on the python plugin design decision (#1247) and a real-world use case. No activity for ~12 months. |
|
craft-parts issue #1256 |
Run CI on Focal | lengau | 373d | keep open | 70 | 80 | CI task to add a self-hosted Focal runner for slow tests. Focal is still supported and referenced in qa.yaml as the lowest Python platform, but the requested runner has not been added. Triaged with a Jira ticket, inactive for ~12 months. |
|
craft-parts issue #1259 |
Refactor repository method dispatching | cmatsuoka | 372d | keep open | 70 | 80 | Refactor _RepositoryProxy in craft_parts/packages to use top-level methods instead of a proxy class for deferred repository detection. Triaged enhancement, no PR created, proxy code still present in codebase. |
|
snapcraft issue #5230 |
Update jsonschema | lengau | 589d | keep open | 70 | 80 | Enhancement to update the ancient pinned jsonschema==2.6.0 dependency and fix breakages. Triaged by maintainers; the pin is still in pyproject.toml at HEAD, and the work is being pursued via follow-up issues replacing jsonschema with pydantic. |
|
snapcraft issue #5145 |
snapcraft fails to launch multipass instance when multipass isn't pre-installed | sed-i | 663d | keep open | 70 | 80 | Snapcraft fails to launch a multipass VM with 'Remote snapcraft is unknown or unreachable' when multipass is installed on-demand. Maintainer triaged it as an image-server availability issue and linked craft-providers#211 for better error messaging; still open. |
|
charmcraft issue #2071 |
yaml validation errors are not helpful if the file is empty | PietroPasotti | 610d | keep open | 70 | 85 | charmcraft pack gives a generic 'Invalid file: metadata.yaml' error when the file is empty (comments only), making it hard to diagnose. A maintainer acknowledged it in June 2025 and left it open as low priority; the error is still generic in current code. |
|
snapcraft issue #5114 |
bash gets built with a /bin/bash that is missing the executable bit | basak | 699d | keep open | 70 | 70 | Staging bash+quilt in a classic snap yields a non-executable bin/bash because craft-parts normalize copies the symlink target from the system via shutil.copyfile, dropping the executable bit. Unfixed in craft-parts; reporter has a chmod workaround. |
|
snapcraft issue #4853 |
Snapcraft doesn't report no-op file filtering usage | dilyn-corner | 820d | keep open | 70 | 75 | Snapcraft does not warn when a stage/prime file filter (e.g. -foo) matches no files, risking unintended file inclusion. Maintainer acknowledged and redirected to craft-parts upstream; no fix implemented as of last check. |
|
charmcraft issue #2396 |
Tutorial spread tests are failing | lengau | 410d | needs triage | 70 | 60 | Tutorial spread tests failed after a craft-application change caused packed charms to lose the 'greeting' option. Root cause identified as craft-application#821; fix expected via craft-application#829 / 5.6.1. No follow-up in this issue. |
|
snapcraft issue #4801 |
Doesn't tell you about conflicting files in staging before exiting the debug shell | seb128 | 856d | needs triage | 70 | 55 | Debug shell shows only the brief staging-conflict message, not which parts/files conflict; details only in log. Reported May 2024, one bot comment, no maintainer triage. |
|
rockcraft pr #981 |
feat: don't emit url for `--profile=test` | lczyk | 346d | needs review | 70 | 60 | One-line change to stop `rockcraft init --profile=test` from printing a docs URL (reference/extensions/test) that does not exist. Approved by one reviewer, all CI checks passing, but inactive for ~11 months. |
|
craft-parts issue #806 |
sources module unaware of the environment | upils | 764d | needs triage | 70 | 60 | craft-parts sources modules run subcommands without passing the process environment, so PATH/env vars from a snap (e.g. imagecraft) are ignored and git is not found. Unlabeled, no maintainer response, last activity ~18 months ago. |
|
snapcraft issue #4737 |
Specifying nonstandard base results in strange error message | dilyn-corner | 878d | needs triage | 70 | 60 | Snapcraft 8.x reports a misleading 'architectures keyword not supported for base foo' error when snapcraft.yaml declares an invalid base, instead of an invalid-base error. No maintainer response; only a Jira sync bot comment. |
|
rockcraft pr #985 |
build(deps-dev): bump junit:junit from 4.11 to 4.13.1 in... | dependabot[bot] | 345d | needs review | 70 | 75 | Dependabot bump of junit:junit from 4.11 to 4.13.1 in the jlink plugin spread test fixture pom.xml (+1/-1). Approved by 2 reviewers, one failing snap-tests CI check, inactive ~11 months; target file still pins 4.11 at HEAD. |
|
rockcraft issue #556 |
Have the `--debug` shell inform the user which part and step failed | sed-i | 876d | needs triage | 70 | 60 | Feature request: have rockcraft's --debug shell tell the user which part and step failed (e.g. via PS1 or /etc/issue) for quicker troubleshooting. Open, no labels, only a Jira-sync bot comment; no maintainer response or implementation found. |
|
snapcraft issue #4587 |
Improvements to the PythonPlugin for core24 | tigarmo | 939d | needs triage | 70 | 70 | Braindump of four proposed improvements to the Python plugin for core24 (linter for bad interpreter symlinks, shebang linter, post-prime shebang rewriting, gnome extension interplay). Open, unlabelled, no maintainer response beyond a Jira sync bot; related core24 Python plugin work has since landed. |
|
craft-parts issue #485 |
Improve logging of Apt issues in Overlays | tigarmo | 1167d | keep open | 70 | 65 | Overlay package install failures show only 'failed to install requested packages' with no apt error details; maintainer suggested adding apt stderr to deb.py. Unlabeled, no fix merged, last activity 538 days ago. |
|
charmcraft issue #1518 |
Utility to autogenerate a terraform module | sed-i | 942d | close stale | 70 | 72 | Feature request for a charmcraft terraform command to autogenerate Terraform modules from charm metadata.yaml. Maintainer proposed jinja templates and requested stakeholder feedback in Aug 2024; no response since. Label: Needs information. |
|
snapcraft issue #4459 |
icon 'discord.webp' must be either a .png or a .svg | merlijn-sebrechts | 1017d | needs triage | 70 | 60 | Snapcraft rejects .webp icons in snapcraft.yaml, requiring .png or .svg, while the Snap Store reportedly allows webp. Labeled enhancement; last activity 489 days ago with no maintainer response. |
|
charmcraft issue #1733 |
Don't allow `build-base` on stable bases | lengau | 788d | needs triage | 70 | 78 | Feature request to reject build-base on stable bases in platforms charms, plus documentation. Created by maintainer 776 days ago, no labels, no maintainer response beyond Jira bot. Code still allows build-base on stable bases; not implemented. |
|
fetch-service issue #473 |
Inspector for DEP-11 metadata files | cmatsuoka | 337d | keep open | 70 | 60 | Feature request to add a DEP-11 metadata inspector to fetch-service. Triaged but no work started in 333 days. No DEP-11 or appstream references exist in the codebase. |
|
rockcraft issue #510 |
Cannot easily skip `go mod download` with the `go` plugin | alnvdl-work | 910d | needs triage | 70 | 75 | Feature request to add an option to skip 'go mod download' in the go plugin for vendored private dependencies. 899 days old, only a bot JIRA-sync comment, no maintainer triage. The hardcoded 'go mod download all' step still exists in craft-parts go_plugin.py. |
|
craft-providers issue #873 |
Switch from external tmate to the Canonical tmate action | lengau | 274d | keep open | 70 | 75 | Refactor workflow files to use canonical/action-tmate instead of mxschmitt/action-tmate. Triaged, 266 days inactive. |
|
charmcraft issue #1282 |
[refactor] Separate unit and integration tests | lengau | 1083d | keep open | 70 | 60 | Refactor to separate unit and integration tests in the tests directory. The repo now has distinct tests/unit (60 files) and tests/integration (107 files) directories, indicating the separation described in the issue has been achieved. |
|
rockcraft issue #447 |
Consider creating and making the _daemon_ user available before running any steps | merkata | 1004d | needs triage | 70 | 60 | Feature request to create the _daemon_ user before build steps (currently created during packaging in package.py) so it is available for part steps and has a writable home dir. No maintainer response or labels after ~2.7 years; code behavior unchanged. |
|
starbase issue #308 |
Auto-format documentation source? | lengau | 630d | keep open | 70 | 60 | Discussion on whether to auto-format documentation source (docstrings and RST), proposing docstrfmt. A maintainer noted it needs rigorous testing against Starter Pack conventions. Unlabelled, undecided, inactive ~16 months. |
|
craft-providers issue #754 |
Run Multipass tests on Linux CI | lengau | 465d | needs triage | 70 | 75 | Enhancement to run Multipass integration tests on Linux CI runners now that nested virtualization is supported. Related WIP PR #932 exists but is inactive. |
|
rockcraft issue #136 |
`base: bare` + `overlay_packages` = unhelpful error message | mr-cal | 1409d | close not a bug | 70 | 85 | base: bare + overlay_packages produced an unhelpful 'No such file or directory: apt-get' error. Fixed: project validation now blocks overlays on bare bases with a clear message. |
|
starbase pr #560 |
test: add version test module | medubelko | 91d | close stale | 70 | 60 | Add version test module for starbase docs, mocking a planned conf.py function. Inactive for 52 days with 10 unresolved review comments. |
|
charmcraft issue #1926 |
Docs: Rebase against newer starter pack | medubelko | 715d | close stale | 70 | 75 | Task to rebase Charmcraft docs onto the newer, modular Canonical RTD starter pack (adding Vale style checks). The rebase was completed via PR #2594 (starter pack 1.5); docs now use extension-based config with Vale in requirements and Makefile. |
|
charmcraft issue #2107 |
lxc - Missing source path... | mcfly722 | 597d | keep open | 70 | 60 | Charmcraft pack fails on LXD cluster when container lands on a node lacking the shared cache pip dir; maintainer offered workaround (CRAFT_SHARED_CACHE) and asked if a patch release accepting a flag would help; no reporter reply since Jan 2025. |
|
snapcraft issue #5517 |
remote build: internal error from 400 response | mr-cal | 473d | keep open | 70 | 60 | Snapcraft remote build exposes an internal error when Launchpad returns a 400 (BadRequest) during repo push; the lazr.restfulclient.errors.BadRequest exception is not caught. Triaged as a bug, fix likely needed upstream in Craft Application. |
|
snapcraft issue #5490 |
Include git revisions for `source-type: git` parts in `manifest.yaml` | MggMuggins | 485d | keep open | 70 | 85 | Request to record git commit hashes of source-type: git parts in manifest.yaml and build logs. Triaged and acknowledged by a maintainer with a proposed 3-repo implementation plan; feature not yet implemented. |
|
snapcraft issue #5387 |
Warn if `--platform` is used for remote builds | mr-cal | 521d | keep open | 70 | 75 | Enhancement: make snapcraft remote-build error when --platform is passed and recommend --build-for, since --platform was dropped in 8.7.0 with no in-tool notice. Triaged by maintainer; no implementation yet. |
|
craft-application issue #313 |
Support local key assets for package-repositories | tigarmo | 877d | close stale | 70 | 85 | Feature request to support local key assets for package-repositories (local dir was always /dev/null). Implemented by merged PR #317 adding an overridable _get_local_keys_path hook; issue is inactive and can be closed. |
|
craft-application issue #110 |
docs: Add developer documentation | lengau | 1058d | close stale | 70 | 65 | Request for developer documentation on how to use craft-application, so migrating an app doesn't require reading source. Labeled Type: Documentation, created by a maintainer; only a bot created an internal Jira ticket (CRAFT-2604). The repo now ships a full Diátaxis docs site (how-to, reference, explanation incl. app structure), so the ask is... |
|
craft-cli issue #287 |
Document the pytest plugin | lengau | 704d | close not a bug | 70 | 75 | Request to document the craft-cli pytest plugin (init_emitter/emitter fixtures). Documentation now exists at docs/how-to/unit-test-with-emitter.rst and is linked in the how-to index, so the ask appears fulfilled. |
|
snapcraft issue #6357 |
Mediate metadata creation for gadget and kernel snaps | cmatsuoka | 56d | close stale | 70 | 85 | Feature request to mediate gadget.yaml and kernel.yaml creation via craft-application 7.1.0 API. The feature has been implemented and merged in PR #6369. |
|
craft-application issue #386 |
Explicitly separate public and private APIs | lengau | 787d | needs triage | 70 | 75 | Feature request to explicitly separate public and private APIs in craft-application (e.g. launchpad, remote modules) to prevent every change from becoming a breaking change. No labels, no comments, no assignee; last activity 465 days ago. |
|
craft-parts issue #995 |
Create a general migration how-to for the `uv` and `poetry` plugins | lengau | 590d | needs triage | 70 | 65 | Docs task to write a tabbed how-to for migrating from the python plugin to the uv or poetry plugins, so the guide can be downstreamed into snapcraft and rockcraft. Open since ~579 days with only an auto Jira-sync comment (CRAFT-4045); no migration how-to exists in craft-parts docs yet. |
|
craft-parts issue #671 |
Define Type: grammar-array | javierdelapuente | 932d | close stale | 70 | 75 | Docs request: part-properties reference shows type 'grammar-array' for keys like build-packages/stage-snaps, but no definition of that type exists. The term is gone from current docs (replaced by real types in #1055), so the request is largely moot. |
|
craft-parts issue #583 |
Documentation is missing important concepts and graphs | sergiusens | 1027d | needs triage | 70 | 75 | Docs gap: overlays and lifecycle explanation pages lack important concepts and diagrams (referenced images missing/broken). Open since 2022, only a Jira-sync bot comment; no maintainer response or labels. |
|
craft-parts issue #1330 |
Improve Pydantic schema for parts | bepri | 354d | keep open | 70 | 80 | Enhancement to model part properties (source-*, override-*, build/stage-packages/snaps) directly in the Pydantic schema instead of raw dicts. Triaged by a maintainer; no activity for ~11 months and the patternProperties workaround still exists in current code. |
|
craft-application pr #1133 |
test(spread): make LXD refresh in prepare more reliable | lengau | 58d | needs review | 70 | 65 | Retry only the known LXD auto-refresh transient error in spread prepare to avoid hard failures. Has 1 unresolved review comment, 49 days of inactivity, and failing CI checks. |
|
craft-parts pr #1632 |
fix: wait when retrying snap store; fail install loudly | james-garner-canonical | 66d | keep open | 70 | 65 | Fixes snap store query failures by adding retry delays and removing the store-query gate on snap install to fail loudly instead of silently skipping |
|
craft-providers issue #942 |
Feature Request for custom software mirror | Kxuan | 149d | needs triage | 70 | 60 | Feature request to add a global environment variable for custom APT mirrors in craft-providers build instances. No maintainer response or implementation yet. |
|
charmcraft issue #2652 |
12-factor plugin installs unnecessary package into charm's venv | dimaqq | 151d | needs triage | 70 | 70 | 12-factor (fastapi-framework) charm builds include extra packages in the venv (packaging, setuptools, wheel, dnspython, email_validator, idna) beyond requirements.txt; untriaged, no maintainer response, 136 days old. |
|
craft-providers issue #312 |
Integration tests are slow due to fixture ordering | mr-cal | 1186d | keep open | 70 | 65 | Enhancement to reorder integration test fixtures for faster test execution by skipping early when snap installation is disabled |
|
craft-providers issue #531 |
Provide a way to set Multipass CPU and memory | mr-cal | 913d | keep open | 70 | 75 | Enhancement request to allow configuring CPU and memory for Multipass instances in craft-providers. Open for 2.5 years with no implementation or assignee. |
|
craft-providers pr #949 |
test: failing reproducer - no error for high UID (>65535) | lengau | 143d | needs review | 70 | 70 | Failing test reproducer for craft-providers#259: _set_id_map() should raise ProviderError for UIDs >65535 before calling LXD. PR incomplete, no fix implemented. |
|
craft-providers issue #326 |
fix type checking | mr-cal | 1180d | close stale | 70 | 60 | Enhancement to improve type checking with pyright strict mode and mypy. Issue is 1172 days old; project has since migrated to ty and dropped mypy/pyright. |
|
craft-providers issue #517 |
Multipass: Use native mounts where available | lengau | 925d | needs triage | 70 | 70 | Enhancement to use native mounts instead of sshfs for faster performance when using Multipass drivers. Awaiting maintainer triage. |
|
debcraft issue #148 |
[Feature] Add support for triggers | hector-cao | 138d | needs triage | 70 | 75 | Feature request to let debcraft install user-provided Debian triggers files into package control metadata. Depends on #145 (maintainer scripts). No maintainer response, unlabelled, inactive 126 days. |
|
snapcraft issue #5228 |
docs(extensions/kde-neon): change reference to use upstream repository | lengau | 590d | keep open | 70 | 78 | Docs link in KDE Neon extensions reference still points to personal fork (alexlowe/keysmith) instead of upstream (utilities/keysmith). Labeled, acknowledged by maintainer, but no PR created in ~16 months. |
|
craft-providers issue #445 |
`developer-id` of the `snap-revision` is not asserted | mr-cal | 1039d | keep open | 70 | 60 | Valid bug: craft-providers fails to assert developer-id when it differs from publisher-id, causing snap injection to fail for snaps like rockcraft revision 1194. Issue is 1032 days old with no maintainer comments. |
|
craft-application issue #1086 |
Remove BuilddBaseAlias string-match guard in handle_runtime_error | tonyandrewmeyer | 102d | needs triage | 70 | 60 | Issue about removing a string-match guard for BuilddBaseAlias ValueError in handle_runtime_error, blocked by craft-providers#969 |
|
charmcraft issue #919 |
unpublish command and revision history for channel | jneo8 | 1408d | keep open | 70 | 80 | Feature request for a per-channel revision history command and an unpublish command to downgrade a channel. Maintainer acknowledged in 2022 but it is blocked on Charmhub (snapstore-server) API support. Still unimplemented; no activity for over a year. |
|
charmcraft issue #2105 |
Unable to enable spread verbose with `charmcraft test` | carlcsaposs-canonical | 598d | needs triage | 70 | 75 | charmcraft test cannot forward -vv to spread for verbose CI output. Custom test command was removed in #2385 in favor of the upstream spread-based command, and PR #1988 proposing a --verbose flag was closed as superseded by that migration. |
|
rockcraft issue #953 |
Enable the maven plugin spread test for Ubuntu 25.10 | lengau | 379d | keep open | 70 | 60 | Enable the Maven plugin spread test for Ubuntu 25.10 once a chisel release exists (ROCKS-2054). Triaged by a maintainer, but no activity since the Jira sync bot comment 367 days ago; no evidence the test has been enabled yet. |
|
charmcraft issue #2092 |
Create a reference page for the charm plugin | lengau | 602d | keep open | 70 | 75 | Documentation task to create a reference page for the charm plugin, mirroring the uv plugin page template. Unaddressed; no charm_plugin.rst exists in docs/reference/plugins/. Project is migrating users toward the uv plugin, which may reduce priority. |
|
charmcraft issue #1160 |
`charmcraft pack` does not recognize updated `charmcraft.yaml` file | lengau | 1156d | needs triage | 70 | 65 | charmcraft pack ignores updated build-snaps channel in charmcraft.yaml without a clean; tracked as a craft-parts bug (canonical/craft-parts#496, still open) awaiting a dependency patch release to pull into charmcraft. |
|
craft-providers pr #932 |
Work/ci linux multipass | lengau | 176d | keep open | 70 | 60 | WIP PR to enable Multipass integration tests on Linux CI runners. Inactive for 169 days with 0 reviewer engagement and failing CI checks. |
|
starbase issue #357 |
`make docs-auto` should ignore editor temp files and stuff. | lengau | 567d | keep open | 70 | 70 | Request to make `make docs-auto` ignore editor temp/swap files (vim, emacs, kate, VS Code) to avoid spurious rebuilds. Discussed by maintainers in Feb 2025 but never implemented; no activity for ~16 months. |
|
debcraft issue #39 |
Validate maintainer names | lengau | 297d | needs triage | 70 | 60 | Feature request to validate the maintainer, original-maintainer, and uploaders fields as RFC822 Name <email> format in debcraft. Open 285 days with no labels, comments, or activity; no evidence of a fix or related work. |
|
charmcraft issue #1562 |
Better error messaging from store errors | lengau | 925d | needs triage | 70 | 75 | Feature request to research and improve error messages returned from the Charm Store for clarity. Open ~2.5 years, unlabelled and untriaged; last activity ~12 months ago when a user asked to be assigned to work on it. |
|
rockcraft issue #421 |
Show link to full execution logs when `rockcraft pack --debug` enters debug session | ca-scribner | 1019d | needs triage | 70 | 60 | Feature request: when `rockcraft pack --debug` drops the user into a debug shell after a build failure, also print the full execution log path so the user knows what failed. Maintainer acknowledged the report and explained the outer/inner instance log-copy behavior; no fix has landed. |
|
craft-parts issue #1158 |
"unknown argument ignored: lazytime" in overlay operations | tigarmo | 436d | keep open | 70 | 80 | fuse-overlayfs on jammy/noble prints 'unknown argument ignored: lazytime' during every overlay operation, polluting build output. Triaged by a maintainer with an internal ticket, but no code fix yet; warning still present in current code. |
|
rockcraft issue #182 |
Provide more meaningful output when rockcraft.yaml is invalid | arturo-seijas | 1314d | keep open | 70 | 75 | Rockcraft pack on an invalid rockcraft.yaml prints a raw pyyaml ScannerError traceback instead of a friendly message with the offending line. The underlying craft-application library now wraps YAML errors in a YamlError with problem text and mark details, so the original complaint is likely already addressed. |
|
charmcraft issue #2336 |
Can't login in headless multipass VM with 24.04 | kimwnasptd | 453d | needs triage | 70 | 65 | charmcraft login crashes in headless Multipass VMs (Ubuntu 24.04) because the keyring library falls back to the null keyring, so credentials can't be stored. Reporter self-diagnosed the gap in craft-store auth.py and shared a PYTHON_KEYRING_BACKEND workaround; no maintainer has responded. |
|
craft-parts issue #874 |
Craft-parts cannot parse advanced grammar in `stage` and `prime` fields | mr-cal | 703d | keep open | 70 | 80 | craft-parts crashes with AttributeError when stage/prime entries use advanced grammar. Maintainer triaged: root cause is snapcraft's expand-extensions not processing grammar for prime (snapcraft#5583, open). No activity for ~18 months. |
|
craft-application issue #721 |
Don't follow symlinks for remote-builds | mr-cal | 521d | keep open | 70 | 85 | Remote builds copy the project dir via copytree without symlinks=True, so symlinks are followed and failures surface as internal errors. Fix still unimplemented in worktree.py; triaged enhancement, still referenced by open snapcraft#5384. |
|
charmcraft issue #1246 |
K8s profiles: Add `--image` arg to `charmcraft init` | sed-i | 1102d | needs triage | 70 | 80 | Feature request to add a --image argument to `charmcraft init` for Kubernetes profiles, so rendered metadata.yaml uses the provided container image instead of the 'some-container-image' placeholder. Unlabelled, no maintainer response, not yet implemented. |
|
craft-parts issue #893 |
Java plugin should not copy all jar files | vpa1977 | 681d | keep open | 70 | 70 | Java plugins (ant/maven/gradle) copy every jar from the build dir into the image, including test dependencies. Maintainers discussed an opt-in fix and a 26.04 breaking change; last activity was a documentation suggestion, no implementation yet. |
|
craft-parts issue #598 |
Add integration tests for namespaced partitions | mr-cal | 1015d | keep open | 70 | 60 | Task to extend integration tests to cover namespaced partitions after implementation PRs #595-#597. Implementation merged via #684; unit tests exist, but no dedicated namespaced-partition integration tests found. Open since 2023, last activity May 2024. |
|
snapcraft issue #5879 |
Base images store out-of-date apt package caches | lengau | 297d | needs triage | 70 | 55 | LXD base images ship stale apt package caches, so new build-packages (e.g. from a PPA) fail to install. Filed by a maintainer as a design question; craft-parts now refreshes the apt cache before installing build-packages, but no maintainer has confirmed the issue is resolved. |
|
craft-parts issue #750 |
Reference docs: Separate "library developer/user" content from "craft user" content | thp-canonical | 827d | needs triage | 70 | 72 | Request to restructure craft-parts reference docs by audience (craft YAML user vs Python library user) and split 'Parts and steps' into Environment variables / Output directories. Untriaged, no labels or comments; the flat structure still exists in current docs. |
|
craft-parts issue #456 |
Explain how `stage` and `prime` work in the docs | ca-scribner | 1212d | keep open | 70 | 75 | Docs request to explain stage/prime fileset semantics and defaults. Open 1201 days with only a bot Jira-sync comment; related issue #921 on the same topic is still open, so the gap persists. |
|
rockcraft issue #483 |
Summarise what has/has not been completed when failing or entering a... | ca-scribner | 941d | needs triage | 70 | 65 | Feature request to print a summary of completed/incomplete build steps when a rockcraft pack fails or when entering a --debug session, to help users understand where they are in the build process. No maintainer response; only an automated Jira sync bot comment. No evidence of implementation in the codebase. |
|
craft-parts issue #751 |
Silent failure on certain store issues | lengau | 827d | keep open | 70 | 82 | craft-parts silently returns None instead of raising an error when store queries fail with 500-series HTTP errors during build-snaps resolution. Triaged as a bug. The retry loop in get_store_snap_info still swallows errors after retries are exhausted. |
|
charmcraft issue #2087 |
Better document how platform names work | lengau | 602d | close stale | 70 | 62 | Docs request to clarify how charmcraft platform names work, especially for multi-base platforms and when a specific name is needed vs. an arbitrary one like 'fred'. The platforms reference now states names are arbitrary and adds naming rules (PR #2590), so it appears addressed. |
|
craft-application issue #435 |
Include appropriate craft-parts environment variables when packing with... | lengau | 744d | needs triage | 70 | 75 | Feature request to expose craft-parts environment variables (e.g. $CRAFT_STAGE) in the shell launched by --shell/--debug on lifecycle commands like pack, to speed up override-script debugging. Open, unlabelled, zero comments, no activity since ~465 days ago. |
|
craft-application issue #750 |
internal errors for platform string | mr-cal | 502d | keep open | 70 | 85 | testcraft pack crashes with AttributeError when a platform value is a string instead of a dict. The bug is still present in current code; _vectorise_platforms calls data.get() without guarding against str values. |
|
rockcraft pr #864 |
docs: add tabs for docker and podman | alesancor1 | 511d | needs review | 70 | 55 | Docs PR adding Podman as a tabbed alternative to Docker in the hello-world tutorial. 500 days old, 0 comments, pending review, 4 failing CI checks (snap-tests, slow tests, lint/files, validate-schema). |
|
rockcraft issue #898 |
Hello world tutorial doesn't work when using 24.04 base | seb128 | 456d | close stale | 70 | 65 | Hello World tutorial fails with bare base + ubuntu@24.04 build-base: 'hello' binary not found at runtime (usrmerge/loader issue). Tutorial has since been updated to use ubuntu@26.04 base, so the specific repro no longer matches current docs. No maintainer response; 0 comments. |