Issue & PR triage
Loading...
Showing 100 of 219 issues
| Issue | Title | Author | Age | Action | Staleness ↑ | Confidence | Summary |
|---|---|---|---|---|---|---|---|
|
charmcraft issue #1096 |
Spread tests should ensure that juju can correctly parse the output. | lengau | 1236d | close stale | 95 | 70 | Feature request to install juju on spread test runners so tests can verify juju can parse the built charm/bundle output. No labels, no comments, no activity in ~3.4 years; bundle support was later removed from charmcraft. |
|
charmcraft pr #2772 |
Work/charmcraft 710 prototype e2e | lengau | 63d | close stale | 85 | 75 | Prototype e2e changes for charmcraft issue #710. Inactive 56 days, no reviewers, no comments. Related craft-parts PR #1635 was closed by the author who abandoned this approach. |
|
charmcraft pr #2780 |
chore(hotfix): track 3.5 CI fixes | lengau | 63d | close stale | 85 | 75 | Draft tracking PR for hotfix/3.5 CI fixes with empty initial commit; no follow-up commits or reviewer engagement in 53 days |
|
charmcraft issue #2112 |
doc: Unexpected None values in CLI description | alex-ramanau | 595d | close stale | 85 | 60 | Auto-generated CLI docs for the close command in charmcraft 3.2.0 show <None> values in parameter descriptions and Usage. No maintainer response in 584 days; current code has proper help strings. |
|
charmcraft issue #1125 |
Add SECURITY.md to templates | sed-i | 1184d | close stale | 85 | 80 | Request to add SECURITY.md to templates. Work completed in starbase#356 (merged). Issue is stale with no activity since Nov 2024. |
|
charmcraft pr #2779 |
[2.7] Hotfix dependency updates | lengau | 63d | close stale | 85 | 75 | Hotfix branch for Charmcraft 2.7 dependency updates to fix CI breakages; inactive for 53 days with 0 reviewers and some failing CI tests. |
|
charmcraft pr #2509 |
Investigation: Spread test failures are due to craft_providers snapd... | Copilot | 280d | close stale | 85 | 82 | Documentation-only PR adding craft-providers-bug-report.md about spread test failures from a snapd socket-activation race in LXD containers. Inactive ~8.5 months; the recommended retry fix was merged upstream in craft-providers. |
|
charmcraft issue #2423 |
Fix the CI for 2.7 | lengau | 392d | close stale | 85 | 72 | Maintainer task to fix CI on the 2.7 branch to enable backporting bugfixes from PR #2422. Triaged but inactive for 381 days; the 2.7.3 hotfix was merged to main (#1903) and the project has advanced to v4.x, making the 2.7 branch CI fix no longer applicable. |
|
charmcraft issue #1790 |
Set a charm version from `charmcraft.yaml` | lengau | 766d | needs triage | 85 | 70 | Feature request to accept a version field in charmcraft.yaml and store it in the output charm. Open 755 days with no comments or labels; blocked on design decisions about where Juju should read the version from. |
|
charmcraft issue #2288 |
uv plugin breaks juju debug-code | PietroPasotti | 484d | needs triage | 85 | 55 | uv plugin's dispatch script prevents juju debug-code breakpoints from being hit; reporter suspects the injected dispatch script is the cause. Open 14 months, no maintainer response, no labels, no reproduction logs beyond a screenshot. |
|
charmcraft issue #2369 |
charmcract pack stuck at `Pausing control of the terminal` | yhaliaw | 429d | close stale | 80 | 65 | charmcraft pack hangs ~30 min at 'Pausing control of the terminal' during LXD container build; reporter says it happened once; maintainer asked for reproducibility details, no response for 381 days. |
|
charmcraft issue #2510 |
CI is failing on the hotfix/2.7 branch | lengau | 280d | close stale | 80 | 80 | CI failures on the hotfix/2.7 branch, triaged but unresolved. The branch was merged into main via PR #1742 and the project has since advanced to v4.5, making the branch-specific CI issue no longer applicable. |
|
charmcraft issue #2180 |
Workflow for documentation contributors needs to be improved | evildmp | 569d | close stale | 80 | 72 | Request to standardize Sphinx docs build workflow to 'cd docs && make install && make run'. The current docs/Makefile already has both 'install' and 'run' targets matching this exact workflow, introduced by the canonical starter pack 1.5 update in PR #2594. Issue is unlabelled with zero comments and no activity in over a year. |
|
charmcraft pr #2553 |
Redo in-page links for: Manage channels, Manage Charmcraft, and Manage... | activus-d | 227d | close stale | 78 | 68 | Docs-only PR moving single-link block references into main text for three How-to guides (Manage channels, Manage Charmcraft, Manage charms). Approved by 1 reviewer, 14 unresolved comments, inactive ~7 months; same in-page-link redo merged via #2575. |
|
charmcraft issue #1710 |
Add Noble support to charmcraft 2.x | lengau | 809d | close stale | 78 | 72 | Feature request (by maintainer lengau) to add Noble (Ubuntu 24.04) support to charmcraft 2.x, marking bases+noble as deprecated ahead of removal in 3.x. No comments; project has since moved to 4.x with full Noble support and the platforms notation. |
|
charmcraft issue #1886 |
Make 2.x version of Charmcraft docs on RTD | lengau | 732d | needs triage | 78 | 65 | Task to publish a 2.x version of Charmcraft docs on Read the Docs to show differences from 3.x. Filed by maintainer 721 days ago, no labels, no comments, no activity for 381 days. Project has since moved to 3.x/4.x. |
|
charmcraft issue #2029 |
Run documentation spread tests in CI | lengau | 639d | close stale | 75 | 72 | Maintainer task to create a CI job for docs spread tests. The workflow (spread-docs.yaml) now exists and runs on PRs/pushes/weekly. The google backend failure reported by @erinecon was addressed by switching backends. Issue remains open but work appears complete. |
|
charmcraft issue #1652 |
Allow `charmcraft status anycharm` for everyone | taurus-forever | 879d | needs triage | 75 | 70 | Feature request to allow anonymous read access to `charmcraft status` so non-publishers can view channel/release info. A maintainer questioned the value over `juju info`; reporter pushed back. No labels, no further activity since Apr 2024. |
|
charmcraft issue #1457 |
Feature request: use Ubuntu version instead of series in cache folder | carlcsaposs-canonical | 982d | needs triage | 75 | 55 | Feature request to use Ubuntu version (e.g. 22.04) instead of series name (e.g. JAMMY) in the charmcraft cache folder path, simplifying cache interaction. No maintainer response, no labels, no activity in ~13 months. |
|
charmcraft issue #1433 |
Improve Documentation for 'charmcraft help analyze' Command | mateofloreza | 1005d | needs triage | 75 | 70 | Request to improve documentation for the charmcraft analyze command. The command exists (analyse.py) with a hidden US-English alias, and docs/reference/analyzers-and-linters.rst covers the checks but not command usage. No maintainer activity in ~13 months. |
|
charmcraft issue #2119 |
Configure spread tests on noble | lengau | 592d | close stale | 75 | 85 | Task to configure spread tests on Ubuntu 24.04 (noble); the Google backend lacked 24.04. The Google backend has since been removed and spread now runs 24.04 via openstack, so the request is fulfilled. No maintainer triage; only a bot comment. |
|
charmcraft pr #2266 |
build(build-deps): install cargo if not installed | lengau | 505d | close stale | 75 | 85 | Adds 3 lines to Makefile to install cargo if missing, needed for non-AMD64/ARM64 CI runners. Change is already present in current Makefile (lines 90-91), making this a no-op. Maintainer raised unaddressed questions about pkg-config and per-arch conditionals 286 days ago. |
|
charmcraft issue #1962 |
Spread test the documentation examples | lengau | 695d | needs triage | 75 | 65 | Feature request to add spread tests for documentation examples (like Rockcraft) to prevent them from becoming outdated. Open since 2023, no labels/assignees, only a Jira-sync bot comment; no evidence of implementation. |
|
charmcraft issue #1843 |
Add charmcraft-specific versions of upstream python plugins | lengau | 746d | close stale | 75 | 85 | Feature request to add charmcraft-specific versions of upstream craft-parts python plugins. Implemented via PR #1899 (Python and Poetry plugins) with docs in #1940 and a uv plugin in #2050. No further action needed. |
|
charmcraft pr #2667 |
tests: add reproducer for remote-build ProjectService AttributeError (#2598) | lengau | 143d | close stale | 75 | 82 | Adds failing unit test reproducing #2598 (remote-build AttributeError) plus fix in remote.py and lifecycle.py. Superseded: #2681 already fixed remote.py and added its own regression test. lifecycle.py fix still unmerged. Inactive 128 days. |
|
charmcraft pr #2775 |
ci: add concurrency cancellation across GitHub workflows | lengau | 63d | close stale | 75 | 70 | Adds top-level workflow concurrency groups with cancel-in-progress to GitHub workflows. Inactive for 52 days with no reviewer engagement. |
|
charmcraft issue #2130 |
Unable to use spread artifacts with `charmcraft test` | carlcsaposs-canonical | 588d | needs triage | 75 | 60 | charmcraft test cannot pass -artifacts to spread; unlabelled, 0 comments, last activity 381 days ago, similar to #2105 (verbose flag). No maintainer triage. |
|
charmcraft issue #2243 |
Consider adding an optional cli argument for base (including the arch) for... | gabrielcocenza | 527d | needs triage | 75 | 70 | Feature request to add optional base/arch argument to charmcraft release command to prevent unwanted cross-base regressions during multi-base releases. No maintainer response, no labels, 0 comments, last activity 381 days ago. |
|
charmcraft issue #1458 |
Feature request: remove build base version from cache folder | carlcsaposs-canonical | 982d | needs triage | 75 | 70 | Feature request to drop the build-base version from the shared cache folder name so pip wheels are reused across base version bumps. Open, unlabeled, one author comment referencing #1457; no maintainer response. |
|
charmcraft issue #1929 |
Docs: Harmonize README with template | medubelko | 714d | close stale | 75 | 65 | Task to harmonize craft project READMEs with the starbase template. Dependency starbase#233 is closed, and charmcraft's README was aligned with the model in PR #2283, but the issue remains open with no maintainer activity since 2024-09. |
|
charmcraft issue #2467 |
remote-build: add support for `--build-for` | sed-i | 331d | needs triage | 75 | 70 | Feature request to add --build-for flag to charmcraft remote-build for building a subset of architectures, mirroring snapcraft. No maintainer response or labels in 319 days; remote-build still lacks the flag in current code. |
|
charmcraft issue #1809 |
--project-dir fails to find metadata.yaml when running in destructive mode | andersson1234 | 759d | keep open | 75 | 65 | charmcraft pack --destructive-mode -p <dir> fails for reactive charms: charm proof cannot find metadata.yaml because the reactive plugin runs it in the wrong directory. Maintainer marked it low priority in Aug 2024; no fix since. |
|
charmcraft issue #1054 |
Charmcraft fails to launch LXD instance with high uid (`raw.idmap=both 595156457 0`) | jamesbeedy | 1265d | close not a bug | 75 | 85 | Charmcraft pack fails to launch LXD instance when host UID is very high (e.g. 595156457) due to raw.idmap subid conflict. Root cause identified in craft-providers; workaround found via forum post; reporter confirmed resolved. Real fix tracked in craft-providers#259 (open). |
|
charmcraft issue #1432 |
Ineffective Output Filtering Using 'charmcraft help --all | grep revision' Command | mateofloreza | 1005d | keep open | 75 | 70 | charmcraft help --all output goes to stderr, so piping to grep shows nothing. Maintainer logged it upstream in craft-cli#273, which was closed without a fix; no local change made. |
|
charmcraft issue #2507 |
Cannot build charm when base is Questing and build-base is devel | lmlg | 280d | needs triage | 75 | 55 | charmcraft pack fails with 'Couldn't get EOL data for devel' when base=ubuntu@25.10 and build-base=ubuntu@devel on charmcraft 4.0.1. Unlabelled, no maintainer activity in 262 days; devel-base support has since been expanded in later releases. |
|
charmcraft issue #1435 |
`charmcraft release` doesn't use output text from the store. | lengau | 1005d | needs triage | 75 | 70 | charmcraft release command echoes user-provided resource revisions instead of the store's actual response, so output can be misleading (e.g. shows r42 attached while store attached r41). No maintainer response or labels; code path unchanged since the issue was filed. |
|
charmcraft issue #1964 |
Provide internal documentation for templates | lengau | 695d | close stale | 75 | 70 | Internal task to add explanatory comments in charmcraft templates for ignored linter rules, originating from PR #1941 review. Open 684 days with no maintainer activity beyond a Jira ticket sync. |
|
charmcraft issue #1842 |
Output build times for each pip package built | sed-i | 749d | needs triage | 75 | 70 | Feature request to output per-package build times during charmcraft pack, since --no-binary builds can be very slow. Open 737 days with no labels, no comments, and no maintainer response. The --no-binary behavior is still active in the codebase. |
|
charmcraft pr #2526 |
docs: add a description to the charmcraft reference page | lengau | 274d | needs review | 75 | 55 | Adds a 3-line description to the charmcraft reference page. Open 260 days, no maintainer review, 0 approvals. Two macOS fast-test CI jobs failing; ty type-check notification only. Diff is trivial docs change. |
|
charmcraft issue #1893 |
Alma Linux builds are broken due to base issues | lengau | 730d | needs triage | 75 | 70 | Downstream tracking bug for craft-application#455 (strict base detection for non-Ubuntu bases breaking AlmaLinux builds). Upstream issue was closed/deferred to Jira CRAFT-3374. No labels, no maintainer engagement beyond bot, inactive 381 days. |
|
charmcraft issue #1991 |
Better error message for unsupported 24.04 base | yanksyoon | 666d | needs triage | 75 | 70 | Request to improve the cryptic 'base requires platforms definition' error when using the deprecated bases model with 24.04. No maintainer response, no labels, 0 comments. The bases model is deprecated in favor of platforms. |
|
charmcraft issue #1643 |
Add debugging logic to spread file | lengau | 883d | needs triage | 75 | 60 | Feature request to copy debugging logic from rockcraft's spread file into charmcraft's spread.yaml. No maintainer response, no labels, no assignee; only an auto-generated Jira sync bot comment. Untriaged and stale. |
|
charmcraft issue #378 |
charmcraft should have a way to search libraries | mthaddon | 1919d | close stale | 75 | 85 | Feature request for a charmcraft search-lib command to discover available charm libraries. The underlying Charmhub-hosted charm libraries feature is now deprecated (PR #2691), making this request obsolete. |
|
charmcraft issue #2218 |
Build cache invalidation misses direct URL dependency change | dimaqq | 550d | needs triage | 75 | 70 | Charmcraft build cache invalidation misses direct URL dependency changes in requirements.txt, causing stale packages to be used. Unlabelled, no maintainer response, inactive for over a year. |
|
charmcraft pr #2774 |
test: speed up spread test runtime by removing redundant package setup | lengau | 63d | close stale | 75 | 70 | Optimizes spread test runtime by consolidating package installs and removing redundant apt updates across 11 test files |
|
charmcraft issue #2233 |
charmcraft should complain if the charm contains a bundle | PietroPasotti | 535d | needs triage | 75 | 80 | Request for charmcraft pack to warn or fail when a charm root contains a bundle.yaml, since juju then deploys the bundle instead of the charm. No labels, no maintainer response; validation still absent from current pack code. |
|
charmcraft issue #1496 |
Re-enable CentOS and alma tests | lengau | 955d | keep open | 75 | 70 | Task to re-enable disabled almalinux and CentOS spread tests in charmcraft, blocked on a craft-providers fix and a CentOS image source; last touched 381 days ago with no resolution. |
|
charmcraft issue #1844 |
Add appropriate ignored packages for stage-packages | lengau | 746d | close stale | 75 | 75 | Feature request to exclude preinstalled OS packages from stage-packages to prevent staging down to glibc. Resolved by merged PR #1875 but issue remains open. Inactive for over a year. |
|
charmcraft issue #2273 |
charmcraft.yaml deleted while packing (working tree not clean) | carlcsaposs-canonical | 501d | needs triage | 75 | 55 | charmcraft pack deletes charmcraft.yaml from the working tree, making git describe --dirty report -dirty on clean release builds. Reported with charmcraft 3.4.3, no maintainer response or labels in ~13 months. |
|
charmcraft pr #2501 |
Fix uv plugin not caching wheels to LXC host | Copilot | 282d | needs review | 72 | 65 | Adds UV_CACHE_DIR to UV plugin build env to cache source-built wheels on LXC host, with unit and spread tests. 268 days old, 0 reviewers, several CI checks failing (snap-tests, macos-13, Conventional Commits). |
|
charmcraft issue #1771 |
Determine whether requiring `libyaml-devel` on yum-based systems creates... | lengau | 773d | needs triage | 72 | 72 | Task to verify if adding libyaml-devel to yum-based charm build deps produces working charms, mirroring the apt-side change in #1766. Unaddressed for ~2 years; almalinux spread tests were later disabled, complicating verification. |
|
charmcraft pr #2505 |
fix: fetch-lib error message showing "Library None not found" | Copilot | 282d | needs review | 72 | 72 | Fixes 'Library None not found' error in deprecated fetch-lib command by using lib_data.full_name. Approved but 2 unresolved review comments, many CI failures, 266 days inactive. Bug still present in main. |
|
charmcraft pr #2572 |
feature: collaborator management commands | niwamo | 212d | needs review | 72 | 62 | Adds Charmhub collaborator management commands (214 lines, 3 files). Pending review with 0 reviewers, 8 CI checks failing (incl. conventional-commits title, typecheck, snap-tests). No maintainer interaction in 197 days. Auth system since migrated to Ubuntu One (#2760), likely requiring rework. |
|
charmcraft issue #2341 |
Packing a bundle produces a zip that is rejected by charmhub | sed-i | 448d | keep open | 72 | 60 | charmcraft 3.x pack produces a bundle zip with metadata.yaml instead of bundle.yaml, so charmcraft upload is rejected by charmhub. A maintainer asked for the charmcraft.yaml on 2025-06-27; no further activity since. |
|
charmcraft issue #2443 |
Add `AGENTS.md` to templates | sed-i | 366d | close stale | 72 | 78 | Enhancement request to add AGENTS.md (agentic coding instructions) to charmcraft init templates. Labeled Needs information; maintainer asked the author for a concrete example in Jan 2026, no response for over 6 months; no template changes made. |
|
charmcraft issue #1977 |
Alert about all charmlib updates available (not just ones matching the spec) on pack | lengau | 681d | needs triage | 72 | 62 | Feature request: charmcraft pack should warn about any available charmlib update, not just those matching the charm-libs spec; fetch-libs likewise. Open since 2023, no maintainer response beyond Jira sync; charmlibs commands are now deprecated. |
|
charmcraft issue #1931 |
Successfully pack charm with incorrect charm.py file permission | yhaliaw | 710d | needs triage | 72 | 62 | charmcraft pack succeeds even when src/charm.py lacks the execute bit, producing a charm that fails at deploy with 'Permission denied'. Requested a warning/error or auto-fix at pack time. No maintainer activity; an entrypoint linter now exists but only runs via charmcraft analyze, not pack. |
|
charmcraft issue #2201 |
Review and update minimum RAM requirements in docs | medubelko | 556d | needs triage | 72 | 80 | Task to re-evaluate and update the 4GB minimum RAM requirement in release notes and 12-factor tutorials, after feedback that tutorials are slow even at 8GB due to Multipass. Unlabeled, no human activity for ~13 months, docs still state 4GB. |
|
charmcraft issue #1923 |
`spread.yaml` templates: consider LXD VMs over or in addition to multipass | lengau | 716d | needs triage | 72 | 65 | Feature request to consider using LXD VMs in charmcraft's spread.yaml templates (test-machine/test-kubernetes) instead of or in addition to multipass. No maintainer response or labels; last activity 381 days ago. |
|
charmcraft issue #1658 |
`login` command should validate channel names as full channel names | lengau | 876d | keep open | 72 | 75 | charmcraft login --channel should validate that channel names are full names (e.g. latest/edge) since Charmhub requires them for permission attenuation. Unlabeled, no maintainer activity since a 2024 bot comment; code still lacks the validation. |
|
charmcraft issue #1598 |
Linter to warn if the summary field is over 78 characters | lengau | 913d | needs triage | 72 | 78 | Feature request to add a linter warning when charm summary exceeds 78 chars. Unimplemented; summary limit is currently 200 chars in project.py with a comment referencing this issue. No maintainer response beyond a bot Jira ticket sync. Last activity 381 days ago. |
|
charmcraft issue #1952 |
Fix docs and help messages about OCI image uploads | lengau | 702d | needs triage | 72 | 62 | Docs and help messages for OCI image uploads in Charmcraft 3 are slightly wrong per a discourse thread. Filed by maintainer lengau, no labels or assignee, only an auto Jira-sync comment. Docs still reference dockerd while code now uses skopeo. |
|
charmcraft issue #1518 |
Utility to autogenerate a terraform module | sed-i | 941d | 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. |
|
charmcraft issue #2105 |
Unable to enable spread verbose with `charmcraft test` | carlcsaposs-canonical | 597d | 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. |
|
charmcraft issue #2336 |
Can't login in headless multipass VM with 24.04 | kimwnasptd | 452d | 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. |
|
charmcraft issue #1811 |
Document using Charmcraft under WSL | lengau | 758d | needs triage | 70 | 78 | Documentation task to write a guide for running Charmcraft on Windows under WSL (systemd, snapd, snapcraft). No labels or comments; still relevant since Charmcraft 4.0 dropped native Windows support and recommends WSL, but no WSL docs exist yet. |
|
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 #1994 |
Allow changing the charm entrypoint with the `python` and `poetry` plugins | carlcsaposs-canonical | 665d | keep open | 70 | 72 | Feature request to support charm-entrypoint with python and poetry plugins (originally reported as missing dispatch file). Maintainer renamed the issue and acknowledged it, but no implementation or further activity since Nov 2024. |
|
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. |
|
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. |
|
charmcraft issue #1983 |
`--bases-index` ignored on charmcraft 3 | carlcsaposs-canonical | 672d | needs triage | 70 | 70 | charmcraft 3 pack ignores --bases-index, building all bases instead of the requested one. Reported on 3.2.1; no maintainer response, only a Jira sync bot comment. Option still exists in code but appears unused in the pack run path. |
|
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 #2006 |
Noisy output in newest charmcraft | dimaqq | 653d | 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 #1282 |
[refactor] Separate unit and integration tests | lengau | 1082d | 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. |
|
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. |
|
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. |
|
charmcraft issue #1733 |
Don't allow `build-base` on stable bases | lengau | 787d | 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. |
|
charmcraft issue #2107 |
lxc - Missing source path... | mcfly722 | 596d | 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. |
|
charmcraft issue #1512 |
Improve error message for provider not installed. | PietroPasotti | 947d | keep open | 70 | 60 | Improve the 'Provider is required but not installed' error message shown by charmcraft pack before lxd init, to clarify what is missing and what answering y does. Maintainers acknowledged in 2024-02 and noted prerequisite craft-providers work was complete, but no fix has landed. |
|
charmcraft issue #2071 |
yaml validation errors are not helpful if the file is empty | PietroPasotti | 609d | 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. |
|
charmcraft issue #1159 |
Build python packages with multiple threads | dstathis | 1156d | keep open | 70 | 70 | Feature request to build Python packages from source with parallel threads (e.g. MAKEFLAGS/-j) in charmcraft. Maintainer acknowledged in 2023 and flagged design questions around mixed build systems; no label, no further activity for over a year. |
|
charmcraft issue #2086 |
Docs: Maintenance tasks that improve consistency | lengau | 602d | 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. |
|
charmcraft issue #2078 |
`charmcraft clean` does not clean all platforms for charm | carlcsaposs-canonical | 605d | 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 #1851 |
How-to doc for charmcraft test | lengau | 746d | keep open | 70 | 75 | Request to write a how-to guide for the charmcraft test command, which is currently undocumented. No maintainer response or labels; only an auto-generated Jira sync comment. The command still exists in the codebase (spread tests, release notes), so the gap persists. |
|
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 #2482 |
`charmcraft test` v4.0.1 lost `--list` support | taurus-forever | 296d | needs triage | 70 | 75 | charmcraft test --list was dropped in v4.0.1 when the custom test command was replaced by upstream spread (PR #2385); reporter requests restoring the --list wrapper for CI use. No maintainer response or labels 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. |
|
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. |
|
charmcraft issue #786 |
Improve status report to expose unregistered tracks | facundobatista | 1549d | needs triage | 68 | 75 | Status command omits tracks that appear in channel-map but not in package.channels (unregistered tracks). Filed by maintainer facundobatista; no labels, no human response, code still exhibits the behavior. |
|
charmcraft issue #1992 |
Document how `stage-packages` differs from installing a package on the system | lengau | 666d | keep open | 65 | 78 | Documentation task to explain how stage-packages differs from system package installation in charms and how to use operator libs instead. Blocked on stage-packages implementation (#1839, #1844), still open; no activity for over a year. |
|
charmcraft issue #2211 |
Kubernetes Resource Requests in charmcraft.yaml | alexdlukens | 554d | keep open | 65 | 75 | Feature request to add a default-requests field to containers in charmcraft.yaml so charm authors can set Kubernetes CPU/memory resource requests. Maintainers confirmed it requires Juju-side support and asked the reporter to file a tracking request in juju/juju; no implementation exists in charmcraft. |
|
charmcraft issue #2707 |
Charmcraft confuses the current directory with the project directory when... | gycsaba96 | 108d | needs triage | 65 | 60 | Regression in charmcraft 4.2.1 where 'charmcraft pack -p' fails if both CWD and project directory contain charmcraft.yaml. Untriaged, 101 days old. |
|
charmcraft issue #2089 |
Charmcraft terminology glossary | lengau | 602d | needs triage | 65 | 75 | Documentation task to create a Charmcraft terminology glossary (Base, Platform, Charm vs .charm file). Filed by a maintainer 591 days ago, no labels, no assignee, no maintainer response beyond a Jira sync bot. No glossary exists in the docs tree. |
|
charmcraft issue #2492 |
Charmcraft crashes with internal error when uploading outside of project directory | morphis | 289d | close stale | 65 | 70 | charmcraft upload crashes with RuntimeError('Project not configured yet.') when run outside a project directory; regression in 4.x from charmlibs warning feature. PR #2497 closed as fix. |
|
charmcraft issue #2709 |
On timeout, `remote-build` should return the artifacts that have... | sinapah | 105d | needs triage | 65 | 70 | Feature request for remote-build to return partially built artifacts on timeout instead of failing entirely. Untriaged, 98 days old. |
|
charmcraft issue #1657 |
Document permissions, channels, etc. in Charmhub login | lengau | 876d | keep open | 65 | 60 | Docs improvement: expand charmcraft login docs to explain required permissions and how to specify channels. The how-to now lists all permissions and explains --channel/--permission options; a minor nit (naked track in the example) from a maintainer comment may remain. |
|
charmcraft issue #1839 |
Provide a way to cleanly stage chiselled packages | lengau | 752d | keep open | 65 | 70 | Feature request to support chiselled stage-packages in charmcraft for charms needing system executables/libraries. Blocked by canonical/chisel#156; Jira ticket CRAFT-3666 created. No activity in ~12 months. |
|
charmcraft issue #2131 |
add explanation chart for each charm plugin | lucabello | 588d | needs triage | 65 | 70 | Feature request to add explanatory charts/diagrams for each charm plugin to improve understanding of build internals. Last activity 381 days ago when a maintainer pinged another for opinion; no labels, no decision, no follow-up. Plugin docs now have text-based 'How it works' sections but no visual charts. |
|
charmcraft issue #2132 |
Prototype integration of testing service | cmatsuoka | 588d | keep open | 65 | 75 | Maintainer-created task to integrate craft-application's TestingService into Charmcraft for multi-platform artifact testing. Feature still unimplemented; upstream TestingService with multi-artifact support now exists in craft-application. |
|
charmcraft issue #1980 |
Check for major charm library updates | lucabello | 680d | keep open | 65 | 80 | Feature request to detect major (LIBAPI) charm library updates via fetch-libs or a new command, enabling CI workflows to flag breaking library upgrades. Maintainer acknowledged as low priority in June 2025; no implementation yet. |