Issue & PR triage
Loading...
Showing 100 of 215 issues
| Issue | Title | Author | Age | Action | Impact ↓ | Actionability | Quick Win | Summary |
|---|---|---|---|---|---|---|---|---|
|
charmcraft issue #2685 |
`uv` plugin produces architecture-mislabeled charm on cross-build... | UtkarshBhatthere | 176d | needs triage | 75 | 80 | 27 | uv plugin silently produces architecture-mislabeled charms on cross-build (build-on amd64, build-for arm64) — host-arch wheels packaged under target-arch manifest. Unlabelled, no maintainer response. |
|
charmcraft issue #2788 |
uv plugin fails on core26: dispatch script uses system Python instead of venv | zyga | 106d | keep open | 68 | 78 | 24 | uv plugin breaks core26 charm builds: craft-parts strips venv python symlinks, dispatch falls back to system Python lacking ops. Acknowledged by lengau, ownership moved into Charmcraft (CHARMCRAFT-714). |
|
charmcraft issue #2243 |
Consider adding an optional cli argument for base (including the arch) for... | gabrielcocenza | 575d | needs triage | 65 | 82 | 19 | Request for an optional base and architecture selector on `charmcraft release` to prevent multi-base legacy charm promotions from changing unrelated architectures; the CLI still lacks this option. |
|
charmcraft issue #2680 |
`name` field missing from packed charm's `metadata.yaml` when defined in... | javierdelapuente | 182d | needs triage | 65 | 85 | 30 | Packed charm metadata.yaml omits name when name is in charmcraft.yaml and separate metadata.yaml lacks it, making charm undeployable. Confirmed by second user; no maintainer triage yet. |
|
charmcraft issue #1900 |
Charm plugin can include unexpected files | lengau | 776d | keep open | 60 | 65 | 14 | Charm plugin packs all non-ignored files from project root, potentially including sensitive files like .envrc in subdirectories. Maintainer proposes filtering or warnings; no fix yet. |
|
charmcraft issue #2132 |
Prototype integration of testing service | cmatsuoka | 636d | needs triage | 60 | 45 | 5 | Feature request to integrate craft-application's testing service into charmcraft, including a strategy for testing multi-platform artefacts. Still unimplemented; no labels or maintainer triage in GitHub, Jira ticket CRAFT-4073 created. |
|
charmcraft issue #2631 |
Multiple `charmcraft pack` fail on mismatching platforms | simondeziel | 210d | needs triage | 60 | 70 | 19 | Consecutive charmcraft pack runs with different platform sets fail: second charm (24.04 only) launches a 22.04 instance and errors 'Platform not found'. Regression from 4.0.1, still present in 4.3.1, no maintainer response. |
|
charmcraft issue #2247 |
The charm build failed due to the recent release of wheel version 0.46.1. | adglkh | 568d | needs triage | 58 | 87 | 33 | Wheel 0.46.1 broke Charmcraft source-dependency charm builds with a missing bdist_wheel command; pinning 0.45.1 works, but the issue remains untriaged. |
|
charmcraft issue #1042 |
add `charmcraft purge` or `charmcraft cleanall` command to clean all instances | sed-i | 1333d | keep open | 58 | 71 | 13 | Proposed `charmcraft purge` to reclaim disk space by clearing provider caches and build instances; the design is taking shape, but implementation is absent and the former blocker is resolved. |
|
charmcraft issue #2461 |
uv plugin doesn't cache wheels to LXC host | carlcsaposs-canonical | 384d | keep open | 58 | 84 | 19 | uv with no-binary builds caches inside the LXC guest instead of CRAFT_SHARED_CACHE; the bug remains open and is blocked on craft-providers PR #900. |
|
charmcraft issue #2707 |
Charmcraft confuses the current directory with the project directory when... | gycsaba96 | 156d | close resolved | 58 | 84 | 23 | Charmcraft 4.2.1 mixed the CWD and -p project files when both had charmcraft.yaml, breaking nested pack builds and CI; targeted project-directory fixes are present in current code. |
|
charmcraft issue #2211 |
Kubernetes Resource Requests in charmcraft.yaml | alexdlukens | 602d | keep open | 57 | 43 | 4 | Valid feature request for charm-declared default container CPU and memory requests; maintainers acknowledge it but say Juju-side support and a cross-project design are required. |
|
charmcraft issue #2273 |
charmcraft.yaml deleted while packing (working tree not clean) | carlcsaposs-canonical | 549d | needs triage | 56 | 86 | 25 | Packing a Charmcraft 3.4.3 reproducer deletes tracked charmcraft.yaml before a dump part, making git describe --dirty tag release builds incompatible; untriaged and apparently unresolved |
|
charmcraft issue #2720 |
`organize` part expects distinct subdirectories since 4.2.1 | natalian98 | 143d | needs triage | 56 | 87 | 20 | Charmcraft 4.2.1 regressed dump-part organize: two glob mappings targeting schemas/ now fail; distinct subdirectories work around it, and the report remains untriaged. |
|
charmcraft issue #1979 |
`charmcraft upload` should allow a user to also release the charm | lucabello | 728d | keep open | 55 | 65 | 13 | Requests single-command charm upload+release with automatic OCI resource handling. --release flag already exists; remaining gap is resource upload by image reference instead of revision number. |
|
charmcraft issue #1893 |
Alma Linux builds are broken due to base issues | lengau | 778d | keep open | 55 | 67 | 15 | Open downstream tracker for unresolved craft-application#455: Alma Linux builds fail due to incompatible base detection; almalinux@9 remains supported, but Alma CI re-enablement was never merged. |
|
charmcraft issue #1816 |
Reactive charm built with charmcraft 3.x is missing options from the... | lgp171188 | 805d | close resolved | 55 | 90 | 31 | Reactive layer options were lost because Charmcraft 3.x overwrote charm-tools' config.yaml; commit aa28f0dc and PR #2245 now preserve the generated configuration. |
|
charmcraft issue #2492 |
Charmcraft crashes with internal error when uploading outside of project directory | morphis | 337d | keep open | 55 | 93 | 36 | Charmcraft 4.x uploads successfully outside a project directory, then crashes because post-upload project checks assume configuration; attempted fix PR #2497 was closed unmerged. |
|
charmcraft issue #2816 |
`charmcraft pack` fails on Resolute | jameinel | 83d | needs triage | 55 | 63 | 11 | charmcraft pack fails on Ubuntu Resolute 26.04 hosts when using a Jammy 20.04 build base: snapd inside the LXD build instance cannot reload snap-confine AppArmor profiles; no maintainer response yet. |
|
charmcraft issue #1313 |
Make it easier to release charms in CI and in general | sed-i | 1120d | keep open | 55 | 68 | 14 | Single-command charm upload and release with OCI resources remains unimplemented; upload accepts only existing resource revisions, so users must upload resources first and track returned IDs. |
|
charmcraft issue #1706 |
Remote build: allow the user to specify a charmcraft channel and default to... | lengau | 868d | keep open | 55 | 62 | 15 | Feature request (maintainer-filed, internal ticket CRAFT-3132): let remote-build users pick the charmcraft snap channel via CLI, defaulting to the locally installed snap's tracking channel. Still open, blocked on craft-application#344. |
|
charmcraft issue #710 |
`charmcraft pack` retains no longer existing files from previous packs | sed-i | 1693d | keep open | 55 | 80 | 18 | Repacking reuses the part's build container, so files deleted from the working tree linger in the resulting charm until `charmcraft clean <part>`. Maintainers confirmed it still reproduces; root cause tracked upstream in craft-parts#851. |
|
charmcraft issue #1518 |
Utility to autogenerate a terraform module | sed-i | 989d | keep open | 55 | 40 | 7 | Feature request to add `charmcraft terraform` to autogenerate Terraform modules from charm metadata. Valid and maintainer-endorsed (gatici, Gmerold, lengau), but no implementation exists; lengau asked about jinja templating and stakeholder ownership, awaiting reply. |
|
charmcraft issue #1953 |
Charmcraft 3 should still accept image digests for `upload-resource` | lengau | 749d | keep open | 55 | 90 | 31 | Maintainer-filed Charmcraft 3 bug remains open: upload-resource still rejects bare OCI digests because Docker lookup returns only image IDs; no resolving change is present. |
|
charmcraft pr #2921 |
feat: add GitHub configuration for kubernetes and machine profiles | tromai | 21d | needs review | 55 | 30 | 9 | Adds GitHub CI configuration templates to charmcraft init for machine and kubernetes profiles. Has 1 approval but 13 unresolved review comments and some failing CI checks. |
|
charmcraft issue #1919 |
Charm venv shadows system python dependencies | silverdrake11 | 765d | close resolved | 55 | 90 | 27 | Reported: charm plugin's PYTHONPATH=lib:venv let Juju charm venv shadow system Python packages (pydantic ImportError). lengau confirmed and pointed to new dispatch-based plugins; dispatch now sets PYTHONPATH=lib:src, so the fix has landed. |
|
charmcraft issue #1997 |
Add ability to `charmcraft close` not supported base. | taurus-forever | 710d | keep open | 55 | 68 | 10 | Charmcraft still closes an entire track/risk[/branch], not one base; base-specific closure awaits Store work in snapstore-server#2088469, while close/re-release is a confirmed workaround. |
|
charmcraft issue #2709 |
On timeout, `remote-build` should return the artifacts that have... | sinapah | 153d | keep open | 55 | 55 | 12 | Feature request: `remote-build` returns 75 on --launchpad-timeout without fetching already-successful artifacts; maintainer-linked to the pending --build-for request #2467. Still open and unlabelled. |
|
charmcraft pr #2665 |
tests: add reproducer for upload crash outside project directory (#2492) | lengau | 190d | close stale | 55 | 35 | 11 | Adds failing unit test reproducing upload crash outside project dir (#2492); Copilot added try/except fix. Stale branch, 163 days inactive, type-check failing. |
|
charmcraft issue #2068 |
Advanced grammar doesn't work with multi-platform (ST124) charms | carlcsaposs-canonical | 659d | keep open | 55 | 82 | 14 | Maintainer-acknowledged feature gap: ST124 charms misinterpret platform-qualified advanced grammar, installing rustup via apt; implementation is planned but has no ETA. |
|
charmcraft issue #2336 |
Can't login in headless multipass VM with 24.04 | kimwnasptd | 500d | needs triage | 54 | 88 | 28 | Open Charmcraft login failure on headless Ubuntu 24.04 Multipass VMs: Python selects keyring.backends.null.Keyring, so credentials cannot be retrieved; only a backend override is known. |
|
charmcraft issue #1530 |
Changing charmcraft.yaml doesn't update the resulting charm's metadata.yaml | lengau | 982d | close resolved | 52 | 67 | 20 | The original stale metadata.yaml bug was fixed by merged PR #2874; a later Charmcraft 5.5.0 stale-repack variant remains tracked in craft-application#821. |
|
charmcraft issue #1994 |
Allow changing the charm entrypoint with the `python` and `poetry` plugins | carlcsaposs-canonical | 713d | keep open | 52 | 82 | 24 | Python and Poetry plugins do not support custom charm entrypoints; dispatch generation expects src/charm.py. Maintainers acknowledge the limitation and are tracking a clearer warning. |
|
charmcraft issue #1159 |
Build python packages with multiple threads | dstathis | 1204d | keep open | 50 | 66 | 16 | Maintainer-acknowledged request to speed source-only Python dependency builds with parallel pip compilation; Charmcraft’s parallel-build count is not yet wired to pip or MAKEFLAGS. |
|
charmcraft issue #2218 |
Build cache invalidation misses direct URL dependency change | dimaqq | 597d | needs triage | 50 | 70 | 16 | Direct URL dependency changes in requirements.txt don't invalidate build cache; charm built with stale rc2 instead of rc3. No maintainer response or labels. |
|
charmcraft issue #1839 |
Provide a way to cleanly stage chiselled packages | lengau | 800d | keep open | 50 | 62 | 9 | Charmcraft support for staging chiseled packages remains open; the maintainer requires Chisel and related package setup and explicitly marked it blocked by canonical/chisel#156. |
|
charmcraft issue #1652 |
Allow `charmcraft status anycharm` for everyone | taurus-forever | 927d | keep open | 48 | 62 | 12 | Anonymous charmcraft status remains unavailable to non-publishers; the request is unresolved and under discussion after a maintainer raised public-data and API scope questions. |
|
charmcraft issue #872 |
charm artifacts from reactive plugin are missing valuable build metadata | addyess | 1500d | keep open | 48 | 92 | 24 | Reactive charm artifacts omit .build.manifest and charmtool-version; an exact fix is proposed in open PR charmcraft#2502 and remains under review. |
|
charmcraft issue #1931 |
Successfully pack charm with incorrect charm.py file permission | yhaliaw | 757d | needs triage | 48 | 86 | 30 | Packing accepts a non-executable src/charm.py, causing Juju to fail at deploy. The report has a clear reproducer but no maintainer triage or recorded fix. |
|
charmcraft issue #2477 |
docs: add tutorial for testing a k8s charm | sed-i | 364d | keep open | 48 | 77 | 19 | Documentation request for an official Spread tutorial covering Kubernetes charm testing, including CI and local-development patterns; acknowledged as a Charm Tech 26.04 roadmap item. |
|
charmcraft pr #2572 |
feature: collaborator management commands | niwamo | 260d | keep open | 48 | 32 | 10 | Adds three untriaged collaborator-management CLI commands and tests, but has no documentation or release notes. Eight checks fail, including type checking, title policy, macOS 13 and several snap tests. |
|
charmcraft issue #2868 |
Mark optional endpoints as optional in extensions | wctaylor | 56d | keep open | 48 | 84 | 30 | Extension-generated charm metadata still omits optional: true for observability endpoints; maintainers support explicit values, but the open request remains unimplemented. |
|
charmcraft issue #2467 |
remote-build: add support for `--build-for` | sed-i | 378d | needs triage | 48 | 74 | 20 | remote-build still rejects --build-for; this untriaged feature request would enable architecture-selective Launchpad builds and reduce queue-related build time. |
|
charmcraft issue #2494 |
charmcraft pack wont produce a proper charm | erik78se | 333d | close resolved | 48 | 88 | 26 | Machine-profile init used Ubuntu 22.04 and lacked clear uv-lock guidance. The current implementation defaults machine to 24.04 and supplies uv/migration instructions, so the reported template concerns appear addressed. |
|
charmcraft issue #2546 |
Use Craft Application's Linter Service | mr-cal | 281d | keep open | 48 | 84 | 15 | Charmcraft’s triaged refactor to adopt Craft Application’s merged LinterService remains open; 11 custom checkers still run through Charmcraft’s AnalysisService. |
|
charmcraft issue #2547 |
Charmcraft init migrated to InitService | mr-cal | 281d | keep open | 46 | 88 | 17 | Core migration landed in #2873, but init still exposes --author, --force, and --project-dir; required warning/help cleanup and testcraft coverage remain incomplete or unverified. |
|
charmcraft issue #1983 |
`--bases-index` ignored on charmcraft 3 | carlcsaposs-canonical | 720d | needs triage | 46 | 84 | 24 | `--bases-index 1` is accepted but Charmcraft 3.2.1 still builds bases 0 and 1; the precise report has no maintainer triage or confirmed resolution. |
|
charmcraft issue #861 |
No support for paralell builds for multi-base charms | fnordahl | 1507d | keep open | 45 | 60 | 8 | Enhancement request (triaged) to let `charmcraft pack` build the bases/platforms of a multi-base charm in parallel; still unimplemented, scoped upstream to the whole craft ecosystem (CHARMCRAFT-655). |
|
charmcraft issue #2288 |
uv plugin breaks juju debug-code | PietroPasotti | 532d | needs triage | 45 | 68 | 16 | Open, untriaged report: charms built with the uv plugin run but never hit juju debug-code breakpoints; the reporter suspects its injected dispatch script. |
|
charmcraft issue #2605 |
Re-enable MacOS tests | lengau | 217d | keep open | 45 | 80 | 16 | macOS CI (macos-smoke-test) is commented out since PR #2606 because Homebrew's libgit2@1.7 disappeared. A maintainer-endorsed proposal to drop brew libgit2 and use pygit2 wheels is in progress via PR #2907. |
|
charmcraft issue #1543 |
`--force` Considered Harmful™ | lengau | 980d | keep open | 45 | 72 | 16 | Charmcraft still exposes ambiguous --force flags; descriptive replacements, hidden legacy flags, and usage warnings requested by maintainer remain unimplemented. |
|
charmcraft pr #2869 |
chore: mark extension-provided endpoints as optional | wctaylor | 56d | needs review | 45 | 50 | 17 | Adds `optional: true` to observability/ingress endpoints in framework charmcraft.yaml templates, addressing issue #2868. +156/-32 across 5 files; unit/lint CI green but 3 snap-tests fail and 1 review comment is unresolved, awaiting maintainer review. |
|
charmcraft issue #1912 |
Add option to annotate resources, to enable vulnerability identification | sed-i | 769d | keep open | 45 | 32 | 7 | Feature request to let users annotate resource revisions (e.g. workload version) so `charmcraft resource-revisions` can map revisions to CVE-affected versions. Maintainer liked it but blocked on Charmhub API; upstream charmhub bug filed, no code yet. |
|
charmcraft issue #244 |
"Tracks" management from charmcraft | facundobatista | 2080d | keep open | 45 | 40 | 8 | Track listing and default-track management remain blocked on Charmhub; create-track support exists, but the requested list and set-default-track commands are absent. |
|
charmcraft issue #1790 |
Set a charm version from `charmcraft.yaml` | lengau | 814d | needs triage | 45 | 30 | 6 | Maintainer request to accept a `version` field in charmcraft.yaml and store it in the built charm. Unimplemented: the model accepts `version` but it is hidden from the schema and unused. Blocked on design of where version lives. |
|
charmcraft issue #1657 |
Document permissions, channels, etc. in Charmhub login | lengau | 924d | keep open | 45 | 70 | 22 | Maintainer-created docs request to improve `charmcraft login` command documentation with permissions, channels, and related details; internal Jira ticket CRAFT-2827 exists. |
|
charmcraft issue #2396 |
Tutorial spread tests are failing | lengau | 458d | close resolved | 45 | 85 | 29 | Tutorial spread tests fail because charms lose the 'greeting' config option after repeated packing without clean. Root cause traced to craft-application #821; fix merged in craft-application #829 and charmcraft now depends on craft-application 7.2. |
|
charmcraft issue #2507 |
Cannot build charm when base is Questing and build-base is devel | lmlg | 328d | close resolved | 45 | 75 | 29 | Build with base ubuntu@25.10 and build-base ubuntu@devel fails with 'Couldn't get EOL data for devel' in charmcraft 4.0.1; fixed in craft-providers 3.2.0 by skipping EOL checks for devel. |
|
charmcraft issue #907 |
`charmcraft pack` does not handle updating a file's execution permissions... | ca-scribner | 1473d | keep open | 45 | 70 | 17 | charmcraft pack keeps stale file permissions in the build container unless `charmcraft clean` is run; root cause is craft-parts' outdated check only comparing mtime. Reproduced upstream, workaround `touch` documented, still open. |
|
charmcraft issue #1917 |
Charmcraft cannot parse a dev version build for multipass | jat-canonical | 765d | close resolved | 45 | 90 | 34 | Charmcraft pack fails on dev multipass versions like 1.15.0-dev.2929.pr661 due to invalid version parsing in craft-providers; fixed upstream and current charmcraft dependency includes the fix. |
|
charmcraft pr #2502 |
fix: add missing build metadata in reactive charm artifacts | copilot-swe-agent | 330d | needs review | 45 | 55 | 12 | Adds .build.manifest preservation and charmtool_version to manifest.yaml for reactive charms. Under active review with 4 unresolved comments; most CI checks pending. |
|
charmcraft issue #1990 |
Cannot stage packages with charmcraft | yanksyoon | 714d | keep open | 45 | 55 | 6 | stage-packages in charmcraft.yaml fails with apt method driver error; maintainer says blocked by #1839 and #1844, internal ticket CRAFT-4393 created. |
|
charmcraft issue #2213 |
Change templates to link to current documentation | lengau | 602d | needs triage | 45 | 55 | 14 | Maintainer task to update charmcraft.yaml templates to link to modern documentation instead of outdated juju.is pages and remove repeated/outdated info; unlabelled and unassessed. |
|
charmcraft issue #1985 |
`--format json` ignored in 3.2.1 | PietroPasotti | 717d | needs triage | 45 | 70 | 20 | charmcraft pack accepts --format json but never emits JSON output; flag is parsed but unused in PackCommand._run. Still present at current HEAD. |
|
charmcraft issue #2216 |
Add showing of `sha256` digest on `charmcraft resource-revisions` | hloeung | 598d | needs triage | 45 | 90 | 32 | SHA-256 is missing from resource-revisions table and JSON output despite being available in the API model. This scoped enhancement is awaiting maintainer triage. |
|
charmcraft issue #2857 |
Implement metadata mediation for manifest.yaml | cmatsuoka | 62d | keep open | 45 | 65 | 15 | Maintainer-triaged feature request to add metadata mediation for manifest.yaml (craft-application packaging API) so unchanged projects are not repacked; impl PR #2877 was closed unmerged, only an autogenerated Jira sync (CHARMCRAFT-724) since. |
|
charmcraft issue #1844 |
Add appropriate ignored packages for stage-packages | lengau | 794d | close resolved | 45 | 95 | 28 | Add per-base ignored-package lists so stage-packages excludes packages preinstalled in Jammy and Noble and does not descend to glibc. Implemented by merged PR #1875, but the issue remains open. |
|
charmcraft issue #2482 |
`charmcraft test` v4.0.1 lost `--list` support | taurus-forever | 344d | needs triage | 45 | 91 | 26 | charmcraft test --list regressed in 4.0 after PR #2385 replaced the custom Spread wrapper; v4.0.1 rejects the flag. The issue is reproducible but remains unlabeled and untriaged. |
|
charmcraft issue #2875 |
Allow custom charm parts with the go_framework extension | trollLemon | 50d | keep open | 45 | 50 | 8 | Feature request: go_framework extension rejects any custom parts in charmcraft.yaml, blocking shared-module monorepos and conflicting with the new monorepo packing docs. Escalated to the design wheelhouse for a decision. |
|
charmcraft issue #2969 |
Repack fails after previous pack with failure (CHARMCRAFT_EXPERIMENTAL_MONOREPO) | carlcsaposs-canonical | 7d | keep open | 45 | 80 | 20 | Repack fails when install directory from a previous failed build is not cleaned. Root cause in craft-parts; acknowledged by maintainer with workaround provided. |
|
charmcraft issue #1962 |
Spread test the documentation examples | lengau | 743d | close resolved | 45 | 95 | 27 | Documentation examples are now covered by dedicated Spread tests and CI through merged PR #2126; the still-open issue should be closed. |
|
charmcraft issue #2687 |
Should support keyrings.alt backend for headless systems | panlinux | 175d | needs triage | 45 | 75 | 22 | Headless systems can't persist charmcraft credentials; setting PYTHON_KEYRING_BACKEND=keyrings.alt.file.EncryptedKeyring fails with ModuleNotFoundError because keyrings.alt isn't bundled in the snap. Requests keyrings.alt support. |
|
charmcraft issue #1054 |
Charmcraft fails to launch LXD instance with high uid (`raw.idmap=both 595156457 0`) | jamesbeedy | 1313d | close resolved | 45 | 80 | 23 | High host UID causes LXD launch failure via raw.idmap=both; diagnosed as craft-providers idmap issue, fixed upstream by separate uid/gid maps and charmcraft now depends on fixed version. |
|
charmcraft pr #2907 |
ci: re-enable macOS smoke tests without Homebrew libgit2 | Omjaiswal26 | 28d | keep open | 45 | 35 | 11 | Re-enables macOS smoke tests by using pygit2's vendored libgit2 instead of Homebrew's. Under active review with unresolved permissions issue; author proposing a fix in craft-providers. |
|
charmcraft issue #2012 |
Charmcraft snap thinks `/cache` is the cache directory if snapd doesn't set... | lengau | 695d | keep open | 45 | 75 | 22 | Charmcraft snap sets XDG_CACHE_HOME to $SNAP_USER_COMMON/cache; when snapd fails to set SNAP_USER_COMMON it becomes unwritable /cache. Maintainer-reported with reproducer, listed as known issue in 3.4 release notes. |
|
charmcraft issue #2428 |
docs: dedicated doc for uploading of OCI images | sed-i | 436d | keep open | 44 | 76 | 16 | Triaged OCI upload documentation remains incomplete: guidance omits transport/archive forms and multi-architecture handling, while CLI help conflicts with the docs about sha256 prefixes. |
|
charmcraft issue #1435 |
`charmcraft release` doesn't use output text from the store. | lengau | 1053d | needs triage | 44 | 84 | 22 | charmcraft release ignores Charmhub's response and prints resource details from CLI arguments, potentially reporting a different revision than was attached; no fix or maintainer response is recorded. |
|
charmcraft issue #2204 |
[3.4.3] Charmcraft fetch-lib fails with `Library None not found in Charmhub.` | phvalguima | 603d | keep open | 43 | 92 | 25 | Bulk fetch-lib aborts on an unavailable local library and misleadingly prints “Library None not found”; current code still uses the absent CLI argument, while PR #2505 remains open. |
|
charmcraft issue #1246 |
K8s profiles: Add `--image` arg to `charmcraft init` | sed-i | 1150d | needs triage | 43 | 64 | 12 | Requested repeatable image arguments for Kubernetes profiles during charmcraft init; the option remains unimplemented and untriaged, with no maintainer response. |
|
charmcraft issue #1199 |
Utility to obtain all PYDEPS | sed-i | 1189d | keep open | 43 | 79 | 24 | Open, triaged enhancement to expose all fetched charm libraries' PYDEPS for tox or pip; collection exists internally, but no CLI utility is available. |
|
charmcraft issue #1896 |
Create a way to adjust the operator endpoint when not using the charm plugin | lengau | 778d | keep open | 43 | 84 | 22 | Auto-generated dispatch files outside the charm plugin still default to src/charm.py; the entrypoint override remains a TODO, leaving non-default operator entrypoints unsupported. |
|
charmcraft issue #2078 |
`charmcraft clean` does not clean all platforms for charm | carlcsaposs-canonical | 653d | keep open | 43 | 90 | 17 | Open, reproducible cleanup bug: charmcraft clean uses current project platforms to derive build instances, leaving containers for removed platforms; no resolving fix is linked. |
|
charmcraft issue #1562 |
Better error messaging from store errors | lengau | 973d | keep open | 42 | 54 | 10 | Store diagnostics remain only partially addressed: missing charm-libs gets a targeted message via #2034, but broader opaque errors and typo suggestions remain unimplemented. |
|
charmcraft issue #913 |
Add `charmcraft fmt` command | sed-i | 1466d | keep open | 42 | 52 | 6 | A maintainer-endorsed feature request to add `charmcraft format` for semantics-preserving charm file formatting remains open pending agreement on scope and standards. |
|
charmcraft issue #1154 |
Use craft-application's store service | lengau | 1204d | close resolved | 42 | 98 | 19 | Store interactions now use a craft-application AppService, and all store commands inherit AppCommand; completed by commit 5dcad2af and related craft-application migration work. |
|
charmcraft issue #2092 |
Create a reference page for the charm plugin | lengau | 650d | keep open | 42 | 91 | 29 | A maintainer-created documentation task remains open: add a standalone charm plugin reference page using uv as the template and replace the inline plugin details with a link. |
|
charmcraft pr #2501 |
fix: cache uv plugin wheels to LXC host | copilot-swe-agent | 330d | keep open | 42 | 52 | 16 | Sets UV_CACHE_DIR for source-built wheels and adds unit and spread coverage; awaiting re-review, with two unresolved comments and most CI checks still pending. |
|
charmcraft issue #1788 |
`fetch-lib` should work from anywhere | PietroPasotti | 815d | keep open | 42 | 84 | 20 | `fetch-lib` regressed in Charmcraft 3.1.1 by requiring charmcraft.yaml outside projects; a minimal reproducer was provided, and a maintainer explicitly kept the compatibility request open. |
|
charmcraft issue #1992 |
Document how `stage-packages` differs from installing a package on the system | lengau | 714d | needs triage | 42 | 57 | 14 | Documentation is still needed to distinguish build-time stage-packages from runtime apt installation; prerequisites #1839 and #1844 remain open, and current docs lack dedicated guidance. |
|
charmcraft issue #1496 |
Re-enable CentOS and alma tests | lengau | 1003d | keep open | 42 | 62 | 8 | AlmaLinux and CentOS Spread coverage remains disabled. The provider fix landed, but charmcraft#1824 was closed unmerged and no CentOS image source is available. |
|
charmcraft issue #2225 |
Allow users to specify custom KNOWN_GOOD_PIP_URL for air-gapped CI/CD pipelines | TresSims | 591d | keep open | 42 | 68 | 17 | Feature request to let users override the hardcoded KNOWN_GOOD_PIP_URL (pip 24.1.1 from pythonhosted) via a --pip-url flag for air-gapped builds. Maintainer lengau replied it is unlikely soon and gave a nil-plugin wheel-swap workaround; still open. |
|
charmcraft issue #2374 |
Add `charmcraft lint` to enforce Canonical recommendations | taurus-forever | 469d | keep open | 40 | 60 | 12 | Feature request for `charmcraft lint` to enforce naming conventions. Maintainer acknowledged; naming linter exists via `charmcraft analyse`, but dedicated lint command and error severity pending LinterService refactor (#2546). |
|
charmcraft issue #642 |
The analyze command should also work on a not-packed charm | facundobatista | 1731d | keep open | 40 | 75 | 22 | Feature request to let `charmcraft analyze` accept an unpacked charm directory (default `.`) in addition to packed charm files. Still open, labelled good first issue; maintainer says trivial via lint_directory but waiting on #1042. |
|
charmcraft issue #1658 |
`login` command should validate channel names as full channel names | lengau | 924d | needs triage | 40 | 84 | 26 | `login --channel` still accepts risk-only names such as `edge`; this precise but unlabelled request remains open with only an automated Jira comment. |
|
charmcraft pr #2664 |
tests: add reproducer for reactive plugin missing .build.manifest (#872) | lengau | 190d | needs review | 40 | 40 | 11 | Adds failing unit test reproducing #872 and Copilot fix copying .build.manifest to install dir; 163 days old, 0 reviewers, pending review |
|
charmcraft issue #709 |
Don't upload if unauthorized | sed-i | 1694d | keep open | 40 | 70 | 14 | Upload proceeds before checking package publisher/collaborator permission; maintainers acknowledged and filed CRAFT-3416, but current code still only checks authentication before pushing bytes. |
|
charmcraft pr #2505 |
fix: fetch-lib error message showing "Library None not found" | copilot-swe-agent | 330d | needs review | 40 | 70 | 24 | Fixes misleading 'Library None not found' error in `charmcraft fetch-lib` by using `lib_data.full_name` instead of `parsed_args.library`. PR is approved with CI passing but has 1 unresolved review comment. |
|
charmcraft issue #2018 |
Package service integration tests fail on non-amd64 architectures | lengau | 692d | keep open | 40 | 84 | 21 | ARM64 CI exposed amd64 assumptions in package/build integration tests; QA remains deliberately restricted to amd64 with an explicit workaround for this unresolved issue. |
|
charmcraft issue #1733 |
Don't allow `build-base` on stable bases | lengau | 835d | keep open | 40 | 70 | 18 | Maintainer task: reject `build-base` on `platforms` charms when `base` is a known stable base, and document proper build-base usage. Still open, tracked as CRAFT-3920. |
|
charmcraft issue #1998 |
Add published date column to `charmcraft statsus` output | taurus-forever | 710d | keep open | 40 | 88 | 25 | Maintainer-acknowledged feature to show Charmhub's per-channel "when" value as a Published column in charmcraft status; current code still discards that field. |