Issue & PR triage
Loading...
Showing 56 of 56 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 #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 #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 #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 #2247 |
The charm build failed due to the recent release of wheel version 0.46.1. | adglkh | 569d | 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 #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 #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 #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 #2218 |
Build cache invalidation misses direct URL dependency change | dimaqq | 598d | 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 #1931 |
Successfully pack charm with incorrect charm.py file permission | yhaliaw | 758d | 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 #2467 |
remote-build: add support for `--build-for` | sed-i | 379d | 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 #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 #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 #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 #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 #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 #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 #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 #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 #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 #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 #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 #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 issue #2854 |
charmcraft pack ignores -o option in version 4.4.1 | jw-can | 63d | needs triage | 38 | 68 | 17 | charmcraft 4.4.1 `pack -o .` does not place the charm in the -o folder when --project-dir points outside cwd. Exact repro given, but reported output location unspecified. Unlabelled, no maintainer response in 36 days. |
|
charmcraft issue #1371 |
Output a nice error message when docker breaks lxd | lengau | 1087d | needs triage | 38 | 63 | 13 | LXD launch timeouts lack guidance when Docker has changed firewall forwarding rules, despite a known iptables workaround being used in Spread configuration |
|
charmcraft issue #2233 |
charmcraft should complain if the charm contains a bundle | PietroPasotti | 583d | needs triage | 38 | 70 | 19 | Feature request: charmcraft pack should error/warn when the produced charm contains a bundle.yaml, since juju deploy then deploys the bundle instead of the charm. Clear repro, but no maintainer triage or labels. |
|
charmcraft issue #1598 |
Linter to warn if the summary field is over 78 characters | lengau | 961d | needs triage | 37 | 88 | 24 | Requested summary-length warning remains unimplemented: summaries are capped at 200 characters, and no checker warns above 78; only an automated Jira-sync comment exists. |
|
charmcraft issue #1991 |
Better error message for unsupported 24.04 base | yanksyoon | 714d | needs triage | 35 | 88 | 25 | Ubuntu 24.04 in deprecated bases syntax still triggers the cryptic "Base requires 'platforms' definition" model error; clearer service guidance is shadowed, leaving the request unresolved. |
|
charmcraft issue #2105 |
Unable to enable spread verbose with `charmcraft test` | carlcsaposs-canonical | 645d | needs triage | 35 | 75 | 16 | Request to pass spread's -vv flag through `charmcraft test`; current TestCommand only accepts test expressions and has no maintainer triage yet. |
|
charmcraft issue #1457 |
Feature request: use Ubuntu version instead of series in cache folder | carlcsaposs-canonical | 1030d | needs triage | 35 | 78 | 18 | Request to use Ubuntu versions such as 22.04 in provider cache paths instead of BuilddBaseAlias series names; the issue is still open, unlabeled, and awaiting maintainer triage. |
|
charmcraft issue #2131 |
add explanation chart for each charm plugin | lucabello | 636d | needs triage | 35 | 55 | 11 | Feature request to add explanation charts/diagrams for each maintained charm plugin to help charm authors understand plugin behavior. No labels, no assignee; one maintainer asked another for opinion. |
|
charmcraft issue #2089 |
Charmcraft terminology glossary | lengau | 650d | needs triage | 35 | 45 | 10 | Maintainer request to add a Charmcraft glossary defining terms like Base, Platform, and Charm (vs. the packed .charm file). Still no glossary page in docs/; docs/reuse/links.txt carries a TODO about it. |
|
charmcraft issue #2866 |
docs: Document that resources are bound to channels, not revisions. | marcusboden | 58d | needs triage | 35 | 72 | 21 | Docs request: clarify resources bind to channels, not revisions, since 'charmcraft release --resource' help text implies per-revision pinning. Behavior is correct; misleading docs/help only. No maintainer response yet. |
|
charmcraft issue #2652 |
12-factor plugin installs unnecessary package into charm's venv | dimaqq | 199d | needs triage | 35 | 65 | 10 | 12-factor fastapi charm venv contains build deps (setuptools, wheel, packaging) and pydantic extras not in requirements.txt. Unlabelled, no maintainer response. |
|
charmcraft issue #2234 |
An unnecessary warning is raised when running charmcraft pack | jdkandersson | 583d | needs triage | 35 | 65 | 17 | charmcraft pack emits a confusing keyring warning when users aren't logged in, despite falling back to ephemeral auth. No maintainer response or labels; still reproducible in current store.py. |
|
charmcraft issue #2915 |
Add ability to specify/skip architecture for *craft promote... | taurus-forever | 24d | needs triage | 35 | 65 | 13 | Feature request to add an --arch option to charmcraft promote so CI/CD can promote only selected architectures instead of all at once. New, unlabelled, awaiting triage. |
|
charmcraft issue #2090 |
Docs: Update links to juju.is/docs | medubelko | 650d | needs triage | 35 | 80 | 15 | Update juju.is/docs links to canonical-juju.readthedocs-hosted.com; docs portion partially done via PRs, but many source-code links remain. |
|
charmcraft issue #2088 |
Docs: Demark links to Ops library | medubelko | 650d | needs triage | 30 | 90 | 24 | Seven of 21 Ops intersphinx references still omit the requested "Ops |" label; the valid, bounded docs request remains formally untriaged, with only automated Jira comments. |
|
charmcraft issue #2552 |
docs: what are the values that the `source-type` can have? | panlinux | 277d | needs triage | 30 | 85 | 23 | Untriaged docs gap: the dump plugin recommends `source-type` but omits its values; the current PartSpec reference documents 7z, deb, git, rpm, snap, tar, zip, local, and file. |
|
charmcraft issue #2112 |
doc: Unexpected None values in CLI description | alex-ramanau | 643d | needs triage | 30 | 70 | 17 | Generated CLI reference docs show `<None>` for positional args (e.g. `close`'s `name` and `channel`) because the doc generator uses `action.metavar`, which is unset for those args. Unlabelled and untriaged. |
|
charmcraft issue #1842 |
Output build times for each pip package built | sed-i | 797d | needs triage | 30 | 55 | 7 | Feature request (untriaged, no labels/comments): print per-package pip build times when packing with --no-binary so charm authors can see which deps (e.g. pydantic_core) dominate build time. |
|
charmcraft issue #1433 |
Improve Documentation for 'charmcraft help analyze' Command | mateofloreza | 1053d | needs triage | 30 | 45 | 10 | Untriaged request for clearer analyze-command documentation; current source has a brief overview and a separate analyzer/linter reference, but no explicit resolution is recorded. |
|
charmcraft issue #2130 |
Unable to use spread artifacts with `charmcraft test` | carlcsaposs-canonical | 637d | needs triage | 30 | 40 | 5 | Request to pass spread's -artifacts flag through charmcraft test; TestCommand currently only exposes test expressions. No labels, comments, or maintainer response. |
|
charmcraft issue #1458 |
Feature request: remove build base version from cache folder | carlcsaposs-canonical | 1030d | needs triage | 30 | 45 | 7 | Feature request to drop the build base version from the pip cache path so wheels persist across base updates; unlabelled and untriaged. |
|
charmcraft issue #2960 |
docs: no relevant results for "set default track" | sed-i | 13d | needs triage | 30 | 60 | 16 | Documentation gap: no charmcraft command or docs found for setting a default track on Charmhub. Reporter provided a workaround script using the Charmhub API. |
|
charmcraft issue #2094 |
Create a reference page for the reactive plugin | lengau | 650d | needs triage | 30 | 88 | 20 | Reactive plugin remains registered, but has no dedicated reference page or plugin-index entry; its details are still buried in the charmcraft.yaml parts documentation. |
|
charmcraft issue #1434 |
Improve Documentation for 'charmcraft help clean' Command | mateofloreza | 1053d | needs triage | 30 | 30 | 6 | Documentation request for `charmcraft clean` help text; current overview is brief and issue lacks specific gaps. Related PR #2795 was rejected as subpar; no maintainer triage on issue. |
|
charmcraft issue #2007 |
`status` command has wrong headers | lengau | 701d | needs triage | 30 | 88 | 20 | The current status command still labels risk values as Channel and combines branches into that column, so the reported output bug remains unresolved. |
|
charmcraft issue #1851 |
How-to doc for charmcraft test | lengau | 794d | needs triage | 25 | 65 | 13 | Documentation request from a maintainer to write a how-to guide for the undocumented `charmcraft test` command. Open with no labels, assignee, or maintainer triage; only an automated Jira-sync bot comment (CRAFT-3957). |
|
charmcraft issue #2642 |
Small bug in `charmcraft release` documentation | Gu1nness | 209d | needs triage | 25 | 80 | 18 | CLI docs generator renders `None` for required positional args lacking an explicit metavar, visible on the `charmcraft release` reference page. |
|
charmcraft issue #2865 |
docs: charmcraft release reference is badly formatted | marcusboden | 58d | needs triage | 25 | 68 | 9 | Docs bug report: the published `charmcraft release` command reference shows `charmcraft release [options] <None> <None> <None>` in Usage, plus unformatted channel and resource examples. Untriaged, no maintainer response. |
|
charmcraft issue #2006 |
Noisy output in newest charmcraft | dimaqq | 702d | needs triage | 25 | 55 | 10 | Verbose Charmcraft 3.2.2 builds expose pip output and a root-cache permission warning. The report lacks maintainer triage, and no resolution was found in the inspected history. |
|
charmcraft issue #2086 |
Docs: Maintenance tasks that improve consistency | lengau | 650d | needs triage | 15 | 48 | 6 | Docs consistency meta-issue to remove “How to” from guide titles; it lacks a defined task list and conflicts with current guidance requiring that prefix. |
|
charmcraft issue #2880 |
https://github.com/canonical/charmcraft/pull/2265 | thantzin7383y-bot | 47d | needs triage | 2 | 5 | 0 | Empty bot-filed issue whose title is only a link to merged PR #2265 (yamllint to prettier chore); no problem statement, expected behavior, or doc location, no labels or maintainer comments. |